Test rules

Simulate transactions and test your integration.

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 your rules to guarantee safety, security, and smooth onboarding using the following Dashboard functionality:

  • Test configuration — a button that allows you to apply the newly created rule conditions to the last 100 transactions to ensure the condition is valid. The Test configuration button is available in the rule card when you create a new rule or edit an existing one. Mind that configuration testing does not affect transaction statuses.
  • Test mode allows you to test the risk matrix or check how the newly created rule or condition would affect your transactions without impacting the transaction status or risk score. Test results are displayed in real time, allowing you to easily calibrate your risk policy or rules. For more information on how to enable test mode, see this article.
  • Create transaction manually — a button that allows you to generate sample transactions for target applicants. For example, you can create transactions that meet the specific rule conditions to test the system behavior and ensure the newly created rule works as intended. The button is available in the applicant profile and on the Transactions page. For more information on how to create transactions manually, see this article.
  • Rule performance — a tab that contains transactions that triggered the specific rule and the calculated score. The tab is located on the target rule page.

Check test results

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

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

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

IndicatorDescription
ScoreThe transaction risk score calculated based on the matched live rules.
Matched rulesThe sum of all rules in live mode that were triggered and matched.
Test scoreThe score that shows what the transaction score would be if the Test mode rules were live (enabled).
Test modeThe sum of all rules in Test mode associated with this transaction.
Considered rulesThe sum of all rules in all modes associated with this transaction, both matched and not matched.

Test webhooks

Set up webhooks and use the Generate sample transactions 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.