Why SWIFT\'s blockchain ledger never touches actual funds

SWIFT\'s blockchain shared ledger is officially launched, but the core design is to do nothing.

On July 9, SWIFT officially launched a blockchain-based shared ledger, and 17 banks are ready to launch pilot projects. It is worth noting that this ledger does not handle actual fund transfers, but only records payment commitments between banks. Final settlement is still completed through the existing RTGS system and agent bank channels. This design allows the entire system to be built in nine months without requiring any changes to the compliance framework.

How can the payment be completed if the funds are not moved?

Its operating mechanism is divided into two independent levels. When a customer\'s payment occurs at night or on a Saturday, the ledger verifies the binding commitment between the paying bank and the receiving bank, and the receiving institution can immediately account for the customer. Debt clearing between banks will wait until the RTGS system and agent accounts are reopened. Banks can transfer funds for customers, including overnight and weekend, before final settlement is completed through existing systems.

This split is the fundamental difference between the SWIFT solution and various stablecin channels and public chain settlement. Custody, private keys and actual deposits are always kept within the commercial bank. SWIFT coordinates work processes rather than holding value-which means compliance officers at pilot banks use exactly the same counterparty controls when reviewing tokenization transactions as they handle traditional payments. The cooperative organization successfully solved its own regulatory problems by not creating regulatory problems.

Level Occurrence content Occurrence place Tokenized deposit Issue and hold Each bank\'s own ledger in digital banking currency Payment commitments Record and verify SWIFT Shared ledger 7×24 hours a day (Hyperledger Besu, EVM compatible) Customer debit Payee immediately receives funds Paying bank, based on the aforementioned commitments Final settlement Inter-bank debt clearing RTGS/correspondent bank system, Pending re-opening

Nine months: From the release of Sibos to the launch of infrastructure

The construction speed itself deserves attention. SWIFT announced the ledger at the Sibos conference in September last year, completed the design phase in March, and partnered with Consensus sys to develop the platform. More than 30 financial institutions participated before the project was advanced to a pilot with 17 banks. For an organization serving more than 200 countries and more than 11500 institutions, the nine-month pace is closer to the pace of fintech companies than to interbank alliances-and the design of only recording commitments explains why: Member banks \'settlement systems do not require any modifications.

The list of pilot banks includes Citigroup, HSBC, UBS, BNP Paribas, DBS Bank, Standard Chartered Bank, Mitsubishi UFJ Financial Group, Overseas Chinese Bank, Itau United Bank, First Abu Dhabi Bank and Lloyd\'s Bank, etc. Thierry Chilosi, chief commercial officer at SWIFT, called the launch a \"key milestone for regulated digital assets.\" Although the infrastructure is now operational, the first transactions have not yet occurred.

Criticism of the \"Half Blockchain\": The flip side of the speed advantage

enables fast-build designs and also defines the upper limit of the system. Since actual funds are still cleared through traditional infrastructure, the overall settlement speed is limited by the slowest link in the chain-commitments recorded at 2 a.m. on Sunday, which still constitute a person\'s book exposure before the RTGS window opens on Monday. Critics argue that SWIFT\'s entire architecture is nothing more than embedding itself into technology originally designed to remove intermediaries and becoming a coordination node. Private alternatives such as JPMorgan\'s Kinexys have already cleared sovereign dollar transactions in commercial operations without the need for SWIFT intervention throughout the process.

The second limitation is more practical than conceptual. Since the ledger is purely an orchestration layer, each participant needs to have their own tokenized deposit capabilities. Although HSBC has connected to its tokenized deposit service, the process of integrating from infrastructure to banks has historically been slow. The 17 banks listed in the press release are different from the 17 banks that actually run actual business.

One point that critics underestimate is: Where are the actual delays in cross-border payments? About 75% of payments on the SWIFT network reach the collecting bank within 10 minutes, so message transmission is never a bottleneck. The real bottleneck lies in the operating calendar of the settlement system. The commitment layer is attacking this calendar without having to wait for the central bank to run RTGS on the weekend.

Competitors Network is building a closed version of the idea

Seventeen U.S. banks, led by JPMorgan Chase, Bank of America, Citigroup and Wells Fargo, plan to launch a tokenized deposit network operated by U.S. clearing houses in the first half of 2027. Japan\'s three major banking groups also announced plans to launch a joint stablecoin platform before fiscal year 2026.

Project Supporters Status SWIFT Shared Ledger SWIFT, Consensus, 17 pilot banks Initial use launch in July 2026 Tokenized Deposit Network JP Morgan Chase, Bank of America, Citigroup, Wells Fargo +13 Banks plans to be operated by U.S. Clearing House in the first half of 2027 Kinexys JP Morgan Chase is already commercially operating

The difference between these projects lies in access rights, which in turn stem from the commitment structure. Kinexys belongs to one bank, and the clearinghouse network will belong to six U.S. giants. SWIFT requires members to reuse their existing secure connections rather than manage dozens of separate blockchain endpoints-the only feasible version for a medium-sized bank in Sao Paulo or Sofia. Whether tokenized settlement becomes standard interbank infrastructure or a private toll road depends largely on which model reaches scale first.

MiCA and choosing a bank currency instead of a stablecoin

Banks chose tokenized deposits in this experiment largely because the regulatory treatment of commercial bank currencies is already established law, which contrasts with the fact that the classification of stablecoins is still changing under frameworks such as the EU MiCA. SWIFT plans to expand the functionality and usability of ledgers after controlled launches, with programmatic money and AI-driven commerce listed as end use cases. The EVM-based payment commitment execution foundation provides the technical foundation for these roadmap projects rather than just a slide show. The more immediate test is the speed with which the first batch of actual transactions and the remaining pilot banks build the ability to token deposits-which determines whether a live platform can become a liquidity platform.