How Money Moves Between Banks

Quick answer

When you send ₹50,000 from an HDFC Bank account to a friend's ICICI Bank account, no "digital packet of money" travels across the internet.

Commercial banks do not maintain direct accounts with each other, nor can one bank simply alter the ledger of a competitor. If HDFC Bank could unilaterally write numbers into ICICI Bank's internal database, modern banking would collapse under counterparty risk and fraud.

Instead, all interbank transfers rely on a common, trusted central ledger:

1. Every scheduled commercial bank holds a reserve current account at the central bank—the Reserve Bank of India (RBI). This central banking system is called e-Kuber.
2. When you initiate an interbank payment, HDFC Bank debits ₹50,000 from your retail account on its internal Core Banking Solution (CBS).
3. HDFC Bank then sends a cryptographically signed electronic message through a secure interbank telecommunication network (SFMS) to the Reserve Bank of India.
4. The RBI's central engine, e-Kuber, executes an atomic transfer across the banks' reserve accounts: it debits HDFC Bank's reserve account by ₹50,000 and credits ICICI Bank's reserve account by ₹50,000.
5. Once this central settlement is recorded on the RBI's books, ICICI Bank receives confirmation and credits ₹50,000 to your friend's retail account.

The "money" did not move across phone lines or fiber cables. What actually happened was an atomic change of ownership in central bank reserves, followed by matching ledger updates inside each commercial bank's private database.

---

The simple mental model: The Sovereign Ledger at the Center

Commercial banks operate like separate islands. Each island has its own private record book of who owns what. But none of the islands trust each other's private paper:

The only money that can extinguish a debt between two commercial banks is central bank money—the ultimate sovereign asset in the domestic economy.

---

What money in a bank actually is

To understand how money moves between institutions, you must first discard the intuitive idea that a bank account is a digital vault storing physical rupee notes.

Commercial Bank Money vs. Central Bank Money

Economists divide modern money into distinct tiers:

1. Commercial Bank Money (Inside Money): The balance in your savings or current account is not physical cash. Legally, it is an unsecured liability owed to you by that specific commercial bank. When your banking app displays ₹1,00,000, it means the bank has an IOU promising to pay you ₹1,00,000 on demand.
2. Central Bank Money (Base Money / M0): This consists of physical paper currency printed by the sovereign and digital reserve balances held by licensed commercial banks in their settlement accounts at the Reserve Bank of India.

When you ask Bank A to pay Bank B, Bank B will not accept Bank A's internal IOU. Bank B does not want a claim against a competing private company that could face insolvency or liquidity strain. Bank B demands payment in sovereign central bank reserves, which carry zero credit risk because they are issued by the monetary authority itself. (To understand how money originated as debt ledgers rather than barter, and why sovereign fiat value is ultimately anchored in the state's power to levy taxes, see Why Humans Invented Money and Why States and Taxation Exist.)

All interbank payment systems—whether RTGS, NEFT, IMPS, or UPI—are simply specialized engineering protocols designed to transfer central bank reserves in e-Kuber and instruct the receiving bank to issue a matching commercial deposit to the beneficiary.

---

The two core interbank settlement rails: RTGS vs. NEFT

In India, interbank fund transfers flow through two primary clearing mechanisms operated directly by the Reserve Bank of India:

Architectural Property	RTGS (Real Time Gross Settlement)	NEFT (National Electronic Funds Transfer)
Settlement Mode	Gross (Order-by-order, individual)	Deferred Net Settlement (DNS) (Batched)
Settlement Frequency	Continuous, real-time	48 half-hourly batches across 24 hours
Minimum Value	₹2,00,000 (customer); ₹1 (interbank)	₹1 (no minimum or maximum)
Processing Latency	Instant (typically under 30 seconds)	End of the 30-minute batch window
Liquidity Usage	High (Requires full reserve value per transaction)	Very Low (Nets offsetting obligations across all banks)
System Operator	Reserve Bank of India	Reserve Bank of India
Statutory Backing	Section 23, PSSA 2007	Section 23, PSSA 2007

---

Rail 1: Real Time Gross Settlement (RTGS)

RTGS is the heavy artillery of the financial system. Designed for high-value wholesale, commercial, and Treasury transactions, it operates on two literal design principles:

1. "Real Time"

Transactions do not wait in a queue or accumulate in a batch. The moment the sending bank's payment message arrives at e-Kuber, the RBI processor evaluates the instruction immediately.

2. "Gross"

Every transfer is settled individually on a one-for-one basis. If Company A transfers ₹10 crore from SBI to HDFC, and two seconds later Company B transfers ₹9.9 crore from HDFC to SBI, RTGS does not subtract the two numbers. It executes two separate, independent transfers of sovereign reserves:

• Transfer 1: Debit SBI ₹10 crore → Credit HDFC ₹10 crore.
• Transfer 2: Debit HDFC ₹9.9 crore → Credit SBI ₹9.9 crore.

The Mechanics of an RTGS Transaction

Sending Bank CBS (HDFC)
      │
      ▼ Formats SFMS pacs.008 customer credit message
SFMS Interbank Gateway (IFTAS)
      │
      ▼ Encrypted PKI routing over INFINET optical network
RBI e-Kuber RTGS Engine
      │
      ├─ 1. Signature Verification: Validates digital certificate of sending bank
      ├─ 2. Reserve Sufficiency Check: Does HDFC have >= transfer amount in RBI account?
      │      ├─ IF YES: Atomically debits HDFC reserve & credits ICICI reserve
      │      └─ IF NO: Shunts message to priority queue (or triggers Intra-Day Liquidity)
      ▼
Irrevocable Settlement Record Written in e-Kuber Ledger
      │
      ▼ Dispatches pacs.002 settlement confirmation
Beneficiary Bank CBS (ICICI)
      │
      ▼ Straight-Through Processing (STP) matches IFSC & account
Beneficiary Account Credited

Because RTGS consumes enormous amounts of central bank reserves throughout the business day, the RBI provides banks with an Intra-Day Liquidity (IDL) facility—an automated, collateralized repo mechanism allowing banks to pledge government securities (SLR gilts) during the day to generate instant intraday liquidity, unwinding the position before the market closes.

Since December 14, 2020, RTGS operates 24x7x365.

---

Rail 2: National Electronic Funds Transfer (NEFT)

For consumer and retail transfers where amounts range from ₹1 to several lakhs, settling every transaction individually in real time would exhaust bank liquidity and place excessive load on central bank reserve ledgers.

To solve this, the RBI designed NEFT, which operates on Deferred Net Settlement (DNS).

How Deferred Net Settlement (DNS) Works

Instead of settling payments continuously as they arrive, NEFT groups transactions into 48 discrete half-hourly batches throughout the 24-hour day:

• Batch 1: 00:00 to 00:30
• Batch 2: 00:30 to 01:00
• ...
• Batch 48: 23:30 to 24:00

During a single 30-minute window, hundreds of thousands of people across India initiate transfers between dozens of banks. The NEFT clearing centre does not move any money during this window; it simply records the instructions:

During Batch Window (e.g. 14:00 to 14:30):
  - Customer 1: Axis -> SBI  ₹5,000
  - Customer 2: SBI  -> Axis  ₹3,000
  - Customer 3: HDFC -> Axis  ₹2,000
  - Customer 4: Axis -> HDFC  ₹6,000

The Multilateral Netting Calculation

At the end of the 30-minute window, the NEFT engine halts ingestion for that batch and runs a mathematical netting algorithm across all participating institutions:

Using the simple four-transaction example above, look at the staggering efficiency gained through netting:

Bank	Total Outbound Debits	Total Inward Credits	Multilateral Net Position
Axis Bank	₹11,000	₹5,000	-₹6,000 (Net Debtor)
State Bank of India (SBI)	₹3,000	₹5,000	+₹2,000 (Net Creditor)
HDFC Bank	₹2,000	₹6,000	+₹4,000 (Net Creditor)
Total Gross Volume	₹16,000	₹16,000	Net Settlement: ₹6,000

To settle ₹16,000 worth of customer payments across three banks, the banking system does not need to execute four transactions. It executes a single Multilateral Net Settlement Batch (MNSB):

• Axis Bank's RBI reserve account is debited by ₹6,000.
• SBI's RBI reserve account is credited by ₹2,000.
• HDFC Bank's RBI reserve account is credited by ₹4,000.

The sum of all net debits strictly equals the sum of all net credits:

Once this single atomic accounting entry is booked in e-Kuber, the NEFT engine releases individual inward transaction files to the respective beneficiary banks. Under RBI regulations, receiving banks must credit customer accounts via Straight-Through Processing (STP) within 2 hours of settlement (in practice, modern automated systems do so within 2 to 5 minutes).

---

The messaging backbone: SFMS and the IFSC Code

Payment instructions cannot travel over the public internet via ordinary email or generic webhooks. They require an encrypted, non-repudiable telecommunications backbone.

In India, that backbone is the Structured Financial Messaging System (SFMS), designed by the Institute for Development and Research in Banking Technology (IDRBT) and operated by IFTAS (a subsidiary of the RBI).

SFMS is the domestic equivalent of the international SWIFT network. It connects all bank data centres over INFINET (Indian Financial Network)—a secure, closed optical fiber and satellite network isolated from the public internet.

[Bank Branch / Internet Banking]
              │
              ▼ Customer inputs IFSC (e.g., HDFC0000123)
[Bank Gateway: SFMS Originating Node]
              │
              ├─ 1. Formats standardized XML message (ISO 20022 format)
              ├─ 2. Attaches asymmetric digital signature (PKI smart card / HSM)
              ▼
[INFINET Secure Backbone (IFTAS)]
              │
              ▼ Verified by RBI Central Hub
[e-Kuber / NEFT Clearing Centre]

Deconstructing the IFSC Code

Every electronic transfer in India requires an IFSC (Indian Financial System Code). The IFSC is an 11-character alphanumeric code that functions as an IP address for banking:

1. First 4 characters: Identifies the bank (HDFC, SBIN, ICIC, PUNB).
2. 5th character: Always 0, reserved by the RBI for future architectural routing needs.
3. Last 6 characters: Identifies the exact physical branch or centralized clearing hub within that bank's network.

When you enter an IFSC, the sending bank's software uses an RBI-maintained routing table to identify the destination bank's SFMS gateway address on the INFINET network.

---

The Legal Anchor: Settlement Finality

What happens if a bank sends ₹500 crore over RTGS or NEFT, and twenty minutes later that bank is declared bankrupt or placed under a moratorium by the government? Can liquidators unwind the transactions and demand the money back from recipient banks?

In an unregulated system, the fear of retroactively cancelled transactions (unwinding) would cause the entire banking sector to seize up.

To prevent systemic panic, India enacted The Payment and Settlement Systems Act, 2007 (PSSA 2007).

Section 23: Absolute Irrevocability

Under Section 23 of the PSSA 2007, once an entry is posted in an authorized payment system (such as RTGS or NEFT in e-Kuber):

• The settlement is final and irrevocable.
• The netting calculation of a DNS batch is legally protected.
• No court order, insolvency proceeding, liquidator, or bankruptcy law can unwind, reverse, or challenge a settled transaction.

Once central bank money moves in e-Kuber, the legal debt between the banks is permanently extinguished. This legal certainty is the invisible bedrock that allows millions of businesses to accept electronic transfers as equivalent to physical cash.

---

How UPI and IMPS connect to the central bank

You might wonder where modern retail payment rails like UPI and IMPS fit into this picture.

Neither UPI nor IMPS is a replacement for the central bank's settlement ledger. Rather, they are high-speed retail transaction switches operated by the National Payments Corporation of India (NPCI). At the messaging layer, UPI uses digitally signed XML over HTTPS payloads (ReqPay/RespPay) between Payment Service Provider (PSP) banks and the NPCI UPI switch, while IMPS (which also serves as the underlying core banking settlement rail for UPI account-to-account debits and credits) communicates with member banks' Core Banking Systems using ISO 8583 financial messages:

Customer Level (Real-time Retail)
  User taps "Pay" on PhonePe/Google Pay
        │
        ▼ Signed XML API (UPI) / ISO 8583 CBS link (IMPS)
  NPCI UPI / IMPS Central Switch
        │
        ▼ Immediate retail debit/credit on Bank CBS
  Customer accounts update in seconds
  (Bank A owes Bank B cumulative funds, backed by SGF collateral)
        │
        ▼ [Multiple Daily Deferred Net Settlement Cycles]
Institutional Level (Central Bank Sovereign Settlement)
  NPCI calculates Multilateral Net Settlement Batches (MNSB)
        │
        ▼ Submits MNSB file directly to RBI
  RBI e-Kuber RTGS Engine
        │
        ▼ Atomic transfer of central bank reserves
  Sovereign interbank accounts settled

When you buy groceries using UPI, the retail banks credit and debit customer accounts in seconds based on mutual trust in the NPCI rulebook and collateral posted in NPCI's Settlement Guarantee Fund (SGF). Because customer accounts are credited before central bank reserves move, member banks carry brief intraday credit exposure to one another—mitigated by collateral caps and multiple daily Multilateral Net Settlement Batch (MNSB) cycles (10+ settlement cycles per day across 24×7 RTGS).

At each scheduled cut-off window, NPCI tallies the total net obligations across all participating banks and submits an MNSB file directly into the RBI's RTGS system inside e-Kuber. The central bank debits and credits the banks' reserve accounts, extinguishing the accumulated retail debts in sovereign money.

---

Global Equivalents and Cross-Border Nostro/Vostro Settlement

While India's interbank engine runs on e-Kuber, RTGS, NEFT, and SFMS, every major monetary jurisdiction operates an identical two-tier central bank architecture:

Jurisdiction	Central Bank Reserve Ledger	Real-Time Gross Settlement (RTGS)	Deferred Batch / Fast Retail Rail
India (INR)	Reserve Bank of India (e-Kuber)	RTGS (≥ ₹2 Lakh, 24×7×365)	NEFT (48 half-hour batches) & UPI / IMPS
United States (USD)	Federal Reserve (Master Account)	Fedwire Funds Service	ACH (FedACH / EPN) & FedNow
Eurozone (EUR)	European Central Bank (Eurosystem)	T2 (TARGET2)	SEPA Credit Transfer & TIPS
United Kingdom (GBP)	Bank of England (RTGS)	CHAPS	BACS (3-day net cycle) & Faster Payments (FPS)

What Happens When Money Crosses International Borders?

An Indian bank cannot hold an account at the US Federal Reserve, and an American bank does not hold an account inside RBI's e-Kuber. When money moves across borders (for example, from Mumbai to New York), banks use Correspondent Banking over the SWIFT ISO 20022 messaging network:

1. Nostro and Vostro Accounts: State Bank of India maintains a foreign-currency commercial account in US Dollars at a partner correspondent bank in New York (e.g., JPMorgan Chase). To SBI, this is its Nostro ("our money on your books") account; to JPMorgan, it is a Vostro ("your money on our books") account.
2. SWIFT Messaging (pacs.008): Just like SFMS domestically, SWIFT does not move money—it transmits cryptographically authenticated ISO 20022 payment instructions between international banks.
3. Domestic Finality on Fedwire: Once JPMorgan receives SBI's SWIFT instruction, it debits SBI's USD Nostro balance and settles the final leg to the American recipient's bank over the US Federal Reserve's Fedwire RTGS ledger.

---

Why this matters

The next time you transfer money between banks, remember the invisible architecture operating beneath your screen:

• You are not moving files over the internet; you are directing an entry in the sovereign balance sheet of the central bank (such as the Reserve Bank of India's e-Kuber or the Federal Reserve's Fedwire).
• RTGS provides continuous, gross, instant finality for systemic high-value commerce.
• NEFT and ACH optimize national liquidity by mathematically netting millions of payments into periodic atomic batches.
• SFMS and SWIFT guarantee that every instruction is cryptographically signed (using Public-Key Cryptography) and shielded from tampering.

To understand why bank transfers used to take days of physical paper sorting and why transfers once froze entirely after 7 PM, read the companion explainer on Why Bank Transfers Used to Take Hours (and Days). You can also see how retail mobile and card payments layer on top of this infrastructure in How UPI Works and How Credit Cards Work.