How the EPC069-12 BCD payload structure works
Every SEPA payment QR code follows a strict 12-line plain-text schema defined in the EPC069-12 v3.1 specification. Each line occupies a fixed position separated by newline characters, beginning with the BCD service tag, version (002 or 001), UTF-8 character set 1, and SCT identification.
Trailing empty lines after the final populated element are omitted automatically so the payload remains compact. Before encoding, you can validate a SEPA IBAN checksum before encoding to ensure the destination account passes MOD-97 verification.
| Line | Field name | Length or range | Format rules |
|---|---|---|---|
| 1–4 | Header (BCD, version, charset, SCT) |
Fixed tags | BCD, 002 or 001, 1 (UTF-8), SCT |
| 5 | BIC / SWIFT | 8 or 11 chars | Optional in EEA for 002; mandatory for non-EEA or 001 |
| 6 | Recipient name | Max 70 chars | Single-line beneficiary name |
| 7 | Recipient IBAN | Up to 34 chars | Valid SEPA IBAN without spaces |
| 8 | Amount in EUR | 0.01 to 999,999,999.99 |
Prefixed with EUR (2 decimals) or blank for open amount |
| 9 | SEPA purpose code | 4 uppercase chars | Optional ISO 20022 code such as GDDS or SUPP |
| 10–11 | Payment reference | 35 chars (RF) or 140 chars |
Structured ISO 11649 RF or unstructured text (mutually exclusive) |
| 12 | Note to payer | Max 70 chars | Optional beneficiary-to-originator display note |
The live preview tracks your total byte count against the 331-byte ceiling in real time. Under the IETF RFC 3629 UTF-8 Standard, accented European letters such as ü, é, or ł require 2 bytes per character instead of 1 byte. Shortening long notes keeps accented payloads below 331 bytes and QR version 13.
Why are BIC rules different in EPC version 002?
EPC version 002 removed the mandatory BIC field for domestic and cross-border euro transfers inside the European Economic Area. Under the EU SEPA Regulation (EU) No 260/2012, European payment service providers route euro credit transfers using the IBAN alone, so leaving BIC / SWIFT blank produces a smaller, cleaner QR matrix.
EEA SEPA accounts vs non-EEA SEPA territories
SEPA includes several non-EEA countries and territories where banks still require an explicit 8- or 11-character BIC. If you enter an IBAN from Switzerland (CH), the United Kingdom (GB), Monaco (MC), Andorra (AD), or San Marino (SM), the validator requires BIC / SWIFT even when EPC version is set to 002.
Switching EPC version to 001 forces a BIC for every SEPA country. Most modern issuers keep 002 active unless an older ERP system explicitly asks for legacy 001 headers, and German issuers can also use the German GiroCode SEPA QR builder preset.
Handling open amounts and ISO 20022 purpose codes
Leaving Amount in EUR blank generates an open-amount QR code where the payer enters the euro figure inside their banking app. Charities, clubs, and variable-fee service providers use this mode on printed flyers and donation cards.
When an exact amount is entered, it must fall between 0.01 and 999,999,999.99 EUR with at most two decimal places. You can also supply a 4-letter ISO 20022 SEPA purpose code such as GDDS for goods, SUPP for supplier payments, or CHAR for charitable donations.
Structured ISO 11649 RF references vs unstructured text
Lines 10 and 11 of the EPC069-12 payload cannot be populated at the same time. Reference format lets you choose between Unstructured text (up to 140 characters) and ISO 11649 RF reference (up to 35 characters).
Building Mod-97 check digits for RF creditor references
An unstructured reference works well for simple invoice numbers when a human reviews incoming bank statements. Automated accounting software, however, benefits from structured ISO 11649 references that start with RF followed by two Mod-97 check digits.
Typing an invoice ID such as INV2026 and clicking Build RF check digits from reference calculates the exact check digits locally. If a customer later mistypes a digit during manual entry, their banking app flags the invalid checksum immediately, reducing reconciliation work alongside tools like the Payment reminder generator.
Avoiding truncation when copying invoice numbers
Many banking apps display only the first 35 to 70 characters of an unstructured Payment reference on mobile confirmation screens. Placing the invoice number at the very start of the string ensures the identifier remains visible even on compact screens.
Keep Note to payer under 70 characters and avoid line breaks, because the EPC069-12 parser strips newlines to preserve the 12-line BCD structure. Clicking Copy BCD text lets you inspect the exact raw payload string before printing.
Exporting PNG, SVG, and stamped PDF invoices locally
Every QR matrix, PDF payment sheet, and stamped invoice is generated inside your browser tab with zero server communication. Raster exports use the MDN HTMLCanvasElement.toBlob() API to write clean black-on-white PNGs with a 4-module quiet zone around the code.
Choosing PNG resolution, vector SVG, or A4 payment sheets
Select 512 px, 1024 px, or 2048 px under PNG resolution for lightweight web images or high-resolution office documents. Download SVG outputs resolution-independent vector rectangles suitable for desktop publishing and HTML invoice templates.
Clicking Download PDF sheet creates an A4 payment card in a Web Worker after a 350 ms preview debounce. Transliteration helpers map Central European characters such as ł, š, or ž cleanly into PDF text captions so beneficiary names render without missing glyphs.
Stamping payment QR codes onto existing PDF invoices
Expand Stamp QR onto an existing PDF invoice to drop a finished .pdf invoice from any accounting app. You can choose Corner (Bottom right, Bottom left, Top right, Top left), Page (Last page or First page), and QR width (mm) between 22 mm and 60 mm (default 32 mm).
Tip: Check Open stamped preview before downloading to verify that the
32mm QR block and optional"Scan to pay"caption do not overlap your invoice footer or totals table.
Keeping Add “Scan to pay” caption beneath the QR code enabled helps first-time payers recognize the square immediately. Once stamped, you can pair the workflow with country templates to issue French EUR invoices with statutory TVA or other European billing presets. Note that this generator formats EPC069-12 QR payloads for operational convenience; confirm any bank-specific remittance rules with your financial institution.