- SWIFT activated its blockchain-based shared ledger on July 9, with 17 banks preparing live pilots.
- No value moves on-chain: the ledger records interbank payment commitments only.
- Final settlement stays on existing RTGS and correspondent banking rails.
- The design allowed a nine-month build without changing any compliance framework.
SWIFT switched on its blockchain-based ledger on July 9, and the most important detail sits in what the system deliberately does not do. No value moves on-chain. The ledger records and validates payment commitments between banks, while tokenized deposits are issued on the banks’ own ledgers and interbank settlement happens separately through conventional channels such as RTGS systems or correspondent banking relationships. That design choice, dismissed by crypto natives as half a blockchain, is precisely what let SWIFT move from concept to activation in nine months without touching a single compliance, credit or risk framework, and it is now heading into live testing with 17 banks from six continents.
How a Payment Moves When the Money Stays Put
The mechanics work in two separated layers. When a client payment moves overnight or on a Saturday, the ledger validates a binding commitment between the payer bank and the payee bank, and the receiving institution can credit its client immediately against that commitment. The interbank obligation itself clears later, once RTGS systems and correspondent accounts reopen. Banks move funds for customers, including overnight and on weekends, before completing final settlement through existing systems.
This split is what separates SWIFT’s approach from every stablecoin rail and from public blockchain settlement. Custody, private keys and the actual deposits never leave the commercial banks. SWIFT coordinates the workflow rather than holding value, which means a compliance officer at a pilot bank reviews tokenized flows with the same counterparty controls used for conventional payments. The cooperative solved its regulatory problem by refusing to create one.
| Layer | What Happens | Where It Happens |
|---|---|---|
| Tokenized deposits | Issued and held as digital bank money | Each bank’s own ledger |
| Payment commitment | Recorded and validated 24/7 | SWIFT shared ledger (Hyperledger Besu, EVM-compatible) |
| Client credit | Beneficiary receives funds immediately | Payee bank, against the commitment |
| Final settlement | Interbank obligation clears | RTGS / correspondent banking, on reopening |
Nine Months From Sibos Announcement to Live Infrastructure
The build speed deserves attention on its own. SWIFT unveiled the ledger at Sibos last September and completed the design phase in March, and developed the platform in partnership with Consensys, with more than 30 financial institutions contributing before the project advanced to live pilots with 17 banks. For an organization serving more than 11,500 institutions across over 200 countries, nine months is closer to fintech pace than to interbank consortium pace, and the commitment-only architecture explains why: nothing in a member bank’s settlement stack needed rebuilding.
The pilot roster includes Citi, HSBC, UBS, BNP Paribas, DBS, Standard Chartered, MUFG, OCBC, Itaú Unibanco, First Abu Dhabi Bank and Lloyds, among others. Thierry Chilosi, SWIFT’s chief business officer, described the launch as “a key milestone for regulated digital assets”, and while the infrastructure is now live, the first transactions have yet to happen.
The Half-a-Blockchain Critique Has a Point About Speed
The same design that made the fast build possible defines the system’s ceiling. Because real value still clears through legacy infrastructure, overall settlement speed remains bounded by the slowest link in the chain, and a commitment recorded at 2 a.m. on Sunday is still an exposure on somebody’s books until Monday’s RTGS window. Skeptics read the whole construction as SWIFT inserting itself as a coordination point on technology originally built to remove intermediaries, while private alternatives like JPMorgan’s Kinexys, already in commercial operation, settle sovereign dollar transactions without SWIFT anywhere in the flow.
A second constraint is practical rather than philosophical. Because the ledger is purely an orchestration layer, every participant needs its own tokenized deposit capability, and while HSBC has connected its Tokenised Deposit Service, the step from infrastructure availability to completed bank integrations has historically been slow. Seventeen names on a press release and seventeen banks moving live volume are different milestones.
What the critique undervalues is where the actual delay in cross-border payments sits. Around 75% of payments on SWIFT’s network already reach beneficiary banks within 10 minutes, so message transmission was never the constraint. The operating calendar of settlement systems was, and the commitment layer attacks exactly that calendar without waiting for central banks to run RTGS on weekends.
Rival Networks Are Building Walled Versions of the Same Idea
A group of 17 US banks led by JPMorgan Chase, Bank of America, Citigroup and Wells Fargo plans to launch a tokenized deposit network in the first half of 2027, operated by The Clearing House. Japan’s three largest banking groups have separately announced a joint stablecoin platform planned by fiscal 2026.
| Initiative | Backers | Status |
|---|---|---|
| SWIFT shared ledger | SWIFT, Consensys, 17 pilot banks | Live for initial use, July 2026 |
| Tokenized deposit network | JPMorgan, BofA, Citi, Wells Fargo + 13 banks | Planned for H1 2027, run by The Clearing House |
| Kinexys | JPMorgan | In commercial operation |
The difference between these projects is access, and access follows from the commitment architecture. Kinexys belongs to one bank, and the Clearing House network will belong to six US giants. SWIFT asks members to reuse the secure connection they already maintain instead of managing dozens of separate blockchain endpoints, which is the only version of this idea available to a mid-sized lender in São Paulo or Sofia. Whether tokenized settlement becomes standard interbank plumbing or a private toll road depends heavily on which model reaches volume first.
MiCA and the Choice of Bank Money Over Stablecoins
Banks picked tokenized deposits for this experiment largely because the regulatory treatment of commercial bank money is settled law, a contrast to the still-moving classification of stablecoins under frameworks like MiCA in the EU. SWIFT plans to expand the ledger’s functionality and availability after the controlled go-live, with programmable money and AI-powered commerce named as eventual use cases, and an EVM base on which payment commitments already execute gives those roadmap items a technical foundation rather than leaving them as slideware. The nearer test comes first: the first live transactions, and the pace at which the remaining pilot banks build the tokenized deposit capability that turns a live platform into a liquid one.