Rules
Leverage ready-to-use scenarios or create custom super-precise rule sequences to make sure no suspicious transaction slips under the radar.
Rules are instructions and conditions Sumsub considers during monitoring. Every time a transaction (or other action) is made, the enabled rules are automatically applied to determine whether it matches the rule parameters.
The Sumsub solution already comes up with the pre-configured rules tailored to different needs.
Pre-configured rules are grouped in two ways:
- Use cases — rules solving a business problem. Examples: Account Takeover, AML Compliance, or Travel Rule: Singapore.
- Bundles — rules, dealing with specific datasets. Examples: Amount Patterns, Device, or Velocity. Each rule belongs to exactly one bundle.
Additionally, you can create custom rules to cover business scenarios that are specific for your organization.
Use cases
You can install rules for the following use cases:
- AML Compliance. Rules that screen transaction parties and payment details against watchlists and detect links to high-risk jurisdictions.
- Brazil Fraud Monitoring (Pix). Rules optimized for Brazil's instant payment network (Pix) to prevent instant payment fraud and scams.
- Scam Prevention. Rules that protect customers from scams by flagging risky beneficiaries and suspicious outgoing payments
- Philippines Fraud Management (AFASA). Rules aligned with the Anti-Financial Account Scamming Act (AFASA) regulatory framework in the Philippines.
- AML Transaction Monitoring. Rules that detect money laundering red flags in transactional behavior, such as structuring, unusual amounts, or suspicious fund flows.
- Account Handover & Money Muling. Rules that detect accounts handed over to third parties and used to move illicit funds.
- Account Takeover. Rules that detect unauthorized access to legitimate user accounts.
- Payments Fraud Monitoring. Rules that detect fraudulent payments using multiple signals, including bank card checks based on BIN data.
- KYB / Company Due Diligence. Rules that assess corporate applicants during onboarding and ongoing reviews.
- Fraud Rings. Rules that detect networks of linked accounts that share devices, contact data, or counterparties.
- Fraud Prevention Starter Kit. A foundational set of onboarding rules that provides baseline protection against common fraud.
- Identity Theft / Impersonation. Rules that detect attempts to use a real person's identity.
- Synthetic Identity. Rules that flag fake identities created by combining real and fabricated personal data.
- Geographic & Sanctions Evasion. Rules that detect attempts to hide the user's real location or bypass high-risk jurisdictions.
- Verification Scams (Social Engineering). Rules that detect applicants who are being coached or manipulated into passing verification on someone else's behalf.
- Automation / Bots. Rules that detect bots and automated activity.
- App / Device Tampering. Rules that detect modified apps and compromised or emulated devices.
- Transaction Risk Score. Rules that evaluate the final transaction score accumulated from all triggered rules.
- Multi-accounting & Account Farming. Rules that detect a single person or group operating multiple accounts.
- Bonus / Promotion Abuse. Rules that detect users who create multiple accounts to abuse promotional offers and bonuses.
- FINTRAC AML Compliance. Rules that detect transactions subject to FINTRAC reporting requirements in Canada.
- Crypto Monitoring: Chainalysis. Rules that screen wallet addresses and blockchain transactions through Chainalysis.
- Crypto Monitoring: Crystal Intelligence. Rules that screen wallet addresses and blockchain transactions through Crystal Intelligence.
- Crypto Monitoring: CYVERS. Rules that screen wallet addresses and blockchain transactions through CYVERS.
- Crypto Monitoring: Elliptic. Rules that screen wallet addresses and blockchain transactions through Elliptic.
- Crypto Monitoring: Merkle Science. Rules that screen wallet addresses and blockchain transactions through Merkle Science.
- Crypto Monitoring: Nominis. Rules that screen wallet addresses and blockchain transactions through Nominis.
- Crypto Monitoring: TRM Labs. Rules that screen wallet addresses and blockchain transactions through TRM Labs.
- Travel Rule Compliance. Core rules that initiate Travel Rule checks and let you act on the results regardless of jurisdiction.
- Travel Rule: Australia. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Australia's requirements.
- Travel Rule: British Virgin Islands. Rules that validate the data and exchange requirements of the Travel Rule in accordance with the Virgin Islands’ requirements.
- Travel Rule: Canada. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Canada's requirements.
- Travel Rule: Cayman Islands. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Cayman Islands' requirements.
- Travel Rule: Dubai. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Dubai's requirements.
- Travel Rule: EU. Rules that validate the data and exchange requirements of the Travel Rule in accordance with EU requirements.
- Travel Rule: Hong Kong. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Hong Kong's requirements.
- Travel Rule: India. Rules that validate the data and exchange requirements of the Travel Rule in accordance with India's requirements.
- Travel Rule: Indonesia. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Indonesia’s requirements.
- Travel Rule: Japan. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Japan's requirements.
- Travel Rule: Kazakhstan. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Kazakhstan’s requirements.
- Rule: Montenegro. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Montenegro’s requirements.
- Travel Rule: Namibia. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Namibia’s requirements.
- Travel Rule: Oman. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Oman's requirements.
- Travel Rule: Singapore. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Singapore's requirements.
- Travel Rule: South Africa. Rules that validate the data and exchange requirements of the Travel Rule in accordance with South Africa's requirements.
- Travel Rule: Thailand. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Thailand's requirements.
- Travel Rule: Turkey. Rules that validate the data and exchange requirements of the Travel Rule in accordance with Turkey's requirements.
- Travel Rule: UK. Rules that validate the data and exchange requirements of the Travel Rule in accordance with the UK’s requirements.
- Travel Rule: USA. Rules that validate the data and exchange requirements of the Travel Rule in accordance with the US’ requirements.
Rule bundles
You can install the following bundles:
-
AML Screening. Rules that initiate screening of the transaction counterparty, the counterparty institution, and the payment details against watchlists via the desired data provider.
These rules let you uncover advanced AML cases requiring additional attention, including transactions to sanctioned banks and individuals, money laundering instructions, and suspicious wording in the transaction's payment reference related to potential sexual abuse, drug trafficking, or terrorism financing.
-
Amount Patterns. Rules that flag suspicious transaction amounts, such as repeated, round, or high-value amounts.
-
Behavioral. Rules that detect unusual user behavior around transactions.
-
Company Profile. Rules that evaluate corporate data, such as company type, tenure, and ownership structure.
-
Counterparty Analysis. Rules that evaluate the risk of the second party in a transaction.
-
Cross-Check. Rules that validate information consistency across multiple systems and user inputs by cross-referencing data.
-
Crypto Monitoring. Rules that screen wallet addresses and blockchain transactions through a connected blockchain analytics provider.
-
Device. Rules that evaluate device data to detect spoofing, root, or jailbreak status.
-
Digital Footprint. Rules that assess a user's digital identity footprint across web services to determine the overall legitimacy of the persona.
-
Email. Rules that assess email risk, such as disposable, fresh, or non-deliverable addresses.
-
Geographic Risk. Rules that calculate geographic risk based on the applicant, counterparty, IP, and card-issuing countries, flagging links to high-risk jurisdictions.
-
Historical Deviation. Rules that identify sudden spikes relative to a user’s historical baseline.
IP. Rules that evaluate IP reputation, proxy or VPN usage and ISP consistency. -
List Screening. Rules that check transaction data against your custom lists and shared risk data.
-
Payment Method. Rules that evaluate cards and payment methods, including Bank Identification Number data.
-
Phone. Rules that assess phone number risk, such as disposable, fresh, or virtual numbers.
-
Profile Risk. Rules that evaluate static customer attributes, such as account and customer age.
-
Scoring Thresholds. Rules that evaluate the final transaction score accumulated from all triggered rules.
-
Selfie. Rules that analyze selfie checks for signs of fraud.
-
Travel Rule. Rules that initiate automated Travel Rule data collection and verification protocols for virtual asset transfers in accordance with jurisdiction-specific requirements.
-
Velocity. Rules that measure the frequency and speed of specific actions over defined time windows.
Get started with bundles and use cases
Bundles and use cases are installed from the Rules Library. To install a bundle or a use case follow the steps described in this article.
NoteEach rule belongs to one bundle but can belong to several use cases. Anyway, it will be installed only once. You can see where a specific rule belongs in the Use case column.
Configure and manage rules
Updated 3 days ago