Wyden Integration

DFNS and Wyden are now integrated, giving banks and brokers a straight-through path from trade execution to settlement, with a configurable boundary between the trading layer and the core banking platform beneath it.

Clarisse Hagège
Clarisse Hagège
| 6 min read

DFNS is now integrated with Wyden, the institutional trading platform for digital assets. Banks, traders, and brokers building a digital asset offering can run the trade lifecycle on Wyden, price discovery, best execution, netting, and trade accounting, with DFNS as the core banking platform beneath and around it. The result is straight-through processing from the moment a client places an order to the moment assets settle in governed wallets, with no manual stitching in between, and with the freedom to decide which platform runs which part of the operation.

Wyden, the institutional trading platform for digital assets

Wyden is a unified trading and operating layer that banks and brokers use to run digital asset trading across the full trade lifecycle. Its platform brings together an end-to-end OEMS with Smart Order Routing and best execution across a connectivity network of 65+ exchanges, brokers, and OTC desks, treasury and risk management across counterparties, a settlement engine covering both real-time and end-of-day netted routines, and accounting and reconciliation that maintain a consistent internal book of records.

It is trusted where the bar is highest. Banks and brokers including Garanti BBVA Kripto, flatexDEGIRO, Luzerner Kantonalbank, Banque Delubac & Cie, InCore Bank, and Baader Bank run their digital asset trading on Wyden. The platform operates within ISO/IEC 27001 and SOC 2 environments and positions as an ICT third party under DORA, enabling MiCA-regulated services for European financial institutions. For a regulated institution, that is the profile a trading layer has to have.

What the integration does

The integration wires Wyden’s trade lifecycle directly into DFNS, at every stage where trading meets the institution’s assets. The reference architecture below is one common configuration. Exactly where the boundary sits between the two platforms is a choice, and we return to it in the next section.

  1. Before a trade, Wyden’s pre-trade checks extend to the asset layer: buying power, balances, and positions are verified against DFNS wallets alongside liquidity provider balances, so an order is only accepted when the assets and controls behind it are actually in place.
  2. After a trade, settlement is automated end to end. Wyden’s settlement engine supports both real-time settlement and netted routines, calculating the net payable and receivable with each counterparty at the agreed cycle and generating the instructions, and the digital asset legs execute on DFNS. For retail brokerage models, the omnibus wallet on DFNS is updated and post-trade allocation flows to sub-ledger customer wallets, keeping client-level books accurate while settlement stays efficient.
  3. And around it all, reconciliation and reporting stay whole. Wyden reconciles client-side and street-side trades, transfers, and balances across venues and custody, and reports into the bank’s back office and core banking systems, while every operation on DFNS lands in its own complete, exportable audit trail.

Under the hood: DFNS as a native venue in Wyden

For the teams who will actually run this, DFNS appears as a first-class venue inside Wyden. Connecting is configuration. An operator creates a named DFNS connector, points it at the DFNS API, and authenticates it with a DFNS service account.

That authentication is worth pausing on. The connector is configured with a service account token, a registered credential, and that credential’s private signing key, which means every request Wyden makes to DFNS is cryptographically signed, not merely presented with a bearer token. This is DFNS’ standard model extended to machine callers: actions are signed by a credential, verified at the platform, and then still subject to the Policy Engine below the API.

One thing this private key is not: a key to assets. Wallet keys never leave DFNS’ MPC or HSM infrastructure. The connector credential authenticates API calls, nothing more, and the policies governing what those calls may do are enforced on the DFNS side regardless of who is calling.

Two operational controls round it out. Each connector carries a default network fee priority, low, medium, or high, so settlement transfers land at the urgency the treasury desk chooses, adjustable per connector. And operators define explicit rate budgets for the connection, in plain syntax like 100 requests per second or 1,000 over two minutes, along with the behavior at the limit: park requests until capacity frees, or reject them with a stated reason. Parking maximizes completion, rejecting maximizes determinism, and Wyden documents the trade-off honestly, since a parked order executes later than the market that priced it. Institutions choose per their risk posture.

Where DFNS sits, and where it can

DFNS is a core banking platform for digital assets. Transaction lifecycle management is native to it: construction, simulation, broadcast, rebroadcast, speed-up and cancel, deterministic nonce management, indexing, webhooks, and idempotency on every mutating call. So is treasury, moving and rebalancing assets across wallets, networks, and counterparties. So are Workflows, which can orchestrate multi-step settlement routines, sweeps, and approvals natively, and the Policy Engine, which enforces limits, allowlists, quorums, and roles below the API on every movement, no matter what initiated it.

What genuinely belongs in the OEMS is the trading-native work: price discovery and quoting, order management, smart order routing and best execution across venues, and the netting mathematics across trading counterparties. That is Wyden’s craft, and it is excellent at it.

Everything between those two poles is configurable. Some institutions will run the deck’s reference flow, Wyden’s settlement engine orchestrating, DFNS executing and governing each leg. Others will invert it: trades captured on Wyden, with settlement orchestration, treasury logic, and transfer scheduling living inside DFNS Workflows and Transaction Management, and Wyden consuming the results. Most will land somewhere between, and move the line as their operation matures. The integration supports the spectrum, because DFNS was built as the operating layer an institution runs its digital asset business on, not as a signing endpoint at the end of someone else’s pipeline.

Wherever the line is drawn, two things are constant. Every asset movement, however initiated, passes the Governance and Policy Engines before anything signs, so automation runs inside controls that cannot be bypassed. And underneath, security is the floor: keys protected by MPC or HSM and never assembled in one place. Deployable as SaaS, hybrid, or fully on-premises.

What this unlocks for banks and brokers

  • Launch faster. Execution and the asset layer are pre-integrated, so a digital asset offering goes live without building and maintaining the connective tissue between a trading system and its operational foundation.
  • Operate 24/7, hands off. Crypto markets do not close. With settlement flowing automatically between Wyden and governed DFNS wallets, intra-day and end-of-day routines run without manual intervention, and without giving up control.
  • Serve retail and institutional clients from one stack. Agency-model retail brokerage with omnibus efficiency and client-level sub-ledger accuracy, and institutional brokerage across deep, regulated liquidity, on the same foundation.
  • Draw the architecture your way. Put the trade lifecycle where it serves you best, in the OEMS, in the core banking platform, or split across both, and move the boundary later without re-platforming.
  • Answer the regulator with evidence. Pre-trade checks, policy-enforced transfers, reconciliation across the full lifecycle, and audit trails on both sides of the integration.
  • Trading is where a digital asset business meets its clients. The operating layer is where it meets its regulator. With Wyden and DFNS integrated, banks and brokers get both, built to institutional standards, working as one, arranged however their business requires.

Get started

Contact us