Rules with paid features

Boost your transaction monitoring with extra checks.

With Sumsub, you can create custom rules or use the existing ones to detect and prevent fraudulent activities, money laundering, and other financial crimes. However, incorporating additional rules can significantly enhance the effectiveness of your transaction monitoring procedure.

We offer some rules with paid features crafted by seasoned professionals that involve Sumsub advanced functionalities and data obtained from our partners with in-depth knowledge of financial regulations, industry trends, and emerging threats.

To activate rules with paid features, install them from the Rules Library.



Rules with paid features come at a charge, but you will only be charged if the rule is triggered. To learn more about the pricing, contact your Customer Success Manager.

Code nameTitleDescription
AML 8Payment details checkChecks payment details for suspicious words, phrases, instructions and identifies names that don't belong to the Remitter or Beneficiary using AI.
AML 13Name check on paymentChecks payment details for extra names that match on the AML watchlist.
AML 0Check counterparty for AML (sanctions, peps, etc.)Creates an AML case for the transaction counterparty.
AML 10Check Travel Rule counterparty for AML (sanctions, peps, etc.)Creates an AML case for the counterparty of the Travel Rule transaction.
AML19Run a suspicious beneficiary institution info checkInitiates an AML screening check of the beneficiary institution.
CTC0Check crypto txn for risksInitiates crypto transaction risk scoring.
CTCCAChainalysis crypto txn checkInitiates the screening of the cryptocurrency transaction through the Chainalysis and record the check result.
TRI0Prepare Travel Rule information exchangeCollects the counterparty data for exchange and detects available data exchange protocols.



All rules with paid features are pre-scoring rules. This means that to affect the transaction, they must be bundled with the scoring rules. For example, the rule creating an AML case for the transaction counterparty should be used with the rules putting the transaction where the counterparty has a potential AML match on hold, and the rule rejecting the transaction where the counterparty has a true positive AML match.