How it works
Submit a transaction
Send transaction data via the Create Transaction API. Each transaction includes:
| Field | Description |
|---|---|
| Applicant | The user initiating the transaction (linked by vendor_data or session) |
| Counterparty | The receiving or sending party |
| Amount & currency | Transaction value and ISO currency code |
| Direction | INBOUND or OUTBOUND |
| Payment method | Card, bank transfer, crypto wallet, etc. |
| Custom properties | Any additional fields your rules need (e.g. product category, channel) |
Rules engine evaluates
Didit runs the transaction against all active rules for your application. Rules can check:
- Single-transaction thresholds — amount limits, high-risk countries, blocklisted entities
- Velocity windows — cumulative volume or count over time (e.g., more than $10,000 in 24 hours)
- Behavioral patterns — structuring detection, rapid in-and-out movement, round-amount patterns
- AML screening — sanctions and watchlist checks on counterparties and linked users via external providers
- Wallet risk — mixer exposure, high-risk wallet addresses (for crypto transactions)
Score and decide
Based on the cumulative score and the highest-severity rule match, the transaction receives a status:
When a transaction enters
| Status | Meaning |
|---|---|
APPROVED | Below all thresholds — transaction is clean |
IN_REVIEW | Flagged for manual analyst review |
DECLINED | Automatically rejected by a rule |
AWAITING_USER | Requires additional verification from the user |
AWAITING_USER, Didit automatically creates a linked remediation session and returns a verification URL so you can continue the flow without leaving the transaction workspace.Key capabilities
| Capability | Description |
|---|---|
| Real-time scoring | Every transaction is scored instantly against all active rules |
| Built-in rule library | Pre-configured rules for AML/CTF, fraud, crypto, and responsible gaming |
| Custom rules | Build rules from the console with conditions, velocity windows, scopes, and automated actions |
| AML screening | Screen counterparties and wallets against sanctions and watchlist databases via integrated providers |
| Remediation workflows | Automatically trigger user verification when a rule requires additional checks |
| Case management | Open cases, link alerts and transactions, assign analysts, and attach evidence |
| Webhooks | Receive transaction.created and transaction.status.updated events in real time |
Integration
Submit transactions via the API and receive results via webhooks:Next steps
Rules & scoring
How the rule engine works, built-in bundles, and custom rule creation.
Cases & investigations
Open cases, assign analysts, and manage investigation workflows.
Console guide
Using the Transactions section in the Business Console.