In addition to the built-in Travel Rule bundle and your country-specific pack that you can install and use right from the start, Sumsub lets you create super-precise rule sequences to ensure your Travel Rule data exchange flow meets the needed requirements and transaction scenarios.

What are Travel Rule rules?

These rules initiate Travel Rule-related checks before, during, and after the data exchange process and keeps you compliant based on your jurisdictional requirements,.

For example, you may decide not to transact with the VASPs operating in FATF red/grey list countries or send cases with potential AML matches found during the transaction counterparty screening for manual review.

Benefits of using Custom Travel Rule rules

Creating custom Travel Rule rules in Sumsub can offer several benefits, particularly for businesses that operate in complex legal environments or need to comply with very strict and specific local regulations:

• Custom rules allow businesses to define specific risk factors relevant to their operations and local jurisdictional requirements, enabling a more accurate assessment of potential threats.
• Automating Travel Rule data exchange through customized rules reduces the need for manual reviews, freeing up resources and allowing teams to focus on higher-priority tasks.

Create your own Travel Rule rule

To create a rule, go to the Rules page, click Create rule, and give your rule a preferred name and optional description (we recommend mentioning Travel Rule there and adding them to the Travel Rule bundle to ease rules filtering in the future). Then follow the steps described below.

Step 1: Define rule triggers

Set the transaction type to Travel Rule and select whether you want to process transactions issued by any source key or only the specified one.

Step 2: Set up rule actions

To set up rule actions:

1. Select any of the following actions: Only score, Put on hold , Awaiting user, or Reject. For example, if you want to verify an unhosted wallet, you need your rule to put the applicant on hold until the wallet is verified.
2. Set the general score to be added to the transaction risk score if the rule matches. Set 0 if you do not want to assign any score.
3. Add tags to transactions for further filtering.
4. Set a priority based on which the rule should be triggered.
5. Select Stop on match to terminate the transaction check if the rule is matched.

For example, if you want to tag and put on hold transactions with potential AML hits, the actions will be the following: Put on hold, Add score: X, Add Tags: AML, Hits to review.

Step 3: Build conditions

To set up conditions:

1. In the Conditions section, click Add condition.
2. Select a logical condition that you want to be applied, such as IF or IF NOT.
3. Select a variable type (Values, Fields, or Functions) and build a condition according to your scenario.
4. Add an AND block if needed to continue the condition chain.
5. Add score points if needed. For example, you can build a rule with two conditions, add a score to each condition, and leave the general score—the score you configure when setting up rule actions—empty. In this scenario, the total transaction score will depend on how many conditions have been triggered.
6. Add an OR group if needed.

Step 4: Save your changes

In most situations when dealing with Travel Rule rules, you do not need to fill in the Create Case and Applicant actions as these rules apply to transactions, not applicants. To learn more about these sections, refer to this article.

Once you configure all of the settings above, click Create rule in the upper-right corner to save it.

Step 5. Test your rule

Make sure to test your new rule to double-check if it is rightly set up and works as intended.