Most businesses start with a printed UPI QR taped to the counter, and for a while it works perfectly. Then the questions start. Who paid ₹450 at 6:12 pm? Did table 7 pay the full ₹1,280 or ₹1,200? Why doesn't the day's UPI total match the till?
The answer usually isn't a different payment app. It's a different kind of QR code. This guide compares the two kinds, static and dynamic, explains what NPCI's rules say about each, and works through which one suits which kind of business. If you run a counter and want the practical side of speaker devices and fake screenshots, our QR and soundbox guide goes into that.
What a UPI QR code contains
A UPI QR code is a picture that holds payment details: at minimum, the UPI ID of the account that will be paid, and sometimes an amount and a reference. When a customer scans it with any UPI app, the app reads those details, looks up who the payee is, and asks the customer to confirm and enter their UPI PIN.
Two rules make QR codes work the same everywhere. Every UPI app must be able to read both UPI QR codes and Bharat QR codes (an older standard that can also take card payments). And the name the customer sees before paying comes from the payee's records, never from a name written into the QR itself.
How a QR payment works, step by step
From the customer's side, paying a UPI QR takes a few seconds, and each step is a check:
- The customer opens any UPI app and scans the code with its camera.
- The app reads the payee's UPI ID, and the amount and reference if it's a dynamic QR.
- The app looks up the payee and shows the name from the payee's bank records, or a verified merchant's brand name with a green tick.
- The customer types the amount for a static QR, or confirms the fixed amount on a dynamic one.
- The customer approves with their UPI PIN, or pays from UPI Lite for small amounts, or with fingerprint or face where their bank allows it.
- Both sides get confirmation: the customer's success screen, and your soundbox, merchant app or bank notification.
Only the last step counts for you. A customer's screen can be faked or show an old payment; your own notification can't. Our beginner's guide to what UPI is explains what happens between the banks during those seconds.
Paying from a saved QR image
Customers sometimes pay from a photo or screenshot of a QR code instead of scanning it live, for example a code you sent on WhatsApp. NPCI calls this "QR share and pay", and since April 2025 caps it at ₹2,000 for payments to people and to non-verified offline merchants, and doesn't allow it for UPI payments abroad. If customers regularly pay you larger amounts from a shared image, they'll hit that cap: send a payment link or a dynamic QR generated for the order instead.
Static and dynamic QR, defined
NPCI's definitions are short and useful:
- A static QR contains the payee's details but is not generated for a specific transaction, so it can be used for many payments. It's the one you print once.
- A dynamic QR contains the payee's details and is generated uniquely for each transaction. It's created by a billing system, terminal, app or website for one particular sale, usually with the amount and an order reference built in.
| Compared on | Static QR | Dynamic QR |
|---|---|---|
| Made | Once, printed or displayed | Fresh for every bill or order |
| Amount | Typed by the customer | Set by your system; the customer can't change it |
| Order reference | None | Built in, so the payment comes back tagged to the sale |
| Matching payment to sale | By amount and time, by hand | Automatic, by reference |
| Wrong amounts | Common: underpaying, typos, rounding down | Rare |
| What you need | Nothing but the printed code | A billing system, terminal, app, website or payment link that can generate it |
| Best at | Low-volume counters, donations, quick start | Anything with a bill, an order number or a busy counter |
What NPCI's rules say
A few of UPI's operating rules affect which QR you can use and how:
- Websites must use dynamic QR. NPCI requires payment providers to enable intent-based UPI (a button that opens the customer's UPI app) for app and mobile-web merchants, and dynamic QR for other web-based merchants, such as a desktop checkout. A static QR image on a checkout page doesn't meet that.
- Any UPI app must work. Customers must be able to pay your QR from any UPI app, without restriction. You can't limit acceptance to a particular app.
- No surcharge for paying by UPI. If you charge a convenience fee at all, it must be shown before the customer chooses how to pay, and be the same across UPI, debit card, credit card and net banking.
- Your QR has to be approved. Payment providers must get each merchant QR design approved by NPCI before using it.
- New and replacement QRs from 1 December 2026 follow updated brand rules. Any merchant QR issued, or any existing one replaced, on or after that date must comply with the updated BHIM UPI merchant QR brand guidelines. Your provider handles this; it's a reason to get replacements from them rather than printing your own copies.
Which one fits your business
Match the QR to how you bill, not to what's cheapest to print.
| Business | Good fit | Why |
|---|---|---|
| Small kirana or tea stall, few UPI payments a day | Static QR plus a payment alert or soundbox | No billing system needed; volumes are low enough to match by hand |
| Busy counter with a billing system or POS | Dynamic QR on the bill or terminal screen | The amount can't be mistyped, and every payment comes back tagged to a bill |
| Restaurant with table service | Dynamic QR printed on each bill | Each table pays exactly its bill, and the payment matches the right table |
| Online store or booking website | Intent on mobile, dynamic QR on desktop | NPCI requires it, and the order is confirmed automatically |
| Delivery or cash-on-delivery orders | Dynamic QR on the delivery app, or a payment link | The agent collects the exact order amount and the order updates itself |
| Doctors, tutors, salons and other services | Dynamic QR or a payment link per invoice; static QR as a fallback | Invoices get paid against a reference, so you know who has paid |
| Donations, events, collection boxes | Static QR | Amounts vary by design and there's no bill to match |
The real difference: matching payments to sales
Taking the payment is the easy part with either kind of QR. The work, and the cost of getting it wrong, is in matching each payment to what was sold.
Here's an evening at a small restaurant with a static QR. Three tables pay ₹1,280, ₹640 and ₹640 within ten minutes. One of the ₹640 payments is actually from table 4 settling a ₹680 bill and rounding down. At closing, the UPI total is ₹40 short of the bills, and nobody can tell which table it was, because the payments carry nothing but an amount and a time.
With a dynamic QR printed on each bill, the same evening looks different. Each QR carries its bill's amount and reference, so table 4 can't pay ₹640 for a ₹680 bill, and each payment arrives already tagged to its table. Closing the day is a matter of checking that every bill is marked paid.
Knowing a payment has arrived
Whatever QR you use, trust only your own systems: your merchant app, terminal, soundbox or bank notification. Never a customer's phone screen, which is how fake-screenshot fraud works. Your payment provider must give you a way to check a payment's status in real time, which is what to use when a customer says they've paid and you've seen nothing.
If a customer's payment shows pending, it may still arrive a few minutes later. Our guide to pending UPI payments explains why, and what to do at the counter.
Keeping your QR safe
QR fraud against businesses is low-tech and effective. The protections are simple:
- Check your printed QR every day. The common trick is a sticker with someone else's QR placed over yours. Laminate it, mount it where staff can see it, and scan it yourself now and then to check the name that comes up.
- Ask customers to check the name before paying. Their app shows your verified brand name or your bank account name; if it shows anything else, the QR isn't yours.
- Remove old QR codes when you change accounts, owners or providers. Payments to an old QR go to the old account.
- Never ask customers to scan a QR to receive a refund. Scanning is always for paying. Refunds go back to the customer through your provider, to the original payment method.
- Keep your staff off personal QR codes. Payments should go to your business's QR, not a staff member's.
Business QR or a personal one?
Very small sellers can start with a personal UPI ID and QR, but a merchant QR from a bank or payment provider soon becomes worth it. Small merchants expecting up to ₹1 lakh of incoming UPI payments are set up in UPI's small-merchant category ("P2PM") and are paid into their own account in real time. A merchant QR also gives you a transaction record, status checks and a way to process refunds, which a personal account doesn't.
Our guide to payment gateways for small businesses covers the account, documents and costs. For what LILPE offers for UPI and QR collection, see the UPI and QR guide; availability for your business is confirmed during onboarding.
A quick decision guide
Answer these in order:
- Do you sell online? Then use intent buttons on mobile and dynamic QR on desktop. A static QR isn't an option for a web checkout.
- Do you produce a bill or invoice for each sale? If yes, use a dynamic QR on it, or a payment link for remote customers.
- Do you handle more than a few dozen UPI payments a day? If yes, the time saved on matching usually justifies a dynamic QR even without a full billing system.
- Are amounts genuinely variable, like donations or tips? A static QR is fine.
- Whatever you choose, keep a static QR as a backup for when the billing system or terminal is down.
Frequently asked questions
Can I use my personal UPI QR for my shop?
You can start that way, but a merchant QR is better once payments become regular. Small merchants expecting up to ₹1 lakh of incoming UPI payments can be set up in UPI's small-merchant category, which pays straight into their own account in real time, and a merchant set-up gives you transaction records, status checks and refunds.
Can customers pay my QR from any UPI app?
Yes. NPCI's rules require that merchants accept UPI payments from every UPI app without restriction, so a customer can scan your QR with whichever app they use.
What is Bharat QR, and do I need it?
Bharat QR is an interoperable QR standard that can take card payments as well as UPI. Every UPI app must be able to read both UPI QR and Bharat QR codes, so customers can pay either. Whether you need one depends on whether you want to accept card payments by QR; ask your provider.
Do I need a new QR code after 1 December 2026?
Not automatically. The updated BHIM UPI merchant QR brand rules apply to merchant QR codes issued, or replaced, on or after 1 December 2026. If your provider replaces your QR after that date, the new one will follow them.
Why does a dynamic QR stop working after a while?
Because it's made for one transaction. Many systems give a dynamic QR an expiry time so an old bill can't be paid twice or paid late. Generate a new one for the same bill if a customer comes back after it expires.
Official sources
- NPCI — Revision in transaction limits based on merchant and transaction type, NPCI/UPI/OC-76C/2025-26 (8 Apr 2025)QR share and pay capped at ₹2,000 for P2P and non-verified offline merchants; not allowed for UPI Global payments; intent not allowed for offline non-verified merchants.
- NPCI — UPI Consolidated Circular, Version 1.0, NPCI/UPI/CC/01 (18 Sep 2026)Static and dynamic QR, UPI QR and Bharat QR definitions (Annexure A); apps must read UPI QR and Bharat QR (2.4); names from QR codes not shown as the payee name (2.15); no surcharge, convenience fees disclosed upfront and consistent across debit modes (7.5); intent for app and mobile-web merchants, dynamic QR for other web merchants (7.6); pay by any UPI app (7.7); P2PM small merchants (7.2); verified merchants (7.8); merchant QR approval and updated brand guidelines from 1 December 2026 (13.2–13.3); real-time status check for merchants (32.11).
Last reviewed . Examples, amounts and screens marked illustrative are not LILPE figures.
