IBM has connected Digital Asset Haven to Swift’s blockchain-based shared ledger while opening an on-premises beta that lets regulated institutions keep digital asset operations inside their own data centers. The dual announcement, made Sept. 24, extends IBM’s push to become default infrastructure for banks navigating the tokenized asset economy without abandoning the systems they already run.
IBM said Digital Asset Haven clients can now access permissioned blockchain networks, including Swift’s ledger, through a beta ISO 20022 Messaging Adapter. Institutions can use familiar ISO 20022 messages to instruct tokenized deposit transactions instead of creating separate blockchain-specific payment workflows.
The release expands a platform IBM introduced in October 2025 for banks, governments and regulated companies managing digital assets. IBM originally built Digital Asset Haven to cover wallets, transaction orchestration, governance and key management across public and private blockchain networks.
Tokenized deposits meet existing bank messaging
Through the new adapter, participating institutions can initiate tokenized deposit activity on Swift’s blockchain ledger using payment formats already embedded in their back-office systems. IBM said digital assets can move around the clock through the ledger before final settlement occurs through existing banking infrastructure.
Swift’s architecture deliberately separates payment execution from final settlement. Its ledger records and coordinates interbank payment commitments, while banks retain control of their assets, funding and keys. Settlement can continue through real-time gross settlement systems, correspondent banking arrangements or other agreed mechanisms.
The ledger uses an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu. Swift operates the shared orchestration layer, while participating banks continue using their existing compliance processes and payment applications.
IBM’s integration relies on ISO 20022, the financial messaging standard Swift completed migrating its cross-border payment network to in November 2025. The adapter is intended to let banks connect digital transactions with existing operational processes rather than replacing their payment messaging stack — a design choice aimed at adoption friction rather than technical novelty.
Seventeen banks preparing live tokenized payments
Swift declared its blockchain ledger ready for initial use in July after nine months of development work involving more than 40 financial institutions. Seventeen banks from six continents entered its first group preparing live tokenized deposit transactions, including ANZ, BNP Paribas, BNY, Citi, DBS, First Abu Dhabi Bank, FirstRand, HSBC, Itaú Unibanco, Lloyds Bank, Mashreq, MUFG, OCBC, Standard Chartered, UBS, UOB and Wells Fargo.
Swift said the initial use case centers on 24/7 cross-border payments using bank-issued tokenized deposits. In August, HSBC and Standard Chartered completed a live interbank transaction through the ledger, connecting the banks’ separate tokenized deposit systems while final settlement remained on existing banking rails.
Digital asset infrastructure provider Taurus has also connected its custody and tokenization products to the same Swift infrastructure, giving banks another route into the network. IBM’s entry adds a full-platform option on top of those point solutions.
On-premises beta removes the public-cloud dependency
Alongside the Swift connection, IBM has opened Digital Asset Haven to an on-premises beta designed for IBM Z and IBM LinuxONE systems. The deployment keeps the software layer and key-management infrastructure inside the client’s own data center, without requiring public-cloud infrastructure.
Banks can use the deployment for assets including stablecoins and tokenized deposits. IBM said clients can install the platform on compatible IBM hardware already in their environments or add capacity based on operational requirements. The same architecture, APIs and workflows used in its SaaS and Hybrid SaaS products remain available in the on-premises version.
For key protection, IBM uses Crypto Express hardware security modules embedded within its infrastructure. Confidential computing and environment partitioning can separate production, testing and development systems, while the IBM Offline Signing Orchestrator supports cold-storage processes.
Structured key ceremonies form another part of the beta. IBM said organizations can use formal processes for generating root certificate authority keys and produce audit documentation for regulators — a nod to the supervisory scrutiny that accompanies any institution touching digital assets.
Why infrastructure is winning the institutional race
The significance of IBM’s announcement lies less in any single feature than in the pattern it confirms: institutional digital asset adoption is being routed through infrastructure that looks like banking, not crypto. ISO 20022 messaging, permissioned EVM ledgers, HSM-backed key management and on-premises deployment are all answers to the same question — how do regulated institutions adopt tokenization without rebuilding their risk and compliance stacks from scratch?
Swift’s ledger reaching its first deployment phase with 17 global banks, combined with IBM providing the connective tissue, suggests the tokenized deposit use case is moving from proof-of-concept to production pipeline. The 24/7 movement of value before final settlement on traditional rails is precisely the efficiency gain banks have cited when justifying the investment.
For the broader blockchain industry, the development cuts both ways. Public networks gain validation as tokenization goes mainstream, yet the actual settlement rails being built are permissioned, institutionally controlled and largely invisible to retail users. The gap between open blockchain ethos and bank-grade infrastructure is widening, not closing.
What happens next depends on adoption: whether the 17 pilot banks move from preparing transactions to routine volume, and whether on-premises deployments convince security-conscious institutions that digital asset operations can meet their operational-risk thresholds. IBM has placed its bet that the answer is yes.
IBM putting Digital Asset Haven inside bank data centers is the most on brand move ever. regulators will love it, crypto twitter will ignore it
regulators love it precisely because keys never leave the bank datacenter. that detail alone ships this before any pure crypto custody alternative does
ISO 20022 messages on the Swift ledger instead of new rails. the boring integration is the actual news here
^ exactly. no bank is rewriting payment workflows for a ledger, they want to reuse the messages they already run
on prem beta is the smart part. keys staying inside your own DC is the only way compliance signs off on this
on-prem beta is the actually interesting part here. every bank CISO i know flat out refuses to run custody workloads in someone else cloud, ibm finally listened
the beta being on prem tells you ibm got told no enough times that it stuck. banks would rather baby a mainframe than touch shared cloud keys
The ISO 20022 Messaging Adapter is the smart move. Migration cost is what usually kills these bank integrations, letting institutions keep their existing message formats removes the whole excuse
^ exactly. sales cycle for cloud hosted custody at banks is 2 years minimum, on prem cuts that to months
swift historically moves slower than a glacier and somehow they keep shipping ledger integrations this year. pilots, then haven access. somebody over there woke up
somebody at swift finally realized that being the settlement layer beats being disintermediated. good survival instinct honestly
the iso 20022 migration in payments took a decade, no bank is volunteering for another format swap. reusing messages they already run is the only pitch that sells