IBM links Digital Asset Haven to Swift blockchain ledger
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.
- IBM connects Digital Asset Haven clients to Swift’s blockchain ledger through a new beta integration.
- Seventeen banks are piloting Swift tokenized deposits, with final settlement continuing through existing financial systems.
- On-premises beta keeps digital asset operations inside client data centers using IBM Z or LinuxONE.
- ISO 20022 messaging lets institutions instruct tokenized deposit transactions without adopting blockchain-specific operational workflows directly.
- IBM says its on-premises design supports stablecoins, tokenized deposits, HSM security, and cold storage operations.
IBM said on Sept. 24 that Digital Asset Haven clients can access permissioned blockchain networks, including Swift’s ledger, through a beta ISO 20022 Messaging Adapter. The company said 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.
IBM connects tokenized deposits to 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 bank systems. IBM said digital assets can move around the clock through the ledger before final settlement occurs through existing banking infrastructure.
Swift’s architecture 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 instead of replacing their payment messaging stack.
Swift ledger has 17 banks preparing 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.
Participants include 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 related coverage, crypto.news reported on the Swift ledger rollout involving 17 global banks after the infrastructure entered its first deployment phase in July.
Crypto.news later reported that HSBC and Standard Chartered completed a live interbank transaction through the ledger in August. The transaction connected the banks’ separate tokenized deposit systems while final settlement remained on existing banking rails.
Digital asset infrastructure provider Taurus has connected its custody and tokenization products to the same Swift infrastructure. Crypto.news reported in August that Taurus integrated with Swift’s tokenized deposit ledger, giving banks another route into the network.
IBM 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 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.
IBM said qualifying configurations can achieve 99.999999% availability, but the company specifies that the figure comes from internal measurements and projections using a defined hardware and software configuration. IBM states that other configurations may produce different availability results.
Digital Asset Haven originally launched with support for more than 40 connected public and private blockchains. Its existing services include programmable transaction approvals, wallet controls, HSM and multiparty-computation key management, compliance integrations and transaction monitoring.
IBM and Swift move from testing toward bank deployment
Demand for payment modernization remains part of the companies’ case for the new infrastructure. J.P. Morgan Payments reported that 93% of financial institutions are modernizing their payments infrastructure, citing investment in core systems and new payment products among current priorities.
Tom McPherson, general manager of IBM Z and LinuxONE, said financial institutions increasingly need traditional and tokenized assets to operate alongside one another. He said IBM’s Swift connection and on-premises deployment are intended to give regulated institutions more control over digital asset operations. IBM cautioned that statements concerning future product direction “are subject to change or withdrawal without notice.”
Institutions interested in the on-premises beta can currently join IBM’s waitlist. IBM’s product page describes SaaS, Hybrid SaaS and on-premises deployment as options for financial institutions operating wallet, transaction, governance and key-management services.
Swift is scheduled to discuss the ledger’s implementation during Sibos 2026, running from Sept. 28 through Oct. 1. Its agenda includes sessions on interoperable tokenized money, transaction capabilities and the ledger’s implementation roadmap.