EMVCo QR Standards — and What They Do Not Cover
EMVCo publishes QR specifications so cameras and wallets can share a payload grammar. It does not run UPI, PromptPay, or SGQR. This page stops the academy from pretending those are the same thing.
What the standard is for
Merchant-presented and consumer-presented QR data objects, TLV layout, CRC, and related payment QR documents listed on emvco.com. Trademark: EMVCo, LLC.
What it is not
Not a bank licence. Not a list of which Indian or Thai apps must accept your GUID. Not a ranking of wallets. Not this website — we are independent.
How we use it
Our generator constrains tags to MPM-shaped fields. Our academy restates those fields in operator language with worked payloads. For certification, use the PDFs and your scheme’s test cases.
Documents people actually mean
Teams say “EMVCo QR spec” when they mean the QR Code Specification for Payment Systems (merchant-presented and related books). Always record the version year you certified against. A 2017 test kit can fail a 2024 generator.
Relationship to ISO QR
ISO/IEC 18004 is the symbol (modules, error correction). EMVCo QRCPS is the meaning of the bytes inside a payment QR. You can have a scannable ISO symbol that still contains a useless payment payload.
National overlays
Central banks add GUIDs, branding, and sometimes extra templates. Those overlays are mandatory in-market even though they are not “the EMVCo spec.” Treating overlays as optional is a launch defect.
How this site stays honest
We never call ourselves EMVCo Academy as an official program. We never paste specification PDFs. We implement fields and send you to emvco.com for the source.
EMVCo is a standards and testing organisation
EMVCo publishes specifications and runs testing and approval programmes across several payment technologies: contact chip, contactless, 3-D Secure, tokenisation, Secure Remote Commerce, and QR. QR is one of those families, not the whole organisation. The public site emvco.com is where you find the current document set, lab information, and approved-product lists. It is not a merchant QR generator and it is not this website.
When a vendor says they are “EMVCo certified for QR,” ask which document version, which product type, and which lab. “We scanned a sample on emvqrhub.com” is not that claim. We implement encode/decode compatibility with Merchant-Presented Mode as we understand it; we do not issue approvals.
Which QR documents people usually mean
In merchant projects, “the EMVCo QR spec” almost always means the QR Code Specification for Payment Systems (QRCPS) and related books for merchant-presented and consumer-presented modes. Always record the year and version you built against. A generator frozen to an older example can fail a newer scheme kit even if CRC still matches your unit tests.
Do not paste specification PDFs into an academy page or into source comments you plan to publish. The normative text lives with EMVCo. This site cites the public QR technology page and then shows original examples from our own generator and decoder.
ISO symbol versus EMVCo payload
ISO/IEC 18004 defines the QR symbol: modules, error correction, how a camera recovers bits. EMVCo QRCPS defines the meaning of the recovered characters for payment. You can print a perfectly scannable ISO symbol whose payload is garbage for every wallet, and you can have a legal MPM string encoded in a symbol that is too small to scan at the counter. Debug those layers separately.
Our Standard QR tool is the symbol/styling layer for non-payment and utility codes. Our EMV tool is the payment-payload layer. Mixing the two in a single screenshot is a common support failure: the picture looks sharp while Tag 53 is still the letters INR.
National overlays sit on top, not instead
Central banks and switches add GUIDs, extra templates, branding, and sometimes extra CRC or length rules. Those overlays are mandatory in-market. They do not replace QRCPS; they constrain it. Launching with “pure EMVCo” samples and a foreign GUID is a certification defect, not a display issue.
Read the scheme merchant-QR guide as law for that country, then use this academy for the shared TLV skeleton. We will not claim that one cookbook string is valid for PromptPay, SGQR, and Bharat QR at once. See the national schemes article for how those programmes differ without copying their private specs.
How this site stays on the honest side of the trademark
EMVCo is a registered trademark of EMVCo, LLC. EMV QR Hub is operated by Pankaj Kalra. We are not sponsored, endorsed, or affiliated. We do not run an official Academy. We do not sell certification. Learn pages exist to explain the grammar you can exercise in the browser and to point you at emvco.com for the source.
If a page on the live site still reads like a doorway of synonym articles, that is the old production copy. This branch rewrites English depth and drops duplicate URLs. The standard of quality we are aiming at is closer to a named explainer than to a keyword farm — without pretending to be EMVCo.
Reading order on emvco.com
Start at the QR technology overview, then download QRCPS for merchant-presented mode if that is your product. Skim testing/programme pages only if you are entering a lab. Do not treat marketing PDFs as field dictionaries. Come back here to exercise bytes in the browser.
Trademark and affiliation (again, on purpose)
Merchants sometimes ask “are you EMVCo certified?” This website is not. EMVCo certifies products and programmes listed on emvco.com. We are an independent toolkit by Pankaj Kalra. Point auditors to your acquirer and lab for cert questions; point engineers here and to EMVCo for grammar questions.