IBM announced a beta connection between its Digital Asset Haven and SWIFT’s shared ledger for tokenized deposits on Sept. 24, using an ISO 20022 Messaging Adapter that lets participating institutions instruct ledger transactions through standard payment messages.
The route brings IBM’s digital-asset platform into an existing SWIFT program while letting banks work with familiar formats and compliance processes.
IBM also announced a separate on-premises beta for institutions that want to run Haven in their own data centers.
Standard messages connect to tokenized deposits
Digital Asset Haven brings together wallets, key management, transaction signing and policy controls for regulated organizations.
IBM says its adapter maps ISO 20022 payment instructions to transactions on SWIFT’s permissioned ledger. This lets institutions use the payment messages they already exchange to test transfers of bank-issued tokenized deposits.
The adapter works alongside Haven’s digital-asset controls and Hyperledger Besu connectivity. IBM says institutions already participating in SWIFT’s program have tested tokenized deposits on the shared ledger with Haven.
Participating clients can move digital assets around the clock through the ledger, according to IBM. Final settlement still uses existing mechanisms, including real-time gross settlement systems, so a tokenized-deposit transfer can move ahead of the final settlement step.
That distinction matters for banks assessing a continuous service: the beta adapter provides a route to instruct and move value on the ledger while established systems complete the underlying payment.
SWIFT said in July that its ledger was ready for initial use, with 17 banks preparing to pilot live tokenized-deposit transactions in a controlled rollout. IBM’s September announcement adds Haven as a beta route into that existing effort.
On-premises beta keeps Haven in client data centers
The second beta lets clients run Digital Asset Haven entirely inside their own data centers on IBM Z and LinuxONE, without a public-cloud dependency. IBM says both the solution layer and key-management layer stay within the client’s environment.
That gives regulated institutions direct control over the infrastructure used for custody and transaction management as they evaluate digital-asset services.
IBM says the on-premises option uses the same architecture, APIs, and workflows as Haven’s SaaS and hybrid deployments. Institutions can evaluate that deployment choice separately from the SWIFT connection.
A bank could focus on where its keys and platform operate while testing whether the messaging adapter fits its payment processes. Tom McPherson, general manager of IBM Z and LinuxONE, framed the expansion as a way for regulated institutions to participate in emerging digital-asset networks while retaining control of critical operations.
