UPI is a payment flow, not only a QR image
A professional merchant setup connects the customer’s payment action to an order, a transaction identifier, a final status and a reconciliation record. A screenshot or customer confirmation is not enough. The merchant should fulfil an order only after the dashboard, API or verified webhook reports final success.
Choose the correct collection experience
An all-method QR can open a checkout with the payment methods enabled for the merchant. A dynamic UPI QR can encode order-specific amount and reference information. A fixed-amount QR is useful for a known price, while a reusable counter QR may let the customer enter an amount. Separate QR records also make branch, campaign and counter-level reporting easier.
Pending is not paid
Network timeouts can leave a payment pending even when the customer sees a debit. Do not create a second untracked order or manually mark success based on a message. Keep the order pending, poll the authorized status endpoint where available and reconcile the bank or gateway reference. A failed debit may reverse automatically through the customer’s bank.
Reconcile every business day
Compare successful orders, gateway records, webhooks, refunds and settlement entries. Investigate missing webhooks, duplicate references and amount mismatches. The total collected amount is not the same as the amount eligible for settlement after fees, refunds, disputes, reserves or adjustments.
Protect the customer
Show the merchant name, order description, amount and support channel clearly. Never request a UPI PIN to receive a refund. A UPI PIN authorizes a debit and should be entered only in the customer’s UPI application. Refunds should follow the original payment route and include a traceable reference.
Move from Test to Live carefully
Test Mode validates screens and integration behavior but does not prove that a live bank or payment partner has approved the merchant. Before launch, complete KYC, confirm the approved use case, activate live credentials, verify webhooks, test small controlled payments and document the refund and settlement process for support staff.