QR Code Payments: Merchant Flows, Security Checks, and Customer Trust
Understand merchant-presented and customer-presented QR payment flows, then build controls for destination integrity, confirmation, fraud, and support.
Merchant workflow
QR Payments
Use QR to begin a payment while preserving the checks that tell the customer who will be paid, how much, and whether the merchant actually received confirmation.
Experience design
Make every payment state explicit
The code can begin the flow, but the app and merchant system must verify identity, amount, currency, status, and exceptions.
🏪
Merchant identity
Show the expected merchant or account name before authorization and keep provider records current.
💱
Amount and currency
Use transaction-specific data where practical and give the customer a final review before approval.
✓
Trusted confirmation
Fulfill only from a provider or point-of-sale status, not a customer screenshot or animation.
Operational workflow
Connect the physical code to payment operations
Public placement, account configuration, point-of-sale data, confirmation, refunds, and incident response must agree.
Choose the scheme
Identify the applicable payment provider, presentation mode, standard, certification, and merchant account.
Configure safely
Validate amount, currency, terminal, reference, expiry, fees, and test-versus-production separation.
Inspect the placement
Use branded tamper-evident material and check public codes at scheduled intervals.
Reconcile the result
Match provider confirmation to the sale and handle pending, duplicate, reversed, and refunded states.
Controls and ownership
Protect the payee, account, and customer
A malicious sticker or compromised dashboard can reroute money while the square still looks legitimate.
Administrative access
Use strong authentication, role separation, key rotation, audit logs, and rapid revocation.
Physical inventory
Map each code to merchant, location, terminal, account, and inspection schedule.
Destination integrity
Monitor configuration and routing changes, certificate health, and unexpected account updates.
Anomaly response
Alert on unusual refunds, velocity, operating hours, locations, or destination changes.
Customer alternatives
Provide another approved payment method for people who cannot or do not want to scan.
Data boundaries
Keep payment completion separate from marketing consent and collect only needed transaction data.
Fallback: Provide a staffed alternative such as card, cash, or another approved method and a secure lookup for pending transactions; never ask customers to prove payment only with a screenshot.
Recommended reading
Go deeper before launch
Use the long-form guides to test the physical asset, mobile flow, and operating model.
Static vs. Dynamic QR Codes: Which Architecture Fits Your Campaign?
Compare direct-encoded static codes with redirect-based dynamic codes across editing, analytics, longevity, privacy, cost, and operational control.
QR Code Analytics: What Scan Tracking Can—and Cannot—Tell You
Define useful QR metrics, label physical placements, reconcile redirect events with web analytics, and avoid treating scans as people.
QR Payments FAQ
Questions to settle before publishing
The merchant displays the code and the customer scans it. A customer-presented flow reverses those roles.
It can be appropriate under a provider’s rules, but it may rely on manual amount entry and requires strong payee verification and physical tamper controls.
Use the provider or point-of-sale status tied to the transaction reference, not the display on the customer’s phone.
Verify the merchant name, amount, currency, destination or app context, and final confirmation. Stop if the information is unexpected.