Shops collecting by static UPI QR cannot tell which customer or order a payment belongs to when several payments share the same amount.
A dynamic QR embeds the amount and a merchant reference for each bill, so the payment record carries a unique key; static payments can only be matched on amount and time.
Generate a dynamic QR per bill from the billing or POS system, keep the static QR for unbilled small sales, and export both payment lists daily with reference, amount and time.
Billed UPI sales match to invoices by reference, and only the static-QR payments need matching by amount and time window.
A static UPI QR code is one fixed code for your shop. The customer scans it and types the amount, so every payment reaches you as a bare amount with no order attached. A dynamic UPI QR code is created for each bill, with the exact amount and a reference built in. That reference comes back with the payment, which makes matching to orders far easier.
How are static and dynamic QR codes different?
| Static QR | Dynamic QR | |
|---|---|---|
| How it is made | Printed once, linked to your UPI ID | Generated per bill by billing software, POS or gateway |
| Who enters the amount | The customer | Your system; the customer cannot change it |
| Order reference in the payment | None, unless the customer types a note | Yes, your bill or order number |
| Risk of wrong amount | Real: ₹499 typed as ₹49 or ₹4,990 | Very low |
| Effort to match | Amount plus time, by eye or spreadsheet | Reference lookup, often automatic |
| Best use | Small counter sales, tips, donations | Billed counter sales, online orders, deliveries |
How do I know which customer paid when I only have a static QR?
Usually you work it out from three clues: the amount, the time and the payer name or UPI ID shown in your app. That works on a quiet morning. It breaks when several people pay the same amount close together, or when a customer pays from a family member’s account.
Some shops ask customers to show the success screen before leaving. That proves a payment happened. It does not link the payment to a bill in your books.
Worked example: five ₹499 payments in one hour
A café sells a ₹499 lunch combo. Between 1 pm and 2 pm, five customers pay.
On a static QR, the UPI app shows:
| Time | Amount | Payer shown |
|---|---|---|
| 1:04 pm | ₹499 | R KUMAR |
| 1:11 pm | ₹499 | 9876XXXX10@ybl |
| 1:12 pm | ₹499 | 9876XXXX10@ybl |
| 1:12 pm | ₹499 | S IYER |
| 1:40 pm | ₹449 | ANITA M |
Total received: 4 × ₹499 + ₹449 = ₹1,996 + ₹449 = ₹2,445. Billed: 5 × ₹499 = ₹2,495. ₹50 is short. Three payments look identical in amount and arrive within a minute, and two come from the same UPI ID. Was one customer paying for a friend? Did the ₹449 customer mistype? You cannot tell from the payment alone.
On dynamic QR, each of the five bills (B-2201 to B-2205) shows its own code for exactly ₹499. The payment list then reads B-2201 ₹499, B-2202 ₹499, and so on. The total is ₹2,495, and an unpaid bill would stand out by its number.
Can a shop use dynamic QR codes at the counter?
Yes. Common ways:
- A POS card machine that also shows a UPI QR for the bill amount.
- A small display or soundbox linked to your billing software.
- A billing app on a tablet that turns the bill into a QR on screen.
The bill number your system creates is the reference. Keep it, because that is what lets the payment find its order later.
What happens after the payment arrives?
If the QR is linked straight to your current account, each payment lands individually. If it is issued by a payment gateway, payments land in the gateway’s escrow account and reach you as a combined settlement, and you match the gateway report’s rows to your bills.
What to read next
- Next in this series: order ID, payment ID, RRN, UTR and ARN: which reference number is which?
- Tying counter takings to the bank: cash-to-bank reconciliation for UPI and POS
- Matching UPI settlements at volume: UPI settlement reconciliation
- When matching becomes daily work: payment gateway reconciliation
Payment-gateway settlement reconciliation is on the TransactIG roadmap.