Integration settings
Set up your Travel Rule integration to use the full potential of our solution.
To apply the Sumsub Travel Rule solution to your transactions, you need to configure the Travel Rule settings.
To configure the settings:
- In the Dashboard, navigate to Transactions and travel rule -> Settings -> Travel Rule .
- Explore the settings described below and set the preferences for your operations to ensure that your transactions are processed properly.
Note
The Travel Rule settings are available only if your organization has the Travel Rule service enabled.
Confirmation timeout
Use this setting to specify the time period during which you want to receive the Travel Rule data exchange transaction details from the beneficiary VASP. It works when the data transfer status is OnHold or Awaiting counterparty.
Within the specified period, the counterparty VASP must review the customer details and confirm or decline the data match:
- If the confirmation timeout is disabled, the enabled rules work as expected.
- If the confirmation timeout is enabled, the counterparty VASP has to respond within the allotted time. If the response has not been received and the configured time has expired, the transaction will be automatically approved. The data transfer will get the Expired status.
Originator participant data
Select which originator identity fields will be shared with the counterparty VASP during the Travel Rule exchange.
These fields will be stored with the transaction for compliance and audit purposes but will not be used for data matching by the counterparty VASP.
You can select all fields or only the appropriate options from the list:
- Payment address
- External ID
- Full name
- Date of birth
- Place of birth
If no fields are selected, the system will automatically share the following originator identity fields with the counterparty VASP:
- Payment address
- External ID
- Full name
Tip
Your choice of fields should align with the Travel Rule requirements in your jurisdiction.
However, including more data can improve transparency and reduce friction when sending funds to other jurisdictions with stricter requirements.
Beneficiary participant data
Select which beneficiary identity fields will be shared with the counterparty VASP during the Travel Rule exchange. These fields will be used by the counterparty VASP for data matching.
If the data provided does not match the beneficiary information the counterparty VASP has on record, the Travel Rule exchange may be rejected.
You can select all fields or only the appropriate options from the list:
- Payment address
- External ID
- Full name
- Date of birth
- License number
- LEI code
If no fields are selected, the system will automatically share the following beneficiary identity fields with the counterparty VASP:
- Payment address
- External ID
- Full name
Tip
Your choice of fields should align with the Travel Rule requirements in your jurisdiction.
However, including more data can improve transparency and reduce friction when sending funds to other jurisdictions with stricter requirements.
Confirmation ownership mode
Choose confirmation ownership mode to set up the way your transactions will be validated based on the wallet ownership data.
You can store this data to automate the validation process or choose to manually manage each transaction.
| Name | Description | Required action |
|---|---|---|
| Full validation | You are required to fully validate each incoming transaction. | You will need to confirm each transaction and then assign an applicant. |
| Simplified validation | The system will store the data about wallet ownership from previous successful transactions. Addresses involved in previous successful transactions will be automatically labeled as owned by you. | You will only need to confirm transactions with new wallets and assign an applicant for each transaction. |
| Automated validation | The system will store the data about wallet ownership and chosen applicants from previous successful transactions. If a transaction will come to an address involved in previous successful transactions, it will be processed automatically. | You will only need to confirm transactions with new wallets and assign an applicant for transactions with new wallets. |
BCC Email for Counterparty Verification
Add an email address (typically your compliance team) to be "blind copied" on Travel Rule emails sent when you initiate outgoing transactions to VASPs that are not reachable via a supported protocol.
This helps you maintain a record of outreach attempts, which may be required by regulators in some jurisdictions.
Note
Emails are only sent when we have a counterparty VASP's email address on file.
You can also select the Activate TR SDK on transaction checkbox to generate a verification link that you can share with your users to confirm details about the recipient wallet, including its type (hosted or unhosted), with the option to select the VASP (if hosted).
For more information refer to this article.
Data comparison settings - Sumsub protocol
Use the data comparison settings to configure how your organization will match the beneficiary data in incoming Travel Rule transactions submitted via the Sumsub protocol against the data your organization provides when confirming wallet ownership.
You can configure settings separately for:
- Individual beneficiaries.
- Company beneficiaries.
Depending on your jurisdiction, you can define:
- Which fields to match (for example, full name, address, date of birth).
- How strictly to match them.
Here are some examples:
| Setting | Description |
|---|---|
| No matching required | Skips comparison for this field. |
| Strict matching | Requires an exact match of the field value, ignoring case. Recommended for precise identity checks. |
| Weak containment | A flexible name matching that converts names to lowercase and removes spaces for broader matches: John Manuel Smith will match with Johnmanuel Smith. |
| Default matching | Allows limited variations in spelling or formatting. Strikes a balance between strict and fuzzy matching. |
| Fuzzy matching | Allows a wide range of text variations. Useful for catching misspellings, transliterations, or abbreviations. For example, Ltd. and Limited. |
If the incoming data does not match your configured requirements, the transaction will be automatically rejected to ensure compliance with Travel Rule obligations.
Tip
Align your matching settings with your local regulatory requirements.
Setting the strictest matching may increase the risk of unnecessary rejections, so it is often best to enforce only the minimum required checks for smooth transaction processing.
Updated 2 days ago