DFNS now tells you about incoming transactions earlier. With the new Included Transaction API, a wallet receiving funds no longer goes straight from nothing to confirmed. The moment an incoming transaction is included in a block, DFNS records it in a new Included state and can notify you through a new webhook, so you see money on the way before it has fully settled.
Incoming funds were invisible until they confirmed
Receiving onchain has, until now, been close to binary. A wallet shows no sign of an incoming transfer, and then, once the transaction has enough confirmations, it appears as confirmed. The window in between, where the transfer has been broadcast and even placed in a block but has not yet cleared your confirmation threshold, was invisible.
For an institution, that blind spot has real costs. Support and operations teams cannot see that a customer’s deposit is on its way. Dashboards stay empty while funds are minutes from arriving. Reconciliation can only begin at confirmation. And anyone watching for an expected inbound payment has no signal until the very end. Traditional banking has shown customers funds in flight for decades. Onchain, that intermediate state was simply not surfaced.
A Included state for incoming transactions
The Included Transaction API introduces an intermediate state for incoming transactions, called Included, and a webhook to notify you when a transaction reaches it.
It helps to be precise about where this sits in a transaction’s life. A transaction is first broadcast to the network and waits in the mempool, verified but not yet in a block. A validator then selects it and includes it in a newly produced block. It is only considered confirmed once it has reached the depth, or finality, your operation relies on. The new Included state captures that middle moment: the transaction is in a block, no longer just waiting in the mempool, but not yet confirmed.
Two things make this usable. First, Included is recorded as a new event in the wallet’s transaction history, so the incoming transfer is visible in the record, not only at confirmation. Second, a new webhook fires when an incoming transaction reaches Included, so your systems are notified in real time rather than polling or waiting for the confirmation event. The confirmation event you already rely on continues to fire exactly as before. Included is added in front of it, not in place of it.
What this unlocks
- See incoming funds sooner. Know the moment an inbound transfer lands in a block, not only when it finally confirms.
- Show funds in flight to users. Reflect an incoming deposit as arriving, the way account holders expect from modern finance, with finality tracked separately.
- React in real time. Trigger workflows, notifications, and back-office updates the moment a transfer is
Included, through the new webhook, rather than waiting or polling. - Start reconciliation earlier. Surface the inbound event the moment it is in a block, with the confirmation following as today.
Part of Transaction Management on DFNS
The Included Transaction API extends DFNS Transaction Management, which already tracks the full lifecycle of outbound transactions, construction, broadcast, inclusion, confirmation, and the tools to speed up, replace, or cancel them. Bringing the same lifecycle visibility to incoming transactions closes the loop: whether value is leaving or arriving, you have a complete, real-time view of where every transaction stands, on one platform.
Get started
- Learn more about onchain core banking: dfns.co
- Explore the platform and documentation: docs.dfns.co
- Talk to our team: sales@dfns.co