Swift is moving its blockchain-based shared ledger into live transaction pilots with 17 global banks, advancing one of the financial industry’s most closely watched attempts to connect tokenised commercial bank money with established cross-border payment infrastructure.

The Belgium-based financial messaging cooperative said the ledger is ready for initial use after approximately nine months of design and development. Banks participating in the controlled rollout will use tokenised deposits to test cross-border payments that can be initiated and coordinated around the clock, rather than being constrained by conventional operating windows, time-zone differences or weekend cutoffs.

The pilot group spans six continents and includes 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. Its composition gives Swift a geographically diverse test environment covering major financial centers in North America, Europe, Asia-Pacific, the Middle East, Africa and Latin America.

The move is important because the project is progressing beyond a conceptual demonstration. Participating institutions are preparing to process live transactions, bringing operational systems, compliance controls, liquidity arrangements and client-payment workflows into the test. Swift described the rollout as an initial controlled go-live phase and said the ledger’s functionality and availability would expand after early implementation.

The platform is not intended to replace banks’ existing deposit ledgers or transfer ownership of customer money to Swift. Instead, the shared ledger acts as an orchestration layer for tokenised deposits issued by participating banks and maintained within their own controlled environments. It records, sequences and validates interbank payment commitments, providing institutions with a synchronised view of a transaction as it progresses.

Final settlement can still occur through existing systems, including real-time gross settlement infrastructure, correspondent banking relationships or another mechanism agreed between the participating institutions. That hybrid design is central to Swift’s strategy: introduce blockchain-based coordination without requiring banks to dismantle the legal, liquidity and risk-management structures already supporting international payments.

Tokenised deposits represent claims on regulated commercial banks in digital form. Unlike many privately issued stablecoins, they remain bank liabilities and are designed to operate within the institution’s existing regulatory, capital, compliance and customer-protection framework. The Swift project therefore focuses on transferring regulated bank money rather than introducing a separate settlement asset controlled by the network.

During the pilots, banks will retain authority over their keys, assets, funding and settlement decisions. Swift will operate the common ledger and coordinate workflows, including validation of funding commitments and sequencing of interbank processes. This division of responsibility is intended to preserve institutional control while providing a shared technical environment for communicating and enforcing transaction states.

The first commercial objective is to support cross-border payments outside traditional processing hours. A corporate customer could, for example, initiate a transaction after the receiving market has closed or during a weekend. The tokenised payment commitment could be coordinated immediately on the ledger, giving the participating banks and the customer visibility into the transaction before final settlement is completed through the appropriate existing channel.

For multinational companies, the potential benefits include more predictable payment timing, improved cash-flow visibility and reduced uncertainty over when funds become available. Treasury departments frequently manage balances across multiple currencies, banks and time zones. A system capable of coordinating regulated value continuously could reduce the need to pre-position excess liquidity solely to accommodate cutoffs and settlement delays.

Banks may also gain more precise control over intraday and overnight liquidity. Traditional cross-border payments can involve several intermediaries, each maintaining its own records and operating schedule. A shared ledger does not remove every intermediary or funding requirement, but it may provide a common view of obligations and funding commitments, allowing institutions to make liquidity decisions with more current information.

The pilot will test whether those theoretical advantages remain meaningful under real operating conditions. Participants must demonstrate that tokenised deposits can be issued, transferred, reconciled and redeemed reliably across institutions with different technology stacks, regulatory obligations and internal controls. They must also determine how exceptions, reversals, sanctions screening, fraud reviews and operational disruptions will be handled when payment coordination is available continuously.

Swift has built the minimum viable product on open-source foundations using an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu. The design allows the ledger to use smart-contract functionality while operating as permissioned financial infrastructure rather than a public, permissionless cryptocurrency network.

Smart contracts can record transaction states, verify that agreed conditions have been met and enforce workflow rules. In the cross-border payment context, that could include confirming that the sending institution has made a valid funding commitment before the transaction advances. The system is also intended to create a consistent record shared by authorised participants, reducing differences between separate institutional views of the same payment.

Technical compatibility alone will not determine whether the project scales. Banks must integrate the ledger with payment engines, customer interfaces, treasury systems, compliance platforms and accounting processes. They will also need operating models for transactions that move between the blockchain environment and conventional settlement infrastructure.

Swift’s existing standards and network reach could provide an advantage. The cooperative connects more than 11,500 banking and securities organisations, market infrastructures and corporate customers in more than 200 countries and territories. Its messaging network does not itself hold funds, but it provides standardised communications and connectivity used across global financial markets.

That position gives Swift a potential role as a neutral coordinator between tokenised money platforms that might otherwise develop as separate institutional or regional systems. Banks have launched numerous blockchain networks, tokenised deposit products and digital-asset platforms, but many remain limited to transactions between clients of the same institution or a small group of approved counterparties.

Interoperability has consequently become one of the central challenges in regulated digital finance. A bank-issued token may function effectively on its native platform but provide limited value if it cannot be exchanged or used across other networks. Swift’s ledger is designed to connect participating bank environments while also remaining compatible with traditional payment rails and future forms of regulated digital value.

Several pilot banks have already developed their own tokenisation capabilities. HSBC said it plans to connect its Tokenised Deposit Service to the Swift infrastructure, while DBS cited its previous work with tokenised deposits and cross-border payments. ANZ, Citi, Standard Chartered, UBS and other participants have similarly invested in digital-asset, blockchain or always-on payment initiatives.

The diversity of the pilot group will allow Swift to test whether those institution-specific capabilities can operate through a shared layer. It may also reveal differences in how banks define tokenised deposits, manage funding, verify transaction finality and connect digital records with balance-sheet accounting.

The initiative developed from a project announced in September 2025, when Swift said it would work with more than 30 financial institutions and blockchain software company Consensys on a conceptual prototype. The original group provided feedback on architecture, governance, interoperability and possible settlement models. By March 2026, Swift had completed the design phase and begun implementing the minimum viable product.

The 17 live-pilot banks are a narrower group than the broader design coalition. That distinction reflects the transition from industry consultation to operational testing, where participating institutions must commit technology resources, compliance preparation and transaction capacity. Swift has not disclosed the payment volumes, currency pairs, customer segments or exact corridors that will be included in the initial pilots.

It has also not announced a timetable for broad commercial availability. Expansion will depend on results from the controlled phase, including system performance, operational resilience and the ability to integrate the ledger with banks’ internal environments. Questions surrounding governance, liability and transaction finality will be particularly important if participation grows beyond a limited group of early adopters.

Cybersecurity and access control will be another focus. A shared ledger used by globally significant banks must limit participation to authorised institutions, protect confidential transaction data and maintain reliable service across jurisdictions. It must also allow individual banks to preserve control over sensitive customer and liquidity information rather than exposing all transaction details to every network participant.

Regulatory treatment may vary by market. Tokenised deposits generally remain claims against issuing banks, but supervisors may differ on issues such as ledger governance, outsourcing risk, operational resilience, liquidity recognition and the legal point at which a transaction becomes final. Cross-border transactions can involve multiple regulatory regimes at the same time, increasing the importance of clear operating rules.

Swift is positioning the ledger as a complement to continuing improvements on existing payment rails. The cooperative says 75% of payments sent through its network reach the beneficiary bank within 10 minutes, with many arriving in seconds. However, rapid transmission to the beneficiary institution does not always mean that funds are immediately credited to the final customer, particularly where local processing, compliance checks or operating-hour restrictions create last-mile delays.

The blockchain project addresses a different part of the problem by providing a continuously available coordination mechanism for tokenised value. Swift is also developing a retail cross-border payments framework aimed at increasing fee transparency, ensuring full-value delivery and making settlement more predictable for consumers and small businesses.

The ledger’s initial focus remains commercial bank deposits rather than stablecoins, central bank digital currencies or tokenised securities. Swift has indicated that additional settlement assets and use cases could be considered later. Potential extensions include programmable payments, where transfers execute when predefined business conditions are satisfied, and automated commerce involving software agents.

Those future applications remain dependent on the performance of the first live pilots. The immediate test is more practical: whether large regulated institutions can use a common blockchain layer to coordinate real transactions without weakening compliance, resilience or control.

Successful implementation would not necessarily eliminate correspondent banking or conventional settlement systems. It could instead create a bridge between established financial infrastructure and emerging digital-money networks, allowing banks to add always-on services while continuing to rely on familiar legal and risk frameworks.

For the fintech sector, the project demonstrates that blockchain adoption in payments is increasingly moving toward regulated, institution-led models. Early digital-asset systems often sought to bypass banks and centralised networks. Swift’s approach uses distributed-ledger technology to strengthen coordination among those institutions, rather than removing them from the transaction chain.

The competitive implications will depend on execution. Stablecoin platforms and specialist payment companies have gained attention by offering continuous transfers and faster movement across borders. Banks will need to show that tokenised deposits can deliver comparable availability while offering the regulatory protections, credit relationships and treasury services expected by large corporate customers.

The 17-bank pilot therefore represents both a technology test and a commercial test. Swift and the participating institutions must prove that the ledger produces measurable improvements in speed, liquidity management, transparency and client experience. They must also demonstrate that those gains justify the cost and complexity of integrating another infrastructure layer into global payment operations.

If the controlled rollout succeeds, Swift could provide a common route for regulated tokenised money across a banking network that already operates at global scale. If integration, governance or settlement challenges prove difficult, the project may remain limited to selected corridors or institutional use cases. The live pilots will provide the first substantive evidence of which outcome is more likely.