UPI for Online Merchants in India: Integration and Reconciliation

Header image: conceptual illustration.

UPI (Unified Payments Interface) is India's real-time payment system, operated by the National Payments Corporation of India (NPCI) under the oversight of the Reserve Bank of India. NPCI's UPI product overview describes the system. Online merchants typically access UPI through a payment aggregator or bank rather than connecting to NPCI directly. This guide explains the common flows and how to reconcile them.

Common UPI flows for online merchants

• Collect / request: the merchant sends a payment request to the customer's UPI ID; the customer approves in their UPI app.
• Intent: on mobile, the customer is handed to a UPI app installed on their device.
• QR: the customer scans a dynamic QR code generated for that order.

Which flows are available depends on your provider and on current NPCI rules, which change over time. Ask your provider which flows they support and recommend.

Integration checklist

1. Merchant onboarding with an aggregator or bank — eligibility is decided by them.
2. Create a unique order reference per payment.
3. Generate the request, intent link or dynamic QR via the provider's API.
4. Wait for the provider's callback, verify it, and confirm via status API before marking paid.
5. Expire unpaid requests after a set time and stop accepting late duplicates for the same order.
6. Handle refunds through the provider's API.

Why server-side verification matters

The customer's UPI app may show success while your callback is delayed, or the customer may screenshot a payment for a different order. Mark orders paid only from a verified, successful final provider status that matches your order reference, amount and currency, and credit idempotently on the provider transaction ID.

Reconciliation

Store, per payment:

• Your order reference.
• The provider transaction ID.
• The UPI transaction reference (often called RRN or UTR) if your provider returns it.

Daily, match provider reports to orders, then match settlement totals. Typical exceptions: paid but not marked paid (missed callback), amount mismatch, payment against an expired request, refunds.

Hypothetical example

*Invented.* A customer pays a QR code after it expired. The provider still reports the payment. The merchant's rule says late payments for expired orders are matched and either fulfilled or refunded automatically within a defined time, and support has a macro explaining this.

The UPI flows merchants use

Collect request

The merchant requests payment and the customer receives a notification in their payment app to approve it. Simple to implement, but dependent on notification delivery and customer attention, and generally lower converting than intent flows on mobile.

Intent flow

The customer is deep-linked directly into their chosen payment app with the payment pre-populated. On mobile this is the highest-converting pattern because it removes steps and ambiguity. Offer an app chooser showing the customer's likely apps.

QR code

The customer scans and pays from any UPI app. Essential for desktop checkouts and in-person contexts, and useful as a universal fallback.

Mandates and recurring

Recurring collection via mandate supports subscriptions within defined limits and authorisation rules. Treat setup and modification flows carefully, as failures here are invisible until renewal fails.

Handles, PSPs and why routing matters

UPI transactions route through a payment service provider handle backed by a sponsor bank. Different handles perform differently, and performance varies by issuing bank, time of day and load. A gateway with multiple handles and health-based routing can recover a meaningful share of transactions that a single-handle provider simply loses.

When evaluating an Indian gateway, ask how many handles they route across, how routing decisions are made, and for success rates segmented by handle and issuing bank. This is one of the most consequential and least-discussed differences between Indian providers. See also best payment gateway India.

Handling UPI states correctly

The pending problem

UPI's most operationally significant behaviour is the pending state. A transaction can remain unresolved for minutes, then resolve either way. Merchants who treat pending as failure double-charge customers; merchants who treat it as success ship goods they were not paid for.

The correct pattern:

1. Credit only on a confirmed terminal status from a signed webhook or verified status query.
2. Define an explicit pending timeout aligned to your provider's guidance.
3. Run a reconciliation sweep against the provider's status endpoint for anything unresolved.
4. Tell the customer clearly that the payment is being confirmed and not to retry immediately.
5. Auto-refund any late-confirmed duplicate promptly.

Improving UPI success rates

• Use intent flows on mobile and QR on desktop; do not force collect requests everywhere.
• Keep amounts within comfortable limits and route larger tickets to IMPS or bank transfer.
• Route across multiple handles with automatic health-based failover.
• Retry intelligently — bounded, idempotent, and never on terminal declines.
• Monitor by issuing bank so you can detect a specific bank's degradation rather than blaming UPI generally.
• Reduce time to payment page — every extra step costs completion.
• Show the payment app chooser rather than a single default.

Limits and rail pairing

UPI is designed for consumer-scale transactions and subject to network and bank-level limits. High-ticket merchants must pair UPI with IMPS for immediate higher-value transfer, and NEFT or RTGS for larger and business flows. Present the right method by amount automatically, and communicate limits before the attempt.

Detail on the full Indian rail set is on the India payment gateway page.

Refunds and disputes

Refund behaviour on UPI is fast relative to card rails but not instantaneous, and partial refunds have their own semantics. Define your policy, communicate expected timing to customers, and reconcile refunds daily. Refund friction is one of the top drivers of support cost and complaint escalation for Indian merchants.

Compliance context for UPI merchants

Merchant category coding must reflect the real business. Website compliance — accurate pricing, refund policy, terms, contact details and a grievance channel — is checked and matters. Providers will expect complete corporate KYC and a truthful flow-of-funds description. Merchants who prepare this properly onboard faster and stay live longer.

International and high-risk merchants

Merchants incorporated outside India generally cannot contract a domestic PSP directly, because settlement assumes an Indian entity and bank account. Cross-border capable providers collect on Indian rails and settle abroad — see the cross-border payment guide for South Asia.

For Forex, gaming and betting merchants, mainstream providers exclude the category outright. Specialist providers can support legitimate flows with correct coding, transparent narration and dedicated banking. Read how high-risk payment processing works, the Forex payment processing guide and the high-risk payment solution India page.

Go-live checklist

1. Implement intent, collect and QR flows and select by device context.
2. Add idempotency keys to all creation calls.
3. Verify signed webhooks; make handlers replay-safe.
4. Define pending timeouts and an automated status sweep.
5. Pair UPI with IMPS and bank rails by ticket size.
6. Route across multiple handles with health-based failover.
7. Monitor success by handle, issuing bank, hour and ticket band.
8. Automate daily reconciliation including late resolutions.
9. Publish refund and grievance policies clearly.
10. Confirm MCC and business description with your provider in writing.

Frequently asked questions

Can I connect directly to NPCI?

Online merchants generally integrate through a licensed aggregator or bank.

Are UPI payments refundable?

UPI payments themselves are push payments; refunds are new transfers initiated through your provider.

Related: UPI vs IMPS for merchants and our UPI payment gateway page.

How does UPI work for merchants?

A merchant initiates a UPI payment through a gateway using a collect request, an intent deep link or a QR code. The customer authorises it in their payment app, and the merchant credits the order on a confirmed terminal status delivered by signed webhook or verified status query.

Which UPI flow converts best?

Intent deep links convert best on mobile because they remove steps and ambiguity, QR is best for desktop and in-person, and collect requests are the weakest on mobile because they depend on notification delivery and customer attention.

Why do UPI transactions stay pending?

UPI transactions can remain unresolved briefly while the network and banks confirm, then settle either way. Merchants must credit only on terminal status, define a timeout, and run reconciliation sweeps against the provider's status endpoint rather than assuming success or failure.

What are UPI transaction limits for merchants?

UPI is designed for consumer-scale payments and is subject to network and bank-level limits. Merchants with higher ticket sizes should pair UPI with IMPS for immediate transfer and NEFT or RTGS for larger and business payments.

How can I improve UPI success rates?

Use intent flows on mobile and QR on desktop, route across multiple PSP handles with health-based failover, keep tickets within limits and route larger ones elsewhere, apply bounded idempotent retries, and monitor performance by handle, bank and hour.

Can foreign merchants accept UPI payments?

Not usually by contracting a domestic Indian PSP, since settlement requires an Indian entity and bank account. Foreign merchants typically use a cross-border capable provider that collects on Indian rails and settles internationally.

Sources

• NPCI, UPI product overview: https://www.npci.org.in/what-we-do/upi/product-overview
• Reserve Bank of India: https://www.rbi.org.in/