How UPI Interoperability Works Technically

Interoperability means any UPI app can send money to, or receive money from, any other UPI app, regardless of which bank or PSP issued either account. This is fundamentally different from a closed-loop wallet, where a balance in one company's app could historically only be spent within that same company's ecosystem, unless a separate transfer was made out of it first.

Every UPI transaction, regardless of which app initiates it, passes through NPCI's central switching infrastructure. NPCI acts as the common rail that every bank and every PSP app plugs into, which is what allows a payment initiated on one app to be correctly routed to a completely different bank's account on the receiving end, without the sender or receiver's app needing any direct relationship with each other.

Additional Read: The Future of UPI: Faster, Safer, and Everywhere

1. A merchant's QR code encodes their VPA and, sometimes, a fixed amount, in a standardized format defined by NPCI, not by whichever app generated the code.

2. Your app, regardless of which one it is, reads that standardized code and extracts the recipient's VPA and amount.

3. Your app sends the payment instruction to NPCI's switch, which resolves the VPA to the correct bank account behind it.

4. NPCI routes the debit and credit instructions to the sender's and recipient's respective banks simultaneously, confirming the transaction back to both apps in real time.

This same standardized routing is what lets a pay credit card bill tool accept a payment from any UPI app you happen to have installed, rather than requiring you to use one specific app to settle your card.

NPCI, as a not-for-profit utility rather than a competing commercial player, had every incentive to mandate interoperability from the start, since its mission is a shared national payment rail rather than a proprietary ecosystem competing for lock-in. This is a meaningful contrast to how some private payment networks have historically operated, where interoperability was resisted precisely because it reduced a platform's ability to keep users inside its own walls.

Since the core routing is identical across apps, what actually differs between them is the interface, additional features like UPI Lite or Tap and Pay rollout timing, rewards programs, and how many bank accounts you can link in one place. The fundamental guarantee that any app can pay any other app's VPA never changes, which is exactly why switching your primary UPI app does not require your friends or the merchants you pay to switch along with you.

Interoperability at the app level does not remove the need for both the sender's and the recipient's underlying bank to actually be online and responsive at the moment of the transaction. If a specific bank's servers are undergoing maintenance or facing an outage, a UPI payment involving that bank, on either side, can fail or time out, even though the apps and NPCI's switch itself are working perfectly. This is why an occasional failed transaction is not necessarily a sign of a broken app or a fraud attempt, and simply retrying after a short wait, or checking your bank's own status page, often resolves it without any other action needed.

Card networks like Visa and Mastercard achieved a broadly similar kind of interoperability decades earlier, letting a card issued by one bank be accepted at a terminal deployed by an entirely different acquiring bank. UPI's achievement is arguably more ambitious in one specific respect: it extended this same principle to instant, account-to-account transfers using a human-readable identifier, rather than requiring a physical card and a point-of-sale terminal at all. This is part of why UPI could scale to peer-to-peer payments, a shopkeeper collecting money from a customer with nothing more than a printed QR code, in a way that traditional card interoperability was never really designed to reach.

Stashfin's UPI service is built on this same interoperable NPCI infrastructure, letting you 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, regardless of which app the person or merchant on the other end happens to be using.

• UPI interoperability means any app can send to, or receive from, any other app, regardless of bank or PSP.

• NPCI's central switching infrastructure is what allows this, acting as the common rail every app plugs into.

• A QR code's format is standardized by NPCI, not by the app that generated it, which is why any app can scan any code.

• NPCI's not-for-profit, utility structure made mandating interoperability a natural design choice from the start.

• Switching your primary UPI app changes the interface and extra features, but never the fundamental ability to pay or receive from any other app.