Swift Advances Blockchain Ledger Into Pilot Use for Bank Cross-Border Payments

What happened

On July 9, the Brussels-based global bank messaging network Swift announced that its blockchain shared ledger was ready to enter an initial-use phase. 17 banks from six continents are preparing a real-time transaction pilot, with the first use case being bank tokenized deposits to support 24/7 cross-border payments.

This is neither a new public blockchain open to the public nor a move for banks to immediately abandon existing correspondent banking networks. Under Swift’s design, the ledger is more like a coordination system layered on top of existing payment infrastructure: it records, orders and validates transaction commitments between financial institutions, embeds execution rules through smart contracts, and then connects tokenized deposits at different banks. Swift previously disclosed that the system uses an architecture compatible with the Ethereum Virtual Machine and is built on open-source infrastructure such as Hyperledger Besu.

Participating banks include Citi, HSBC, UBS, BNP Paribas, Standard Chartered, MUFG, ANZ and Lloyds Banking Group, among others. Swift said the project took about nine months to move from conceptual design to initial use.

Why it matters

Cross-border payments have long had a timing problem: money flows depend on multiple institutions, multiple time zones and different settlement windows. Even if a payment instruction can be sent within seconds, the final availability of funds, compliance checks and ledger confirmation can still be interrupted by weekends, holidays or bank business hours.

Tokenized deposits attempt to represent bank deposits as programmable digital value, while the blockchain ledger is responsible for letting different institutions share the same transaction state. If the pilot can run stably, banks may gain more continuous cross-border liquidity management capabilities without changing the nature of deposits or regulatory responsibilities. This is also an important way for traditional financial institutions to respond to stablecoins and other on-chain payment networks: not by simply copying crypto assets, but by putting blockchain into existing identity, compliance, messaging and clearing control systems.

For market infrastructure, Swift’s move is more notable than a single bank launching tokenized deposits. Swift connects about 11,500 financial institutions, covering more than 200 countries and regions. If it becomes the entry point between multiple forms of tokenized value, the competitive focus could shift from “who issued the digital currency” to “who can make different ledgers interoperate securely.”

What still needs watching

First is the practical scope of pilot transactions, including the number of participating banks, currencies covered, settlement timing and whether exceptions and refunds can be handled. Second is the legal finality of tokenized deposits: completion on the ledger does not automatically mean all jurisdictions recognize the funds as finally settled. Third is interoperability. Swift emphasizes that it will connect existing and emerging networks, but how different banks’ liabilities, compliance standards and on-chain permissions will be unified still needs to be tested in real transactions.

Therefore, the more accurate current judgment is: blockchain infrastructure for bank cross-border payments has moved from proof of concept into a pilot phase, not yet completed commercial replacement. The real inflection point will come when the pilot can be converted into measurable improvements in liquidity efficiency, lower operating costs and more stable around-the-clock service.

Sources

• Swift: Blockchain ledger ready for initial use, 17 banks advance tokenized cross-border payments pilot
• Swift: Technical note on digital payment infrastructure and shared ledger
• Reuters: Swift launches blockchain ledger to enable banks’ around-the-clock cross-border payments
• International Monetary Fund: Financial market infrastructure in a tokenized economy