SETTLEMENT — 8 MIN READ

TARGET2 RTGS: Euro Settlement and T2 Modernization

TARGET2 RTGS euro settlement architecture: T2 modernization, CLM liquidity, ISO 20022 adoption, and operating boundaries for euro-area gross settlement.

|

Eurosystem T2 and Central Liquidity Management

The Eurosystem's T2 service provides real-time gross settlement for high-value and commercial euro transfers. Modernized under the T2-T2S consolidation, the platform separates Central Liquidity Management (CLM) from dedicated RTGS settlement components.

This modular separation allows central banks and direct participants to maintain master liquidity accounts while allocating dedicated sub-balances for RTGS operations, TIPS instant clearing, and securities settlement.

Euro Interbank Protocol Connectivity

Direct participants connect to T2 via the Eurosystem Single Market Infrastructure Gateway (ESMIG) using certified SwiftNet or SIA-Colt network links. Standardized server-to-server contracts defined under Global Server Protocol frameworks assist institutions in bridging internal ledgers to European central bank gateways.

Operating resilient T2 processing nodes requires Tier-4 cloud banking server instances featuring active-active European data sovereignty compliance and FIPS 140-3 cryptographic modules.

T2 ISO 20022 Message Flows

T2 processes payments exclusively using ISO 20022 messages including pacs.008, pacs.009, and camt account management records. The platform enforces strict operational cut-off times and automatic liquidity sweeps between RTGS and CLM accounts at the close of business.

FURTHER CLARITY

Frequently asked questions

What is ESMIG in Eurosystem architecture?

ESMIG (Eurosystem Single Market Infrastructure Gateway) is the common technical entry point for direct participants accessing T2, T2S, TIPS, and ECMS.

What is the difference between CLM and RTGS in T2?

CLM manages central bank liquidity, reserve requirements, and standing facilities, whereas RTGS is dedicated to the execution of interbank and customer wire transactions.

PRIMARY SOURCES & STANDARDS

References and citations

DIRECT NODE ACCESS & PROTOCOL ROUTING

Connect directly to production rails or cloud server infrastructure

Depending on your operational scope, route your node integration directly to the designated infrastructure:

PROTOCOL 101.1 & 201.3 RAILS

Global Server Protocol

For Protocol 101.1, Protocol 201.3, IP-to-IP / S2S transaction rails, and financial transfer protocol specifications.

Access globalserverprotocol.com

MT 103 / MT202 & HOSTING

Cloud Global Server

For MT 103 / MT202 wire messaging infrastructure, dedicated cloud financial servers, Tier-4 hosting, and banking node deployment.

Access cloudglobalserver.com
Need institutional capability evaluation or custom sandbox discovery? Submit a Node Access Evaluation Request →

AN INFORMED NEXT STEP

Bring architectural discipline to your payment and ledger systems.

Start with your architecture, integration boundaries and operational requirements.

Discuss your requirements