UPI Intent and Collect Flow

Every business accepting digital payments in India has a choice in how customers actually complete a UPI collection, and that choice sits between two flows: UPI Intent and UPI Collect.

One redirects the customer straight into their UPI app. The other sends a request they have to notice and approve manually. Since NPCI made Intent mandatory for mobile transactions from February 2026, this choice has stopped being a technical preference and become a compliance question. Here's everything a merchant or lender needs to know to pick the right flow.

What is UPI and How Does It Work?

UPI (Unified Payments Interface) runs on a central switch operated by the National Payments Corporation of India (NPCI). A standard UPI collection operates across three layers:

• The base layer of public rails, provided by NPCI: handles the routing of payment messages.
• The bank layer: holds customer funds and updates account balances.
• The top layer of payment apps and fintechs: builds the customer-facing application on top of the underlying system.

Every UPI payment flows through these same three layers. What changes based on the flow you choose is how the customer interacts with the top layer, which is exactly where how businesses collect payments is won or lost.

What is UPI Intent Flow?

UPI Intent is a user-initiated push payment. The merchant doesn't send a request to the customer; instead, the customer actively selects and triggers the payment from their own device.

The customer clicks "Pay via UPI," the device shows a list of installed UPI apps, and on selection the app auto-launches with transaction details already filled in. The customer enters their UPI PIN, and the payment is done. For businesses, this means faster completion, fewer drop-offs, and higher transaction success rates.

What is UPI Collect Flow?

UPI Collect is the reverse: a merchant-initiated request that the customer approves manually. Unlike Intent, Collect requires the customer to enter their VPA (Virtual Payment Address) before the request can even be sent.

The process runs like this: the customer enters their VPA, the merchant's system validates it against bank servers and sends a collect request, and the customer then waits for a push notification or SMS before they can open their UPI app and approve the payment.

Every step in that chain, VPA recall, validation latency, notification delivery, app switching, is a place the transaction can stall or fail. A customer who misremembers their VPA, receives the notification late, or simply loses patience during the wait is a lost transaction. This friction is the primary reason NPCI deprecated UPI Collect for most mobile use cases effective 28 February 2026, making UPI Intent the mandatory standard for Android apps and mobile web checkouts. Collect remains available for specific exempted categories, covered below.

UPI Intent vs UPI Collect Flow: Key Differences

Before choosing a flow for your UPI collections, here's how the two compare across the factors that actually matter:

How UPI Intent Flow Works Step by Step

1. Customer action: The customer chooses UPI as their checkout method on the merchant's platform.
2. App launch: The chosen UPI app auto-launches, showing the transaction amount and the merchant's UPI ID, with no manual input required.
3. Payment authorisation: The customer verifies the details and enters their UPI PIN to complete the transaction.
4. Confirmation: Confirmation messages go out to both the customer and the merchant once payment succeeds.

For a business, Intent also means better visibility into the transaction funnel. You can see which UPI app the customer used, while the flow itself reduces the scope for human error across the board.

How UPI Collect Flow Works Step by Step

1. Customer provides VPA: When a customer chooses UPI, the merchant's system prompts them to enter their VPA.
2. Request routed to customer's app: The merchant raises a collect request through its payment service provider, which NPCI routes to the customer's own UPI app, where it appears as a payment request awaiting approval.
3. Payment authorisation: Once the customer enters their PIN and approves within their UPI app, the transaction processes.
4. Confirmation: The merchant's system receives confirmation, and the order or service proceeds.

Use Cases for UPI Intent Flow

Effective from February 2026, NPCI guidelines restrict manual VPA entry for mobile transactions, making Intent compliance mandatory for mobile apps. Beyond compliance, Intent is also simply the better-suited flow for:

• Mobile-first e-commerce platforms and marketplaces
• In-app subscription sign-ups for OTT, SaaS, and membership platforms
• Mobile checkout for quick-commerce and food delivery
• UPI AutoPay mandate registration on mobile

Use Cases for UPI Collect Flow

Despite deprecation for most mobile use cases, UPI Collect remains available for a specific and fairly narrow set of exempted categories:

• Stock market and IPO applications (merchant category codes 6012 and 6211)
• iOS mobile apps and iOS mobile web, where universal link handling is complex
• Executing, modifying, or revoking existing UPI mandates
• PA-CB (Payment Aggregator – Cross Border) merchants handling cross-border and international payments

Desktop is not on that list. It's a common misreading of the change: Collect is being phased out on desktop too, with UPI QR as the designated replacement rather than Intent, since deep-linking to a phone app isn't possible from a desktop browser.

For recurring payment mandate registration specifically, merchants can acquire mandates through Intent for app-native experiences, while QR covers desktop and offline-to-online setups.

Benefits of UPI Intent and Collect Flow for Merchants

Both flows have genuine advantages depending on the situation:

1. Higher conversion on mobile: Per industry benchmarks, Intent flows deliver 10 to 15% higher success rates by eliminating typing errors and notification latency, converting at roughly 92 to 95% by keeping the customer in a continuous action loop, merchant to UPI app and back, rather than sending them off to wait on a notification.
2. Better transaction visibility: Merchant visibility is limited with Collect, but Intent gives merchants complete visibility over the transaction funnel, including which UPI app the customer used.
3. Coverage for exempted cases: Collect remains the working option for IPO and stock market applications, iOS-specific scenarios where universal link handling is complex, executing or modifying existing mandates, and PA-CB cross-border merchants — categories NPCI's mobile deprecation doesn't reach. For desktop and other non-app environments, regulated lenders, enterprise software, and government payment portals should route to UPI QR instead.
4. No app dependency: Collect doesn't require the customer to have a specific UPI app installed or active on the device they're purchasing from.

How RocketPay Enables UPI Collection for Businesses

RocketPay's UPI Autopay infrastructure supports Intent and QR flows for mandate onboarding, giving businesses the flexibility to onboard customers across mobile and offline channels without building the routing logic themselves.

Once a mandate is registered through either flow, RocketPay handles the full collection lifecycle automatically. On the due date, a debit instruction triggers via UPI AutoPay or eNACH e-mandate. If the debit fails, AA-based partial recovery fetches the available balance and recovers what's present. Non-cancellable mandates and intelligent retry are designed to improve credit recovery, and every attempt, status change, and settlement is logged in real time, accessible via dashboard or API webhook.

Conclusion

NPCI's February 2026 guidelines made UPI Intent the mandatory standard for mobile transactions, turning what used to be a technical preference into a compliance requirement. For mobile-first businesses, migrating from Collect to Intent is no longer optional. Desktop traffic moves to UPI QR, while Collect continues to serve a narrower, defined set of exempted use cases — IPO and stock market applications, iOS-specific scenarios, mandate execution and modification, and PA-CB cross-border merchants.