Expanding globally, many Virtual Asset Service Providers (VASPs) operate through region-specific entities. In these cases, Umbrella VASP support is crucial for Travel Rule compliance — it links all subsidiaries under a single parent VASP, streamlining the process of managing transactions.

For example, Good Exchange Turkey and Good Exchange EU may be linked under the main Good Exchange VASP. Even if an originator (end user) is unable to identify a specific entity, the transaction will be routed correctly to the appropriate VASP within the parent-subsidiary system.

How Umbrella VASP support works

Umbrella VASP support lets you group multiple legal entities of the same company under one brand. This way, counterparties do not need to know which specific entity services a given user.

For example, Good Exchange can operate through several regional entities, such as Good Exchange EU, Good Exchange Singapore, and Good Exchange US. The flow works as follows:

1. Each entity is set up separately. Each entity is created and configured in Sumsub with its own dedicated license key.
2. The entities are grouped under one brand. In the VASP directory, these entities appear under one brand name: Good Exchange.
3. Counterparties select the brand, not the entity. When a transaction is initiated, the originator or the originating VASP selects the counterparty VASP by its brand name, Good Exchange, instead of choosing a specific legal entity.
4. Sumsub handles the routing. Sumsub automatically routes the Travel Rule data and the transaction to the appropriate entity within the group.

As a result, originators and originating VASPs only interact with the brand name, while Sumsub ensures that the Travel Rule data reaches the correct legal entity behind it.

Create Umbrella VASP

The VASPs are only linked by the Sumsub team. To create an Umbrella VASP for your entities, contact your Customer Success Manager.

Deposits: inbound Travel Rule data transfer logic

Inbound Travel Rule data transfer (deposit) behavior varies depending on whether a VASP is integrated within the Umbrella VASP structure.

If a VASP is linked under the Umbrella VASP structure, the process works as follows:

1. The counterparty sends the Travel Rule data to the main VASP and it will automatically redirect the information to all affiliated VASPs for the wallet ownership confirmation.
2. The affiliated VASP that confirms ownership first will then proceed with the data-sharing step.

If a VASP wants to receive inbound Travel Rule data transfers without the redirection logic, it is necessary to upload the wallet addresses belonging to the VASP’s users to the Wallet Address Book.