A reusable QR at a shop counter and an order-specific QR at online checkout can both start a UPI payment. The useful question is what the code is configured to do: identify a recipient, require an amount, accept one or many payments, or associate the payment with an order. The labels “static” and “dynamic” alone do not tell you every setting.
Choose the workflow you need
| Situation | Useful configuration | What staff still check |
|---|---|---|
| Small counter with varied bills | Reusable recipient code, with the amount entered or otherwise supplied for each sale | Correct amount and an actual receipt in the merchant’s records |
| Checkout linked to one order | Order reference, expected amount and single-payment or expiry controls where supported | Payment status matches the specific order |
| Several counters or branches | Provider-supported identifiers and reporting per location | The transaction is attributed to the correct counter |
One bank account does not automatically make branch reconciliation impossible. Ask the payment provider what identifiers and reports are available. Conversely, displaying different QR images is not enough unless the records distinguish them.
Amount and expiry are settings, not visual clues
Razorpay’s QR creation documentation illustrates the distinction: it offers single- or multiple-payment usage, fixed or customer-entered amounts, and supported closure settings. Single-payment codes require a fixed amount in that product. Some options are unavailable for multiple-payment codes. Those are provider-specific controls, not a universal definition for all UPI QRs.
A prefilled amount does not, on its own, prove that a code is dynamic. An order-specific code can also be printed or shared as an image; a screen is not an essential property. Ask how the code was generated and what happens after payment or expiry.
Checks for the customer
- Inspect the physical QR for an unexpected sticker or replacement.
- Scan with your genuine payment app.
- Read the recipient shown and compare it with the merchant’s expected trading or legal name.
- Check the amount and selected payment account or instrument.
- Approve only the purchase you intended, then check the result.
A business’s displayed payment name can differ from its shop sign. That is a reason to ask and verify, not proof of fraud by itself. If the merchant cannot explain the recipient, use another verified payment method.
NPCI’s fraud-awareness guidance warns about QR and PIN misuse. You should not approve an outgoing payment merely because someone describes it as receiving a refund. Scanning alone is not the same as completing a payment, but the next screen must still be read carefully.
Checks for the merchant
Confirm receipts in your own app, dashboard or bank records rather than relying solely on a customer’s screenshot. A soundbox can help staff notice a payment, but it does not eliminate disputes, delayed updates or mistakes. Match the amount and transaction to the bill before marking the order paid.
At opening, inspect the displayed code and confirm staff know the expected recipient name. At closing, compare recorded sales with payment receipts, pending items and refunds. If more than one person handles payments, give them a consistent way to record exceptions without exposing account credentials.
Test the code’s lifecycle
Before using a new checkout flow, document what happens when a customer pays the wrong amount, retries after a pending result, returns after expiry or requests a refund. Use the provider’s supported test environment where available. A successful scan does not prove that order matching and settlement reporting work.
Do not promise that a printed code works forever. Its account or provider configuration can change. Review old signage after changing accounts or payment providers, and retire codes through the appropriate controls.
Fees and mistaken payments
A QR image does not determine all charges. Check the merchant agreement, payment instrument, hardware rental and applicable processing terms. Our UPI fees guide separates customer costs from merchant charges.
If money went to the wrong recipient, preserve the reference and report it promptly to your bank or app. Do not assume every mistaken transfer follows the same automatic reversal rule as a technical failure. Suspected fraud needs prompt reporting; no universal three-day refund guarantee applies.
Reviewed on 27 October 2026. Provider features differ; the configuration example is illustrative, not a recommendation to buy a service.
Techleez Editorial Team
The Techleez publishes practical digital guides. For our scope, use of AI assistance and corrections process, read our editorial policy.
More from this author →
