Settlement Risk in Payment Systems: RTGS, DvP and CCIL

Settlement risk in payment systems is the risk that one leg of a transaction is paid or delivered while the other leg fails, leaving the surviving party exposed for the full principal amount rather than just a mark-to-market difference. For a bank treasury or a payment systems officer, this is not an abstract concept — it shows up every time a large-value RTGS transfer, an interbank forex deal, or a government securities trade is waiting for its counterparty to complete its side. Getting the mechanics right is core RFS exam material.

💳 What Is Settlement Risk in Payment Systems

Settlement risk arises in the gap between when a party performs its obligation and when it receives the corresponding value. In a payment or securities transaction, one side may pay cash or deliver securities before confirming that the counterparty has done the same. If the counterparty defaults, is suspended, or simply fails to deliver in that window, the paying party has lost the entire principal — not merely the replacement cost of the trade. This is what separates settlement risk from ordinary counterparty credit risk, where exposure is usually limited to a smaller replacement-cost figure.

The risk is highest in cross-border and cross-currency transactions because time zones widen the exposure window. A bank in Mumbai may pay out rupees in the morning against a US dollar leg that only settles hours later in New York, during which the counterparty bank could fail. This exact scenario — a bank paying one leg and never receiving the other — is historically named after the 1974 collapse of Bankhaus Herstatt in Germany, and it remains the textbook reference point for settlement risk in international finance.

Indian payment infrastructure is built specifically to shrink this exposure window: gross settlement systems, delivery-versus-payment mechanisms, and a central counterparty for money and forex markets. The rest of this article works through how each of these mechanisms functions and where the residual risk still sits.

🏦 RTGS, NEFT and the Shift to Real-Time Finality

India's Real Time Gross Settlement (RTGS) system settles each transaction individually and irrevocably, in real time, on a gross basis rather than netting transactions across the day. Once a payment is processed through RTGS, it is final — there is no unwinding, which removes principal settlement risk between the paying and receiving banks for that transaction. RTGS has operated on a 24x7 basis in India for large-value payments, which further reduces the window during which counterparty failure could disrupt a pending settlement.

NEFT, by contrast, settles in half-hourly batches on a deferred net basis. Because NEFT nets multiple transactions before settlement, individual banks carry a small net position exposure to each other rather than gross principal exposure on every transaction — a different but still relevant risk profile that treasury and risk teams must monitor through their market risk framework.

Banks assess settlement exposure alongside broader counterparty limits set out in their credit risk management framework, since a settlement failure by a counterparty bank ultimately behaves like a credit event even though it originates from an operational and timing mismatch rather than a change in the counterparty's underlying financial position.

💡 Exam Tip: If a question asks why RTGS eliminates settlement risk but NEFT does not eliminate it entirely, the answer hinges on gross-and-final versus net-and-deferred settlement — not on transaction size or system speed.

🌐 Foreign Exchange Settlement Risk and CLS

Foreign exchange deals are especially prone to settlement risk because the two currency legs are typically cleared through separate national payment systems in different time zones. A bank can pay away the currency it owes hours before it is due to receive the currency it is owed, creating a window of full principal exposure to its counterparty — precisely the pattern that gave Herstatt risk its name.

CLS (Continuous Linked Settlement) Bank was created internationally to address this by settling both legs of an FX trade simultaneously on a payment-versus-payment (PvP) basis, so neither leg completes unless the other does too. Indian banks dealing in eligible currency pairs rely on CLS membership or correspondent arrangements to shrink this exposure, while FEDAI and RBI guidance set out prudent limits on daylight and overnight settlement exposure that a treasury desk can carry to any single counterparty bank.

The same underlying discipline — matching two obligations so that neither completes without the other — appears again in equity and derivatives markets. Clearing members managing risk in stock broking operations use margining and pay-in/pay-out cycles for exactly this reason, and a broker or bank that repeatedly fails to settle on time also accumulates reputational risk in financial services with counterparties and regulators alike, since settlement discipline is one of the most visible signals of institutional soundness in the market.

⚖️ CCIL, DvP and Central Counterparty Guarantees

The Clearing Corporation of India Ltd (CCIL) acts as the central counterparty (CCP) for government securities, the money market, and a large share of the interbank forex market in India. Through a process called novation, CCIL interposes itself between the original buyer and seller, becoming the buyer to every seller and the seller to every buyer. This means a bank no longer carries direct settlement exposure to its original trading counterparty — it carries exposure to CCIL instead, which is backed by a settlement guarantee fund funded by member contributions.

Securities settlement in this system runs on a Delivery versus Payment (DvP) basis: securities and funds move simultaneously, so a bank cannot deliver securities without receiving payment, or pay funds without receiving securities. This structural link is what removes principal settlement risk from government securities trading, and it directly underpins the pricing and behaviour covered in portfolio credit risk for a bank's investment book.

RBI's oversight of CCIL and other financial market infrastructures is guided by internationally accepted standards for systemically important payment and settlement systems, published on rbi.org.in, which set capital, risk-management and default-fund expectations for any entity performing this central counterparty role.

⚠️ Common Mistake: Candidates often assume CCIL "guarantees" a trade completes at the originally agreed price. It guarantees settlement completion, not the price — market risk on the position itself remains with the bank throughout.

📜 Regulatory Framework — the PSS Act and RBI Oversight

The Payment and Settlement Systems Act, 2007 (PSS Act) gives RBI the statutory authority to authorise, regulate and supervise every payment system operating in India, including RTGS, NEFT, CCIL's settlement systems, and card and prepaid instrument networks. Under this framework, RBI designates certain systems as Systemically Important Payment Systems (SIPS) — RTGS and CCIL's settlement operations fall into this category — and subjects them to closer oversight because their failure could disrupt the wider financial system.

RBI's oversight increasingly draws on the CPMI-IOSCO Principles for Financial Market Infrastructures (PFMI), which set global expectations on credit risk, liquidity risk, settlement finality and default management for systems like CCIL. This is the same regulatory instinct that runs through RBI's other conduct and fair-practice rules for lenders, such as the penal charges on loan accounts framework — transparent, predictable rules that reduce the chance of a routine financial obligation turning into a dispute or a loss event.

Banks and clearing members are also expected to hold adequate liquidity buffers to meet settlement obligations even under stress, a discipline that mirrors the capital cushions insurers must hold, as covered in the article on solvency margin for insurers — different sectors, same underlying idea of pre-funding against a shock rather than reacting to it after the fact.

🛡️ Settlement Risk Mitigation Techniques for Banks

Banks manage settlement risk through a combination of structural and operational controls. Bilateral and multilateral netting reduces the number and size of gross obligations that must actually settle. Settlement limits per counterparty cap the maximum exposure a treasury desk can build up on any single day, and these limits are reviewed as part of the same counterparty assessment used for measurement of credit risk.

Real-time monitoring of nostro account balances and pending settlements lets treasury staff spot a stuck or delayed leg before it becomes a loss. Where possible, banks route eligible trades through a central counterparty like CCIL specifically to convert bilateral settlement risk into exposure to a well-capitalised, guarantee-fund-backed entity instead.

Liquidity planning matters just as much as counterparty selection — a bank that has not provisioned enough intraday liquidity can itself become the source of a settlement delay, even without any counterparty default. Desks track short-term funding costs against RBI rates when sizing these buffers, since the cost of holding idle settlement liquidity has to be weighed against the cost of a missed or delayed payment.

📌 Remember: Settlement risk mitigation is layered — netting reduces the amount at risk, DvP/PvP removes the timing gap, and a central counterparty guarantee fund absorbs what is left if a member still defaults.

🧠 Practice MCQs: Settlement Risk in Payment Systems

Want chapter-wise mock tests with 100+ MCQs? Start practising free →

Settlement risk in payment systems sits at the intersection of operations, credit and market risk, which is exactly why RFS examiners test it from multiple angles. Reinforce the RTGS, DvP and CCIL mechanics with timed practice on iibf.store's CAIIB course to make sure these concepts hold up under exam pressure. For more on the wider syllabus, browse the Risk in Financial Services tag hub on the blog.