Learning objectives
By the end you can:
- State the three questions that decode any payment rail, whose balance sheet expands (grows on both sides), shrinks, or merely reshuffles at each hop; whether settlement is gross (transaction-by-transaction) or net (batched and offset); and the exact moment settlement becomes final and irrevocable, and apply all three, from primary-source mechanics, to RTGS/Fedwire, ACH/NACH, UPI, card payments, correspondent banking, and CLS.
- Trace a domestic high-value payment through RTGS (India) or Fedwire (US) hop by hop, naming the balance-sheet entry at the payer's bank, at the central bank, and at the payee's bank, and explain why gross, real-time settlement in central-bank money gives immediate, irrevocable finality, at the cost of intraday liquidity.
- Trace a batch/mandate payment through ACH (US) and NACH (India), explaining why deferred net settlement is provisional (reversible via returns) until the batch itself settles, and compute which same-day settlement window a given submission time falls into.
- Explain UPI's two-layer architecture: an NPCI-operated real-time messaging/switching layer that gives the customer instant finality-*feeling*, sitting on top of a periodic, netted interbank settlement layer whose real finality occurs only when member banks' accounts at the RBI move, and compute a multilateral net settlement across several banks from a matrix of gross flows.
- Trace a card payment through the four-party model (cardholder, merchant, issuer, acquirer, network), separating the real-time authorization message from the batched clearing/settlement that follows days later, decompose the merchant discount rate into interchange, scheme fee, and acquirer margin, and contrast a credit-card swipe (which creates a new loan, expanding the issuer's balance sheet) against a debit-card swipe (which merely draws down an existing deposit).
- Explain why SWIFT is a messenger, not a mover, trace a cross-border payment through a correspondent-banking chain, define nostro and vostro precisely as the same account named from two sides, and compute the balance-sheet expansion at each correspondent, the all-in cost of a remittance (explicit fee plus the FX-spread cost hidden in the exchange rate), and the netting efficiency of a correspondent relationship handling many customers' flows.
- Explain CLS's payment-versus-payment (PvP) mechanism, state precisely what Herstatt risk is and how PvP eliminates it, and compute a multilateral net funding requirement across several settlement members and currencies from their gross matched trades.
- Define settlement finality per the BIS's Principles for Financial Market Infrastructures, rank every rail in this module by how and when it reaches finality, and explain (with a Python-computed intraday-liquidity trajectory) why gross settlement's safety is bought with a real, sometimes collateral-backed, intraday liquidity cost that net settlement avoids at the price of a settlement-risk window.
- (Productivity objective: R10 duality.) Use an AI tool to accelerate drafting a settlement-netting function or summarizing an operating-rules circular, while treating every stated threshold, hour, or fee as unverified until traced to the actual BIS/Fedwire/RBI/NPCI document, because this region's precise, perishable operational facts are exactly where a fluent, confidently wrong AI answer does the most damage.
The duality, stated once (R10). Objectives 1–8 are the understanding gate, the mastery check rewards correctly tracing balance sheets and computing netting arithmetic, not knowing which button moves money. Objective 9 is the productivity payoff you carry forward: AI can usefully draft a netting function's scaffolding or summarize a dense operating-rules PDF, but in a region built entirely from jurisdiction-specific operational facts that change by regulatory circular, every one of those facts is unverified until you have opened the actual BIS, Federal Reserve, RBI, or NPCI document yourself.