Swift activated a blockchain-based shared ledger on July 9, 2026, enrolling 17 banks across six continents in a live pilot for 24/7 cross-border payments using tokenized deposits. The ledger runs on Hyperledger Besu, an EVM-compatible permissioned network, with Chainlink CCIP providing interopera...
Swift activated a blockchain-based shared ledger on July 9, 2026, enrolling 17 banks across six continents in a live pilot for 24/7 cross-border payments using tokenized deposits. The ledger runs on Hyperledger Besu, an EVM-compatible permissioned network, with Chainlink CCIP providing interoperability to external blockchain networks. Participating institutions include ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand, HSBC, Itaú Unibanco, Lloyds, Mashreq, MUFG, OCBC, Standard Chartered, UBS, UOB, and Wells Fargo.
The launch positions Swift — whose messaging platform connects more than 11,500 institutions across 200+ countries and processes approximately 53 million messages daily — as the orchestration layer for institutional tokenized money movement. It also places tokenized deposits, not stablecoins, at the center of the next phase of cross-border settlement infrastructure.
The shared ledger is a permissioned blockchain network that serves as an orchestration layer for bank-issued tokenized deposits. It does not replace Swift's existing messaging infrastructure. Instead, it adds a settlement coordination capability on top of it.
The system enables participating banks to issue tokenized representations of their deposits on their own internal ledgers. Swift's shared ledger then synchronizes obligations across institutions, providing a unified view of transaction status as payments progress. The key operational improvement: payments can execute overnight and on weekends, before completing final settlement through existing real-time gross settlement (RTGS) systems during business hours.
The ledger was designed and built in nine months, following a design phase that incorporated feedback from international financial institutions. It is currently in initial production use — not full general availability. Swift has not specified a timeline for expanding beyond the 17-bank pilot group.
Tokenized deposits in this context are bank-issued digital instruments backed one-to-one by customer deposits. They carry the same regulated, credit-backed standing as conventional account balances. This is a critical distinction: unlike stablecoins, tokenized deposits sit within the banking regulatory perimeter, carry deposit insurance (up to statutory limits), and the issuing bank retains access to central bank lending facilities.
The ledger runs on Hyperledger Besu, an open-source Ethereum client that operates as a permissioned network. Key technical specifications:
The choice of Besu is architecturally significant. EVM compatibility means Swift's developers use the same smart contract language and tooling as the broader Ethereum ecosystem — an estimated 4,000+ developers and auditors — while maintaining a permissioned environment. Swift moved the Chainlink integration from pilot to production in November 2025, and member banks can now route tokenized asset instructions through CCIP using ISO 20022 messages.
This design creates a technical path from permissioned institutional infrastructure to public blockchain networks. Whether banks will use that path for production flows remains to be seen, but the optionality is built in.
The Swift ledger launch crystallizes a debate that has been building throughout 2026: should institutional cross-border payments run on tokenized deposits or stablecoins?
Stablecoins — approximately $315 billion in market capitalization as of April 2026, predominantly USD-denominated — are bearer instruments issued by non-bank entities. Under the GENIUS Act framework, they are backed 1-to-1 by high-quality liquid assets such as U.S. Treasury bills. Possession of the token equates to ownership. They excel in open-ecosystem reach, crypto-native liquidity, and global retail payments, particularly in markets underserved by traditional banking rails.
Tokenized deposits are account-based, not bearer instruments. They are commercial bank money represented on a blockchain — functionally identical to regular deposits except for the underlying ledger technology. They are backed by deposit insurance (up to the $250,000 statutory limit in the U.S.), and issuing banks retain access to the Federal Reserve's lender-of-last-resort window.
According to a February 2026 New York Federal Reserve Staff Report, this distinction matters for financial stability. Tokenized deposits preserve the fractional-reserve banking model and its associated safety net. Stablecoins, as narrow-bank-like instruments backed by liquid reserves, could in theory draw deposits away from the banking system — a structural disintermediation risk that bank regulators have flagged.
The practical implication: tokenized deposits are built for closed, regulated environments — interbank settlement, corporate treasury management, and payment flows between known participants. Stablecoins are built for open ecosystems — crypto trading, DeFi, cross-border transfers, and platform-based payments where participants may not have banking relationships.
Swift's ledger firmly plants its flag on the deposit side.
Swift's ledger does not operate in isolation. Multiple institutional tokenized deposit initiatives are now active or in development:
JPMorgan Kinexys: The most mature institutional blockchain payment platform, having processed more than $4 trillion in cumulative transactions since launch. Average daily volume now exceeds $7 billion across eight currencies (USD, EUR, GBP, SGD, AUD, HKD, JPY, CNY). In November 2025, JPMorgan deployed its JPMD deposit token on Base, Coinbase's Ethereum Layer 2 — the first time a globally systemically important bank placed real institutional dollars on a public blockchain for live payments.
U.S. Bank Consortium (The Clearing House): JPMorgan, Citi, Bank of America, Wells Fargo, and at least 13 additional banks — including BNY, HSBC, PNC, TD Bank, Truist, and U.S. Bank — announced plans in June 2026 for a shared tokenized deposit network operated by The Clearing House, targeting a first-half 2027 launch. No blockchain partner has been publicly selected.
Swift's Ledger: Sits between these two models. It does not seek to displace Kinexys or the Clearing House network. Instead, it aims to provide a cross-border orchestration layer that could connect disparate domestic tokenized deposit systems. Given Swift's existing position as the messaging backbone for 11,500+ institutions, this is a network-effects play: if enough banks already use Swift infrastructure, the marginal cost of adding a tokenized deposit layer through Swift is lower than building a standalone network.
The question is whether these systems converge or fragment. Three incompatible approaches — proprietary (Kinexys), consortium (Clearing House), and network-utility (Swift) — are developing simultaneously. Interoperability between them is not guaranteed.
Cross-border payment flows provide context for the economic stakes:
The cross-border payments market is projected at $238 billion in revenue for 2026, growing at a 7.16% CAGR through 2031, according to Mordor Intelligence. Even marginal efficiency gains on $190 trillion in annual flows represent billions in reduced friction costs.
Pilot ≠ Production. The 17-bank group is running initial live transactions, not full-scale production flows. Swift has not announced a general availability date. History suggests multi-bank infrastructure pilots can take 12-24 months to reach production scale.
Settlement finality. The shared ledger enables payments to move before final settlement through existing RTGS systems. This introduces a timing gap — tokenized deposit transfers may appear complete to end users while underlying settlement remains pending. The risk management implications of this gap have not been publicly detailed.
Fragmentation risk. Three competing tokenized deposit architectures (Kinexys, Clearing House consortium, Swift ledger) are developing without a clear interoperability standard. If each requires separate integration, the efficiency gains of tokenization are partially offset by integration complexity.
Regulatory uncertainty. Tokenized deposits currently operate under existing banking regulations, but no jurisdiction has published a comprehensive framework specifically addressing tokenized deposit issuance, transfer, and settlement. The UK's FCA finalized crypto rules on June 30, 2026, with authorization opening in September 2026 — but these primarily address cryptoassets and stablecoins, not tokenized bank deposits per se.
Public chain connectivity. Chainlink CCIP provides a technical bridge to public blockchains, but it is unclear whether bank compliance frameworks will permit production flows that touch permissionless networks. The optionality exists; regulatory appetite for using it remains uncertain.
Swift's shared ledger marks the point at which the world's dominant cross-border messaging network committed to blockchain infrastructure for institutional money movement. The choice of tokenized deposits over stablecoins reflects the banking system's preference for instruments that sit within the existing regulatory perimeter — deposit-insured, central-bank-accessible, and account-based rather than bearer.
The economic logic is straightforward: $190 trillion in annual cross-border flows currently settles through batch-processed systems with limited weekend and overnight availability. Tokenized deposits on a shared ledger can reduce settlement timing from days to hours, even if final settlement still occurs through traditional RTGS.
Whether Swift's approach wins over Kinexys or the Clearing House consortium — or whether all three coexist as layers in a multi-tier settlement stack — remains an open question. What is no longer in question: the institutional banking system has chosen its digital money format, and it is not the stablecoin.