SWIFT has begun a live pilot of a blockchain-based shared ledger with 17 global banks, testing whether tokenized commercial-bank deposits and automated on-ledger workflows can accelerate cross-border settlement without moving payments outside the regulated banking system.
The July 2026 pilot marks a shift in SWIFT’s role. The cooperative has traditionally provided the messaging layer that tells banks how to move money through correspondent-banking networks, while the actual transfer and settlement take place through bank accounts and established payment systems. Its new shared-ledger design would bring parts of that coordination and execution onto a common blockchain-based platform operating around the clock.
The project targets corporate and institutional payments, where delayed settlement can tie up liquidity across time zones. A shared ledger could allow participating banks to confirm payment instructions, conduct required checks and settle funds through a single coordinated process rather than passing messages through several correspondent institutions.
Tokenized deposits sit at the center of the pilot
The pilot uses tokenized deposits as its primary settlement asset, according to SWIFT. These are digital representations of commercial-bank deposits: a claim on a regulated bank rather than a separate privately issued cryptocurrency.
That distinction shapes the project’s design. Tokenized deposits would remain liabilities of their issuing banks and, where applicable, would operate under existing rules governing deposits, including the frameworks relevant to deposit protection. They could also retain features of traditional bank deposits, such as interest accrual.
SWIFT’s approach places the banking sector’s own money at the centre of a 24/7 settlement network. It differs from models that rely on fiat-backed stablecoins, including USDC and USDT, which have grown in cross-border payments partly because they can move at any hour and support atomic settlement. Atomic settlement means the payment and the associated transfer complete simultaneously, or neither does.
Banks are pursuing similar speed while keeping the settlement asset inside the two-tier monetary structure in which central banks issue base money and commercial banks issue deposits. For lenders, that offers a route to modernize payment operations without surrendering client balances or compliance controls to external token issuers.
Besu and Chainlink link the technical components
The shared ledger is built on Hyperledger Besu, an open-source blockchain client designed for permissioned enterprise networks. Besu is compatible with the Ethereum Virtual Machine, or EVM, the environment used to run smart contracts on Ethereum and many other blockchain networks.
EVM compatibility could reduce the effort required for banks and technology vendors that have already built digital-asset tools or smart-contract applications for that standard. Rather than creating an entirely new programming environment, the pilot can draw on an established development stack while maintaining controlled access to the network.
SWIFT has also integrated Chainlink’s cross-chain interoperability protocol, known as CCIP, to connect the shared ledger with other blockchain networks. Such interoperability is a practical problem for bank-led tokenization projects. Without a common connection layer, each institution or network could need separate technical links for every other system it wants to reach.
CCIP is intended to transmit instructions and support asset transfers between networks with different technical standards. In a financial setting, the usefulness of that model depends less on crypto-style token movement alone than on whether institutions can reliably synchronize instructions, permissions and settlement conditions across separate systems.
The ledger also connects the ISO 20022 messaging standard with smart-contract logic. ISO 20022 provides structured data fields for financial transactions; embedding those fields into automated execution could allow sanctions screening, know-your-customer checks and anti-money-laundering controls to run as a payment is initiated. That could reduce manual review and reconciliation work, though the operational rules will need to meet the requirements of every jurisdiction involved.
Faster settlement comes with a liquidity trade-off
Instant or near-instant settlement changes how banks manage cash. Correspondent banking often uses netting arrangements, in which institutions offset payment obligations over a period and settle a smaller final balance later. A continuous shared ledger would tend to require pre-funding: a bank must have sufficient funds available before it can send a payment.
Pre-funding reduces the risk that a counterparty will fail before a deferred obligation is settled. It also raises the daily importance of liquidity planning, because funds parked for immediate settlement may not be available for other uses.
That trade-off will be central to whether the pilot can move beyond a technical demonstration. A system that settles quickly but requires participants to lock up substantial cash could improve certainty while increasing funding costs. Banks will need to weigh those effects against lower reconciliation expenses, fewer intermediaries and faster access to received funds.
Native bridge-token claims face a more selective market
The project may narrow some of the use cases claimed for payment-focused native tokens such as XRP and XLM, which were designed to act as bridge assets between currencies. A bank network that can issue regulated digital deposits, screen transactions and settle across borders continuously would remove the need for a volatile intermediary asset in some institutional workflows.
That does not eliminate public blockchain settlement or token-based foreign-exchange models. Many payment routes involve currencies, banks and jurisdictions that may not join the same network, and interoperability between systems remains difficult. The addressable market for bridge assets will depend on actual bank participation, available currency corridors, liquidity arrangements and legal recognition of on-ledger settlement.
SWIFT’s pilot also arrives alongside other institution-focused blockchain efforts. Canton Network, for example, has concentrated on capital-markets processes including securities issuance, asset management and derivatives. Its design seeks to synchronize data and transactions across separate ledgers while allowing firms to keep sensitive internal records private. That model is aimed at delivery-versus-payment and similar workflows where several parties need to align transaction states without exposing full books and records to each participant.
Legal finality and privacy remain unresolved tests
A live pilot does not settle the legal questions surrounding cross-border blockchain payments. Transactions recorded across nodes in multiple jurisdictions can raise disputes over governing law, regulatory authority and the location of the relevant financial activity.
Settlement finality is another issue. Banks and courts need clear rules on the moment an automated transaction becomes legally irreversible, especially where a smart-contract error, compromised system, faulty external data feed or cyberattack causes an incorrect release of funds. Code can execute a transfer immediately; legal systems must determine whether and how that transfer can be reversed.
Privacy rules add a further constraint. Financial crime controls require traceability and access to transaction information, while data-localization and privacy laws can restrict the movement of client data across borders. Zero-knowledge proofs could eventually help institutions demonstrate that a transaction meets certain conditions, such as sufficient funds or valid authorization, without exposing account balances or full customer details. The computational burden of those systems remains a challenge for high-volume global payments.
SWIFT’s test therefore places tokenized deposits in direct competition with stablecoins for a portion of cross-border settlement, while leaving the harder work—liquidity, law, privacy and interoperability—to be proven in live banking operations.
For deeper context on bank-led digital settlement, explore how stablecoins became a real settlement tool today.
Disclaimer: The content on this page is provided for general informational purposes only and does not represent the views or financial advice of Toobit. We make no guarantees regarding the accuracy or completeness of this information and shall not be held liable for any errors, omissions, or outcomes resulting from its use. Investing in digital assets involves risk; users should independently evaluate their financial situation and the risks involved. For further details, please consult our Terms of Service and Risk Disclosure.
