SWIFT steps in directly: 17 banks circle a single chain

On the massive machine of global cross-border payments, a crucial gear is being quietly swapped out.

SWIFT, the Society for Worldwide Interbank Financial Telecommunication, announced that its blockchain-based ledger has reached the minimum viable product stage and is about to be rolled out in initial pilots. 17 banks from six continents are preparing to execute real 7x24 cross-border payments on this underlying architecture using tokenized deposits. From the first reveal at last September’s Sibos conference to being ready today, the entire process took only nine months.

This pace is almost “agile” in the traditional financial system. But speed itself isn’t the point—the point is who is stepping in, and what this new pipeline looks like.

17 pioneers

The pilot roster reads like a “old money” list of global trade finance and FX trading: Australia and New Zealand Banking Group, BNP Paribas, Bank of New York Mellon, Citibank, DBS Bank, First Abu Dhabi Bank, FirstRand Bank, HSBC, Itau Unibanco, Lloyds Bank, Maersk? Bank, Mitsubishi UFJ Bank, Oversea-Chinese Banking Corporation, Standard Chartered, UBS Group, United Overseas Bank, and Wells Fargo. More than 40 institutions participated in the early design, and the final group of 17 on deck are the pioneers. Just picking any two or three from the list can cover market-making and settlement routes across most of the world’s major currency pairs.

What they’re aiming to do is, on a permissioned chain, complete real-time recording and verification of payment commitments using tokenized deposits.

A “no-rights-seizure” chain

SWIFT’s ledger is built on Hyperledger Besu—an enterprise-grade permissioned private chain framework led by the Linux Foundation that is compatible with the Ethereum Virtual Machine (EVM). This is a permissioned network: each bank retains custody control over its own private keys and assets, with no funds centrally custodied to a public address on a chain. SWIFT only acts as the coordination layer—recording and实时 validating payment commitments between banks, while final settlement still follows the existing system. The message standards adopt the ISO 20022 that SWIFT has already mandated and pushed.

The core logic behind this design is only one thing: not interfering with banks’ existing custody and settlement finality. Banks retain asset control within the compliance framework, while the private chain only synchronizes a verifiable payment ledger among members. For licensed institutions, this means they can gain the real-time reconciliation and liquidity visibility brought by tokenization without changing the existing risk-control and compliance architecture.

This is the real need in the “old money” world—they want real-time reconciliation and liquidity visibility from tokenization, but they’re not willing to cede even a single cent of risk-control authority.

Narrative captured

Tokenization, programmable money, 24/7 real-time liquidity—these terms didn’t initially emerge in the context of traditional financial institutions. But now, SWIFT has packaged them into its own member-based framework. The press materials also mention “agentic commerce”—a vision in which AI agents autonomously transfer value across sovereignties in a programmable way.

SWIFT’s entry objectively puts a compliance stamp on tokenized payments. When the world’s most important interbank coordination network begins defining tokenization standards, this logic moves from industry experimentation into infrastructure-level discussion.

The ceiling of permissioned systems

The design of this private chain creates some natural boundaries. It is a member-based system: governance rules, access eligibility, and upgrade decisions are jointly controlled by SWIFT and member banks. Entities that can use this chain must be listed on the permissioned roster. That means its scope from day one is a closed loop among known counterparties.

The advantage of this architecture is obvious: extremely low compliance costs, controllable counterparty risk, and maximum regulatory visibility. The limitations are equally clear: it can’t reach market participants outside the permissioned circle, and it can’t support asset issuance and trading scenarios that have no access requirements.

Old money can eat the “efficiency” cake, but with its member-based genes, it can’t bite into the “openness” cake.

The opportunity for interoperability

There’s a detail in the technology selection that can’t be ignored: EVM compatibility.

This means the smart contract logic of this private chain, in theory, shares the same language across the entire EVM ecosystem. Right now it may just be convenient for banks to reuse existing toolchains, but over a longer cycle, it quietly leaves the door open for interoperability between different networks.

In addition, SWIFT has clearly stated that the ledger supports mutual recognition of tokenized assets, CBDCs, stablecoins, and other tokenized assets. This private chain isn’t an isolated island—it has been designed with interfaces for external connection. As for how these interfaces will be used in the future and where they’ll connect, the decision power lies with member banks and regulatory bodies.

The share of traffic migration

The 17-bank pilot is only the beginning. Next, what needs to be observed isn’t who takes sides in the narrative, but hard operational data: transaction volumes, the intraday overdraft handling logic, the settlement resilience of the permissioned network under extreme market conditions, and how large a proportion of cross-border payment traffic member banks will move to this chain in real business.

There’s another bigger question: whether the tokenized deposit standards validated by this private chain will spill over and become the industry’s default universal template.

If the answer is yes, it won’t just change the internal efficiency of these 17 banks—it will change who holds pricing power over the three words “tokenization” across the entire sector.

SWIFT’s move doesn’t overturn anything. It merely embeds a shared ledger module into the cross-border payments machine that has been running for half a century.

Whether this module ultimately runs as an isolated closed VIP channel, or sparks chemical reactions with other financial networks, no one can answer yet.