Glossary

RTGS (Real-Time Gross Settlement)

RTGS is a payment system that settles high-value transactions individually and instantly in central bank money without netting.

Key Takeaways

  • RTGS systems settle each payment individually (gross) and immediately (real-time) in central bank reserves, providing instant payment finality with zero counterparty risk.
  • Every major economy operates an RTGS system: Fedwire (US), T2 (Eurozone), CHAPS (UK), and BOJ-NET (Japan) collectively process trillions of dollars daily, forming the backbone of global settlement infrastructure.
  • Bitcoin's on-chain settlement functions as a form of digital gross settlement: each transaction settles individually without netting, though with probabilistic rather than legal finality.

What Is RTGS?

Real-Time Gross Settlement (RTGS) is a funds transfer system in which payments between banks are settled individually and immediately on a continuous basis throughout the processing day. "Real-time" means each transaction is processed the moment it is submitted, with no batching or waiting periods. "Gross" means each payment is settled on its own, one-to-one, without being bundled or offset against other transactions.

RTGS systems are operated by central banks and settle in central bank money: the safest form of money in any economy. When Bank A sends a payment to Bank B through an RTGS system, the central bank debits Bank A's reserve account and credits Bank B's reserve account in a single, atomic operation. Once settled, the payment is final and irrevocable.

The concept emerged in response to systemic risks exposed by the failure of Germany's Bankhaus Herstatt in 1974. Herstatt was shut down after receiving Deutsche Mark payments but before sending corresponding US dollar payments to counterparties in New York, creating cascading losses across the banking system. This event demonstrated the danger of settlement timing gaps and catalyzed global adoption of RTGS. By 1985, only 3 central banks operated RTGS systems. Today, over 120 countries have implemented them.

How It Works

RTGS settlement follows a straightforward process, though the infrastructure behind it is highly resilient and complex:

  1. The sending bank submits a payment instruction to the RTGS system, specifying the amount, the receiving bank, and the beneficiary details
  2. The RTGS system validates the instruction and checks whether the sending bank has sufficient reserves in its central bank account
  3. If funds are available, the system simultaneously debits the sender's reserve account and credits the receiver's reserve account
  4. The payment is marked as final: it cannot be reversed, recalled, or unwound, even if the sending bank subsequently becomes insolvent
  5. The receiving bank is notified and can credit the beneficiary's account with immediate certainty

This entire process completes in seconds. The key distinction from other payment systems is that no netting occurs. In a deferred net settlement (DNS) system, if Bank A owes Bank B $10 million and Bank B owes Bank A $7 million, only the $3 million net difference settles. In RTGS, both payments settle independently at their full gross amounts.

Liquidity Management

Because each payment settles at full value without netting, RTGS systems require participating banks to hold substantially more central bank reserves than DNS systems. A bank processing $50 billion in daily payments cannot rely on incoming payments to offset outgoing ones: each outgoing payment must be funded individually.

To address this, modern RTGS systems incorporate liquidity-saving mechanisms (LSMs). These features queue non-urgent payments and periodically attempt to settle them in offsetting pairs or groups, reducing the aggregate liquidity needed while preserving real-time finality for urgent transactions. Both Fedwire and T2 include LSM capabilities alongside their core gross settlement engines.

Major RTGS Systems

Each major economy operates its own RTGS system, tailored to its currency and regulatory framework:

SystemCountryCurrencyOperatorOperating Hours
FedwireUnited StatesUSDFederal Reserve22 hrs/day, Mon-Fri
T2 (TARGET2)EurozoneEUREurosystem (ECB)07:00-18:00 CET, Mon-Fri
CHAPSUnited KingdomGBPBank of England06:00-18:00, Mon-Fri
BOJ-NETJapanJPYBank of JapanBusiness hours, Mon-Fri
RTGSIndiaINRReserve Bank of India24/7/365

Fedwire (United States)

Fedwire is the oldest continuously operating RTGS system, launched in 1970. It connects over 9,000 financial institutions and processes approximately 840,000 transactions per day, averaging $4.5 trillion in daily value. The average Fedwire transaction is approximately $5.4 million, though there is no formal minimum or maximum: the system handles everything from $1 transfers to transactions exceeding $9 billion.

In 2024, Fedwire processed over 209 million transactions totaling $1.13 quadrillion. The Federal Reserve has announced plans to expand Fedwire operating hours to include Sundays and holidays, targeted for no earlier than 2028.

T2 (Eurozone)

The Eurosystem replaced TARGET2 with the renewed T2 platform on March 20, 2023, consolidating RTGS and securities settlement onto a single technical infrastructure. T2 processes approximately 420,000 transactions daily across over 1,000 participating institutions in 20+ European countries. In 2024, total T2 transaction value reached EUR 463.7 trillion. The ECB is consulting on extending T2 operating hours toward 24/7 availability.

CHAPS (United Kingdom)

CHAPS has operated since 1984, with the Bank of England serving as the RTGS infrastructure operator. In the year ending February 2025, CHAPS processed 53.3 million transactions worth GBP 93.9 trillion. The Bank of England launched a renewed RTGS platform (RT2) in April 2025, with plans to extend the settlement window to begin at 01:30 (from 06:00) by September 2027, and eventual 22-hour, 6-day operation targeted for 2029 onward.

RTGS vs. Deferred Net Settlement

Understanding RTGS requires contrasting it with deferred net settlement (DNS), the alternative approach used by systems like ACH and many retail clearing networks:

FeatureRTGSDeferred Net Settlement
Settlement timingContinuous, real-timeBatched at scheduled intervals
Settlement basisGross (each transaction individually)Net (only differences between credits and debits)
FinalityImmediate and irrevocableOnly at designated settlement times
Counterparty riskNone (settled in central bank money)Accumulates between settlement cycles
Liquidity requirementHigher (full amount per transaction)Lower (netting reduces totals)
Typical useHigh-value, time-critical transfersHigh-volume, lower-value retail payments

The critical advantage of RTGS is the elimination of settlement risk. In a DNS system, if a bank fails between the time a payment is submitted and the end-of-day netting cycle, all queued payments involving that bank may need to be unwound, potentially causing cascading failures. RTGS removes this risk entirely: each payment is final the moment it settles.

The tradeoff is liquidity efficiency. DNS systems require far less liquidity because netting dramatically reduces the total value that must actually move. For example, CHIPS, the US private-sector payment system, typically nets down 95% of its gross payment flows, meaning only 5% of the total value actually needs to be funded.

Why RTGS Matters

RTGS systems serve as the foundation of the global financial system. Nearly all high-value and time-critical payments ultimately settle through RTGS:

  • Interbank lending and money market operations settle via RTGS to eliminate overnight counterparty exposure
  • Securities transactions require RTGS for delivery-versus-payment, ensuring that securities and cash transfer simultaneously
  • Cross-border payments routed through correspondent banks rely on domestic RTGS systems for final settlement in each currency
  • Corporate treasury operations use RTGS for large vendor payments, payroll funding, and cash concentration where same-day certainty is required
  • Government disbursements, tax payments, and central bank operations all flow through RTGS infrastructure

The global trend is toward extending RTGS availability. India's RTGS system already operates 24/7/365, and both the Federal Reserve and the Bank of England have published roadmaps for expanding to near-continuous operation. The ISO 20022 messaging standard, which Fedwire adopted in July 2025, is further modernizing RTGS systems by enabling richer, more structured payment data.

For more on how real-time settlement is evolving across payment systems, see the real-time payments global landscape deep dive.

Bitcoin as Digital Gross Settlement

Bitcoin's on-chain settlement shares a fundamental characteristic with RTGS: each transaction settles individually without netting or batching. When a Bitcoin transaction is confirmed in a block, the transfer of value is complete and independent of every other transaction in that block.

FeatureTraditional RTGSBitcoin On-Chain
Settlement typeGross (individual)Gross (individual)
OperatorCentral bankDecentralized network
Finality typeDeterministic (legal, immediate)Probabilistic (grows with confirmations)
Time to finalitySeconds~60 minutes (6 confirmations)
Operating hoursLimited (expanding toward 24/7)24/7/365
Counterparty riskNone (central bank guarantees)None (peer-to-peer, no intermediary)
AccessRestricted to licensed institutionsPermissionless (anyone can transact)

The key distinction is the nature of finality. RTGS provides deterministic finality backed by law: once settled, a payment is legally irrevocable. Bitcoin provides probabilistic finality backed by computational difficulty: the cost of reversing a transaction grows exponentially with each block confirmation, becoming computationally infeasible after six confirmations.

The parallel extends to layered architecture. Just as retail payment systems batch and net transactions before final RTGS settlement, Bitcoin's Layer 2 networks process payments off-chain with periodic on-chain settlement. The Lightning Network and Spark function as high-speed payment layers that ultimately settle to Bitcoin's base layer: a permissionless, 24/7 gross settlement system.

Risks and Considerations

Liquidity Demands

Gross settlement without netting requires participants to maintain substantially larger central bank reserve balances than DNS systems demand. Banks must either pre-fund their accounts or access intraday credit from the central bank (typically against collateral). This liquidity cost is the primary tradeoff for the safety RTGS provides.

Operational Risk

Because RTGS systems are single points of settlement for an entire economy, any outage has severe consequences. Central banks invest heavily in redundancy, with geographically separated data centers and failover capabilities. The Bank of England's renewed RT2 platform, for example, was designed specifically to support extended operating hours with enhanced resilience.

Limited Operating Hours

Most RTGS systems still operate only on business days during limited windows, creating gaps where instant settlement is unavailable. Payments submitted outside operating hours queue until the next settlement window, introducing delay that contrasts with the always-on expectations of modern commerce. The industry-wide push toward 24/7 operations, led by India's example and followed by planned expansions at the Federal Reserve and Bank of England, aims to close these gaps.

Access Restrictions

RTGS participation is generally limited to banks and licensed financial institutions that hold accounts at the central bank. Non-bank payment providers, fintechs, and individuals cannot access RTGS directly. They must route through a participating bank, adding cost and intermediation. This contrasts sharply with permissionless systems like Bitcoin, where anyone can settle transactions on the base layer without institutional gatekeeping.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.