UPI Intent vs UPI Collect for Merchants: What Changed in 2026
UPI intent vs UPI collect for merchants used to be a conversion question. In 2026 it is also a compliance question. With intent, the customer taps pay on your checkout and lands inside their UPI app with the amount already filled in. With collect, the merchant sends a payment request to a UPI address the customer typed in. Since NPCI moved merchant payments away from collect, mobile checkouts in India are expected to run on intent, and desktop checkouts on a QR code. This guide explains how each flow works, what changed, and how to design checkout, reconciliation and your payin API around it.
Talk to sales on Telegram: @Bestpay24SalesSupport
If you are new to the rails behind these flows, read our comparison of UPI vs IMPS for high risk deposits in India first, then return here for the checkout details.
How UPI intent works for merchants
Intent is a push flow started by the customer. On a phone, your checkout shows a UPI button. The customer taps it, your page or app opens a deep link, and the phone offers the UPI apps it has installed, such as PhonePe, Google Pay or Paytm. The chosen app opens with the merchant, the amount and your order reference already filled in. The customer checks the details, enters the UPI PIN and the payment is made. Your system then receives a confirmation from the provider.
There is no typing of a payment address and no waiting for a notification, which removes the two steps where customers most often drop out. One large Indian gateway has published a benchmark showing intent flows converting roughly 10 to 15 percent better than collect, with success rates in the low to mid 90s. Treat any such figure as indicative, because results depend on traffic, banks and device mix, but the direction is consistent across providers. Intent also gives you more visibility, because you can often see which UPI app the customer used.
How UPI collect works
Collect is a pull flow started by the merchant. The customer chooses UPI at checkout and types a UPI address, called a VPA, into a field. Your provider validates the address and sends a collect request through the UPI network to the customer's app. The customer has to notice a notification, open the app, review the request and approve it with the PIN, and usually has only a few minutes before the request expires.
Every step is a place to lose the customer. A mistyped VPA fails validation, a delayed notification lets the request expire, and a customer on a desktop browser has to pick up a phone to finish. For years collect was the standard way to take UPI payments on desktop, which is why many older integrations still have it hard-wired into the cashier. It was also the feature fraudsters abused most, which is the background to what NPCI did next.
What NPCI changed for merchant collect requests
NPCI first ended person-to-person collect requests on 1 October 2025, according to its circular of 29 July 2025 as reported by Angel One and other Indian outlets. Merchant payments were left in place at that stage. Industry estimates reported by Business Standard in 2025 put collect at under 3 percent of merchant UPI payments, and NPCI then moved to phase it out for merchants as well.
Payment providers' documentation describes the result. Razorpay, PayU and Cashfree each say that, in line with NPCI guidance, UPI collect for merchant payments was deprecated from 28 February 2026. Android mobile traffic is expected to use UPI intent, and desktop traffic is expected to use UPI QR. Cashfree's guide notes that iOS is exempted for now, and other guides describe a narrow set of exemptions, for example for certain market applications and mandate management. The exemptions that apply to you depend on your provider and your category, so confirm them in writing before you plan your checkout.
The practical effect is simple. If your cashier still asks a customer to type a UPI address on a phone, expect failures, and expect your provider to switch that option off for you.
Side by side: UPI intent, UPI QR and UPI collect
| Factor | UPI intent | UPI QR | UPI collect |
|---|---|---|---|
| Started by | Customer taps pay | Customer scans a code | Merchant sends a request |
| Best device | Mobile | Desktop | Legacy flows and narrow exemptions |
| Customer steps | Tap, review, PIN | Scan, review, PIN | Type address, wait, review, PIN |
| Typing errors | None | None | Common |
| Status in 2026 | Expected on mobile | Expected on desktop | Deprecated for most merchant flows |
| Reference for matching | In the link | In the dynamic code | In the request |
UPI QR on desktop: what to show on each device
A desktop visitor cannot tap a deep link into a phone app, so the replacement for collect is a dynamic QR code. Your checkout generates a code that carries the amount and a unique reference, shows it with a short expiry, and waits for the confirmation callback while the customer scans it with any UPI app. The experience is closer to intent than to collect: scan, review, enter the PIN.
Detect the device and show the right flow. On a phone, offer the intent button first and let the customer pick an app. On a desktop, show the QR with a plain instruction to open any UPI app and scan. Do not show both on one screen without a clear default, because a customer who sees a QR code on their own phone cannot scan it. Keep a visible timer, and let the customer regenerate the code when it expires. Make sure the page keeps listening for the result, because the customer will leave your tab to pay.
Checkout and reconciliation for high risk merchants
High risk merchants feel the flow choice more than others, because a failed or disputed deposit costs more to support. A few design rules help.
- Create a unique order reference for every attempt and carry it through the link or the QR, so the confirmation, the bank reference and your ledger line up.
- Treat the provider callback, not the browser return, as the source of truth, and verify its signature.
- Keep a status query for payments that stay pending, and show the customer a clear pending state instead of a blank page.
- Log which flow, device and UPI app each payment used, so you can see where success rates fall.
- Reconcile daily from a report that ties every payment to your reference, a bank reference and a timestamp.
Intent and QR payments are approved by the payer with a PIN and are not card transactions, so the classic card chargeback does not apply. Disputes and bank reviews still happen, and your provider should tell you in writing how they are handled. If international cards are your current route into India, read why card acquiring fails for high risk merchants in India.
What it means for your UPI payin API integration
For API merchants the change is small in code and large in behaviour. Instead of sending a payment request with a customer address, you ask the provider for an intent link on mobile or a QR payload on desktop. Provider migration guides show the same pattern: remove the address parameter from the request and switch the flow type to intent. Your front end then decides which one to render.
Check three things with your provider before launch: which flows are enabled on your account, what happens on iOS and in in-app browsers, and how expired or abandoned payments are reported. A hosted checkout can take most of this off your hands, since it shows the right flow for the device. On our UPI payment gateway for high risk merchants page we describe the two presentations we use, UPI intent for mobile and UPI QR for desktop, together with IMPS payouts and daily reconciliation. For the wider picture, see how onboarding works and our India page.
Compliance note
Nothing here is a route around local law. India prohibits online money games under the Promotion and Regulation of Online Gaming Act, 2025, and providers cannot process payments for them. The flows in this guide suit businesses that are lawful in India, such as digital goods, subscriptions and brokers that are authorised to serve the customers they onboard. Take your own legal advice for your vertical before you route traffic.
FAQ
What is the difference between UPI intent and UPI collect? Intent is started by the customer, who taps pay and approves in a UPI app that opens with the amount already filled in. Collect is started by the merchant, who sends a request to a UPI address the customer typed in, and the customer must find and approve it.
Is UPI collect still allowed for merchants in 2026? Payment providers such as Razorpay, PayU and Cashfree describe NPCI guidance that deprecated collect for most merchant payments from 28 February 2026, with narrow exemptions. Confirm what applies to your category with your provider in writing.
What replaces UPI collect on desktop? A dynamic UPI QR code that carries the amount and a unique reference. The customer scans it with any UPI app and approves with the PIN.
Does the choice of flow change reconciliation? Not in principle. Every flow should return a signed callback with your reference and a bank reference. What changes is the number of failed and expired payments you have to explain, which falls when intent and QR replace collect.
Working with BestPay24
BestPay24 is a high risk payment gateway for Asia with UPI collection and IMPS payouts in India through one API. There is no setup fee and no prepayment, and sales quotes rates on Telegram. To plan your flows and callbacks, talk to us.
Talk to sales on Telegram: @Bestpay24SalesSupport
Sources: Razorpay, PayU and Cashfree documentation on the UPI collect deprecation; Business Standard and Angel One reporting on NPCI circulars.
BestPay24 collects and pays out in twelve Asian countries for betting, casino, forex and digital merchants. No setup fee.
Message @Bestpay24SalesSupportMore articles
Hosted Payment Page vs Direct API vs Payment Links: Choosing an Integration Model for High Risk Merchants in Asia
A buyer guide comparing the three ways to connect a payment provider, what each means for compliance scope, callbacks, reconciliation and launch speed, and which fits a sportsbook, casino or forex broker.
Rolling Reserve vs Fixed T+1 vs USDT Settlement: Comparing Settlement Terms for High Risk Merchants in Asia
A buyer guide to the three settlement structures high risk operators are offered in Asia, how each affects cash flow and reconciliation, and which questions to put to a provider before you sign.
NAPAS 247 vs Standard Clearing for High Risk Payouts in Vietnam
A decision guide for operators paying out in Vietnam: how instant 24/7 transfers differ from standard interbank clearing since the 500 million VND instant cap and the end of automatic splitting, and how to design payouts around it.
Ready to accept local payments in Asia?
Tell us your vertical, countries and volume. You get an offer with rates and settlement terms, usually the same day.