UPI Merchant Payment Guide: Accepting UPI Payments in India

UPI is the highest-volume real-time retail payment system in the world and the default payment behaviour for Indian consumers. For merchants, UPI is not one thing but a set of flows and routing choices whose configuration determines conversion. Two merchants on the same rail can see very different success rates purely because of how their integration and routing are built.

This guide explains UPI from a merchant operations perspective.

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.

Idempotency

Every creation call needs an idempotency key. UPI retries are common in real-world networks, and duplicate charges are the fastest way to generate disputes and support load.

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.

Reconciliation

Reconcile daily against the provider settlement file. Match by provider reference and internal order ID, categorise breaks, and specifically watch for late-resolved pending transactions that arrive after your reporting cut-off. Track fee and tax components separately so your net revenue reporting stays accurate.

System design guidance is in the merchant payment infrastructure guide.

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.

How PayEurasia supports UPI merchants

PayEurasia routes UPI alongside IMPS, NEFT and RTGS through dedicated India banking, with signed webhooks, idempotent APIs, method-level reporting and reconcilable settlement, plus cross-border settlement for merchants incorporated outside India.

See the UPI payment gateway overview or contact our team.

Frequently asked questions

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.