IBM announced a beta integration that links its Digital Asset Haven platform with SWIFT’s permissioned ledger for tokenized deposits. The connection uses an ISO 20022 Messaging Adapter, allowing participating banks to issue ledger transactions through the same payment messages they already exchange. By mapping standard payment instructions to ledger actions, the solution enables continuous movement of tokenized deposits while the underlying settlement still occurs through existing real-time gross settlement systems.

On-premises deployment gives banks control over infrastructure

In addition to the cloud-based beta, IBM released an on-premises version of Haven that can run on IBM Z and LinuxONE hardware inside a bank’s own data centre. Both the platform layer and the key-management component remain within the client environment, eliminating any dependence on public-cloud providers. IBM says the on-premises deployment mirrors the architecture, APIs and workflows of its SaaS and hybrid offerings, allowing institutions to evaluate the same functionality while retaining full control over critical operations.

Participation by seventeen banks in a controlled rollout

SWIFT previously disclosed that seventeen banks were preparing to pilot live tokenized-deposit transactions on its ledger. IBM’s September announcement adds its Haven platform as a beta pathway into this effort, giving banks a familiar messaging format and compliance framework to test the new asset-tokenization workflow. The dual-track approach—cloud-based and on-premises—offers regulated institutions flexibility in how they experiment with digital-asset services.

Why it matters

The integration demonstrates a concrete step toward mainstream adoption of tokenized deposits, marrying existing payment infrastructure with emerging blockchain-based ledgers. By providing an on-premises alternative, IBM addresses regulatory and security concerns that have limited cloud adoption in the financial sector, potentially accelerating broader participation among banks reluctant to expose critical functions to public-cloud environments.