Back
Technical Guide to UPI Intent vs Collect Flow
Every UPI checkout you have ever completed used either an Intent flow or a Collect flow, even if you never noticed the distinction. Both end in the same place, money moving from your account to someone else's, but the technical sequence that gets there, and who initiates which step, is meaningfully different between the two.
Intent Flow: The App-to-App Handoff
Intent flow is what happens when tapping a UPI payment option on a merchant's app or website directly opens your own UPI app, pre-filled with the amount and recipient VPA, ready for you to confirm with your PIN. Technically, the merchant's app sends an Intent, a structured request recognized by your phone's operating system, that hands off directly to whichever UPI app you have installed, without you needing to manually copy or scan anything.
Collect Flow: The Reverse Request
Collect flow works in the opposite direction. Instead of your app opening automatically, you enter your own VPA into the merchant's checkout page, and a payment request is then pushed to your UPI app asking you to approve an outgoing payment. You authorize it the same way, with your PIN, but the request originates from the merchant's side reaching out to you, rather than your device opening its own app directly.
| Aspect | Intent Flow | Collect Flow |
|---|---|---|
| Who initiates the technical request | Your own device, via an app-to-app handoff | The merchant, sending a request to your VPA |
| Typical use case | Mobile checkout, tapping a UPI button in an app | Desktop checkout, entering your UPI ID on a website |
| Speed | Generally faster, since it skips manual VPA entry | Slightly slower, since it waits for a pushed request to arrive |
| Common risk | Low, since you control the entire flow on your own device | Higher, since scammers disguise fraudulent Collect requests as refunds or prizes |
Additional Read: What is My UPI? Finding and Managing Your Virtual Payment Address
Why Collect Flow Is the More Commonly Abused Pattern
Because Collect flow involves a request arriving on your phone asking for approval, it is easier for a scammer to disguise a fraudulent request as something legitimate, a refund, a prize, or a payment someone supposedly owes you. Intent flow does not have this weakness in the same way, since you are always the one initiating the handoff from your own device rather than approving an incoming request.
A credit card bill payment tool typically uses Intent flow when initiated from within its own app, and Collect flow when you enter your VPA on a desktop checkout page instead, but the underlying security principle is the same either way: you should only ever be approving a payment you expect to send.
How to Tell Which Flow You Are Using
If tapping a payment button on your phone automatically opens your UPI app with details pre-filled, that is Intent flow. If you are instead typing your own UPI ID into a form on a website or a desktop checkout and then waiting for a notification on your phone, that is Collect flow. Knowing which one you are in the middle of helps you correctly judge whether a notification you receive makes sense in context.
Why Both Flows Still Matter
Intent flow works beautifully on mobile but has no equivalent on a desktop browser without a phone's operating system involved. Collect flow fills that gap, letting desktop checkout still complete through UPI. Both are necessary parts of UPI's overall design, each solving a different practical constraint of where the payment is actually being initiated from.
What This Means for Developers Building Checkout
A merchant building a checkout experience typically needs to support both flows to cover the full range of devices their customers use, an Intent-based deep link for mobile web and in-app purchases, and a Collect-based VPA input field for desktop. Most payment gateway integrations handle this automatically behind a single UPI checkout option, detecting the customer's device and routing to the appropriate flow without the merchant needing to build two entirely separate payment paths from scratch.
Stashfin's UPI service supports both flows depending on how you choose to pay: scan and pay to any mobile number or UPI ID, or move money to your own bank account, directly through bank-to-bank UPI rails, with the same clear recipient confirmation regardless of which flow initiated the request.
Key Takeaways
Intent flow hands off directly from a merchant's app to your own UPI app, pre-filled and ready for your PIN.
Collect flow works in reverse: you enter your VPA on the merchant's side, and a request is then pushed to your app for approval.
Intent flow is generally used on mobile checkout, while Collect flow fills the gap for desktop checkout.
Collect flow is the more commonly abused pattern by scammers, since a request arriving on your phone can be disguised as a refund or prize.
Both flows exist to solve different practical constraints of where a UPI payment is actually being initiated from.
