Banking · 30 October 2026
SettleMint Integrates DALP with IBM Digital Asset Haven for Tokenised Assets
SettleMint has integrated its Digital Asset Lifecycle Platform with IBM Digital Asset Haven, targeting regulated institutions and governments that manage tokenised assets, as reported by Finextra.
What happened
SettleMint has announced that its Digital Asset Lifecycle Platform (DALP) is now integrated with IBM Digital Asset Haven. The integration is aimed at financial institutions, governments and other regulated organisations that need to manage tokenised assets across their full lifecycle, according to the announcement as reported by Finextra.
The combined offering draws on IBM Digital Asset Haven's secure wallet management, transaction orchestration and policy governance capabilities. Together, these cover the operational stages of a tokenised asset and the controls that determine how transactions are executed and who is permitted to act on them.
The move reflects a wider shift among regulated bodies towards running digital assets on the same governed infrastructure as their other operations, rather than on separate, bespoke systems. The available reporting does not disclose commercial terms, deployment timelines or named customers.
Why it matters
For leaders in digital transformation, the significance lies in how the capability is packaged. Wallet management, transaction orchestration and policy governance are typically built and maintained as separate workstreams. Bringing them into a single lifecycle stack makes it more practical for institutions and public bodies to treat tokenised assets as an operational service, with defined roles, auditable transactions and rules set up front, rather than as an experimental side project.
The experience implications are less visible but significant. Staff who approve, reconcile and service these assets, and the counterparties who rely on them, will judge the system by how smoothly governance works in practice. Controls that are clear, predictable and embedded in the workflow tend to be used correctly. Controls that sit outside it tend to be worked around.
The Renascence take
Most coverage will focus on the tokenisation headline. The more consequential detail is that policy governance is being sold as part of the platform, not left to a separate compliance function.
When the rules are built into the workflow, compliance stops being a checkpoint and becomes the path of least resistance, which is a behavioural design choice as much as a technical one. Operators should map every approval, exception and handover in their digital asset processes and ask where people would naturally go if the controls got in the way. Treat policy as a designed user experience with its own testing and feedback loops, not as a back-office gate that is reviewed once a quarter. The organisations that get this right will be the ones whose staff trust the system enough to use it as intended.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in Banking
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


