Static QR and dynamic QR
| Static QR | Dynamic QR | |
|---|---|---|
| What the QR carries | The payee's UPI ID | The payee's UPI ID, the amount and a unique reference for one payment |
| Who enters the amount | The customer | Pre-filled for the customer |
| Matching a payment to an order | By amount and time, often by hand | By the reference in the payment |
| Life of the QR | Printed once, used for years | One payment, then it expires |
| Typical use | A small shop counter | Billing counters, invoices, app checkout, cash withdrawal at BC points |
A static QR is simple, but every payment has to be matched to a sale by amount and time. A dynamic QR puts your reference into the payment itself, so your system knows which order or withdrawal it belongs to.
Who needs authorisation to collect by QR
This section is our general reading, not legal advice. RBI's definitions don't single out QR codes, so confirm your own model with a legal adviser.
- The QR carries your own UPI ID from your own bank. Payments land straight in your account. The software only creates the QR and checks the payment status, and the bank remains your payment provider.
- Your platform collects into an account it controls and settles merchants later. That is payment aggregation. RBI's Payment Aggregator Directions of 15 September 2025 require authorisation for non-bank aggregators, and separate the categories for transactions where the payment instrument is physically present and where it isn't.
- You work as a technology provider. Your software serves a bank or an authorised payment aggregator, and the merchant's funds flow through their accounts, not yours.
Payonclick India is not a payment aggregator. It doesn't collect or hold funds for merchants, and it doesn't issue UPI IDs.
What we build, and what we don't
| Capability | Status |
|---|---|
| Dynamic QR for UPI cash withdrawal at BC points | Live in the Payonclick platform |
| Merchant collection QR on your own bank or payment aggregator | Custom development, scoped per project |
| A Payonclick QR collection service or partner QR API | Not offered |
A custom QR integration is built around your bank's or aggregator's API:
A QR per payment
Each order or invoice gets its own QR with the amount and a unique reference, and an expiry time.
Payment confirmation
The payment is confirmed through your bank's or aggregator's status API. A callback only triggers that check.
Reconciliation
Payments are matched to orders by reference, and daily against your settlement report.
Screens and receipts
Counter and customer screens that show paid, pending and expired clearly, with a receipt for every paid order.
Exceptions
A workflow for late payments on expired QRs, duplicate payments and refunds, run by your operations team.
Reports
Collections by counter, by day and by status, with exports for your accounts team.
Where dynamic QR already runs
The Payonclick platform renders dynamic QR codes for UPI cash withdrawal today. Each QR belongs to one withdrawal and expires in about 60 seconds. The result is verified through the provider's status API before the retailer's wallet is credited, and the credit uses a unique reference, so a repeated callback can't pay twice. A custom collection build follows the same rules.
Rules for QR payments that don't lose money
- Never accept a screenshot. A customer's screen can be faked. Only your bank's or aggregator's status is proof of payment.
- One reference per payment. Never reuse a reference, or two payments will match one order.
- Expire every QR. Treat a payment on an expired QR as an exception to review, not a new order.
- Verify callbacks. Use a callback as a prompt to check the status, not as proof.
- Reconcile daily. Match your platform's records with the settlement report every day.
- Know the limits. From 15 September 2025, UPI payments to verified merchants in some categories can go up to ₹5 lakh per transaction, while person-to-person payments stay at ₹1 lakh a day, according to News On AIR. Banks can apply lower limits.
Our guide to dynamic versus static UPI QR covers the payment flow in more depth.
Getting started
Choose your collection partner
Your own bank, or a payment aggregator authorised by RBI that offers dynamic QR and a status API.
Scope the build
We map the partner's QR, status and settlement APIs onto your flow and screens.
Build and test
Integration, counter and customer screens, reconciliation and reports, tested with your partner's credentials.
Go live
Launch, train your team, and review the first days of reconciliation together.