I Put a QR on the Counter — Then Customers Asked What to Scan
Last updated
The first UPI sticker I printed was the size of a postage stamp. On my phone preview it looked sharp. On the glass counter, under tube lights and fingerprint smudges, people squinted, gave up, and asked for the UPI ID out loud. That is not the point of a QR.
I run a small counter business. Speed matters more than branding theory. What I needed was a card you could spot from a step away, with a name people trust and a code large enough that mid-range phones lock on in one try.
What went wrong with “just print the QR”
A bare QR is silent. No merchant name, no “Scan to pay,” no hint that PhonePe, GPay, and Paytm all work. First-time customers hesitate. Regulars still ask “is this still the right one?” after you rotate accounts.
Size was the other killer. Compression for WhatsApp status, then print, then laminate, then tape—each step shrank the quiet zone. Scanners hate that.
The counter card pattern that stuck
- Generate the payment QR with the real UPI ID and merchant name filled in—not a screenshot of someone else’s poster.
- Use UPI QR or the matching app QR (Paytm, PhonePe, Google Pay) so the payload matches what you tell customers.
- Switch Output Type to Printable Design so the layout includes a large code, merchant line, and footer—not a floating black square.
- Print on stiff paper or a table tent. Keep the code above 4 cm wide in physical size when you can.
- Place it where hands don’t rest: upright stand beats flat sticker under the card reader.
Copy that reduces awkward questions
- Merchant name in the same spelling as your UPI display name
- Optional amount only when you truly want a fixed bill
- Phone number in the footer for “code won’t scan” moments
- One short line: “Scan with any UPI app”
Quick tip: Test with two phones—one older Android, one iPhone—before you laminate fifty copies.
When to reprint
Change UPI ID, shop name, or GST branding? Reprint. Don’t tape a handwritten correction over an old code. Half-updated posters destroy trust faster than no poster.
Try it free: Open the UPI QR generator, choose Printable Design, and export a print-ready PDF.
More options live under QR Tools.
Lighting and glare on glass counters
Tube lights reflecting off lamination turn a perfect QR into a white blob. Matte laminate or a slight tilt on the stand fixed more “scan failures” for me than regenerating the file.
If the counter faces a window, put the card with its back to the brightest light. Customers should look into the card, not into the sun bouncing off it.
I keep a spare unlaminated print in the drawer. When the display copy gets scratched, I swap in five minutes instead of redesigning from scratch.
Teaching staff what to say
A one-line script helps: “Please open any UPI app and scan this card—the name should match our board.” That stops people typing random VPA guesses.
If the amount field is blank on purpose, say so. Fixed-amount QRs confuse tips and partial payments.
New hires should scan the live card once on day one. If their phone fails, fix the print before peak hour.
Paytm vs PhonePe vs plain UPI branding
Some customers look for a familiar app color. Our printable layouts lean into that without locking you into one wallet—the payload is still UPI.
If you only accept one app for policy reasons, say it on the card. Ambiguity creates arguments at the counter.
I still prefer “any UPI app” copy for walk-ins. Brand colors are decoration; the ID is the truth.
File hygiene before printing
Export PNG for digital share and PDF for print. Don’t screenshot the browser preview—that softens edges.
Keep the generator session values saved so a reprint next month matches last month’s ID.
Version the filename: shop-upi-2026-07.pdf. Future you will thank present you.
Privacy and who can see the code
A counter QR is public by design. Don’t encode personal phone OTP links or private admin URLs on the same card.
If you rotate payment accounts seasonally, archive old prints so they don’t reappear in a festival decoration box.
For delivery staff carrying payment cards, treat them like cash—lost cards mean wrong-account risk until you disable the VPA.
Lighting and glare on glass counters (continued)
Tube lights reflecting off lamination turn a perfect QR into a white blob. Matte laminate or a slight tilt on the stand fixed more “scan failures” for me than regenerating the file.
If the counter faces a window, put the card with its back to the brightest light. Customers should look into the card, not into the sun bouncing off it.
I keep a spare unlaminated print in the drawer. When the display copy gets scratched, I swap in five minutes instead of redesigning from scratch.
Teaching staff what to say (continued)
A one-line script helps: “Please open any UPI app and scan this card—the name should match our board.” That stops people typing random VPA guesses.
If the amount field is blank on purpose, say so. Fixed-amount QRs confuse tips and partial payments.
New hires should scan the live card once on day one. If their phone fails, fix the print before peak hour.
Paytm vs PhonePe vs plain UPI branding (continued)
Some customers look for a familiar app color. Our printable layouts lean into that without locking you into one wallet—the payload is still UPI.
If you only accept one app for policy reasons, say it on the card. Ambiguity creates arguments at the counter.
I still prefer “any UPI app” copy for walk-ins. Brand colors are decoration; the ID is the truth.
File hygiene before printing (continued)
Export PNG for digital share and PDF for print. Don’t screenshot the browser preview—that softens edges.
Keep the generator session values saved so a reprint next month matches last month’s ID.
Version the filename: shop-upi-2026-07.pdf. Future you will thank present you.
Privacy and who can see the code (continued)
A counter QR is public by design. Don’t encode personal phone OTP links or private admin URLs on the same card.
If you rotate payment accounts seasonally, archive old prints so they don’t reappear in a festival decoration box.
For delivery staff carrying payment cards, treat them like cash—lost cards mean wrong-account risk until you disable the VPA.
Lighting and glare on glass counters (continued)
Tube lights reflecting off lamination turn a perfect QR into a white blob. Matte laminate or a slight tilt on the stand fixed more “scan failures” for me than regenerating the file.
If the counter faces a window, put the card with its back to the brightest light. Customers should look into the card, not into the sun bouncing off it.
I keep a spare unlaminated print in the drawer. When the display copy gets scratched, I swap in five minutes instead of redesigning from scratch.
Teaching staff what to say (continued)
A one-line script helps: “Please open any UPI app and scan this card—the name should match our board.” That stops people typing random VPA guesses.
If the amount field is blank on purpose, say so. Fixed-amount QRs confuse tips and partial payments.
New hires should scan the live card once on day one. If their phone fails, fix the print before peak hour.
Paytm vs PhonePe vs plain UPI branding (continued)
Some customers look for a familiar app color. Our printable layouts lean into that without locking you into one wallet—the payload is still UPI.
If you only accept one app for policy reasons, say it on the card. Ambiguity creates arguments at the counter.
I still prefer “any UPI app” copy for walk-ins. Brand colors are decoration; the ID is the truth.
File hygiene before printing (continued)
Export PNG for digital share and PDF for print. Don’t screenshot the browser preview—that softens edges.
Keep the generator session values saved so a reprint next month matches last month’s ID.
Version the filename: shop-upi-2026-07.pdf. Future you will thank present you.
Related tools & categories
Related articles
Base64 Encode: Useful Encoding, Not Encryption
Base64 makes binary safe for text channels—it does not hide secrets. Learn correct use with CalcoWorks Base64 Encode.
EMI Felt Affordable Until I Looked at Total Interest
A borrower’s plain-language walk through EMI comfort vs lifetime interest—and the calculator habit that changed which loan offer I signed.
Pretty-Printed JSON Saved Me From a 2 A.M. “Invalid Payload” Spiral
A developer-adjacent walkthrough of messy API responses, trailing commas, and the formatter habit that makes debugging less emotional.