Swift Shared Ledger Moves Toward Live Tokenised Deposit Transactions

Swift prepares its shared ledger for initial use

Swift has advanced its blockchain-based shared ledger to the next stage of development, nine months after announcing the project. According to the financial messaging cooperative, 17 early adopter institutions are preparing to pilot live transactions using tokenised deposits.

The ledger is intended to help banks coordinate digital-value transactions while continuing to use established financial infrastructure. It records and validates interbank payment commitments, giving participating institutions a shared view of liabilities and funding commitments before settlement takes place.

The ledger is designed as an orchestration layer rather than a replacement for central-bank settlement systems or correspondent banking. Settlement can continue through existing systems outside the ledger, while the shared infrastructure coordinates the information and commitments required to process each payment.

A model for round-the-clock cross-border payments

Swift says the ledger can support 24/7 payment processing based on verifiable funding commitments. Its initial use cases focus on tokenised deposits and cross-border payments that can operate beyond conventional banking hours.

Greater visibility over funding commitments may also help institutions manage liquidity more efficiently. In conventional cross-border banking, differences in operating hours, settlement windows and intermediary processes can create delays or require banks to hold additional liquidity.

A shared record does not remove every source of payment friction, but it may improve coordination between participating institutions.

Swift reports that more than 40 financial institutions have contributed to the broader ledger initiative. The first group preparing live pilots includes 17 early adopters, showing that the project remains in a controlled rollout rather than general network-wide availability.

Connecting tokenised value with established financial rails

The initiative reflects a wider industry effort to connect tokenised money with regulated banking infrastructure. Instead of requiring institutions to move onto a separate payment network, Swift is integrating the ledger with the standards, controls and connectivity already used by banks.

This approach may lower the operational barrier to testing tokenised deposits across institutions. It also keeps participating banks responsible for their own assets, keys, funding and settlement arrangements.

Swift said future applications could extend to programmable money and agentic commerce. Those use cases remain prospective. The immediate focus is the controlled introduction of tokenised deposits and always-on cross-border payment workflows.

What the development means for cross-border payments

For businesses, the longer-term significance lies in payment availability and predictability. Cross-border operations increasingly continue through weekends and public holidays, while much of the underlying banking infrastructure still follows fixed processing windows.

Shared-ledger projects may help financial institutions support more continuous services. Practical performance will still depend on participating banks, settlement arrangements, regulatory requirements and corridor-level implementation.

For payment providers and internationally active businesses, the development is another sign that tokenisation is moving closer to regulated payment operations. Interoperability between new digital-value systems and existing local payment infrastructure will remain essential as these models scale.