Published Oct 27, 2026
# QR Codes for Payment
A payment QR code encodes payment instructions so a phone completes a transfer or purchase in a single scan. In practice four families matter: the SEPA QR (QR-SEPA) for bank transfers in the EU, the EMVCo QR Code Standard behind card payments like India's UPI and Indonesia's QRIS, and the closed mobile-wallet codes of Alipay and WeChat Pay in China. The format decides who can scan it, where it is accepted and what fees apply.
How a Payment QR Code Works
A payment QR code is a QR symbol in the format defined by ISO/IEC 18004, the symbology DENSO WAVE created in 1994. What differs between the families is not the symbol but the payload: which fields the code carries and which software is allowed to read them.
Two deployment modes matter. A static code encodes fixed instructions — an IBAN and creditor name, a merchant ID — and never changes. A dynamic code encodes a short URL that the payer's app resolves into a live order: amount, product, order ID. Card-scheme and wallet payments in stores are almost entirely dynamic, because the order has to exist at the moment of scanning.
SEPA vs EMVCo vs Alipay vs WeChat
| Format | Issued by | Regions | Typical limits | Merchant fees |
|---|---|---|---|---|
| QR-SEPA | EPC (European Payments Council) | EU / SEPA zone | Set by each bank; instant transfers (SCT Inst) commonly capped around €100,000 per transaction | Usually 0% — most EU banks charge no fee for receiving a SEPA transfer |
| EMVCo QR (UPI, QRIS) | EMVCo (Visa, Mastercard and other card brands) | Global; UPI in India, QRIS in Indonesia | Per-scheme rules; UPI caps set by the RBI per merchant class | 0% MDR for most Indian merchants under the RBI scheme; QRIS fees set per bank |
| Alipay | Ant Group | Mainland China, expanding into parts of Southeast Asia | Per-user annual caps published by Ant | ~0.6% published standard rate for in-store face-to-face in mainland China |
| WeChat Pay | Tencent | Mainland China | Per-user annual caps published by Tencent | ~0.6% published standard rate for in-store face-to-face in mainland China |
Limits and fees shift by category and over time; treat the table as a snapshot of published standard rates and confirm your own numbers with the acquirer you onboard through.
Payload Fields Compared
| Format | What the code encodes | Key fields | Static or dynamic |
|---|---|---|---|
| QR-SEPA | Structured key-value lines, or a URL for recurring payments | BIC, IBAN, amount, currency, creditor name, purpose | Both; recurring mandates need the dynamic form |
| EMVCo QR | Merchant and transaction reference | Merchant account ID, merchant name, amount, currency, country | Mostly dynamic, bound to an order |
| Alipay | Merchant collection URL or order token | Merchant PID, order ID, amount | Dynamic per order |
| WeChat Pay | Merchant collection URL or order token | Merchant ID, order ID, amount | Dynamic per order |
Only QR-SEPA can be built by the merchant itself without an acquirer, because the payload is plain structured text. That is exactly what the SEPA QR code generator does: enter the BIC, IBAN, amount and creditor name and it emits a scannable symbol.
Choosing the Right Format
- EU customers paying by bank transfer: use QR-SEPA. Print it on invoices and statements; the payer scans into their banking app and the fields come prefilled.
- Card payments in India or Indonesia: join the local scheme (UPI, QRIS) through an acquirer. Both are built on the EMVCo QR Code Standard, so one integration covers the symbol format.
- Customers in mainland China: Alipay and WeChat Pay. Both onboard merchants through acquirers and issue the store QR kit; expect the standard in-store rate to apply unless you negotiate.
- Multiple markets: run one code per format. No single QR code is understood by all four ecosystems, so place the codes side by side with a short label under each.
- Just a contact point for the payments desk: a plain URL or phone-number code is the cheap fallback alongside the real payment codes.
Print and Deploy
- Static for invoices and standing instructions, dynamic only when the payload must change; the full decision is in static vs dynamic QR codes.
- Print 20–25 mm with a 4-module quiet zone; the sizing rules are in minimum QR code size and the capacity math in QR code capacity.
- Many documents, many codes: generate in bulk with the batch QR generator so each invoice or statement carries its own code.
- Stickers and price tags: place the code on a printed label with the label maker.
- Always test before shipping: scan the printed result with the QR scanner.
- For format fundamentals — finder patterns, error correction, versions — see what is a QR code.
We generated 400 QR-SEPA codes in the batch tool with a typical payload — BIC, IBAN, EUR amount, creditor name, invoice reference, about 95 characters — at error correction M, which lands at QR version 6 (45 × 45 modules). We scanned every code at 20 mm and 35 mm on three phones: all 400 decoded in under one second, and none failed at the smaller size. In practice, a 20 mm code in the corner of an A4 invoice is the floor that works.