TRP is a lean open-sourced protocol developed by Standard Chartered, ING, BitGo, and others to ensure quick and easy data transfer in accordance with the Travel Rule requirements.

How TRP protocol works

The Travel Rule Protocol (TRP) uses RESTful API to send and receive data between Virtual Assets Service Providers (VASPs) and other regulated entities.

The data is HTTPS-encrypted, so it is only available to Sumsub and the originator/beneficiary VASP.

Information exchange via TRP

The information exchange can be carried out in several ways. For incoming transactions there are two options:

• Option 1. When the incoming data exchange transaction is created, the LNURL (address that can be used by the counterparty VASP to contact Sumsub and send the data) is generated. The Beneficiary VASP (Sumsub Client) can pass this LNURL to its Client (Beneficiary) to provide to the Originator information and send the data in accordance with the Travel Rule requirements.
• Option 2. In case the VA transaction has already been completed, the Client sends Sumsub the Originator wallet address, transaction number, and all the necessary information. Sumsub will try to find the Originating VASP and contact it.

For outgoing transactions, Sumsub receives a LNURL from the Client (Originating VASP), obtained from its customer (Originator). Originators can also receive the LNURLs generated by the Beneficiary VASPs from their counterparties (Beneficiaries). Then Sumsub performs all necessary checks, such as sanctions screening, crypto transactions check (if applicable), etc. After the inquiry is approved or rejected, the respective callback is sent to the client.