Swift's Blockchain Ledger Reaches MVP: What Tokenised Deposits Mean for Cross-Border Payments

Swift has moved from design to active construction of a blockchain-based shared interbank ledger, targeting live transactions with tokenised deposits this year, a development that could reshape the architecture of cross-border settlement for its 11,500+ connected institutions across more than 200 countries.

What Is Swift Actually Building?

The minimum viable product (MVP) is a shared digital orchestration layer sitting atop existing bank payment infrastructure. Built on an Ethereum Virtual Machine (EVM)-compatible architecture using Hyperledger Besu, the ledger will record and validate interbank payment commitments while enabling value to move in the form of tokenised commercial bank money, digital representations of deposits held at participating banks.

Swift will operate the ledger's orchestration layer, managing transaction workflows and validating funding commitments. Critically, individual banks retain full custody: each institution controls its own keys, assets, and settlement mechanisms, whether through RTGS systems, correspondent banking relationships, or bilateral agreements. No assets move to a centralised custodian.

The design phase - launched in September 2025 - involved a global cohort of banks working collaboratively to define how a shared ledger could enable more effective cross-border coordination as market expectations shift toward always-on, 24/7 settlement.

How Does It Work in Practice?

The ledger introduces a coordination layer that sits between existing payment applications. When a cross-border payment is initiated, the ledger records and validates funding commitments from participating institutions in real time, enabling settlement using tokenised deposits as the underlying value representation. This removes the asynchronous reconciliation bottlenecks that characterise today's correspondent banking chains.

For participating banks, the architecture promises four concrete operational improvements: faster payment execution, improved liquidity visibility, reduced reconciliation burden, and structural interoperability across institutions, without requiring them to abandon existing rails or rebuild core systems.

Beyond basic transfers, the same infrastructure is designed to support programmable corporate payment flows, foreign exchange payment-versus-payment (PvP), and securities-linked cash movements.

Why an EVM Architecture?

The choice of Hyperledger Besu - an enterprise-grade, EVM-compatible client - is deliberate. It allows Swift's ledger to maintain interoperability with the broader digital asset ecosystem, including emerging central bank digital currency (CBDC) infrastructure and tokenised asset platforms, without locking participating banks into a proprietary stack. The open-source foundation also lowers the integration barrier for banks that have already invested in Ethereum-compatible tooling.

This positions Swift's infrastructure as a potential convergence layer as the tokenised finance landscape fragments across multiple chains, platforms, and digital money formats.

What Is the Timeline?

The MVP is on track for live transactions in 2025, with Swift simultaneously working with banks internationally to define a roadmap for expanded functionality, including support for additional on-chain settlement assets and use cases. In parallel, more than 25 banks are scheduled to adopt Swift's new retail payments framework by end of June, which focuses on cost transparency, full-value delivery, and instant settlement where technically available.

The two tracks are complementary: the ledger addresses wholesale interbank settlement infrastructure, while the retail scheme targets consumer and SME payment experience.

Is the Industry Ready?

The appetite is there. Since announcing plans in September 2025, a broad coalition of global banks has actively shaped the ledger's design, suggesting alignment at the institutional level that has historically been difficult to achieve in infrastructure projects of this scale. Swift's existing network effects - over 40,000 active payment routes - provide a distribution advantage that newer entrants to the tokenised payments space cannot easily replicate.

The more substantive question is regulatory: tokenised deposits do not yet have a harmonised legal treatment across jurisdictions, and the interaction between this ledger and evolving CBDC frameworks in major economies remains an open variable.

Why This Matters to FinanceX Readers

For finance professionals and investors, the Swift ledger MVP is less a technology story and more a structural market event. If it reaches scale, it materially compresses the settlement risk window in cross-border payments, reducing the overnight and multi-day exposure that banks currently carry in correspondent chains. That has direct implications for liquidity requirements, intraday funding costs, and the capital treatment of in-flight cross-border payments under Basel frameworks.

For investors tracking wholesale banking infrastructure, the ledger's open-source, EVM-compatible design signals that Swift is positioning itself as interoperability infrastructure for the tokenised finance era, not as a gatekeeper. That matters for how banks price and allocate technology investment in core payments over the next three to five years.

By Koen Vanderhoydonk, FinanceX Magazine