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.
Shared ledger vs stablecoins
The shared ledger is widely read as SWIFT's institutional answer to stablecoins and public tokenised-money projects. Both aim at instant, 24/7, programmable value transfer — but the trust model is fundamentally different.
| Dimension | SWIFT shared ledger | Public stablecoins |
|---|---|---|
| Value backing | Tokenised commercial-bank deposits (bank money) | Issuer reserves (cash, T-bills) behind a token |
| Network | Permissioned — authorised bank nodes only | Public, permissionless chains |
| Consensus | QBFT, immediate finality, no forks | PoS / PoW depending on chain |
| Compliance | ISO 20022 data + on-ledger checks, built in | Varies; often bolted on off-chain |
| Participants | Regulated financial institutions | Anyone with a wallet |
| Relationship to existing rails | Coordinates on top of correspondent banking | Aims to route around it |
The strategic bet: banks want the speed and programmability of tokenised money without giving up the regulatory perimeter, settlement finality and counterparty trust of the existing system. By keeping value as tokenised deposits and data in ISO 20022, SWIFT positions the ledger as an upgrade to the incumbent network rather than a competitor to it.
Related reading & tools
Stablecoin Reference · Nasdaq Calypso · Settlement & Clearing · SWIFT / BIC Validator · Blockchain in Payments · x402 Payment Protocol