UPI Architecture: Anatomy of a Real-Time Payment Transaction

UPI Architecture: Anatomy of a Real-Time Payment Transaction

The UPI Transaction Flow

Unified Payments Interface (UPI) transactions are processed through a high-speed relay chain involving seven distinct entities: the payer's app, a sponsor bank, the NPCI central switch, the payee's sponsor bank, the payee's app, and the two banks holding the actual funds. This architecture allows a payment to be completed in two to three seconds, despite the complexity of the underlying handovers.

1. The Application Layer (TPAP)

The user-facing app (e.g., PhonePe, Google Pay, Paytm) is technically a Third-Party Application Provider (TPAP). Its role is limited to gathering user intent, displaying the payee's name, and collecting the encrypted PIN via a secure pad.

Crucially, the TPAP does not hold a banking license, does not touch the user's money, and never sees the plain-text PIN. This layer is the primary site of market competition, with PhonePe and Google Pay currently dominating approximately 80% of the market share.

2. The Sponsor Layer (PSP)

Because TPAPs lack banking licenses, they must partner with a Payment Service Provider (PSP), or sponsor bank. The sponsor bank provides the necessary connection to the payment network and issues the UPI address (the @handle).

Key technical details of the sponsor layer include:

  • Handle Resolution: The suffix of a UPI ID (e.g., @ybl or @okaxis) identifies the sponsor bank, not the app.
  • Resilience: Major apps use multiple sponsor banks to prevent a single bank's outage from taking the entire app offline.
  • Efficiency: If both the payer and payee use the same sponsor bank, the bank can resolve both addresses internally, bypassing the central network directory to save time and small resolution fees.

3. The Central Hub (NPCI Switch)

Every UPI payment converges at a single central switch operated by the National Payments Corporation of India (NPCI). The switch acts as the orchestrator for the entire transaction:

  1. Translation: It routes the request to the recipient's sponsor bank to resolve the UPI handle into a real bank account.
  2. Debit First: The switch instructs the payer's bank to debit the funds. The payer's bank is the only entity capable of decrypting and verifying the user's PIN.
  3. Credit Second: Only after the debit is confirmed does the switch instruct the payee's bank to credit the funds.

This "debit-before-credit" sequence ensures that money always leaves the source before it arrives at the destination.

Performance and Reliability Metrics

Transaction Volume and Scale

UPI is one of the world's largest real-time payment systems. In June 2026, the system processed more than 2,272 crore (22.72 billion) payments. While the total volume is massive, the average load on the NPCI switch is estimated at roughly 700 queries per second (QPS), though this peaks significantly higher during high-traffic periods.

Technical vs. Business Declines

Payment failures in UPI are categorized into two distinct types:

  • Business Declines: Failures caused by user-side issues, such as incorrect PINs, insufficient balances, or exceeded daily limits. These have increased over time.
  • Technical Declines: Failures caused by system outages or server timeouts. These have decreased significantly, falling from over 1% to fewer than 0.25% (1 in 400) as the infrastructure has been hardened.

Error Handling and the "Deemed" State

When a transaction is initiated but the confirmation of credit does not return in time, the payment enters a "deemed" state. In this state, the money has left the payer's account, but the network cannot confirm if it reached the payee.

To resolve these, UPI employs a safety net:

  • Status Polling: The app can query the network for the true status after approximately 90 seconds.
  • Auto-Reconciliation: NPCI runs a background process that queries both banks until a definitive answer is reached. If the credit failed, the debit is automatically reversed.
  • Regulatory Guarantees: Under RBI guidelines, reversals for transfers must happen within one day, with penalties imposed on banks for delays.

Ecosystem Insights

Merchant Dominance

Since 2022, merchant payments have surpassed person-to-person (P2P) payments. This shift has created a concentration of "beneficiary banks." For example, Yes Bank handles a disproportionately high volume of incoming payments because it sponsors the QR codes for many large merchant apps, even if the shopkeeper's actual bank account is elsewhere.

Community Perspectives

While the technical engineering of UPI is widely praised for its scale and inclusivity, some critics raise concerns regarding privacy and autonomy:

"It's a terrible system for privacy and autonomy. It has so many intermediaries, requires phone number and linked to person's identity. It is controlled by the government rather than Visa or Mastercard."

Conversely, others highlight its social impact, noting that it has successfully digitized payments for demographics that were previously excluded from the digital economy.

Sources