Lesson 2 · Practitioner · India · 16 min
India Rails: UPI, IMPS, NEFT, RTGS & More
Walk India's retail and wholesale payment stack — UPI, IMPS, NEFT, RTGS, Aadhaar Pay, BBPS, and NACH — with when to use each rail and what ops teams watch.
Objectives
- ▸Choose the right India rail by amount, urgency, and use case
- ▸Explain UPI roles (PSP, remitter/beneficiary banks, NPCI)
- ▸Contrast NACH mandates with card recurring
- ▸Map BBPS and Aadhaar Pay into the broader India stack
Unified Payments Interface (UPI) lets customers pay using a Virtual Payment Address (VPA) or QR without sharing full account numbers. NPCI operates the switch; Payment Service Providers (apps/banks) provide customer UX; remitter and beneficiary banks move the money. UPI supports P2P, P2M, collect requests, autopy (recurring), and lite/offline variants. For merchants, UPI MDR rules and T+ settlement vary by category and regulator policy — always verify current RBI/NPCI circulars when pricing.
- Strengths: instant UX, high trust, QR ubiquity, strong India conversion
- Watchouts: bank downtime, decline codes, collect-request spam/fraud, mandate setup friction for autopy
- Product tip: treat 'UPI success' as near-final for domestic retail, but still reconcile against settlement reports
Pay (intent/QR) is payer-initiated. Collect request asks the payer to approve a debit — powerful for billers, higher abuse risk. Design consent and expiry carefully.