QR Code Payments: How They Work and How to Accept Them
7 min read Last updated 2026-11-17
A payment QR code encodes instructions for moving money: who receives it, optionally how much, and which network should process it. The scan opens the payer's wallet or banking app with the payee details pre-filled, so a transfer that once required account numbers and routing codes happens in two taps.
This guide explains the mechanics behind merchant-presented payment codes - with a focus on UPI, the largest deployment of interoperable payment QR codes anywhere - and the operating practices that keep acceptance safe for both merchants and payers.
What a payment QR code actually encodes
A payment QR never contains money or card numbers. It contains instructions, typically as a URI the wallet app understands. A UPI code, for example, encodes something like upi://pay with the payee's virtual payment address, the payee name and optionally an amount and a note. The payer's app parses that payload, displays the payee and amount, and asks the payer to authenticate; only then does money move.
Globally, most payment schemes build on the EMVCo merchant-presented QR specification, which defines how merchant identity, amount and transaction references are structured. Dynamic merchant codes are generated per transaction and can lock the amount and attach a reference; static merchant codes carry only the payee identity and leave the amount to the payer. Both are ordinary QR codes under the hood - the difference is who fills in the amount.
UPI: interoperable QR at national scale
UPI, the Unified Payments Interface launched by NPCI in India in 2016, is the clearest demonstration of what payment QR codes can do at scale. Interoperability is a core rule: any UPI app can pay any UPI QR code, regardless of which bank or payment service provider printed it. One sticker on a fruit stall therefore serves every wallet and banking app on the payer's phone.
Merchants get dynamic QR codes from their payment service provider that fix the amount and carry a transaction reference, which removes amount-entry mistakes and simplifies reconciliation. Static codes are cheaper and always work, but they rely on the payer to enter the correct amount. From street vendors to large chains, the same format covers the whole range, which is why QR acceptance spread so quickly.
Accepting payments: practical setup
Get your merchant code from your bank or payment service provider rather than hand-building one, because settlement, refunds, disputes and reporting all ride on the provider's rails. Display it physically where the transaction happens: a counter standee or a clean sticker, roughly five to ten centimeters wide at counter distance, on a matte surface away from clutter and glare. Position it at the natural height of the transaction, where the payer's phone is already pointing.
Where your point-of-sale system or provider app supports dynamic codes, use them: the amount is locked, the reference is attached, and reconciliation becomes automatic. For minimal setups with a static code, make the amount unambiguous on the bill and confirm it verbally before the payer authenticates. The list below covers the setup rules that matter most:
- Get the merchant QR from your bank or PSP - settlement and refunds ride on it
- Display it at counter distance: five to ten centimeters, matte surface, clear of clutter
- Prefer dynamic amount-locked codes where your POS or PSP app supports them
- Check the payee name shown in the app matches your business before confirming
- Audit public-facing stickers regularly and use tamper-evident holders
- Never scan and enter a PIN to receive money - receiving never needs your PIN
Fraud risks specific to payment QRs
The main merchant-side risk is sticker swap: a fraudster covers a genuine payment code with one of their own, and payers transfer money to the wrong account while believing they paid the merchant. The defenses are simple and physical: verify that the payee name displayed in the app matches the merchant, mount codes in tamper-evident holders, and inspect public stickers as part of the daily routine. Dynamic codes tied to a live transaction are harder to swap usefully than static ones.
The payer-side pattern to internalize is that paying requires a scan and authentication, while receiving does not. A genuine incoming payment never requires you to scan a code and enter your PIN; messages that claim otherwise - refunds, prizes, cashbacks that start with 'scan this' - are fraud by construction. The payment QR itself cannot move money without your authentication, so the danger is always pointing it at the wrong payee.
Beyond UPI: the wider payment QR landscape
QR acceptance is global but the schemes differ. Wallet ecosystems in China run on merchant codes from their own platforms; several European countries standardize structured creditor QR codes on invoices for bank-transfer payments; and cryptocurrency payments commonly use URI standards such as the bitcoin URI scheme, which encodes address, amount and message into a scannable code. The common thread is that a QR requires no point-of-sale hardware, only a printed code and the payer's app.
For merchants, the practical question is which schemes your provider's QR supports, not which formats exist. Cross-border and multi-scheme acceptance usually comes as a single provider-issued sticker that carries several compatible payloads; assembling one yourself is not something a static generator can safely do, because scheme routing belongs to the payment network rather than to the printed code. Ask your provider which networks their code covers before printing it on public material.
Key takeaways
- Payment QRs encode instructions - payee identity and optionally amount - never money or card data
- UPI QRs are interoperable by mandate: any UPI app can pay any UPI QR code
- Dynamic merchant QRs lock the amount and reference; static QRs rely on the payer to enter it correctly
- Sticker-swap fraud is the main merchant risk - verify the payee name every time and inspect public stickers
- Receiving money never requires scanning a code and entering your PIN; messages that claim it does are fraud
Put it into practice
Frequently asked questions
Continue reading
QR Codes for Restaurants: Menus, Payments and Service
A complete guide to QR codes in restaurants: menu codes, table tents, payments, reservations and WiFi - plus sizing, hygiene and updating advice.
Read guideQR Code Security: Risks, Quishing and Safe Habits
Understand QR code security risks: quishing attacks, malicious links, fake stickers and tampering - and simple habits that keep scanning safe.
Read guideQR Codes for Business: Everyday Uses That Pay Off
Practical QR code uses for small business: packaging, storefronts, loyalty, reviews, WiFi sharing and more - with placement and print guidance.
Read guide