How UPI Works: NPCI, PSPs, and the UPI Architecture Explained

What Is UPI?

UPI is a real-time payment system built and operated by NPCI that allows two bank accounts to exchange money directly, in seconds, using a simple identifier - a UPI ID or Virtual Payment Address (VPA) - instead of a full account number and IFSC code. Since its launch, UPI has become the default way most people in India move money between banks, pay merchants, and pay each other.

Unlike a closed card network, UPI is a switch that any participating bank, or licensed non-bank participant working through a bank, can plug into under a common set of rules. That openness is a large part of why UPI adoption spread so quickly across banks, FinTechs, and merchants of every size.

The Key Players in a UPI Transaction

A UPI payment feels instantaneous to the user, but several distinct participants are involved behind the scenes:

• NPCI - the switch and umbrella operator that owns the UPI system, sets the rules participants must follow, and routes messages between the payer's and payee's PSPs.
• The payer's PSP (Payment Service Provider) - the bank behind the payer's UPI app, responsible for processing the debit instruction on the payer's behalf.
• The payee's PSP - the equivalent participant on the receiving side, responsible for presenting the credit instruction for the payee's account.
• The remitter bank - the bank where the payer's account actually sits.
• The beneficiary bank - the bank where the payee's account sits.
• UPI apps and TPAPs (Third-Party App Providers) - the customer-facing apps that capture the payment instruction and pass it to their PSP for processing.

A UPI Transaction, Step by Step

Stripped down to its mechanics, a single UPI payment moves through a consistent sequence:

1. VPA/UPI ID resolution. The payer enters the payee's VPA (or scans a QR code), and the app resolves which PSP and bank sit behind that identifier.
2. Request to the payer's PSP. The payer authenticates with their MPIN, and the signed request is passed to the payer's PSP.
3. NPCI switch. The payer's PSP forwards the request to NPCI, which validates it and routes it onward to the payee's PSP.
4. Beneficiary PSP and bank. The payee's PSP receives the request and coordinates with the beneficiary bank to accept the incoming credit.
5. Debit and credit at the respective banks. The remitter bank debits the payer's account and the beneficiary bank credits the payee's account, coordinated through NPCI's messaging so both legs complete together.
6. Confirmation back to both apps. NPCI relays the success or failure response back through both PSPs to the payer's and payee's apps, typically within seconds.

Key Concepts to Know

• VPA / UPI ID. A portable identifier, such as name@bank, that maps to an underlying bank account so users never need to share an account number or IFSC code.
• MPIN. A personal PIN set by the user with their bank that authorizes a UPI debit - a separate credential from an ATM PIN.
• Collect vs. Pay. "Pay" is a push transaction the payer initiates; "Collect" is a pull request the payee sends, which the payer must separately approve before any money moves. Both run on the same underlying network.
• UPI AutoPay. A mandate-based flow for recurring payments - subscriptions, SIPs, EMIs - where the payer authorizes a standing instruction once, and subsequent debits within the agreed limits happen automatically without a fresh manual approval each time.

Why UPI Matters for Businesses Building Payment Products

For businesses accepting or building on top of UPI, three qualities usually matter most: near-instant movement of funds and confirmation between banks, materially lower per-transaction cost compared with card processing, and reach into a base of bank accounts and users that is close to universal across India. That combination has made UPI acceptance close to a baseline expectation at checkout, and made "UPI-first" design - built around VPAs, QR codes, and intent/collect flows rather than card fields - a common pattern for new payment products.