India made mobile numbers portable.
It made payments interoperable.
It made digital identity reusable.
It made consent-based financial data sharing possible.
But one of the most basic parts of financial life is still not portable: the bank account number.
A customer can move from one telecom operator to another without changing their mobile number. But if the same customer wants to move from one bank to another, the account number changes. That creates friction across salary credits, EMIs, SIPs, insurance premiums, utility bills, business payments, vendor records, tax records and personal financial relationships.
This is not a small inconvenience.
It is account lock-in.
Bank account number portability should become India’s next major banking reform.
The principle is simple:
A customer should be able to change banks without rebuilding their financial identity from zero.
That is why the idea of bank account portability is so powerful.
This is not just a banking convenience.
It is a shift in power.
Earlier, the bank effectively owned the relationship because the account was difficult to move.
In a portability-led world, the customer owns the financial identity, and the bank becomes a service provider that must earn the relationship continuously.
That is democratization.
The Customer Owns the Account Identity
The deeper reform is philosophical.
Today, the account number belongs to the bank’s infrastructure.
In a portability model, the account number or account identity should belong more to the customer.
The bank should be the service provider.
The customer should be able to say:
“This is my financial identity. I can choose which bank services it.”
That is the same logic that made mobile number portability powerful.
A mobile number became the customer’s communication identity, not the telecom company’s permanent lock-in tool.
Banking needs the same shift.
Why India Needs This Reform Now
India’s financial system is ready for a deeper portability conversation because the country has already built major digital rails.
UPI made payment movement interoperable.
NPCI operates important retail payment systems such as UPI, RuPay, NACH, FASTag and Bharat BillPay.
Account Aggregator created consent-based data sharing.
Digital KYC improved customer onboarding.
NACH and UPI Autopay enabled recurring payments.
The missing layer is portability of the customer’s banking identity.
If India can make money movement interoperable, it should now make account relationships more portable.
True Account Number Portability
In this model, the customer keeps the same account number even after moving from Bank A to Bank B.
Example:
Customer has account number 1234567890 with Bank A.
The customer ports to Bank B.
The same account number 1234567890 now points to Bank B.
Bank A no longer controls that active account relationship.
This is the cleanest customer experience.
But it is technically the hardest model.
Why?
Because account numbers are deeply linked to bank-specific systems:
- branch codes
- product codes
- customer IDs
- core banking ledgers
- audit trails
- reconciliation systems
- fraud monitoring
- regulatory reporting
- payment routing
- internal risk systems
- tax and compliance records
A bank account number today is not designed like a mobile number.
It is often built into the bank’s internal architecture.
So true account number portability would require a major restructuring of banking infrastructure.
| Dimension | Current Banking Model | Portability-led Banking Model |
|---|---|---|
| Customer relationship | Bank-controlled | Customer-controlled |
| Switching banks | High friction | Low friction |
| Deposits | Sticky due to inertia | Contestable due to choice |
| Retention driver | Account dependency | Experience, trust, value |
| Bank advantage | Operational lock-in | Service quality and digital capability |
| Customer power | Limited | Stronger |
| Competition | Slower | Continuous |
| Layer | What Needs to Move or Be Remapped | Why It Matters |
|---|---|---|
| Account identity | Account number / account reference | Customer should not have to change financial identity everywhere |
| Deposits | Balance, holds, liens, pending credits/debits | Prevents loss, mismatch, or duplicate posting |
| Mandates | EMI, SIP, insurance premium, utility bills, NACH, UPI AutoPay | Avoids failed payments and penalties |
| Salary credits | Employer payroll mapping | Prevents salary disruption |
| Government benefits | DBT and subsidy routing | Critical for financial inclusion |
| KYC / CKYC | Customer identity and compliance records | Avoids repeated paperwork |
| Risk history | AML flags, suspicious activity, fraud signals | Prevents misuse of switching |
| Transaction history | Historical banking behaviour | Useful for lending, service, and dispute resolution |
| Reconciliation | Old bank vs new bank ledger matching | Proves that the switch was financially correct |
| Architecture Component | Role |
|---|---|
| PaSS / portability switch | Coordinates the switching journey between old bank, new bank, payment systems, mandate systems, and settlement rails |
| Account registry | Works like DNS for bank accounts; resolves which bank currently serves the account |
| Old bank | Validates customer, freezes account, shares balance, shares mandates, closes/dormants old mapping |
| New bank | Creates internal account, receives settlement, activates customer, imports mandates |
| Settlement layer | Moves funds and confirms value transfer |
| Event streaming layer | Notifies all systems in real time |
| Reconciliation engine | Confirms that money, mandates, and mappings are correct |
How to do Bank Readiness for Bank Account Portability
| Capability | Portability-ready Bank | At-risk Bank |
|---|---|---|
| Core banking system | Agile, modular, API-ready | Legacy, batch-heavy, hard-coded |
| Ledger | Real-time / near real-time | End-of-day processing |
| Mandate management | Centralized and automated | Fragmented across systems |
| Reconciliation | Continuous | Manual or T+1 |
| Customer data | Clean golden record | Duplicated / inconsistent |
| APIs | Secure and standardized | Limited or unstable |
| Fraud monitoring | Real-time and portable | Static and siloed |
| Customer service | Proactive and digital | Reactive and branch/call-center dependent |
| Switching response | Growth opportunity | Logistical nightmare |