IBM Connects Digital Asset Haven to Swift Ledger for Tokenized Deposits

IBM has added beta connectivity between IBM Digital Asset Haven and Swift’s blockchain-based shared ledger, giving financial institutions a way to instruct tokenized-deposit activity through familiar ISO 20022 payment messages instead of relying on a separate blockchain-specific workflow.

The capability is being introduced through a beta version of IBM Digital Asset Haven’s ISO 20022 Messaging Adapter. IBM said clients can use the platform to connect to permissioned blockchain networks, including Swift’s ledger, while continuing to work with existing messaging standards and bank compliance processes. The announcement also adds an on-premises beta deployment option for Digital Asset Haven, aimed at institutions that want to keep the platform and key management inside their own data centers.

In its September 24 announcement, IBM said participating institutions have already tested tokenized deposits on the Swift shared ledger using Digital Asset Haven. The release positions the new adapter as a bridge between bank payment operations built around ISO 20022 and a blockchain-based network designed for always-on movement of regulated digital value.

The adapter keeps ISO 20022 at the front end

The core change is not that banks must replace their existing payment messaging with a blockchain-native interface. IBM’s adapter is designed to let institutions instruct tokenized-deposit transfers using standard ISO 20022 messages. Those instructions can then be used with Swift’s shared-ledger infrastructure, allowing banks to preserve payment-message formats that are already embedded in their operating systems and controls.

That distinction matters because the Swift ledger is being built as an orchestration layer, not as a wholesale replacement for every part of the existing settlement system. Swift says participating banks issue tokenized deposits on their own ledgers. The shared ledger coordinates the movement of value between institutions, including overnight and on weekends, while final settlement still takes place through existing systems.

IBM describes the same boundary in its new release. Digital Asset Haven clients participating in the program can move digital assets 24 hours a day, seven days a week ahead of final settlement, while still using established Swift standards and their own compliance processes. The beta therefore focuses on interoperability between existing bank infrastructure and tokenized money rather than requiring institutions to move all payment processing onto a new rail.

The shared-ledger connection also fits Digital Asset Haven’s original role. IBM launched the platform in October 2025 for banks, governments and other regulated organizations seeking to manage digital assets across different blockchains. The product was designed to cover functions ranging from custody to transfers and settlement, with an emphasis on policy controls, security and support for regulated environments.

Swift’s ledger is moving into controlled use with 17 banks

The IBM announcement arrives after Swift moved its ledger from development into initial use earlier this year. Swift said in July that 17 banks from six continents were preparing to pilot live activity using tokenized deposits. Its first use case is focused on 24/7 cross-border payments.

Swift said the ledger moved from concept to activation in nine months. The cooperative has described the system as a secure shared record that can validate and sequence payment commitments between financial institutions. It is intended to give banks real-time visibility into those commitments and make it easier to coordinate tokenized value across institutions without creating a parallel network that ignores existing payment standards.

For the banks involved, the operating model keeps several responsibilities where they already sit. Swift provides the shared ledger and orchestration layer, while banks retain control over their assets, funding and internal environments. Final settlement can still occur through existing mechanisms, including real-time gross settlement systems or correspondent banking arrangements agreed by the participating institutions.

That makes IBM’s role narrower than operating the Swift ledger itself. Digital Asset Haven provides a way for an institution to connect its digital-asset operations and ISO 20022 messaging to that ledger. IBM said financial institutions in the program have already tested tokenized deposits through the connection. The capability is still in beta, so the announcement should not be read as a general production rollout to all Digital Asset Haven users or all Swift members.

The controlled scope also reflects where tokenized deposits sit in the broader digital-money market. Rather than introducing an unregulated crypto asset, the Swift project is centered on deposits issued by banks and designed to work alongside established compliance, credit and risk controls. The objective is to make bank money usable in an always-on digital environment while keeping links to conventional settlement infrastructure.

IBM is also pushing Digital Asset Haven on premises

Alongside the Swift connectivity, IBM is expanding Digital Asset Haven with an on-premises beta option. The deployment is designed to run entirely inside a client’s data center on IBM Z and IBM LinuxONE, without depending on public cloud infrastructure. IBM says both the application layer and key-management layer can remain in the client’s own environment.

The on-premises option extends the SaaS and hybrid deployment models IBM introduced when Digital Asset Haven launched in 2025. For banks and other regulated institutions, that adds another choice over where sensitive digital-asset operations are hosted. IBM also says the deployment can use Crypto Express hardware security modules embedded in LinuxONE and support separate production, test and development environments.

The timing links two issues that large financial institutions are dealing with at once. Banks are exploring tokenized deposits and blockchain-based payment infrastructure, but they still have to fit those systems into existing security, compliance, messaging and settlement processes. IBM is trying to position Digital Asset Haven as the layer that connects those requirements rather than forcing a bank to choose between traditional payment operations and tokenized assets.

The immediate test will be whether the beta adapter works reliably as Swift’s early-adopter banks move from trials toward live use. Swift’s ledger is already designed around interoperability with existing systems, and IBM’s addition gives Digital Asset Haven customers a route into that model using ISO 20022. The on-premises beta broadens the deployment choices at the same time, giving institutions a way to keep the supporting digital-asset infrastructure under direct control inside their own data centers.