To get started with Travel Rule:

In the Dashboard, open the Rules Library page, select the Travel Rule bundle, and install the rules. We recommend installing all rules available in the bundle, as it is the quickest and easiest way to cover all of the check steps.
Open the Rules page and enable the installed rules.
Create Travel Rule transactions and review results.
Handle transaction scenarios.

Create Travel Rule transactions

You can create Travel Rule transactions in the Dashboard using a convenient constructor or with the help of the API methods.

Use Dashboard

To produce a Travel Rule transaction in the Dashboard:

Go to the Transactions page.
Click Create transaction manually.
Select the No applicant (Travel Rule only) checkbox.
Specify transaction information, such as the transaction amount, asset, and transaction hash.
Specify originator and beneficiary information.
Set the custom transaction date by selecting the associated checkbox if necessary.
Click Create transaction.

Use API

To produce a Travel Rule transaction via API, send a single transaction or upload transactions in bulk having the type field set to travelRule.

curl -X POST \
  'https://api.sumsub.com/resources/applicants/631f268442d8290001e1eee9/kyt/txns/-/data' \
  -H 'Content-Type: application/json' \
  -d '{
          "type": "travelRule",
          "applicant": {
              "type": "individual",
              "idDocType": "PASSPORT",
              "idDocs": [
                  {
                      "idDocType": "PASSPORT",
                      "dob": "1987-10-12",
                      "placeOfBirth": "Berlin",
                      "country": "Germany",
                      "number": "DE1111111s"
                  }
              ],
              "paymentMethod": {
                  "type": "account",
                  "fingerprint": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"
              },
               "device": {
                  "fingerprint": "lh0g6l7jk5k",
                  "ipInfo": {
                      "ip": "87.141.63.130"
                  }
              },
              "fullName": "SVEN MAGNUS"
          },
          "counterparty": {
              "externalUserId": "6cll13mtmogichnwghu38",
              "fullName": "Jack Posek",
              "type": "individual",
              "paymentMethod": {
                  "type": "",
                  "fingerprint": "bc1q080rkmk3kj86pxvf5nkxecdrw6nrx3zzy9xl7q"
              },
              "formattedAddress": "Chauseestr. 20, 10115, Berlin, Germany",
              "institutionInfo": {
                  "internalId": "64677eef1bd2aa487ba31e5b"
              }
          },
          "info": {
              "direction": "out",
              "amount": 0.01,
              "currencyCode": "BTC",
              "fingerprint": "1234567777777"
          },
          "travelRuleMode": "sumsub",
          "props": {
              "customProperty": "Custom value that can be used in rules",
              "dailyOutLimit": 10000
          },
          "txnId": "syyjtoxagbanvt0l1buwo",
          "txnDate": "2023-08-22 13:27:53+0200"
    }'

📘
Note
For more information about the Travel Rule API, see this article.

Review results

Once a Travel Rule transaction is checked, it can be found on the Transactions page.

All suspicious transactions which get the Requires action status appear in Queues. Such transactions must be carefully evaluated by your experts and an appropriate action must be taken.