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:
- 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.
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.
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.
Updated 5 days ago