A mistake in a rule, a missed webhook, or an unaccounted API field can turn costly in case it impacts many transactions, VIP clients, or significant transaction amounts. That’s why Sumsub offers you easy-to-use scenarios that let you double-check if the new rule is rightly set up and works as intended.

Test rules

Test your rules to guarantee safety, security, and smooth onboarding:

The Test configuration button initiates a check to ensure the condition and action selected for the rule are viable.
The Dry run option enables the rule for the selected source keys or all transactions without any impact on the transaction status or risk score. However, it is still displayed in the transaction information. This scenario lets you find out how the newly created rule would affect your transactions.
The Generate test transactions automatically button lets you create four sample transactions with the selected transaction rule. This option is useful in situations in which you want to test your webhook settings without creating transactions from the applicant profiles.
The Create transaction manually button in the applicant profile allows to generate a sample transaction for the applicant. You may need this if you want to set up the test transaction manually.

Check test results

The results of the checks are displayed in the test transactions list and on the transaction page.

Live and Dry Run rules are highlighted in different colors for easier navigation. You can also hover over the specific rules block to get additional information about them.

The numbers located next to the transaction and in the Matched Rules section of the Transaction page represent the following:

Indicator	Description
Score	The transaction risk score calculated based on the matched live rules.
Matched rules	The sum of all rules in live mode that were triggered and matched.
Dry score	The score that shows what the transaction score would be if the Dry Run rules were live (enabled).
Dry run rules	The sum of all rules in Dry run mode associated with this transaction.
Considered rules	The sum of all rules in all modes associated with this transaction, both matched and not matched.

Test webhooks

Set up your webhooks and use the Generate test transactions automatically or Create transaction manually buttons to run a test transaction. Then check if the webhooks are delivered to your system and it responds correctly, e.g. proceeds with a transaction when it is approved and notifies the compliance team if a transaction is put on hold.

Test API

The JSON file that your system receives from Sumsub should contain the required data fields and meet your file size, format, and structure requirements.

To check if everything operates normally, generate one or several test transactions and upload the results in accordance with the instructions provided in this article.