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 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.
Note
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.
Available rules
The following is a complete list of available rules with paid features.
Code name | Title | Description |
---|---|---|
AML 8 | Payment details check | Checks payment details for suspicious words, phrases, instructions and identifies names that don't belong to the Remitter or Beneficiary using AI. |
AML 13 | Name check on payment | Checks payment details for extra names that match on the AML watchlist. |
AML 0 | Check counterparty for AML (sanctions, peps, etc.) | Creates an AML case for the transaction counterparty. |
AML 10 | Check Travel Rule counterparty for AML (sanctions, peps, etc.) | Creates an AML case for the counterparty of the Travel Rule transaction. |
AML19 | Run a suspicious beneficiary institution info check | Initiates an AML screening check of the beneficiary institution. |
CTC0 | Check crypto txn for risks | Initiates crypto transaction risk scoring. |
CTCCA | Chainalysis crypto txn check | Initiates the screening of the cryptocurrency transaction through the Chainalysis and record the check result. |
TRI0 | Prepare Travel Rule information exchange | Collects the counterparty data for exchange and detects available data exchange protocols. |
Important
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.
Updated 13 days ago