Interactive: The UPI Intent Flow (And Where It Breaks)

How to Use This

Click any node in the flow diagram that has a small indicator dot. The success path will show the failure branch, and a PM Insights panel will open explaining what happened technically and what a PM should build to handle it.

Why This Flow Matters for PMs

The UPI Intent flow is the most executed software flow in India. More transactions run through this nine-hop sequence every day than through most other payment systems globally.

Understanding it at the node level — not just the happy path — is the difference between a PM who ships payment features and a PM who ships payment features that users trust when things go wrong.

The six failure modes in this simulator are not edge cases. Each represents a class of production incidents that any Fintech PM will encounter. The PM response to each is not theoretical — it is the spec that needs to be written.

The Most Important Failure Mode

The network drop post-debit is the failure mode that causes the most user harm and the most support tickets. Money leaves the user's account. The merchant never gets confirmation. The user sees "Payment Failed."

This is not a payment failure. It is a reconciliation failure. The PM who understands the difference ships a reconciliation job — not a better error message.

What This Doesn't Cover

This simulator covers the Intent flow only. The Collect flow was deprecated by NPCI in February 2026. AutoPay (UPI mandates) has a separate flow with different failure modes. BBPS payments run on a different rail entirely.

The Intent flow is the right starting point because it is the dominant flow for peer-to-merchant payments — which is where most Fintech PM work lives.