Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

SettleMint integrates token issuance platform with IBM wallet and transaction governance

The available DALP–Digital Asset Haven integration connects issuance rules, wallets and approvals for regulated institutions, but is not a report of a new bank-led securities issuance.

SettleMint has integrated its Digital Asset Lifecycle Platform (DALP) with IBM Digital Asset Haven, giving institutions an announced way to connect token issuance and asset servicing with wallet administration, approvals and policy controls. The Belgian technology company announced the integration on 29 October 2026 and says it is now available. The release describes software capabilities, not a completed tokenised Treasury issue by a named bank or evidence of production trading volumes.[1][2]

DALP governs an asset’s lifecycle, including how it may be issued, transferred and serviced. IBM Digital Asset Haven supplies a different layer: secure wallet and key management, transaction orchestration, approval workflows and governance. In the combined arrangement, a business rule about who may hold or transfer an asset can be represented separately from the process authorising a specific transaction.[1][2]

The companies say the integration can support tokenised securities, deposits, equities, Treasuries and stablecoins. These are prospective categories within the platform’s design, not confirmation that each has received regulatory approval on every blockchain. Legal entitlement and asset-specific transfer limitations still depend on the instrument, issuing entity, governing documents and jurisdiction.[1][2]

Issuance rules, transaction approval and wallet custody form distinct controls

A particular technical capability is delivery versus payment on a permissioned Ethereum Virtual Machine network. In a properly configured arrangement, the asset leg and the payment leg can be coordinated so that one does not settle without the other. The announcement does not supply independently tested failure-rate data, transaction throughput or a live comparison with established clearing and settlement platforms.[1][2]

At a glance01

DALP–IBM integration — responsibilities

DALP–IBM integration — responsibilities
ComponentRole described by developers
SettleMint DALPAsset issuance, lifecycle and transfer rules
IBM Digital Asset HavenWallet and key controls, transaction approvals
Target deploymentsRegulated institutional environments
Blockchain examplePermissioned Ethereum Virtual Machine
Settlement patternDelivery versus payment capability
Product commercial contractSeparate licences, pricing and support
Verified transaction volumesNot disclosed

The governance separation matters for broker and securities-market technology vendors. A wallet signing function should not be treated as independent investment approval, and an order-routing permission is not interchangeable with the right to issue securities. By maintaining separate eligibility and approval rules, a regulated firm can design checks for who initiated, approved and settled a digital-asset transaction.[1][2]

The press release includes a noteworthy commercial qualification: SettleMint DALP and IBM Digital Asset Haven are independent products, with separate sale, licensing, pricing and support arrangements. The partners do not guarantee one another's services merely by describing the integration. Any institution buying the combination still needs to allocate responsibility for security, operations and exception handling in contracts.[1][2]

What is newly confirmed is availability of the integration and its stated architecture. No specific institution’s completed securities issue, realised cost saving or permission to launch a new regulated financial product follows automatically from that fact. The next evidence for industry adoption would be documented production deployments and service terms.[1][2]

Follow the evidence

Sources & further reading

  1. IBM Digital Assets offering description IBM · 29 Oct 2026 · Accessed 31 Oct 2026

Report an error or submit an update