UPI QR payments, from the counter to the checkout

UPI (Unified Payments Interface) moves money straight from one bank account to another, in real time, using an app on the customer's phone. It is run by NPCI. The customer never shares a card number or bank details with you: they approve the payment in their own app with a UPI PIN that only they know.

Every payment passes through a handful of parties. The customer only sees their app; the merchant only sees a confirmation. Everything in between happens in seconds.

A UPI QR is a payment request in picture form. When scanned, it tells the customer's app who to pay: at minimum the merchant's UPI ID and name. A QR generated for a particular sale can also carry the amount and your own reference for the order, so the customer only has to check and approve.

Because every UPI app reads the same format, one QR works with any UPI app the customer prefers. There's nothing for the customer to install, and nothing for you to integrate per app.

There are two kinds of UPI QR. The difference decides who types the amount, whether a payment can be matched to an order automatically, and how much room there is for mistakes and fraud.

For the customer, a QR payment takes a few taps. What matters for the merchant is what the customer checks along the way, because that is where most mistakes and most fraud are caught.

On the merchant's side, the work happens before and after the customer's few taps: creating the right QR, knowing when a payment has really arrived, and closing the sale in your records.

A dynamic QR can be created from your billing system or a dashboard for each bill. Confirmation reaches you through whichever channels your setup includes: an audible sound box at the counter, a dashboard or app notification, or a status update sent to your own system.

A QR is one of three ways to start a UPI payment. Online, the right choice depends on the customer's device: on a phone, the payment page can open the customer's UPI app directly (intent); on a desktop, there's no app to open, so the page shows a QR to scan with the phone. If you build your own checkout, the collection API covers both.

A collect request, where the customer types their UPI ID and approves a request that appears in their app, is the third option. NPCI has been narrowing where collect requests can be used, so check the current rules with your provider before relying on it.

A UPI payment ends in one of three states: success, failure or pending. The first two are final. Pending means the bank hasn't confirmed the outcome yet, and it can still go either way.

The only confirmation that counts is the one on yourside. A customer's success screen can be old, edited, from a different shop, or a payment that is still pending on the bank's side.

Most UPI failures are on the customer's side and resolve with a second attempt. A few need the merchant to act.

Two different things can send UPI money back to a customer. A refundis your decision after a successful payment: it goes back to the bank account linked to the customer's UPI ID, through the provider that processed the payment. See refunds.

An auto-reversalhappens on its own when a payment debited the customer but wasn't confirmed to the merchant. Under RBI's turnaround-time framework it has to be completed within T+5 days, with ₹100 a day in compensation to the customer if the bank is late. You don't issue it, and refunding the same payment as well would pay the customer twice.

Reconciling UPI means proving that every bill marked paid has a payment behind it, and every payment reached your bank in a settlement. Dynamic QRs make this straightforward, because each payment carries your bill or order reference. Static QRs don't, so payments are matched by amount and time, which breaks down on a busy day when two customers pay the same amount.

Tagging each QR by store and counter lets one report show counter, delivery and online UPI collections side by side, each matched against settlement.

Until 14 October 2026, government rules set zero MDR (the merchant discount rate, the percentage fee on each payment) on UPI payments to merchants. From 15 October 2026, NPCI keeps payments up to ₹2,000 at zero and sets 0.4% on merchant payments above ₹2,000, capped at ₹300; our MDR explainer has the full table. Even at zero MDR, not every UPI setup is free: providers can charge for other services, such as sound box devices, software or reporting, and GST applies to those charges. Peneu pricing is quoted per business, so ask what, if anything, applies to your setup.

UPI itself is secure: the customer approves every payment in their own app with a PIN. Counter fraud works by fooling people, not by breaking UPI. A few habits stop almost all of it.

Whether QRs are created from a dashboard or from your billing system, a few decisions shape how well UPI works for you:

• Create one dynamic QR per bill or order, carrying your own reference, rather than reusing one QR for everything.
• Decide how long an unpaid dynamic QR should stay valid, where your setup allows expiry, and what happens to the bill if it lapses.
• Mark bills paid from the payment's confirmed status, not from the customer's screen or a manual tick.
• Handle pending payments explicitly: keep the bill open, and don't generate a second QR for the same bill while the first is pending.
• Tag QRs by store, counter or agent from day one; it is hard to add later.

The same QR works everywhere; what changes is the kind of QR and how payments are confirmed.