IBM Connects Digital Asset Haven to Swift’s Blockchain Ledger With On-Premises Beta for Banks
IBM has connected its Digital Asset Haven platform to Swift’s blockchain-based shared ledger while simultaneously opening an on-premises beta that allows regulated institutions to run digital asset operations entirely inside their own data centers. The twin announcement, made on Sept. 24, 2026, pushes tokenized deposit infrastructure one step closer to everyday bank back offices, and it does so using payment messaging standards that banks already know.
At the center of the rollout is a beta ISO 20022 Messaging Adapter. Digital Asset Haven clients can now access permissioned blockchain networks, including Swift’s shared ledger, and instruct tokenized deposit transactions using the same ISO 20022 message formats embedded in their existing bank systems. Instead of building separate blockchain-specific payment workflows, institutions can treat tokenized deposits as another message type flowing through infrastructure they already operate.
The integration builds on a platform IBM introduced in October 2025 for banks, governments and regulated companies. Digital Asset Haven was originally designed to cover wallets, transaction orchestration, governance and key management across more than 40 connected public and private blockchain networks. Its existing services include programmable transaction approvals, wallet controls, hardware security module and multiparty-computation key management, compliance integrations and transaction monitoring.
Seventeen Banks Already Preparing Live Tokenized Payments
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 cryptographic keys. Settlement can continue through real-time gross settlement systems, correspondent banking arrangements or other agreed mechanisms. The ledger itself runs an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu, with Swift operating the shared orchestration layer while participating banks keep their existing compliance processes and payment applications.
Swift declared the ledger ready for initial use in July 2026 after nine months of development involving more than 40 financial institutions. Seventeen banks from six continents entered the first group preparing live tokenized deposit transactions: 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. The initial use case centers on around-the-clock cross-border payments using bank-issued tokenized deposits. In August, HSBC and Standard Chartered completed a live interbank transaction through the ledger, connecting their separate tokenized deposit systems while final settlement remained on existing banking rails. Custody provider Taurus has also integrated with the same infrastructure.
The ISO 20022 connection matters because Swift completed the migration of its cross-border payment network to the standard in November 2025. IBM’s adapter means digital transactions plug into that operational backbone rather than replacing a bank’s payment messaging stack. Through the new integration, digital assets can move on the ledger at all hours before final settlement occurs through conventional banking infrastructure.
On-Premises Beta Removes the Public-Cloud Dependency
Alongside the Swift connection, IBM 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, removing the public-cloud dependency that has slowed some regulated institutions from adopting digital asset tooling. Banks can use the deployment for stablecoins and tokenized deposits, installing the platform on compatible hardware already in their environments or adding capacity as needed. The same architecture, APIs and workflows used in IBM’s SaaS and Hybrid SaaS products remain available on premises.
For key protection, IBM relies on Crypto Express hardware security modules embedded in its infrastructure. Confidential computing and environment partitioning separate production, testing and development systems, while the IBM Offline Signing Orchestrator supports cold-storage processes. Structured key ceremonies let organizations use formal processes for generating root certificate authority keys and produce audit documentation for regulators. IBM said qualifying configurations can achieve 99.999999% availability, though it specifies that the figure comes from internal measurements and projections using a defined hardware and software configuration, and other configurations may produce different results.
Why It Matters for Institutional Adoption
Demand for payment modernization underpins the case. 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, and that the Swift connection and on-premises deployment are intended to give regulated institutions more control over digital asset operations. IBM cautioned that statements about future product direction are subject to change or withdrawal without notice.
Institutions interested in the on-premises beta can join IBM’s waitlist. The company’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, which runs from Sept. 28 through Oct. 1, with sessions on interoperable tokenized money, transaction capabilities and the implementation roadmap.
The combined message to banks is straightforward: tokenized deposits no longer require new messaging standards, public clouds or custody handovers. Whether that convenience finally pulls tokenized money from pilot projects into production flows will depend on how quickly the seventeen participating banks convert preparation into volume. As of Sept. 24, Bitcoin trades near 84,014 USD, Ethereum near 2,666 USD and Solana near 115 USD, down 1.9%, 1.7% and 1.5% respectively over 24 hours.
Besu under the hood with an ISO 20022 adapter on top is the least sexy and most realistic institutional stack I have seen all year. Banks are not ripping out Swift messaging, they are bolting ledgers onto it.
Exactly. That 17 bank list reads like a tier-1 reunion, BNY to MUFG. Interop with existing compliance tooling is the whole game here, not raw chain performance.
every bank pitch i sat through since 2023 promised rip and replace. this is the first one that admits banks keep their Swift mailboxes and just bolt a ledger on. took the words out of my mouth
Eight nines of availability from internal projections, and they actually disclose the fine print that other configurations may differ. Credit for the honesty, most vendors would bury that caveat three pages deep.
The on-prem beta is the quiet headline. EU banks will not touch shared infra without their own key ceremonies, and the Offline Signing Orchestrator with structured audit docs sounds built precisely for that regulator conversation.
the ISO 20022 adapter is the actual story here. banks are not rebuilding rails, they are treating tokenized deposits as just another message type. that is how you get adoption
^ 40+ networks connected and they still speak ISO 20022. honestly the boring parts are what makes this survive past the pilot phase
tokenized deposits as just another iso 20022 message type means zero new training and no new reconciliation team. the boring compatibility is the whole moat here
boring is the pitch, agreed, but seventeen banks on a beta still means a decade of ISO migration scar tissue. whoever mapped existing payment messages onto ledger commitments without a rip and replace deserves the quiet promotion
boring is the pitch, agreed, but seventeen banks on a beta still means a decade of ISO migration scar tissue. whoever mapped existing payment messages onto ledger commitments without a rip and replace deserves the quiet promotion
On-premises beta is the detail most will skip. Regulated institutions spent years rejecting custody over key control, and HSM plus MPC inside their own data center answers that objection directly.
The custody debate in Europe always died on the key control question. On-prem HSM inside your own data center ends that argument before legal even opens the file.
BNY to MUFG on the beta list and barely any price reaction anywhere. big blue shipping an on-prem beta means this is years closer than the timeline spreadsheet people think
years closer is right. seventeen banks doing live prep against a beta is past the pilot deck stage, this is procurement now