SWIFT's Blockchain-Based Shared Ledger
SWIFT is extending its network into a digital environment with a blockchain-based shared ledger: a permissioned, EVM-compatible orchestration layer that records and validates interbank payment commitments and lets banks move value 24/7 using tokenised deposits — bank money, not crypto. Announced at Sibos 2025 and moved to live pilot in July 2026 with 17 global banks. This guide covers the architecture, the flow, current status, and how it differs from stablecoins.
What is the SWIFT shared ledger?
The shared ledger is a new layer inside SWIFT's infrastructure that combines distributed-ledger technology with SWIFT's existing global reach, security and standards. Instead of each bank confirming a cross-border payment through a chain of messages and manual back-office checks, the ledger acts as a shared digital orchestration layer that records and validates interbank payment commitments in one place, and executes them using tokenised deposits as the representation of value.
Crucially, it does not replace correspondent banking or SWIFT messaging — it coordinates on top of them, adding an always-on rail for institutions that want instant, 24/7 movement of value while keeping the same compliance, credit and risk data flowing through ISO 20022 messages.
24/7 settlement
Move funds overnight, on weekends and outside banking hours — not bound to the business-day windows of legacy RTGS and correspondent rails.
Tokenised deposits
Value is represented as tokenised commercial-bank deposits issued by the participating banks — regulated liabilities, not a new crypto token.
Smart-contract rules
Payment initiation, compliance gates and counterparty confirmation are encoded as smart contracts instead of manual back-office confirmations.
One-line summary: it is SWIFT's answer to stablecoins and tokenised money — built on bank deposits and existing standards rather than on public-chain crypto — designed to bring instant, programmable, 24/7 settlement to the network's ~11,000+ institutions without discarding the compliance rails they already run.