Travel Rule 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 Travel Rule settings. In the Dashboard, go to the Transactions and Travel Rule section, and in the Settings, select General.
Explore the settings described below and set preferences for your operations to ensure that your transactions are processed properly.
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, then 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.
Participant data
This setting allows you to select which originator and beneficiary participant data will be checked in accordance with the following rules:
- Not enough originator information — If any of the selected fields in the originator information are missing, the transaction will be rejected.
- Not enough beneficiary information — If any of the selected fields in the beneficiary information are missing, the transaction will be rejected.
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 (applicable only to the originator participant data)
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 | 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 | 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. |
Updated about 12 hours ago