Payments Academy
India layered payment system PAYMENT OPERATIONS STARTED LIVE 01 India layered payment system - runs one of the most layered domestic ACTIVE 02 Below it - sits the National Payments Corporation of India QUEUED 03 Instant small-value payment need - street vendor who needs ten rupees QUEUED 04 RTGS - transfers where settlement must be immediate QUEUED 05 UPI - day limits that change with the use case. QUEUED India runs one of the most layered domestic payment systems in the world Step 1 of 5 India layered payment system STARTED India layered payment system runs one of the most layered domestic ACTIVE Below it sits the National Payments Corporation of QUEUED Instant small-value payment need street vendor who needs ten rupees instantly QUEUED RTGS transfers where settlement must be QUEUED UPI day limits that change with the use case. QUEUED India runs one of the most layered domestic payment systems in the world
Below it PAYMENT OPERATIONS IN PROGRESS LIVE 01 India layered payment system - runs one of the most layered domestic DONE 02 Below it - sits the National Payments Corporation of India ACTIVE 03 Instant small-value payment need - street vendor who needs ten rupees QUEUED 04 RTGS - transfers where settlement must be immediate QUEUED 05 UPI - day limits that change with the use case. QUEUED Below it sits the National Payments Corporation of India, known as NPCI, which operates UPI, IMPS, NACH, RuPay and the National Financial Switch. Step 2 of 5 Below it IN PROGRESS India layered payment system runs one of the most layered domestic DONE Below it sits the National Payments Corporation of ACTIVE Instant small-value payment need street vendor who needs ten rupees instantly QUEUED RTGS transfers where settlement must be QUEUED UPI day limits that change with the use case. QUEUED Below it sits the National Payments Corporation of India, known as NPCI, which operates UPI, IMPS, NACH, RuPay and the National Financial Switch.
Instant small-value payment need PAYMENT OPERATIONS IN PROGRESS LIVE 01 India layered payment system - runs one of the most layered domestic DONE 02 Below it - sits the National Payments Corporation of India DONE 03 Instant small-value payment need - street vendor who needs ten rupees ACTIVE 04 RTGS - transfers where settlement must be immediate QUEUED 05 UPI - day limits that change with the use case. QUEUED A street vendor who needs ten rupees instantly has a very different need from a company that must settle a five crore rupee supplier payment with legal finality before the end of the day. Step 3 of 5 Instant small-value payment need IN PROGRESS India layered payment system runs one of the most layered domestic DONE Below it sits the National Payments Corporation of DONE Instant small-value payment need street vendor who needs ten rupees instantly ACTIVE RTGS transfers where settlement must be QUEUED UPI day limits that change with the use case. QUEUED A street vendor who needs ten rupees instantly has a very different need from a company that must settle a five crore rupee supplier payment with legal finality before the end of the day.
RTGS: built for high value PAYMENT OPERATIONS IN PROGRESS LIVE 01 India layered payment system - runs one of the most layered domestic DONE 02 Below it - sits the National Payments Corporation of India DONE 03 Instant small-value payment need - street vendor who needs ten rupees DONE 04 RTGS - transfers where settlement must be immediate ACTIVE 05 UPI - day limits that change with the use case. QUEUED RTGS is built for high value transfers where settlement must be immediate and final. Step 4 of 5 RTGS: built for high value IN PROGRESS India layered payment system runs one of the most layered domestic DONE Below it sits the National Payments Corporation of DONE Instant small-value payment need street vendor who needs ten rupees instantly DONE RTGS transfers where settlement must be ACTIVE UPI day limits that change with the use case. QUEUED RTGS is built for high value transfers where settlement must be immediate and final.
UPI has per transaction PAYMENT OPERATIONS COMPLETE LIVE 01 India layered payment system - runs one of the most layered domestic DONE 02 Below it - sits the National Payments Corporation of India DONE 03 Instant small-value payment need - street vendor who needs ten rupees DONE 04 RTGS - transfers where settlement must be immediate DONE 05 UPI - day limits that change with the use case. ACTIVE UPI has per transaction and per day limits that change with the use case. Step 5 of 5 UPI has per transaction COMPLETE India layered payment system runs one of the most layered domestic DONE Below it sits the National Payments Corporation of DONE Instant small-value payment need street vendor who needs ten rupees instantly DONE RTGS transfers where settlement must be DONE UPI day limits that change with the use case. ACTIVE UPI has per transaction and per day limits that change with the use case.

Key points of this lesson, in order.

0:00 / 2:17 Step 1 of 5

The Indian payments landscape at a glance

India: UPI, IMPS, NEFT, RTGS, Lesson 1 of 8, Narration 2:17, D05 Domestic payment systems

ReconciliationSettlementFinality

What you will learn

Your objective. By the end of this lesson, you will be able to explain indian payments landscape at a glance. India runs one of the most layered domestic payment systems in the world, and a business analyst who works on Indian payments needs to understand how the layers fit together rather than treating each rail as a separate.

Why it matters. India runs one of the most layered domestic payment systems in the world, and a business analyst who works on Indian payments needs to understand how the layers fit together rather than treating each rail as a separate product.

Chapter objective: Learner compares UPI, IMPS, NEFT, and RTGS in India, explaining limits, settlement timing, operating hours, and use cases, and selects the right rail for a given payment need. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.

Key learning points

  • India layered payment system
  • Below it
  • Instant small-value payment need
  • RTGS: built for high value
  • UPI has per transaction

Key terms

Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

Finality: The point at which a payment settlement becomes irrevocable and unconditional, so it cannot be reversed by the payer or the system.

Payment flow diagram showing The Indian payments landscape at a glance.

Practise this lesson

Exercise

Decide which settlement model fits the scenario in this lesson and explain why.

Use the settlement models, the liquidity trade-off and the finality rules in this lesson.

  1. What to do. Name the model, state when settlement becomes final, and explain what happens if the sending bank does not have enough liquidity.

Correct result. Real time gross settlement settles each payment individually in central bank money with immediate finality, but it needs liquidity for every payment. Deferred net settlement nets payments and settles the net position, which needs less liquidity but leaves settlement risk until the net settles.

Why. Settlement is where money actually moves. The model decides the risk, the liquidity need, and when the payment is truly final.

Check your understanding

Practice question

A customer in India wants to send INR 50,000 instantly to another bank account at any hour. Which system fits best?

Takeaway and next step

What to remember

When a business requirement says instant, the analyst must ask whether instant means seconds, minutes or same day, because the answer decides the rail, the customer promise and the reconciliation design.

Follow a payment through every stage, from instruction to beneficiary credit, and note where it can stop.

Open the Payment Lifecycle Simulator →

Builds on "Operational Dashboards, KPIs, Resilience and Disaster Recovery".

Transcript and full text

Show transcript

India runs one of the most layered domestic payment systems in the world, and a business analyst who works on Indian payments needs to understand how the layers fit together rather than treating each rail as a separate product. At the top sits the Reserve Bank of India, which owns and operates RTGS and NEFT, sets the rules for the system, and licenses the operators of the retail rails. Below it sits the National Payments Corporation of India, known as NPCI, which operates UPI, IMPS, NACH, RuPay and the National Financial Switch. Commercial banks connect to these systems, and on top of the banks sit payment apps, payment service providers and fintech companies that give customers a simple screen to tap. The reason India has so many rails is that no single system can serve every use case well. A street vendor who needs ten rupees instantly has a very different need from a company that must settle a five crore rupee supplier payment with legal finality before the end of the day. UPI is built for instant, low value, high volume retail payments. IMPS is built for instant account to account transfers at any hour. NEFT is built for reliable, lower cost transfers that can wait for a batch. RTGS is built for high value transfers where settlement must be immediate and final. NACH handles bulk recurring debits and credits such as salaries, EMIs and utility bills. A good analyst maps the business requirement to the right rail instead of forcing every payment through one channel. Each rail also carries its own limits, timings, costs and failure modes, and these details matter in real projects. UPI has per transaction and per day limits that change with the use case. IMPS works around the clock but charges more than NEFT for some values. NEFT has no upper limit in theory but settles in half hourly batches, so it is not instant. RTGS has a minimum value of two lakh rupees and settles continuously around the clock. When a business requirement says instant, the analyst must ask whether instant means seconds, minutes or same day, because the answer decides the rail, the customer promise and the reconciliation design. Take a worked example with real numbers. A customer in Bengaluru needs to pay a street vendor INR 200 for lunch, pay a supplier INR 4,50,000 for goods, pay an employee INR 85,000 as salary, and pay a property seller INR 75,00,000 as a deposit. The lunch is paid by UPI, because it is instant, free for the customer, and works from a phone. The supplier is paid by IMPS, because it is instant and allows up to INR 5,00,000 per transaction. The salary is paid by NEFT as a batch file, because it is one of many salaries and does not need to settle in seconds. The property deposit is paid by RTGS, because it is above the INR 2,00,000 minimum and needs immediate final settlement in central bank money. Four payments, four rails, and the choice is driven by value, urgency and finality, not by habit. Failure and recovery: a UPI payment fails when the customer enters the wrong PIN three times and the account is locked, and the recovery is to reset the PIN through the bank, not to retry the payment. An IMPS payment fails when the beneficiary IFSC is wrong, and the money is returned to the sender, usually within a few hours, because IMPS validates the account before debiting. The customer message for each failure must name the rail, the reason and the next step, because a generic payment failed message leaves the customer with no way to recover. A NEFT payment fails when the batch file has a wrong account number, and the payment is returned the next day with a reason code, and the sender must correct it and resend. An RTGS payment fails when the sending bank does not have enough funds in its settlement account at the Reserve Bank, and the payment is queued, and the bank must fund the account or the payment is rejected at the cut-off. Each rail fails differently, and the customer message must explain the specific failure, not just that the payment failed. For a business analyst, product owner or subject matter expert, the test is to name, for every payment product in India, the rail, the operator, the settlement model, the value range, the timing, and the failure mode. UPI, IMPS and NACH are operated by NPCI, and NEFT and RTGS are operated by the Reserve Bank of India. UPI and IMPS settle instantly, NEFT settles in half-hourly batches, and RTGS settles individually in real time in central bank money. A requirement that names the wrong operator will be built against the wrong specification, and a requirement that does not state the value range will allow a payment that the rail cannot carry. Source: Reserve Bank of India, Payment and Settlement Systems; NPCI, UPI, IMPS and NACH product specifications. Last reviewed 7 November 2026.

India runs one of the most layered domestic payment systems in the world, and a business analyst who works on Indian payments needs to understand how the layers fit together rather than treating each rail as a separate product. At the top sits the Reserve Bank of India, which owns and operates RTGS and NEFT, sets the rules for the system, and licenses the operators of the retail rails. Below it sits the National Payments Corporation of India, known as NPCI, which operates UPI, IMPS, NACH, RuPay and the National Financial Switch. Commercial banks connect to these systems, and on top of the banks sit payment apps, payment service providers and fintech companies that give customers a simple screen to tap.

The reason India has so many rails is that no single system can serve every use case well. A street vendor who needs ten rupees instantly has a very different need from a company that must settle a five crore rupee supplier payment with legal finality before the end of the day. UPI is built for instant, low value, high volume retail payments. IMPS is built for instant account to account transfers at any hour. NEFT is built for reliable, lower cost transfers that can wait for a batch. RTGS is built for high value transfers where settlement must be immediate and final. NACH handles bulk recurring debits and credits such as salaries, EMIs and utility bills. A good analyst maps the business requirement to the right rail instead of forcing every payment through one channel.

Each rail also carries its own limits, timings, costs and failure modes, and these details matter in real projects. UPI has per transaction and per day limits that change with the use case. IMPS works around the clock but charges more than NEFT for some values. NEFT has no upper limit in theory but settles in half hourly batches, so it is not instant. RTGS has a minimum value of two lakh rupees and settles continuously around the clock. When a business requirement says instant, the analyst must ask whether instant means seconds, minutes or same day, because the answer decides the rail, the customer promise and the reconciliation design.

Take a worked example with real numbers. A customer in Bengaluru needs to pay a street vendor INR 200 for lunch, pay a supplier INR 4,50,000 for goods, pay an employee INR 85,000 as salary, and pay a property seller INR 75,00,000 as a deposit. The lunch is paid by UPI, because it is instant, free for the customer, and works from a phone. The supplier is paid by IMPS, because it is instant and allows up to INR 5,00,000 per transaction. The salary is paid by NEFT as a batch file, because it is one of many salaries and does not need to settle in seconds. The property deposit is paid by RTGS, because it is above the INR 2,00,000 minimum and needs immediate final settlement in central bank money. Four payments, four rails, and the choice is driven by value, urgency and finality, not by habit.

Failure and recovery: a UPI payment fails when the customer enters the wrong PIN three times and the account is locked, and the recovery is to reset the PIN through the bank, not to retry the payment. An IMPS payment fails when the beneficiary IFSC is wrong, and the money is returned to the sender, usually within a few hours, because IMPS validates the account before debiting. The customer message for each failure must name the rail, the reason and the next step, because a generic payment failed message leaves the customer with no way to recover.

A NEFT payment fails when the batch file has a wrong account number, and the payment is returned the next day with a reason code, and the sender must correct it and resend. An RTGS payment fails when the sending bank does not have enough funds in its settlement account at the Reserve Bank, and the payment is queued, and the bank must fund the account or the payment is rejected at the cut-off. Each rail fails differently, and the customer message must explain the specific failure, not just that the payment failed.

For a business analyst, product owner or subject matter expert, the test is to name, for every payment product in India, the rail, the operator, the settlement model, the value range, the timing, and the failure mode. UPI, IMPS and NACH are operated by NPCI, and NEFT and RTGS are operated by the Reserve Bank of India. UPI and IMPS settle instantly, NEFT settles in half-hourly batches, and RTGS settles individually in real time in central bank money. A requirement that names the wrong operator will be built against the wrong specification, and a requirement that does not state the value range will allow a payment that the rail cannot carry. Source: Reserve Bank of India, Payment and Settlement Systems; NPCI, UPI, IMPS and NACH product specifications. Last reviewed 7 November 2026.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.