Swift, the messaging backbone connecting 11,500+ financial institutions across 200 markets, completed its first live tokenized deposit transactions in September 2026. First Abu Dhabi Bank and Citibank settled a USD payment on September 2. Eight days later, DBS, OCBC, and UOB executed Singapore's ...
"With our new ledger capability, we're extending the trust and stability of established finance into the frontiers of digital money." — Thierry Chilosi, Chief Business Officer, Swift
Swift, the messaging backbone connecting 11,500+ financial institutions across 200 markets, completed its first live tokenized deposit transactions in September 2026. First Abu Dhabi Bank and Citibank settled a USD payment on September 2. Eight days later, DBS, OCBC, and UOB executed Singapore's first interbank SGD transactions on the same ledger. Both sets of transactions used bank-issued tokenized deposits — not stablecoins, not a CBDC — moving across a permissioned blockchain built on Hyperledger Besu.
The shared ledger, announced as ready for initial use on July 9, 2026, now has 17 banks from six continents preparing to pilot live operations. Built in nine months, it represents Swift's answer to a question the industry has debated for a decade: how to bring 24/7 settlement to cross-border banking without abandoning the regulated deposit system. Swift moves the equivalent of world GDP every two to three days. The ledger does not replace that infrastructure. It adds a programmable layer on top of it.
The design choice matters. Tokenized deposits remain bank liabilities, covered by existing supervision and deposit insurance frameworks. Stablecoins, at $307 billion market capitalization in early 2026, do not carry those protections. Swift chose the instrument that preserves the regulatory trust model while adding speed and programmability — a decision consistent with the preference of its 11,500-member network.
The Swift shared ledger is a permissioned blockchain built on Hyperledger Besu, an Ethereum Virtual Machine (EVM)-compatible client developed under the Linux Foundation's Decentralized Trust project. It is not a public blockchain. There is no native cryptocurrency. Access is restricted to authorized financial institutions.
The system operates as an orchestration layer, not a standalone payments platform. Its functions include:
Final settlement still occurs through conventional channels — real-time gross settlement (RTGS) systems, correspondent banking relationships, or other agreed mechanisms. The ledger does not disintermediate central banks or settlement systems. It adds a coordination layer that enables 24/7 operation, including overnight and weekend transactions.
Tokenized deposits are issued on individual banks' own ledgers. The shared ledger records and validates payment commitments between banks, then passes the settlement obligation to existing infrastructure. Banks retain full authority over their own keys, assets, and settlement processes.
The design phase completed in March 2026 with input from over 30 global banks. The MVP went live four months later, on July 9.
First Abu Dhabi Bank (FAB) and Citibank completed a live USD tokenized deposit transaction on September 2, 2026. FAB became the first bank in the Middle East and Africa region to execute a live transaction on the Swift ledger at scale.
The transaction validated the end-to-end interaction between existing Swift payment messaging, tokenized deposits, and distributed ledger infrastructure. Tokenized deposits remained on participating banks' balance sheets. The Swift ledger coordinated payment commitments and recorded corresponding interbank liabilities without taking custody of funds.
On September 10, DBS, OCBC, and UOB completed Singapore's first live interbank transactions using tokenized SGD deposits on the Swift ledger. The shared ledger acted as a secure orchestration layer, enabling obligations to be matched and netted between the banks prior to final settlement through existing systems.
Rachel Chew, Chief Operating Officer and Co-Head of Digital Assets at DBS, stated: "In a digital economy, our clients' businesses operate round the clock, and their money should too."
Carmen Chan, Deputy Head of Global Transaction Banking at OCBC, noted: "Singapore's first live SGD interbank transactions enabled by bank-issued digital money demonstrate the value of industry collaboration."
The banks did not disclose transaction values, number of transfers, participating clients, or a timetable for wider commercial availability.
Both sets of transactions omitted key data points: transaction size, throughput, latency benchmarks, and error rates. The absence of volume data makes it difficult to assess whether the system is operating at a scale relevant to production workloads or remains a controlled demonstration. Until Swift or its pilot banks publish throughput metrics, the operational significance of these transactions remains unquantified.
The following institutions are preparing to pilot live transactions on the ledger:
| Bank | Headquarters | |------|-------------| | ANZ | Australia | | BNP Paribas | France | | BNY | United States | | Citi | United States | | DBS | Singapore | | First Abu Dhabi Bank | UAE | | FirstRand Bank | South Africa | | HSBC | United Kingdom | | Itaú Unibanco | Brazil | | Lloyds Bank | United Kingdom | | Mashreq | UAE | | MUFG Bank | Japan | | OCBC | Singapore | | Standard Chartered | United Kingdom | | UBS | Switzerland | | UOB | Singapore | | Wells Fargo | United States |
The geographic distribution spans six continents. HSBC has connected its Tokenised Deposit Service to the ledger. The remaining banks are at various stages of integration.
The cohort collectively represents trillions of dollars in daily payment flows. However, participation in the pilot does not indicate committed production volume. Multiple banks are simultaneously participating in competing tokenized deposit and stablecoin initiatives.
Swift's choice to build on tokenized deposits rather than stablecoins or CBDCs reflects a specific institutional calculus.
Tokenized deposits are bank liabilities represented as digital tokens. The customer claim remains a deposit claim on a regulated bank. Qualifying deposits are typically covered by banking supervision and deposit insurance frameworks. The wrapper changes; the legal and regulatory status does not.
Stablecoins reached $307 billion in market capitalization in early 2026. They are privately issued tokens, not bank liabilities, and do not automatically confer the same protections as insured deposits. The 21-bank consortium announced on September 1, 2026 — including Bank of America, Citi, Goldman Sachs, and Wells Fargo — is pursuing a bank-issued stablecoin as a separate initiative, targeting H1 2027 launch.
Wholesale CBDCs offer settlement finality backed by central banks but remain in pilot phases across Europe, Asia, and the Americas. The ECB's Pontes service, connecting ECB payment systems with blockchain markets, represents the most advanced European effort.
The likely end-state, according to analysis from Quant Network, is an interoperable stack: tokenized deposits for commercial bank money, regulated stablecoins for open-network distribution and cross-border portability, and CBDC or tokenized central-bank money as the public settlement anchor. Swift's ledger is positioning itself as the institutional plumbing connecting these layers.
The Swift ledger does not operate in isolation. It can interoperate with public Ethereum-compatible networks through Chainlink's Cross-Chain Interoperability Protocol (CCIP), which currently connects approximately 70 public and private networks.
This design gives the permissioned ledger a technical path to the broader tokenized asset ecosystem. Cross-chain transfers via CCIP surged 1,972% to $7.77 billion in 2025, according to Chainlink data, indicating growing demand for institutional-grade cross-chain connectivity.
The architecture creates what Chainlink describes as an institutional access point: Swift acts as the gateway for its 11,500+ member institutions to reach public and private chains through a single integration, while CCIP provides the verification and connectivity required to execute across multiple networks.
This is significant because it means a bank connected to the Swift ledger could, in principle, interact with tokenized assets on Ethereum, Avalanche, or other EVM-compatible chains without building separate integrations for each network. Whether banks will use this capability at scale remains to be seen.
Swift's ledger has implications for several incumbent revenue streams and cost structures:
Correspondent banking fees. Cross-border payments currently traverse multiple correspondent banks, each charging fees. A shared ledger that enables direct bilateral settlement could compress the intermediary chain, reducing costs but also reducing fee revenue for correspondent banks.
FX settlement windows. 24/7 operation eliminates the concept of "business hours" in payment processing. This reduces overnight settlement risk but also challenges the FX market structure built around cut-off times and batch processing.
Infrastructure lock-in. Swift already connects 11,500+ institutions. Adding a blockchain layer to that existing network creates a powerful network effect. Competing tokenized deposit systems — from the 21-bank stablecoin consortium to individual bank efforts — face the challenge of building connectivity from scratch.
Cost of participation. Swift has not disclosed pricing for ledger access. The economic model — whether per-transaction fees, subscription-based, or bundled with existing Swift services — will determine adoption velocity.
According to Thierry Chilosi, Swift's Chief Business Officer: "The strong support from banks demonstrates the practical value of this approach — one that will help scale benefits globally while creating a foundation for future innovation in areas like programmable money and agentic commerce."
Swift's shared ledger represents the most significant infrastructure upgrade to the global interbank messaging network since SWIFT gpi launched in 2017. It is not a prototype. Live transactions have been completed. But it is also not yet a production system at scale — transaction volumes remain undisclosed, pricing is undefined, and the 17-bank pilot represents a fraction of Swift's 11,500-member network.
The architectural decisions are deliberate. Tokenized deposits instead of stablecoins preserve the bank deposit model. A permissioned Hyperledger Besu chain instead of a public network maintains institutional control. Chainlink CCIP for interoperability keeps the door open to public chains without committing to any single one. Each choice optimizes for institutional adoption over speed-to-market.
The open question is throughput. Swift moves the equivalent of world GDP every two to three days. The shared ledger needs to demonstrate it can handle meaningful fractions of that volume before it shifts from milestone to infrastructure. The September transactions are a proof point, not a proof of scale. The data that matters — transaction volumes, latency, error rates, cost per transaction — has not yet been published.