EPC Payment QR Code Generator

What happens when someone scans it

Scanned from inside a supporting banking app, the transfer form comes up filled: your name, your IBAN, the amount, the reference. The payer checks it and confirms — the money moves as an ordinary SEPA transfer.

What the code actually contains

BCD
002
1
SCT

Cafe Flatwhite
DE89370400440532013000
EUR14.50


Invoice 214

The EPC069-12 layout, line by line: service tag, version, encoding, SEPA credit transfer, then name, IBAN, amount and reference. The blank lines are optional fields — BIC, purpose code and structured reference — left empty.

How to make one

1. 1

   Enter the account holder’s name and IBAN — the checksum is verified on the spot.

2. 2

   Fix the amount, or leave it open for the payer to fill.

3. 3

   Add a reference that tells you what arrived — “Invoice 214”.

4. 4

   Export. Studio locks error correction to level M, as the EPC standard requires.

Fields

• pname

  Account holder

• iban

  IBAN, checksum-validated

• amt

  Amount in EUR (optional)

• ref

  Reference (optional)

A request, not a payment

Nothing moves until the payer confirms inside their own banking app, against their own login. The code carries the same details you would print on the invoice — it just types them for the payer.

Support varies by bank

EPC codes are read by most banking apps in Germany, Austria, the Netherlands, Belgium, Finland and beyond — from inside the app, not the camera. Before printing a run, test with the banks your payers actually use.

Questions

Is it safe to print my IBAN?

An IBAN can only receive. It is the same information you put on every invoice; the code merely spares the payer the typing.

Fixed or open amount?

Either. A fixed amount prevents typos; an open one suits donations. The reference arrives with the money either way.

Why is error correction locked to M?

The EPC standard mandates level M, so every compliant reader can rely on it. Studio enforces it for this type and lets you choose elsewhere.