Swift, the Belgium-based cooperative that routes approximately $150 trillion in annual cross-border payments across 11,500 institutions in 200+ countries, announced on July 9, 2026 that its blockchain-based shared ledger is ready for initial use. Seventeen banks spanning six continents — includin...
"With our new ledger capability, we're extending the trust and stability of established finance into the frontiers of digital money. It allows tokenised value to move across borders with the velocity and flexibility modern commerce expects, while maintaining the same high levels of resiliency, security, and compliance global finance requires." — Thierry Chilosi, Chief Business Officer, Swift
Swift, the Belgium-based cooperative that routes approximately $150 trillion in annual cross-border payments across 11,500 institutions in 200+ countries, announced on July 9, 2026 that its blockchain-based shared ledger is ready for initial use. Seventeen banks spanning six continents — including HSBC, Citi, UBS, BNP Paribas, Standard Chartered, and Wells Fargo — are preparing to pilot live tokenized deposit transactions on the infrastructure, which was built on Hyperledger Besu, an open-source Ethereum Virtual Machine (EVM)-compatible framework.
The ledger does not replace existing payment rails. It adds an orchestration layer that records, sequences, and validates interbank commitments using smart contracts, enabling tokenized deposits to move 24 hours a day, seven days a week — including overnight and on weekends — before final settlement occurs through conventional systems such as RTGS or correspondent banking. The nine-month build cycle, from October 2025 design announcement to July 2026 readiness, signals that the incumbent messaging giant views tokenized commercial bank money — not stablecoins, not CBDCs — as the most immediately deployable form of on-chain value transfer for institutional finance.
The announcement lands in a crowded field. The Clearing House disclosed in June 2026 that 17 U.S. banks including JPMorgan, Bank of America, and Citigroup will build a separate tokenized deposit settlement network bridged to CHIPS and RTP, targeting H1 2027. JPMorgan's Kinexys unit already processes live tokenized payments. Partior operates production settlement in USD, EUR, and SGD. Swift's competitive advantage is not technology — it is the network itself.
Swift's shared ledger is constructed on Hyperledger Besu, an enterprise-grade, EVM-compatible blockchain client maintained by the Linux Foundation's Hyperledger project. The choice of an Ethereum-compatible execution environment is significant: it means smart contracts deployed on the ledger use Solidity, the same language underpinning the $50 billion+ DeFi ecosystem on public Ethereum, though the ledger itself is permissioned and operated by Swift.
The architecture functions as an orchestration layer, not a settlement engine. It records and validates payment commitments between participating institutions. Each bank retains full authority over its own keys, assets, funding decisions, and settlement processes. Swift operates the shared layer, providing transaction workflow orchestration, funding commitment validation, and interbank process coordination.
The design phase completed in March 2026. The build took approximately four months. Swift confirmed the ledger supports tokenized deposits, regulated stablecoins, and central bank digital currencies, though the initial pilot focuses exclusively on tokenized deposits — bank-issued digital instruments backed one-to-one by conventional deposits.
According to Chilosi, the ledger's support extends beyond payments: "The strong support from banks shows the practical value of this approach — one that will help scale benefits globally while creating a foundation for future innovation in areas like programmable money and agentic commerce."
The pilot covers six continents. The full list of participating institutions:
| Bank | Headquarters | |------|-------------| | ANZ | Melbourne, Australia | | BNP Paribas | Paris, France | | BNY | New York, USA | | Citi | New York, USA | | DBS | Singapore | | First Abu Dhabi Bank (FAB) | Abu Dhabi, UAE | | FirstRand Bank | Johannesburg, South Africa | | HSBC | London, UK | | Itaú Unibanco | São Paulo, Brazil | | Lloyds Bank | London, UK | | Mashreq | Dubai, UAE | | MUFG Bank | Tokyo, Japan | | OCBC | Singapore | | Standard Chartered | London, UK | | UBS | Zurich, Switzerland | | UOB | Singapore | | Wells Fargo | San Francisco, USA |
The geographic spread is deliberate. Cross-border payments are constrained by time zone mismatches — when Tokyo closes, New York is opening, and settlement queues stall during the gap. A 24/7 ledger removes that friction. Three Singapore-headquartered banks (DBS, OCBC, UOB) participate alongside three U.S. institutions and three UK-based global banks, covering the major FX and trade corridors.
HSBC disclosed it has already connected its Tokenised Deposit Service to the shared ledger — the first confirmed integration of a bank-specific tokenized deposit platform with Swift's infrastructure.
Tokenized deposits are digital representations of commercial bank money, issued on a bank's own ledger and backed 1:1 by conventional deposits. They carry the same regulatory standing as traditional account balances: deposit insurance applies, prudential rules govern issuance, and the issuing bank retains full liability.
On Swift's shared ledger, the process operates in two steps:
The first step is on-chain. The second step is not. This is a deliberate design choice: it allows banks to adopt the ledger without overhauling their existing settlement infrastructure, compliance frameworks, or risk management systems.
The two-step model creates a temporal gap between the moment a customer payment clears on the shared ledger and the moment the underlying interbank obligation settles through traditional rails. During that gap, one bank has extended credit to another.
This is not a new concept — it mirrors how correspondent banking has always worked. But it means the ledger does not deliver atomic, instantaneous finality the way on-chain settlement on public blockchains does. The economic value of the system is speed of customer-facing execution, not elimination of counterparty exposure between banks.
According to Ledger Insights, how interbank settlement will operate at scale remains one of the two critical unresolved questions, alongside how banks lacking their own tokenized deposit capability will participate. Swift has not publicly detailed the settlement timing mechanics or whether netting will occur daily, intraday, or on some other schedule.
The tokenized deposit infrastructure market now has three distinct tracks running simultaneously:
Swift's Shared Ledger — 17 global banks, six continents, Besu-based, orchestration-layer approach leveraging Swift's 11,500-institution network. Ready for initial use July 2026. Advantage: unmatched network reach.
The Clearing House (TCH) — 17 U.S. banks including JPMorgan, Bank of America, Citigroup, Wells Fargo, and PNC. Announced June 2026, targeting H1 2027 launch. Bridges to CHIPS (which clears $1.8 trillion daily) and RTP. Advantage: direct integration with U.S. domestic payment rails and existing clearing relationships.
JPMorgan Kinexys — Live in production since 2019 (originally as Onyx/JPM Coin). Processes tokenized payments for institutional clients. Has expanded from its permissioned Ethereum instance to Coinbase's Base network, driven by client demand. Advantage: operational track record and single-entity execution speed.
Additionally, Partior — a joint venture backed by DBS, JPMorgan, and Temasek — operates production tokenized deposit settlement in USD, EUR, and SGD. Partior's model differs from Swift's in that it handles both the payment movement and the interbank settlement on-chain.
The fragmentation is notable. A bank like Citi or Wells Fargo appears in both the Swift pilot and the TCH consortium. JPMorgan runs its own Kinexys platform while backing Partior and participating in TCH. The industry has not converged on a single standard. Whether Swift's network effects will consolidate these efforts or whether multiple rails will coexist is an open question.
Swift's existing network already delivers 75% of cross-border payments to beneficiary banks within 10 minutes, according to the organization's own data. However, according to Swift, 80% of a transaction's average journey time is spent in the "last mile" — the period between arrival at the beneficiary institution and crediting to the end account.
The economic friction in cross-border payments is substantial. According to the Bank for International Settlements, cross-border transactions carry an average cost of 6.5% of transaction value for consumer payments. For business-to-business transfers through banks, fees range from 2% to 7% when accounting for transfer charges, FX spreads, and intermediary markups. In 2023, U.S. e-commerce firms experienced an 11% failure rate in cross-border transactions, resulting in an estimated $3.8 billion in lost sales, according to PYMNTS Intelligence data.
The 24/7 availability of tokenized deposits addresses the time-zone problem but not the cost problem directly. Reducing intermediary hops and enabling direct bank-to-bank value transfer on a shared ledger could compress fees over time, but the initial pilot maintains existing settlement infrastructure and, by extension, existing fee structures.
PYMNTS Intelligence data shows 36% of internationally active small-to-medium businesses now prefer fintech providers for cross-border payments, up from 30% previously, with 91% rating fintech experiences favorably. Swift's blockchain pivot is, in part, a response to this competitive pressure from non-bank payment providers.
Swift explicitly designed its ledger to support regulated stablecoins and central bank digital currencies alongside tokenized deposits. However, the decision to pilot with tokenized deposits first is significant.
Tokenized deposits preserve the existing commercial banking model. The issuing bank retains the deposit relationship, the associated lending capacity, and the customer data. Stablecoins — whether issued by banks under the GENIUS Act framework or by non-bank entities like Circle or Tether — disintermediate that relationship by moving value onto a bearer instrument.
The Clearing House's parallel initiative carries the same emphasis on tokenized deposits over stablecoins. As Fireblocks noted in its analysis of the tokenized deposit landscape, banks are building tokenized deposit networks specifically so that "stablecoins stop stealing treasury work." The framing is defensive: tokenized deposits are the banking system's answer to the $180 billion+ stablecoin market.
If Swift's 11,500-institution network adopts tokenized deposits as a standard payment instrument, the addressable market for non-bank stablecoins in institutional cross-border payments narrows considerably. The question is execution speed and whether the two-step settlement model can compete with the atomic finality offered by stablecoin transfers on public chains.
Swift's shared ledger is live for initial use as of July 9, 2026, built on Hyperledger Besu (EVM-compatible), with 17 banks across six continents preparing to pilot tokenized deposit transactions.
The architecture is an orchestration layer, not a settlement engine. Customer-facing payments move 24/7 on-chain; interbank settlement remains off-chain through conventional RTGS and correspondent banking.
Three competing tokenized deposit initiatives are now running in parallel: Swift (global, 17 banks, live), The Clearing House (U.S., 17 banks, H1 2027), and JPMorgan Kinexys (single-entity, live since 2019). Partior operates a fourth track with on-chain settlement.
HSBC is the first confirmed integration, connecting its Tokenised Deposit Service directly to Swift's ledger.
The 9-month build cycle from announcement to readiness is fast by financial infrastructure standards, suggesting urgency in Swift's response to non-bank payment competition.
Tokenized deposits are the banking system's strategic response to stablecoins. Both Swift and TCH prioritize bank-issued digital money over third-party stablecoins, preserving existing deposit relationships and associated revenue streams.
Unresolved questions remain around interbank settlement timing, netting schedules, and how banks without their own tokenized deposit capabilities will participate.
Swift's blockchain ledger represents the largest incumbent financial messaging network placing a direct stake in on-chain infrastructure. The choice of Hyperledger Besu aligns the system with Ethereum's developer ecosystem while maintaining permissioned access controls. The 17-bank pilot covers major global payment corridors, and HSBC's immediate integration suggests at least some institutions have been building toward this moment.
The economic logic is clear: Swift processes $150 trillion annually across 11,500 institutions. If even a fraction of that volume migrates to tokenized deposit rails, the resulting on-chain flow dwarfs the entire current DeFi ecosystem. The question is not whether institutional demand exists — it is whether a two-step model with off-chain settlement delivers enough improvement over existing rails to justify adoption, particularly when competing initiatives from TCH and JPMorgan offer alternative paths.
For the broader Web3 ecosystem, this announcement crystallizes a pattern: the largest financial institutions are adopting blockchain infrastructure — permissioned, EVM-compatible, enterprise-operated — not to participate in DeFi, but to build parallel systems that serve the same functions with different trust assumptions. The value capture will flow to the institutions that control the network, not to token holders or protocol treasuries. This is blockchain as plumbing, not as a financial revolution.