GiroCode format EPC069-12 and the 331-byte payload ceiling
Every GiroCode encodes a structured 12-line plain-text payload rather than a web URL, allowing mobile banking apps to populate a SEPA transfer offline. Keeping the payload within 331 bytes guarantees the QR matrix stays at or below Version 13 under Error Correction Level M.
The generator follows the European Payments Council EPC069-12 v3.1 Guidelines and measures UTF-8 byte length in real time so German umlauts (ä, ö, ü, ß) never overflow the ceiling. If you bill clients across Belgium or the Netherlands as well, the EPC QR code generator uses the same standard with non-German sample defaults.
| Line | Field name | Requirement | Validation rule in code |
|---|---|---|---|
| 1–4 | Header (BCD / 002 / 1 / SCT) |
Mandatory | Fixed service tag, EPC version (002 or 001), UTF-8 charset 1, and SCT code. |
| 5 | BIC / SWIFT | Conditional | Optional in EEA for v002; mandatory 8 or 11 chars for v001 or non-EEA SEPA. |
| 6 | Recipient name | Mandatory | Beneficiary name up to 70 characters; line breaks are stripped automatically. |
| 7 | Recipient IBAN | Mandatory | Validated with Mod-97 checksum and checked against 43 SEPA countries/territories. |
| 8 | Amount in EUR | Optional | EUR0.01 to EUR999999999.99 (2 decimals), or blank for open-amount payments. |
| 10–11 | Remittance reference | Optional | Mutually exclusive: ISO 11649 RF (max 35 chars) or unstructured text (max 140 chars). |
Verwendungszweck vs ISO 11649 RF reference and BIC rules
Choosing between free-text remittance and a structured creditor reference depends on how your accounting software reconciles incoming transfers. Both formats share the same 331-byte payload budget, and the specification forbids populating both lines at once.
Choosing unstructured Verwendungszweck or Mod-97 RF references
Use Unstructured text for standard German invoice numbers (Rechnung RE-2026-0142), customer IDs, or donation notes up to 140 characters. Switch Reference format to ISO 11649 RF reference when your ERP requires machine-checked reconciliation up to 35 characters.
Clicking Build RF check digits from reference calculates the two Mod-97 check digits locally and prepends RF to your invoice identifier. If you also collect payments from British clients outside SEPA EUR transfers, you can verify UK bank clearing codes offline before sending invoices.
When EPC version 002 requires a BIC outside the EEA
Under EU Regulation No 260/2012 on SEPA, banks inside the European Economic Area route euro credit transfers by IBAN alone. Selecting 002 · BIC optional inside EEA (recommended) covers Germany, Austria, and 29 other EEA countries without requiring a BIC.
However, 12 non-EEA SEPA countries and territories, including Switzerland (CH), the United Kingdom (GB), and Monaco (MC), still require an 8- or 11-character BIC even under version 002. The validator enforces that distinction automatically before drawing the QR code.
What is the difference between EPC QR and GiroCode in German apps?
German and Austrian banking apps parse the 12-line BCD text directly through their built-in camera scanners without touching an external payment server. Both names refer to the identical EPC069-12 standard, with GiroCode serving as the German banking industry label.
Sparkasse, VR-Bank, ING, DKB, and Austrian Foto-Überweisung support
Major German institutions including Sparkasse, Volksbanken Raiffeisenbanken, Deutsche Bank, Commerzbank, ING, DKB, and N26 support GiroCode natively in their iOS and Android apps. Austrian banks such as Erste Bank (George) and Raiffeisen use the identical Deutsche Bundesbank SEPA Payment Systems credit transfer format.
For international vendor onboarding outside Europe, you can also run offline business identifier checksum verification for Australian suppliers in the same browser suite.
Preventing scan failures with Level M error correction
EPC069-12 mandates QR Error Correction Level M (roughly 15% damage recovery) so phone cameras decode the symbol reliably even on folded paper bills. The PNG and SVG exporters surround every symbol with a 4-module white quiet zone so adjacent invoice borders never interfere with finder patterns.
If you leave Amount in EUR empty for charity appeals or open-amount retainers, banking apps fill in the IBAN and reference while letting the payer type their own euro sum.
Client-side private GiroCode generator for PDF invoices and SVG export
You can either export standalone QR graphics for your accounting template or stamp a finished PDF invoice directly in your browser. Every calculation, PDF modification, and image export runs locally with 0 bytes of IBAN or invoice data leaving your device.
Placing a 22 to 60 mm GiroCode stamp onto existing PDF invoices
Expand Stamp QR onto an existing PDF invoice, drop your PDF, and select Corner (Bottom right, Bottom left, Top right, or Top left) and Page (Last page or First page). Adjust QR width (mm) between 22 and 60 mm (default 32 mm), toggle the Add “Scan to pay” caption beneath the QR code checkbox, and inspect the live preview after its 350 ms debounce.
Tip: Open Open stamped preview before clicking Stamp QR onto PDF to confirm the 32 mm QR block sits inside clear whitespace without overlapping your invoice total or footer text.
Exporting vector SVG, high-resolution PNG, and keeping IBANs private
Click Download SVG for crisp vector output built to the W3C Scalable Vector Graphics 2 Specification when embedding codes into Word, LibreOffice, or LaTeX templates. For raster workflows, choose 512 px, 1024 px, or 2048 px under PNG resolution and click Download PNG, or generate an A4 card via Download PDF sheet.
Once clients pay your stamped invoices, you can reconcile incoming bank CSV statements as OFX files locally. Treat this tool’s IBAN and EPC checks as technical formatting helpers rather than formal banking or tax advice.