IBM has connected its Digital Asset Haven platform to Swift’s blockchain-based shared ledger through a new beta ISO 20022 messaging adapter, the company announced Thursday. The move lets banks instruct tokenized deposit transactions using the same standardized payment messages they already rely on for conventional transfers, rather than adopting separate blockchain-native workflows. IBM also unveiled an on-premises deployment option for Digital Asset Haven, giving institutions more control over where and how they manage their digital asset infrastructure.
Bridging Two Worlds of Payments
Swift is the messaging backbone of global finance, connecting more than 12,500 financial institutions across over 200 markets. Its shared ledger, first announced at Sibos 2025 and built on a prototype developed with Consensys, was designed to let banks settle tokenized transactions on a blockchain-based rail while preserving the operational habits and compliance frameworks that already govern trillions of dollars in daily transfers. More than 40 financial institutions contributed to the ledger’s design, and a pilot program involving 17 institutions is testing tokenized deposit transactions on it.
Digital Asset Haven, which IBM launched in October 2025, is the company’s platform for issuing and managing tokenized assets, built in partnership with wallet infrastructure provider Dfns. Until now, it offered software-as-a-service and hybrid deployment models. The new ISO 20022 adapter effectively translates blockchain-based instructions into the messaging format banks already use, meaning a treasury or operations team can trigger a tokenized deposit transfer with the same message types used for a routine wire, without learning new systems from scratch.
It’s worth noting that final settlement of these tokenized deposits still runs through existing systems — the shared ledger and the ISO 20022 adapter sit on top of, rather than replace, the infrastructure banks already depend on. That distinction matters: this is an integration layer, not a wholesale migration to a new settlement system.
What This Means for Banks and Tokenization
The core value proposition here is familiarity. Banks have spent decades building compliance, reconciliation, and risk-management processes around ISO 20022 messaging. Asking them to run tokenized deposits through an entirely separate blockchain-specific pipeline would mean duplicating that infrastructure, training staff, and absorbing operational risk. By instead letting institutions issue standard payment instructions that resolve into blockchain-based settlement behind the scenes, IBM and Swift are lowering one of the biggest practical barriers to institutional adoption of tokenized money.
This fits into a broader pattern this year of traditional financial institutions moving tokenized deposits from pilot projects into live infrastructure. Banks in the United Kingdom have already completed their first interbank tokenized deposit transfers, while a group of Canada’s largest banks has joined forces on a shared tokenized deposit initiative. Each of these efforts, like the IBM-Swift integration, is less about introducing a new asset class to retail users and more about rebuilding the plumbing of interbank settlement so it can carry blockchain-based value alongside — or instead of — traditional ledger entries.
The new on-premises option for Digital Asset Haven addresses a separate but related concern: custody and control. Running on IBM Z and LinuxONE hardware with IBM Crypto Express hardware security modules, the on-premises deployment keeps private key management inside a client’s own data center rather than in a shared cloud environment. For banks and regulated institutions handling client assets, this kind of control over cryptographic key material is often a prerequisite for internal risk committees and regulators alike, particularly as tokenized asset activity expands into securities markets, as seen in recent moves like the NYSE’s tokenized stock arrangement with Blockchain.com and the broader regulatory groundwork laid by the SEC’s new exemption for tokenized US equities.
What to Watch Next
Several markers will indicate whether this integration moves beyond a beta feature into standard banking practice. First, watch the progress of the 17-institution pilot on Swift’s shared ledger — expansion of that participant list, or public reporting on transaction volumes and settlement times, would signal growing confidence among banks. Second, keep an eye on whether other digital asset platforms besides Digital Asset Haven adopt similar ISO 20022 adapters, since interoperability across multiple vendors would be a stronger sign of industry-wide standardization than a single company’s product update.
Third, adoption of the on-premises deployment option will be worth tracking as a proxy for how seriously large institutions treat self-custody of cryptographic keys for tokenized deposits. Finally, since this beta adapter is explicitly a bridge between legacy messaging and blockchain settlement rather than a replacement for existing settlement systems, any future announcements about deeper settlement-layer integration — as opposed to messaging-layer integration — would mark a more significant shift in how tokenized deposits actually move value between institutions.
Source: The Block
This content is for informational purposes only and does not constitute financial or investment advice.
Create a free account to comment and earn rewards.
Create account Log in