Sumsub has launched its own Travel Rule protocol that lets us quickly process the data and confirm data exchange in case both VASPs are our clients.

How Sumsub protocol works

The Sumsub protocol utilizes the API and the data exchange mechanism similar to the TRP protocol. The only difference is that we use our own callbacks to deliver the data.

Information exchange via Sumsub protocol

For inbound transactions, the information exchange is carried out in the following manner:

1. The client initiates a transaction and sends a POST request with this API method.
2. Sumsub verifies all the required fields and performs basic AML checks on the counterparty.
3. If the screening is passed, the client receives the applicantKytOnHold webhook.
4. Additional information is obtained by sending a GET request using this API method.
5. Sumsub responds with the full information about the transaction.
6. When the Travel Rule data exchange is completed, Sumsub sends the applicantKytTxnApproved or applicantKytTxnRejected webhook to the client.
7. If the transaction is approved, the Travel Rule transaction is finalized and a financial transaction is expected.

For outbound transactions, the data exchange process remains the same as specified above, except for steps 3 and 4. At step 3, the counterparty VASP confirms the wallet ownership and beneficiary details. If the screening is passed, and depending on the results, the client receives an appropriate webhook.