A QR payment is a transaction in which the payer scans a QR code with a banking, wallet or payment app. The code encodes the payee's identifier, and sometimes the amount and reference, so the payer does not have to type them.
Why it matters
QR payments need no card terminal, only a printed or on-screen code, which lowered the cost of accepting digital payments for small shops. Two styles exist. A static QR contains only the payee details, and the payer enters the amount. A dynamic QR is generated per transaction and carries the exact amount and an order reference, making automatic reconciliation easier. Standards vary: India's UPI uses a URI-style payload, while EMVCo defines a merchant-presented QR specification used in many countries.
Example
A UPI-style payment link inside a QR code looks like this:
upi://pay?pa=shop@examplebank&pn=Example%20Shop&am=250.00&cu=INR&tn=Order%201042
The fields identify the payee address, name, amount, currency and note. A merchant can create one with the QR code generator for testing the encoding, but production payments should come from a regulated provider.
Common mistakes
- Pasting a sticker QR over a shop's real one. Customers should check the payee name shown before approving.
- Reusing a static code when an exact order amount is needed.
- Confusing the QR code with the payment itself; settlement still goes through the network.
Rules vary by country; this entry is a definition only.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.