Travel Rule requires originating Virtual Assets Service Providers (VASPs) to obtain the required and accurate Originator information and required Beneficiary information, and share it with counterparty VASPs (Beneficiary VASP) during or before the transaction:

Sumsub can exchange the required data about the Beneficiary and Originator via the most secure protocols on the market.
Sumsub can also contact the counterparty VASP not bound to any legal arrangements with Sumsub and not using any of the supported protocols via email as described below.

The protocol to be used is selected depending on the following parameters:

Originator/Beneficiary wallet URL. For example, if the wallet has the LNURL, only the TRP protocol can be applied.
Counterparty VASP type.

Sample protocol selection scenarios

Scenario	Description
Both VASPs are Sumsub clients	If both VASPs are Sumsub Clients, the information will be sent directly by the Sumsub Protocol (API).
One VASP is a Sumsub client while its counterparty uses the TRP protocol.	If the Client is in the TRP (Travel Rule Protocol) network, and its counterparty also uses TRP, the data will be sent via the TRP network.
One VASP is a Sumsub client, while its counterparty uses a connected protocol.	If the client is in a network that is interoperable with Sumsub, the data will be sent to the other protocol through Sumsub’s bridge.
One VASP is a Sumsub client, while its counterparty is not connected to any known protocol network.	If the counterparty VASP is not in any of the connected networks, Sumsub tries to send it an email notification. Sumsub may also provide a free account to exchange the required data with the counterparty, if the counterparty is ready to transfer/receive data.