IBM connects Digital Asset Haven to Swift's tokenised-deposit ledger
Victoria Shinder2 min readIBM announced on 24 September two beta capabilities for Digital Asset Haven, its platform for banks and other regulated institutions managing digital assets. The first connects the platform to permissioned blockchain networks, including Swift's blockchain-based shared ledger. The second lets institutions run the platform entirely in their own data centres.
The Swift connection runs through an ISO 20022 messaging adapter: institutions instruct tokenised deposit transactions with standard ISO 20022 messages, so they can use existing payment formats and operational processes instead of blockchain-specific workflows. According to IBM, Swift's ledger supports bank-issued tokenised deposits, lets participating clients move them around the clock ahead of final settlement through existing systems, and keeps Swift standards and banks' own compliance processes in place. IBM says the ledger, announced at Sibos 2025 and designed with more than 40 institutions, went from concept to activation in nine months and is being used first by 17 institutions piloting tokenised deposits, some of which have tested with Digital Asset Haven.
The on-premises option runs on IBM Z and LinuxONE with no dependency on public cloud infrastructure. Keys are protected by the Crypto Express hardware security modules built into LinuxONE, with confidential computing separating environments, and key ceremonies produce documentation that clients can present to regulators. IBM says the architecture, APIs and workflows match its SaaS and hybrid versions, so clients can move between deployment models without rewriting applications.
What it means
Tokenised deposits are the banks' answer to stablecoins: the money stays a liability of a regulated bank, but moves on a ledger at any hour. Connecting through ISO 20022 matters because it lets a bank treat the ledger as another payment rail rather than rebuilding its operations around a blockchain.
The on-premises option speaks to a different concern. Many institutions are wary of running custody and key management on someone else's cloud, and supervisors ask where keys live and who can reach them. Both features are betas; the pilot with 17 institutions is the part to watch for evidence of use beyond testing.