Inside a UPI Payment: Seven Entities in Two Seconds

When a user scans a QR code and enters a PIN, the experience ends with a green tick in about two seconds. Behind that instant lie seven distinct actors that each perform a security‑critical step.

1. The third‑party app – PhonePe, Google Pay, Paytm, etc. – is merely a UI. It collects the payment intent, displays the payee name, and captures the MPIN in a trusted library that never exposes the PIN to the app itself. The app holds no licence and never touches money; it passes a signed request to its sponsor bank【1】.

2. The sponsor (PSP) – the bank that issued the UPI address (the @handle). It validates the request, resolves the handle to an actual account, and signs the message. Most top‑ranked apps are attached to multiple PSPs to avoid single‑point outages and to gain “on‑us” efficiency when payer and payee share the same sponsor, saving the ₹0.01 resolution fee【7】.

3. The NPCI switch – the single, nation‑wide hub that routes the request to the payee’s sponsor. It first debits the payer’s bank, confirms the PIN, and only then instructs the beneficiary bank to credit the account. The debit‑then‑credit order guarantees that money always leaves before it arrives【2】.

4. The payer’s bank – decrypts the MPIN, checks balance and limits, and executes the debit. If any business rule fails (wrong PIN, insufficient funds, daily limit), the transaction is rejected at this point and the app shows a clear error【3】.

5. The payee’s bank – receives the credit instruction, posts the amount to the merchant or individual account, and acknowledges the switch. When the payee is a merchant, the bank that sponsored the QR code (often Yes Bank) receives the credit first, then settles with the shop’s own account【6】.

6. The payee’s PSP – forwards the success message back to the payee’s app, which displays the “money received” buzz.

7. The payer’s PSP – informs the payer’s app that the transaction succeeded, triggering the green tick.

Business implications

• Cost structure – Each hop adds marginal processing fees (e.g., the ₹0.01 resolution fee when the same PSP handles both sides). Enterprises can reduce fees by consolidating sponsor banks for high‑volume merchants.
• Reliability – Technical declines (network or switch failures) have fallen below 0.25 % of transactions, thanks to hardened bank systems and NPCI hardening【10】. Business declines now dominate, reflecting user‑level limits rather than rail failures.
• Risk management – The split‑role architecture isolates credential handling to the trusted MPIN library and the payer’s bank, limiting exposure if a third‑party app is compromised. NPCI’s auto‑reconciliation for “deemed” transactions ensures that any debit without a confirmed credit is reversed within a day, with RBI‑mandated penalties for delays【4】【9】.
• Organisational change – Enterprises integrating UPI must treat the PSP as a critical partner, not just a gateway. Multi‑bank sponsorship mitigates outage risk, while real‑time monitoring of decline categories helps optimise user experience and limit settings.

Overall, the two‑second UPI experience hides a rigorously sequenced flow that balances speed, security, and cost. Understanding each participant’s responsibility lets enterprises design more resilient payment strategies and forecast the true cost of scaling on India’s largest real‑time payment rail, which processed 2,272 crore transactions in June 2026 alone【5】.