# Sumsub Integration

> Sumsub joins Notabene as a Travel Rule provider on DFNS. Outbound transfers that match a Travel Rule policy are checked with the counterparty VASP before they are signed, fail closed when the exchange does not complete, and leave a complete record for the supervisor.

- Author: Chris Sutton (CPO)
- Published: 2026-11-17
- Category: Product
- Canonical: https://dfns.co/article/sumsub-integration/
- All DFNS articles: https://dfns.co/llms-full.txt

---

DFNS now integrates Sumsub for Travel Rule compliance. Institutions that run their verification and compliance program on Sumsub can now use it for Travel Rule exchanges directly inside the DFNS Policy Engine, alongside [Notabene](https://www.dfns.co/article/notabene-integration), which DFNS has supported since 2025. The integration runs before a transfer is signed, so a transfer that has not cleared the Travel Rule never reaches the chain.

## What the Travel Rule asks

The Travel Rule is the requirement, set by the Financial Action Task Force and written into law in the European Union under the Transfer of Funds Regulation and in most other major jurisdictions, that a virtual asset service provider sending a transfer shares originator and beneficiary information with the receiving provider before the funds move. The FATF standard lets jurisdictions set a threshold of USD/EUR 1,000 below which only a reduced set of information is required; the European Union applies the rule to every transfer between providers, whatever the amount. In practice, a transfer out of a regulated institution's wallet has to be matched with a counterparty VASP and the required data sent in a standard format called IVMS101, in advance of or alongside the transfer, and the institution must not execute the transfer before it has done so. DFNS goes one step further and waits for the counterparty's acceptance, recorded against the transfer, before anything is signed.

Doing that by hand does not scale, and doing it after the transfer is a breach. It has to sit inside the transaction flow, at the moment the institution decides whether to sign.

## How the integration works

Sumsub is configured once, from the Integrations page in the dashboard, with the credentials Sumsub provides and the institution's own VASP identifier. The secrets are encrypted at rest and never returned by the API.

From then on, a Travel Rule transaction prescreening policy can name Sumsub as its provider. When a transfer matches the policy, the flow runs in four steps.

The evaluation is created. DFNS submits the transfer to Sumsub with the beneficiary wallet, the beneficiary VASP or an indication that the destination is an unhosted wallet, and the originator and beneficiary data the institution supplied in the transfer request, in IVMS101 format, encrypted by the institution with Sumsub's public key so that DFNS never reads it. The transfer waits.

Sumsub exchanges with the counterparty. Sumsub handles the exchange with the beneficiary VASP through its network and notifies DFNS as the status of the exchange changes. Every notification is verified against Sumsub's signature over the raw message before it is accepted, and every one is recorded in an audit table.

The policy resolves. When the counterparty accepts, the evaluation clears and the transfer proceeds to signing. When the exchange is rejected, or when it has not completed by the deadline the policy allows, the evaluation fails closed and the transfer is blocked. DFNS also tells Sumsub the exchange has been canceled, so no stale request lingers on either side.

The record is completed. Once the transfer is confirmed onchain, DFNS attaches the transaction hash to the Travel Rule record at Sumsub, so the exchange and the settlement are tied together for the regulator.

## Designed to fail closed

One design decision is worth stating plainly. In this first version, a Travel Rule exchange that does not reach acceptance, for any reason, blocks the transfer. That includes a counterparty rejection, an exchange stuck waiting for information the institution did not supply, and a notification from Sumsub that never arrives. A fail-closed timer is the backstop. If nothing resolves the evaluation by the deadline, it fails, and the transfer does not go.

We choose safety over availability. A legitimate transfer that is blocked can be investigated and retried. A transfer that should have been blocked and was sent cannot be recalled. The next version will reduce false blocks with status polling, handling of counterparty requests for additional information and recovery of exchanges in flight. The order of those two things is deliberate.

## What it means for institutions

For institutions already on Sumsub, the Travel Rule stops being a separate workflow. The same provider that runs their onboarding and monitoring now runs their Travel Rule exchanges, inside the same policy framework that governs every other transfer on DFNS. Approval quorums, limits, allowlists, KYT screening and the Travel Rule evaluate together, before signing, with one audit trail.

For institutions choosing a provider, DFNS now offers two. Notabene and Sumsub both run through the same Policy Engine rule, so the choice is about network coverage and existing relationships rather than integration effort. Switching providers is a policy change plus a change to the travelRule object in your transfer requests, rather than a project.

For compliance teams, the record is the point. Every evaluation, every notification from Sumsub and every outcome is stored with the transfer it belongs to and tied to the onchain hash once settled. When a supervisor asks how a transfer cleared the Travel Rule, the answer is a record rather than a reconstruction.

## Getting started

The Sumsub integration is available now for outbound transfers. Configure Sumsub from the Integrations page in the dashboard with the credentials from your Sumsub account and your VASP identifier, then select Sumsub as the provider in a Travel Rule transaction prescreening policy. Inbound transfers and the recovery features described above follow in the next version.

* Learn more about onchain core banking: [dfns.co](https://dfns.co/)  
* Explore the platform and documentation: [docs.dfns.co](https://docs.dfns.co/)  
* Talk to our team about Travel Rule compliance: [sales@dfns.co](mailto:sales@dfns.co)