Standards & Specs
Every QR or barcode type Abundera generates maps to a published standard. This is the reference — spec link, canonical test vectors, in-browser validator where we have one, scanner compatibility, and the pitfalls that break codes in the field.
Why this page exists: most QR tools treat specs as trivia. Operators treat them as contracts. When a Swiss bank rejects a QR-bill, it's because a character in the QR didn't match the Swiss Implementation Guidelines — not because your phone camera failed. These pages document every contract we fulfill so you can audit the match yourself.
GS1 Digital Link
GS1 Digital Link Standard v1.4 The Sunrise 2027 successor to EAN-13. One QR carries product identity plus batch, expiry, serial, and marketing URL.TOTP
RFC 6238 Time-based one-time passwords. Every authenticator app reads the sameotpauth:// scheme. HOTP
RFC 4226 Counter-based sibling of TOTP. Canonical mode for YubiKey OATH and legacy hardware tokens where the server can't rely on clock sync.Swiss QR-bill
SIX Swiss Implementation Guidelines v2.3 The ISO 20022 payment QR that replaced the Swiss inpayment slip. QR-IBAN rules, reference format, and the mandatory Swiss-cross overlay.AAMVA driver license
AAMVA Card Design Standard v10 The PDF417 barcode on the back of every US driver license. Element codes, jurisdiction IINs, version history.EMVCo merchant QR
EMV QR Code Specification v1.1 The TLV-encoded merchant QR behind most national mobile-payment schemes (PIX, PromptPay, UPI, SGQR, DuitNow…).PIX
BACEN Resolution 103/2021 · BR Code Brazil's instant-payment scheme. EMVCo MPM subset with CPF/CNPJ/email/phone/EVP key formats in tag 26.UPI
NPCI BR Code ·upi:// URI India's instant-payment rail. Two QR formats — plain upi://pay URI and NPCI BR Code with VPA in tag 26. EPC Girocode
EPC069-12 v2.1 European SEPA Credit Transfer via QR. Twelve fixed-position text lines: BIC, IBAN, amount, structured or unstructured remittance.eSIM activation
GSMA SGP.22 · LPA Activation Code SM-DP+ address plus matching ID. iOS 17.4+ and Android 13+ scan these natively to provision an eSIM profile.Aztec · PDF417 · Data Matrix — compare
ISO/IEC 24778 · 15438 · 16022 Side-by-side comparison of the three non-QR 2D symbologies. Capacity, native-scanner support, and how to pick between them.Aztec Code
ISO/IEC 24778:2008 Airline boarding passes and transit tickets. Bullseye finder pattern, no quiet zone required, ECC 5%–95% selectable.PDF417
ISO/IEC 15438:2015 US driver licenses (AAMVA), FedEx/UPS airbills, government forms. Stacked linear — the only 2D readable by 1D laser scanners.Data Matrix
ISO/IEC 16022:2006 Direct-part marking on pharma vials, electronic components, surgical instruments. ECC 200, GS1 element strings, ISO 29158 DPM grading.Micro QR · rMQR
ISO/IEC 18004 Annex M · ISO/IEC 23941 Compact rectangular QR variants used for tight PCBs, medical devices, and industrial marking. Scanner support is specialist-only.ZATCA e-invoice
Saudi FATOORA · TLV + cryptographic seal Saudi Arabia's mandatory QR on every tax invoice. TLV structure, Phase 1 (simplified) vs Phase 2 (cleared) flows.How to read each page
Every standard page follows the same structure:
- What it is — two sentences, no jargon.
- Canonical spec link — published authority, dated version.
- Test vectors — canonical inputs with their expected encoded outputs. Copy, decode, verify.
- Live validator — where we ship one inline (GS1 check digit, TOTP Base32, SEPA mod-97, Swiss IBAN prefix).
- Common pitfalls — what breaks codes in the wild.
- Scanner compatibility — which phones, apps, and readers decode it and which don't.
See also
- /test-vectors/ — the full fixture JSON our round-trip test suite runs.
- /compatibility/ — the live scanner compatibility matrix.
- /print-size/ — substrate / DPI / ECC guidance that sits alongside the spec.