One QR at the counter: payment, reviews and your menu behind a single code

Look at a busy counter in India today. There is a UPI QR from the payment app. A review QR someone printed last year. Possibly a menu QR left over from the pandemic, and a WhatsApp one for orders.

Four codes. The customer scans whichever is nearest, gets the wrong thing, and gives up.

Why one code is better than four

The scanning habit is already universal here — hundreds of millions of UPI QR codes are in use, and a large share of smartphone owners scan something most days. The habit is not the constraint. Choosing between four identical black squares is the constraint.

There is also a timing argument. The moment just after paying is the single best moment to ask for anything else — a review, a menu look, a follow. The customer is standing still, satisfied, phone in hand. Post-payment asks convert far better than a message sent hours later, when they are on a train and have forgotten you.

Four separate codes waste that moment. One code that knows what to offer does not.

How consolidation actually works

The trick is that the printed code does not contain the payment or the review. It contains a link. What that link opens is decided when someone scans it, not when the sticker was printed.

That indirection is the whole thing, and it has one consequence worth understanding: you can change what your code does without reprinting it. Add a menu link in the morning and every sticker already stuck to a table has it by lunch.

With Sunaam, a scan of your existing review QR can now open a small welcome page carrying your shop's name and logo, and up to five things you choose:

• Pay — opens the customer's own UPI app addressed to you
• Write a review — the assisted flow, in any language
• See the menu — or your price list
• Any link you like — Instagram, WhatsApp, directions, bookings

Switch none of them on and a scan goes straight to the review flow, exactly as before. Nothing to reprint either way.

Where the money goes, and where it does not

This is the part to be clear about, because it is where most "all-in-one QR" pitches get vague.

Sunaam never touches your money. The payment button opens the customer's own UPI app, addressed to your UPI ID. The money goes from them to you, directly, the same as if they had scanned your bank's QR. There is no amount pre-filled — the customer types what they owe — and there is no settlement account in between.

We do that deliberately. Collecting payments and passing them on would make us a payment aggregator, which in India is a licensed activity. It would also mean your money sitting somewhere it does not need to sit. A link is enough.

The honest limits

Two things worth knowing before you consolidate:

Some UPI apps refuse payment links. PhonePe and Google Pay decline browser-opened payment links for certain merchant account types, showing an error like "payment through a link is not allowed for this merchant". Other apps — Paytm, BHIM, bank apps — accept the same address without complaint. Where this happens, the customer can still pay by copying your UPI ID into their app, and we show them how. If most of your customers use PhonePe, keep your existing payment QR up as well. One code is a convenience, not a reason to remove something that works.

A typo in your UPI ID pays a stranger. Because nobody is holding the money in the middle, nothing catches a wrong address — it simply pays whoever owns it. Check it character by character, and send yourself ₹1 before you print anything.

A reasonable place to start

Keep your bank's payment QR where it is. Add a review QR that also carries your menu and your Instagram. See what customers actually use over a fortnight.

Then consolidate what earns its space, and leave up what people rely on. The goal is fewer decisions at the counter — not a tidier counter for its own sake.

---

Sunaam turns your existing review QR into one that can also take payments, show your menu and carry your links — without reprinting anything. See how it works.