Swift readied blockchain ledger for 17-bank tokenized-deposit pilot

Swift said on July 9, 2026 that its blockchain-based shared ledger was ready for initial use, with 17 banks across six continents preparing to pilot live cross-border transactions using tokenized commercial-bank deposits. The announcement moved the project from design and implementation into a controlled activation phase. It did not establish that all 17 banks had completed production transactions on July 9.

The distinction matters. Swift was not announcing a public cryptocurrency, a retail stablecoin or a new settlement asset. It described an orchestration layer connecting tokenized deposits issued and controlled by participating banks. Customers could initiate value movements outside conventional business hours, while final settlement would still occur through existing systems.

A bank-operated route to always-on money

Swift named ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand Bank, HSBC, Itaú Unibanco, Lloyds Bank, Mashreq, MUFG Bank, OCBC, Standard Chartered, UBS, UOB and Wells Fargo as the initial pilot group.

That roster made the development institutionally significant. The participating banks spanned major financial centers and brought existing transaction-banking, liquidity-management and tokenization programs into one interoperability test. Instead of requiring every bank to adopt one issuer’s digital money, the design aimed to coordinate separate bank liabilities across a common technical layer.

Swift’s July 9 account said the ledger could let banks move customer funds overnight and on weekends and then complete final settlement through established infrastructure. That architecture preserved a boundary between the blockchain workflow and the legal discharge of payment obligations. On the evidence available on July 9, the ledger synchronized commitments and payment steps; it did not replace central-bank money, correspondent accounts or real-time gross-settlement systems.

What the ledger actually did

Swift’s implementation description, published before the July activation, said the minimum viable product used an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu. Swift would operate the shared ledger, validate funding commitments and coordinate interbank workflows. Participating banks would operate their own environments and retain authority over keys, assets, funding and settlement.

This hybrid design was the core development. Blockchain supplied a shared execution and state-coordination layer, while regulated institutions kept custody and compliance controls inside their existing operating models. For banks, the proposed benefits were faster execution, improved liquidity visibility, less reconciliation and interoperability among separate tokenized-deposit systems. Those were design goals and participant claims on July 9, not independently measured performance results.

Why July 9 mattered

The announcement marked a practical institutional response to the same demand that had helped digital-asset payment networks gain attention: value transfer without weekday cutoffs and with programmable transaction logic. Reuters characterized the project as a major attempt by mainstream banks to use blockchain infrastructure while retaining regulatory and operational controls.

The significance was therefore less about creating another tradable token than about putting distributed-ledger technology inside a network already used by thousands of financial institutions. If the pilot worked as intended, banks could offer some always-on features associated with tokenized money without moving customer balances onto a public crypto asset.

The limits were equally important on July 9. Swift disclosed no pilot transaction volume, throughput, fees, participating currency pairs, service-level results or independent security assessment. “Ready for initial use” described operational readiness and a controlled rollout, not universal availability or proven economic advantage. The July 9 record supported a milestone in regulated tokenized deposits; it did not yet prove scale, cost savings or displacement of stablecoins and existing cross-border rails.