SWIFT's Blockchain Shared Ledger: How Legacy Banking Infrastructure Is Evolving

On March 30, 2026, SWIFT announced that it had completed the design phase of a blockchain-based shared ledger and was moving into MVP implementation. The system, built on Hyperledger Besu with an EVM-compatible architecture, aims to enable 24/7 cross-border payments using tokenized bank deposits. More than 40 global banks participated in the design, including JPMorgan, HSBC, Deutsche Bank, Bank of America, and Wells Fargo.

This is the most significant infrastructure change at SWIFT since the cooperative launched its messaging standard in 1977. It is also the clearest signal yet that traditional finance considers distributed ledger technology essential to the future of payments. The question for crypto is whether SWIFT adopting blockchain validates the thesis behind permissionless payment networks or undermines the case for them.

How SWIFT Works Today

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is not a payment network. It is a messaging network. When a bank in New York sends a SWIFT message to a bank in Tokyo, no money moves through SWIFT itself. The message instructs the receiving bank to debit or credit accounts on its own books. Settlement happens separately, through correspondent banking relationships and linked accounts.

The network connects over 11,500 financial institutions across more than 200 countries and territories. In 2025, members sent an average of 59.8 million messages per day, a 12% increase over 2024. Roughly every three days, the equivalent of global GDP passes through SWIFT messages.

The Correspondent Banking Chain

Cross-border payments through SWIFT rely on correspondent banks: third-party institutions that act as intermediaries when the sender and receiver lack a direct banking relationship. This system depends on nostro and vostro accounts: pre-funded accounts that banks maintain at each other. A nostro account ("ours, on your books") holds the sending bank's funds at the correspondent. A vostro account ("yours, on our books") is the mirror image.

A typical cross-border payment might pass through two or three intermediary banks before reaching the beneficiary. Each bank in the chain performs its own compliance checks, currency conversion, and reconciliation. Each hop adds cost (typically $15 to $25 per intermediary) and delay (hours to a full business day per hop). The result: banks charge $15 to $50 per SWIFT transfer in visible fees, but the total cost including FX spreads and intermediary deductions can reach 2% to 7% of the transfer amount.

Why Payments Still Take Days

SWIFT's GPI (Global Payments Innovation) service, launched in 2017, has improved speed considerably. SWIFT reports that nearly 60% of GPI payments are credited within 30 minutes and over 90% within 24 hours. But these statistics mask structural limitations:

• Settlement depends on RTGS (Real-Time Gross Settlement) systems that operate during business hours in each jurisdiction
• Time zone mismatches mean a payment sent Friday afternoon in London may not settle in Sydney until Monday
• Compliance screening (KYC, AML, sanctions) happens sequentially at each intermediary, not in parallel
• Banks batch-process many payments rather than settling individually, introducing additional delay
• Nostro account funding requires pre-positioned liquidity across currencies, tying up capital that banks must manage manually

A 2025 study of 5,621 real SWIFT transactions found an average processing time of 27 hours, with only 64% arriving within 24 hours. For corridors involving smaller currencies or multiple intermediaries, delays of 3 to 5 business days remain common. Global remittance costs average 6.36% of the amount sent, according to the World Bank's Q3 2025 data, more than double the UN's Sustainable Development Goal target of 3%.

Key context: SWIFT does not settle payments. It sends messages instructing banks to settle through their own systems. The shared ledger changes this by adding a settlement layer where tokenized deposits can move between banks on a shared infrastructure, 24 hours a day.

What the Shared Ledger Changes

SWIFT's shared ledger introduces a fundamentally different architecture. Instead of sequential message-passing between independent bank systems, participating institutions share a common digital layer that records and validates interbank payment commitments in near-real time.

Technical Architecture

The MVP is built on open-source foundations using an EVM-compatible architecture based on Hyperledger Besu, an Ethereum client designed for both public and private networks. ConsenSys, the company behind MetaMask and the Linea L2 network, developed the initial conceptual prototype. The design choices reflect SWIFT's priorities: EVM compatibility for developer tooling and smart contract capabilities, combined with permissioned access to maintain regulatory compliance and controlled governance.

This is not a public blockchain. There is no native cryptocurrency, no permissionless access, and no mining or staking. It is a permissioned network restricted to approved institutional participants, operated by SWIFT with banks running their own environments.

Tokenized Deposits

The ledger's core mechanism uses tokenized deposits: digital representations of bank deposits on the shared ledger. When Bank A wants to pay Bank B, it mints a tokenized deposit representing the payment amount. Bank B receives the token and can redeem it, hold it, or use it in further transactions. The token represents a direct claim on the issuing bank's reserves, not a new form of money.

This eliminates the sequential correspondent banking chain for participating institutions. Instead of: message → compliance check → intermediary → compliance check → intermediary → credit, the flow becomes: mint tokenized deposit → transfer on shared ledger → redeem. Settlement and messaging happen on the same infrastructure.

24/7 Availability

Because the shared ledger operates continuously, payments are no longer constrained by RTGS operating hours or time zone mismatches. A bank in Singapore can settle with a bank in Brazil at 2 AM on a Saturday. This alone addresses one of the most persistent pain points in cross-border payments: weekend and holiday delays that can add days to settlement timelines.

How Banks Participate

SWIFT operates the ledger, providing orchestration of transaction workflows, validation of funding commitments, and coordination of interbank processes. Banks retain full authority over their own keys, assets, funding, and settlement through RTGS systems, correspondent banking relationships, or other agreed mechanisms. This hybrid model means the shared ledger supplements rather than replaces existing infrastructure, at least initially.

Timeline and Rollout

The development timeline has moved quickly by traditional banking standards:

• September 2025: SWIFT announces the shared ledger initiative at Sibos in Frankfurt, with 30+ banks committed to the design phase
• September 2025 to March 2026: collaborative design phase with banks, growing to 40+ participating institutions
• March 30, 2026: design phase completed, MVP construction begins
• 2026 (target): MVP go-live with real-world tokenized deposit transactions among a select group of pilot banks

The participating banks span every major financial center. The roster includes JPMorgan, HSBC, Deutsche Bank, Bank of America, BNP Paribas, Citi, Wells Fargo, Lloyds Bank, NatWest, Standard Chartered, Societe Generale-FORGE, TD Bank Group, Royal Bank of Canada, MUFG, OCBC, UOB, Westpac, Shinhan Bank, and Saudi Awwal Bank, among others.

The first use case is cross-border payments using tokenized deposits. SWIFT has indicated that the roadmap includes additional functionality beyond payments, potentially including tokenized securities settlement and other real-world asset applications.

What This Means for Crypto

SWIFT's adoption of blockchain technology creates an interesting paradox for the crypto industry. The move simultaneously validates the core technology and challenges the narrative that permissionless networks are the only path to better payments.

The Validation Argument

For years, blockchain advocates argued that payment rails should be programmable, always-on, and capable of near-instant settlement. Banks and regulators pushed back, citing compliance concerns, governance risks, and technological immaturity. SWIFT building its future on an EVM-compatible blockchain is a concession that the advocates were right about the technology, even if the implementation differs from what Bitcoin and Ethereum maximalists envisioned.

The fact that SWIFT chose EVM compatibility rather than building from scratch is particularly telling. It signals that the Ethereum ecosystem's developer tooling, smart contract standards, and battle-tested infrastructure have become the default reference architecture for enterprise blockchain, even in permissioned deployments.

The Competition Argument

If SWIFT delivers 24/7 cross-border settlement through tokenized deposits, one of the strongest use cases for stablecoins in traditional finance weakens. Banks would no longer need to route around their own infrastructure to achieve fast settlement. A corporate treasurer in Tokyo would not need to buy USDC and send it on Ethereum when their bank offers tokenized deposit transfers on the SWIFT ledger with the same speed and regulatory clarity.

This is the bear case for stablecoins as a cross-border B2B payment mechanism within the banking system. If incumbents absorb the technology, the competitive advantage shifts from speed to other factors: cost, accessibility, and permissionlessness.

The bigger picture: SWIFT's shared ledger serves 11,500+ member institutions. But there are roughly 1.4 billion adults worldwide without a bank account and billions more underserved by the correspondent banking system. Stablecoin payment rails and permissionless networks like Bitcoin address a fundamentally different market: the people and businesses that the banking system does not reach.

SWIFT's Shared Ledger vs. Stablecoin Rails

The comparison between SWIFT's new ledger and stablecoin-based payment infrastructure reveals that they are solving different problems for different users, with meaningful tradeoffs on both sides.

The distinction between tokenized deposits and stablecoins is critical. Tokenized deposits remain bank liabilities: they carry the issuing bank's credit risk, fall under existing banking regulation, and benefit from deposit insurance where applicable. Stablecoins are issued by non-bank entities (Circle, Tether, Brale), backed by reserves, and regulated under emerging frameworks like the GENIUS Act in the United States or MiCA in Europe.

Stablecoin payment volume (excluding trading) reached $390 billion in 2025, more than double 2024 levels, with B2B payments accounting for approximately $226 billion. This growth happened while SWIFT's shared ledger was still in design. The question is not whether one replaces the other, but whether they serve overlapping or complementary markets.

Where SWIFT's Ledger Falls Short

For all its promise, the shared ledger inherits structural limitations that no amount of blockchain technology can fix:

Permissioned Access

The ledger is restricted to approved institutional participants. A small business in Lagos cannot join SWIFT's network directly. Neither can a freelancer in Manila receiving payment from a client in London. The correspondent banking model may be faster and cheaper on the shared ledger, but it still requires a bank account on both ends.

Network Effects Take Time

Even with 40+ banks in the design phase, the MVP covers a fraction of SWIFT's 11,500+ members. The value of the shared ledger depends on adoption: if your bank and your counterparty's bank are not both on the ledger, the payment falls back to traditional correspondent banking. Full network migration will take years, possibly a decade.

Governance and Innovation Speed

SWIFT operates as a Belgian cooperative owned by its member banks. Changes require consensus among institutions with different priorities, regulatory environments, and risk appetites. The design phase alone took six months with 40 banks. Compare this to stablecoin infrastructure, where Circle can deploy USDC on a new chain in weeks and CCTP enables cross-chain transfers without committee approval.

Cost Uncertainty

SWIFT has not published fee structures for the shared ledger. The technology reduces intermediary costs, but SWIFT and participating banks will set pricing. Historical patterns suggest that cost savings from infrastructure improvements are not always passed through to end users. Currently, banks remain the most expensive remittance channel at an average of 9.50% of the transfer amount, compared to 3.65% for digital providers.

The Convergence Pattern

SWIFT's shared ledger fits a broader pattern of TradFi-DeFi convergence. Traditional institutions are adopting blockchain infrastructure while maintaining permissioned access and regulatory compliance. Crypto-native projects are adding compliance features, fiat on-ramps, and institutional custody to attract the same users.

This convergence is visible across the industry:

• Visa and Mastercard are integrating stablecoin settlement alongside traditional card rails
• The Federal Reserve launched FedNow for domestic instant payments, while real-time payment systems proliferate globally
• Banks are experimenting with tokenized deposits while stablecoin issuers pursue bank-like regulation
• ISO 20022, SWIFT's new messaging standard, was designed with structured data fields that can interoperate with blockchain-based systems

The end state is likely a layered system: SWIFT's ledger handling large-value interbank flows between regulated institutions, stablecoin rails serving the long tail of corridors and participants that banks do not cover, and permissionless networks like Bitcoin providing a neutral settlement layer that neither depends on nor requires permission from any institution.

Implications for Bitcoin and Permissionless Settlement

SWIFT's move underscores a distinction that the crypto industry sometimes blurs: the difference between faster payments within the banking system and an alternative to the banking system itself. SWIFT's ledger makes interbank settlement faster. Bitcoin and its Layer 2 networks make settlement possible without banks.

This distinction matters most for the billions of people and businesses outside the reach of correspondent banking. A farmer in rural Kenya does not benefit from SWIFT's tokenized deposits. Neither does a Venezuelan saving in dollars to hedge against inflation. These users need permissionless access to sound money and cheap transfer rails: exactly what Bitcoin, stablecoins on Bitcoin, and Layer 2 protocols provide.

Spark, for example, enables instant, self-custodial Bitcoin and stablecoin transfers without channel management or pre-funded accounts. Settlement is final in seconds, available 24/7, and accessible to anyone with a mobile phone. These are the same properties SWIFT is spending hundreds of millions to achieve within its permissioned network. Spark delivers them on a permissionless one, built on Bitcoin.

The two approaches are not in direct competition. They serve different segments of the global economy. But they share a core thesis: programmable, always-on settlement is the future of money movement. SWIFT's decision to build on blockchain validates that thesis more powerfully than any crypto whitepaper ever could.

What to Watch

Several developments in the coming months will shape how this plays out:

• MVP go-live timing and which banks participate in the first live tokenized deposit transactions
• Fee structures for the shared ledger compared to current correspondent banking costs
• Whether the ledger supports interoperability with public blockchain networks or remains entirely siloed
• How regulators treat tokenized deposits versus stablecoins under frameworks like the GENIUS Act
• Whether SWIFT's roadmap extends to tokenized securities and RWA settlement, which would expand its blockchain footprint significantly
• Stablecoin payment volume growth: if it doubles again in 2026, the urgency for SWIFT to deliver increases

For developers building payment infrastructure, SWIFT's shared ledger introduces a new variable. B2B payment flows between large banks will likely migrate to tokenized deposits over time. Consumer payments, remittances, and unbanked markets remain wide open for crypto-native solutions. The Spark SDK provides tools for building on the permissionless side of this divide, with instant settlement and stablecoin support already live.

Explore how traditional and crypto payment rails compare or use the cross-border payment speed comparison tool to see settlement times across different networks.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.