Rule configuration is console-only. All rule tuning — thresholds, conditions, actions, mode — happens from Transactions → Rules → Library in the Business Console. For an end-to-end walkthrough of how rules contribute to scoring, see risk scoring.
How presets are organised
Every preset belongs to a bundle (its functional family) and a category (its broader risk theme). Bundles let you toggle related rules together from the console; categories drive scoring and reporting.How to read this page
Each rule lists itslibrary_key (stable identifier you can reference in the API or console URL), the conditions and aggregation that make it fire, and the default actions it takes. Numeric thresholds shown here are the ship defaults — every value is editable per application without losing the rule’s identity.
Finance bundle
These rules apply to every transaction withtransaction_type = FINANCE. They model the regulatory baseline (BSA/FinCEN reporting thresholds, FATF velocity heuristics) plus money-mule and smurfing patterns.
Structuring & near-threshold
Volume & velocity
Layering, mule & smurfing
Behavioural anomalies
AML / CTF bundle
These rules model classic AML/CTF typologies that don’t depend on blockchain enrichment — they apply universally to fiat and crypto transfers.
The default high-risk jurisdiction list ships with FATF call-for-action and conflict-region territories:
IRN, PRK, SYR, AFG, RUS, MMR. You can override the list per application.
Crypto screening bundle
These rules consume the enriched data produced by Didit’s crypto screening — they’re most useful for crypto-native and VASP applications.Crypto monitoring bundle
Wallet-level exposure rules, plus VASP and Travel-Rule-adjacent integrity checks.Travel Rule bundle
Travel Rule rules apply only totransaction_type = TRAVEL_RULE. Each regional regime ships four rules (pending counterparty, pending action, missing data, failed exchange).
Global Travel Rule
Regional regimes
The same four-rule template is applied per regime. Substitute<regime> below for any of: australia, dubai, eu, hong_kong, india, indonesia, japan, kazakhstan, singapore, south_africa, turkey, uk.
Regime tagging is automatic: Didit stamps custom_values.travel_rule_regime on every Travel Rule transaction from your Travel Rule settings jurisdiction - SG → singapore, GB → uk, and any EU or EEA member code such as DE or FR → eu. Codes without a regional bundle stamp lowercased (US → us), so custom rules can still target them. A props.travel_rule_regime value submitted on the transaction always overrides the derived regime.
That’s 48 region-specific rules in addition to the three global Travel-Rule rules.
Device intelligence & fraud prevention
These rules turn signals from the client SDK (device fingerprint, IP, browser, session age) and provider enrichment into fraud-detection events.Device fingerprint & multi-accounting
IP, network & VPN
Behavioural composite
Account takeover & APP fraud
Affiliate & bonus abuse
Responsible gaming bundle
For iGaming applications. These rules are designed to detect both player-protection signals and bonus-abuse patterns.E-commerce bundle
For marketplaces and merchant-of-record applications.Check fraud bundle
For applications submitting check-deposit transactions. Each rule fires offcustom_values.check_* flags the caller sets when a check carries a known risk signal (washing, missing MICR, dark-web-listed serial, etc.).
BNPL bundle
For buy-now-pay-later providers. Surfaces first-party-fraud (non-payment) and identifier-sharing patterns specific to installment lending.Reference: standards behind the library
Every preset in Didit’s library maps to a widely-accepted AML, fraud, or compliance typology. The standards we lean on:
Didit implements only the typologies that are accepted industry standards and exposes every threshold for you to tune.
Customising presets
Every preset can be:- Tuned — change thresholds, windows, score values, or actions per application
- Disabled — switch a preset to
DISABLEDmode and it stops evaluating without losing its identity - Tested — switch a preset to
TESTmode to evaluate it shadow-mode without affecting transaction outcomes - Extended — create custom rules that complement or override presets