SWIFT, the messaging backbone connecting 11,500 financial institutions across 200+ countries, announced on March 30, 2026, that it has completed the design phase of a blockchain-based shared ledger and is now building a minimum viable product (MVP) for live deployment before year-end. More than 4...
SWIFT, the messaging backbone connecting 11,500 financial institutions across 200+ countries, announced on March 30, 2026, that it has completed the design phase of a blockchain-based shared ledger and is now building a minimum viable product (MVP) for live deployment before year-end. More than 40 global banks — including JPMorgan Chase, HSBC, Deutsche Bank, BNP Paribas, Bank of America, Lloyds Bank, and Banco Santander — participated in the design phase. The MVP will enable 24/7 cross-border payments using tokenized commercial bank deposits, collapsing messaging and settlement into a single programmable layer.
The initiative arrives at a moment when tokenized deposits are emerging as a direct competitor to stablecoins for on-chain institutional settlement, the Federal Reserve is publishing formal analysis of stablecoin implications for cross-border payments, and the correspondent banking network has contracted approximately 30% over the past decade. SWIFT's entry signals that the largest incumbent in global payments infrastructure now views blockchain rails as operationally necessary rather than experimental.
SWIFT first unveiled the shared ledger project at its Sibos conference in Frankfurt in September 2025, initially naming 30 participating financial institutions. By the time the design phase concluded on March 30, 2026, the consortium had grown to more than 40 institutions.
The scope is narrow and deliberate. The initial use case focuses exclusively on real-time international payments using tokenized deposits — digital representations of conventional bank deposits, FDIC-insured and sitting on the issuing bank's balance sheet, but capable of 24/7 programmable settlement. SWIFT will operate the ledger, providing orchestration of transaction workflows, validation of funding commitments, and coordination of interbank processes. Individual banks will retain full authority over keys, assets, funding, and settlement through RTGS systems, correspondent banking relationships, or other bilaterally agreed mechanisms.
The MVP is scheduled to go live with real-world transactions before the end of 2026. SWIFT is simultaneously defining a roadmap for future functionality, including exploration of other on-chain settlement assets and use cases across more than 200 countries and territories.
The ledger MVP is being built on open-source foundations using an Ethereum Virtual Machine (EVM)-compatible architecture based on Hyperledger Besu. The infrastructure layer is permissioned — not a public blockchain — and does not involve a native cryptocurrency.
SWIFT developed a conceptual prototype with ConsenSys, whose Ethereum Layer 2 network Linea provides the underlying technology stack. The architecture choice is significant: by adopting EVM compatibility, SWIFT ensures interoperability with the broader Ethereum ecosystem and the growing universe of tokenized assets deployed on EVM-compatible chains, without exposing the system to public chain risks.
The ledger functions as an orchestration layer operating above existing payment infrastructure. It records and validates bank commitments, provides shared visibility of transaction status, and implements a two-step process: first, client fund movement; second, settlement between payer and payee banks. Initial settlement will use conventional routes — RTGS systems or correspondent banking — with alternative on-chain settlement routes available as bilateral agreements between participants.
This is not a replacement of SWIFT's existing messaging infrastructure. It is an additional layer. The 44.8 million daily messages SWIFT currently handles (44% payment-related, 51% securities-related) will continue to flow. The shared ledger adds a settlement coordination function that the messaging layer was never designed to perform.
The economic rationale for the ledger is embedded in persistent inefficiencies in correspondent banking. According to the Federal Reserve's FEDS Notes publication of March 30, 2026, authored by Kim, Ruprecht, and Styczynski:
The Fed researchers identified multiple cost sources: extended processing times due to intermediary chains, difficulty tracking payment status across intermediaries, message alteration risks through different systems, and redundant anti-money-laundering compliance checks at multiple points in the chain.
The correspondent banking network exhibits high concentration. A shrinking number of global clearing banks handle an increasing share of cross-border volume, concentrating risk and driving up costs. Regulatory pressure and rising compliance costs have accelerated "de-risking" — banks withdrawing from certain markets and terminating correspondent relationships — reducing competition particularly in lower-volume or higher-risk corridors.
SWIFT processes over $10 trillion in payments daily across its network. The shared ledger targets a specific slice of this volume: cross-border payments that currently suffer from weekend delays, multi-day settlement, and opaque intermediary chains. By collapsing messaging and settlement into a single programmable layer, the ledger aims to reduce reconciliation friction and provide continuous, 24/7 transaction capability.
SWIFT's ledger enters a market where tokenized deposits and stablecoins are diverging into distinct use cases and regulatory frameworks.
Tokenized deposits are conventional bank deposits represented as blockchain tokens. They remain on the issuing bank's balance sheet, carry deposit insurance (FDIC in the U.S.), and can pay interest. JPMorgan launched JPM Coin (JPMD) and expanded it to the Base blockchain in November 2025. HSBC plans to launch its Tokenized Deposit Service (TDS) to corporate users in the U.S. and UAE in H1 2026, having already gone live in Singapore, Hong Kong, the UK, and Luxembourg. The Texas Bankers Association announced structured access to tokenized deposit technology for its approximately 600 member banks through its Innovation Magnet program, signaling that the technology is reaching community and regional institutions.
Stablecoins, by contrast, operate under the GENIUS Act framework passed by Congress in July 2025. They must be backed by safe assets (bank deposits, short-term Treasuries, or Federal Reserve balances) and are prohibited from paying interest directly. The stablecoin market stands at approximately $317 billion, dominated by USDT and USDC.
The distinction matters for economic value distribution. Tokenized deposits preserve the bank's role as intermediary and deposit-taker. The economic value — interest margin, fee revenue, balance sheet expansion — stays within the banking system. Stablecoins, by contrast, create a parallel settlement layer where value accrues to issuers (Circle, Tether) and the protocols that facilitate on-chain movement.
SWIFT's choice to build around tokenized deposits rather than stablecoins is a structural bet: that regulated bank deposits, made programmable, will capture the institutional cross-border settlement market. Stablecoins may continue to dominate retail and DeFi corridors, but the $10 trillion daily SWIFT volume is bank territory.
The timing of the Fed's March 30 FEDS Notes publication — the same day as SWIFT's MVP announcement — was notable. The paper by Kim, Ruprecht, and Styczynski provided the first formal Federal Reserve analysis of how payment stablecoins interact with cross-border payment frictions and monetary policy implementation.
Key findings:
The paper implicitly frames stablecoins and tokenized deposits as complementary rather than competing instruments. Stablecoins address gaps in corridors where correspondent banking has retreated. Tokenized deposits address efficiency within the existing banking network. Both reduce intermediation layers, but through different institutional structures.
SWIFT's ledger redesigns how economic value flows through cross-border payments. Under the current correspondent banking model, each intermediary in a payment chain extracts fees — typically FX markups of 2-3% per transaction plus handling fees. A payment traversing three intermediaries generates revenue at each node, with cumulative costs that reach end users as the 6.49% average remittance cost.
The shared ledger compresses this chain. By providing shared visibility and direct settlement coordination between payer and payee banks, it reduces the number of fee-extracting intermediaries. This shifts value from intermediary banks to end-point banks and, potentially, to end users through lower fees.
However, the ledger also creates a new value extraction point: SWIFT itself. As operator of the orchestration layer, SWIFT positions itself as essential infrastructure for on-chain institutional settlement — a role that extends its existing messaging monopoly into the settlement layer. The economic question is whether the efficiency gains from compressed intermediation chains exceed the costs of SWIFT's new infrastructure layer.
For the broader blockchain ecosystem, SWIFT's adoption of EVM-compatible infrastructure validates the Ethereum technology stack as enterprise-grade. Hyperledger Besu and Linea gain a reference deployment processing real institutional volume. The permissioned architecture, however, captures none of this value for public chain validators or token holders — a recurring pattern in enterprise blockchain adoption where the technology is adopted but the public network economics are bypassed.
SWIFT's shared ledger represents the largest single institutional commitment to blockchain-based payment infrastructure to date, measured by network reach (11,500 institutions, 200+ countries) and daily volume ($10 trillion). The project is deliberately conservative: permissioned, bank-operated, deposit-based, and built atop existing infrastructure rather than replacing it.
The significance is not in the technology — EVM-compatible permissioned ledgers are well-understood — but in the institutional commitment. When the operator of the world's dominant interbank messaging network adds a blockchain settlement layer, it confirms that programmable money infrastructure has crossed from pilot to production for wholesale finance. The remaining question is execution: whether 40+ banks can coordinate live tokenized deposit payments across jurisdictions with different regulatory regimes, RTGS systems, and settlement conventions before the end of 2026.