Skip to main content
Didit’s Transaction Monitoring lets you screen every transaction in real time — inbound and outbound — against a configurable rule engine. Each transaction receives a risk score, and rules can automatically approve, flag for review, or decline based on your thresholds. New to Didit TM? Start with the quickstart for a 10-minute setup, then read the integration guide for architecture and production patterns. Risk scoring explains exactly how scores are computed.

​
How it works

Submit a transaction

Send transaction data via the Create Transaction API. Each transaction includes the subject and counterparty parties, financial details (amount, currency, direction), payment method information, and optional device context and custom properties for rule evaluation.Didit supports multiple transaction categories — from standard financial transactions to gambling events, travel rule transfers, and audit trail entries. See Submitting transactions for the full payload reference.

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)
Each matching rule contributes to the transaction’s overall risk score.

Score and decide

Based on the cumulative score and the highest-severity rule match, the transaction receives a status:
StatusMeaning
APPROVEDBelow all thresholds — transaction is clean
IN_REVIEWFlagged for manual analyst review
DECLINEDAutomatically rejected by a rule
AWAITING_USERRequires additional verification from the user
When a transaction enters 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.

Monitor and investigate

Use the Business Console or API to:
  • Review flagged transactions with full context (scores, matched rules, linked parties)
  • Open investigation cases and assign analysts
  • Track analyst performance and resolution times
  • Export transaction data for compliance reporting

​
AML blockchain screening

For cryptocurrency transactions, Didit automatically screens wallet addresses and transaction hashes against blockchain analytics providers (Crystal, Merkle Science, and more). Screening runs server-side during transaction creation — no additional API calls needed from your side. Each screening produces a standardised risk score, source of funds analysis with exposure category breakdowns, counterparty connection mapping, and an interactive network graph. Results feed directly into the rules engine — preset rules like “Sanctions counterparty” and “Darknet market exposure” fire automatically. See AML blockchain screening for provider details, pricing, exposure categories, and network visualization.

​
Key capabilities

CapabilityDescription
Real-time scoringEvery transaction is scored instantly against all active rules
Built-in rule libraryPre-configured rules for AML/CTF, fraud, crypto, responsible gaming, and blockchain analytics
Custom rulesBuild rules from the console with conditions, velocity windows, scopes, and automated actions
AML blockchain screeningAutomatic wallet and transaction screening via Crystal, Merkle Science, and more
Source of funds analysisBreakdown of where funds originated — exchanges, mixers, sanctioned entities, scams
Counterparty connectionsEntity-level view of who the wallet has transacted with
Network graphInteractive visual graph of wallet relationships and fund flows
Travel rule complianceTrack originator and beneficiary data, protocol details, and obligation status for virtual asset transfers
Remediation workflowsAutomatically trigger user verification when a rule requires additional checks
Case managementOpen cases, link alerts and transactions, assign analysts, and attach evidence
Configurable settingsAdjust score thresholds, default currency, provider preferences, and remediation workflows per application
WebhooksReceive transaction.created, transaction.updated, transaction.status.changed, and transaction.alert.generated events in real time via webhooks

​
Integration

Submit transactions via the API and receive results via webhooks: 
curl -X POST https://verification.didit.me/v3/transactions/ \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "txn_id": "finance0001",
    "direction": "OUTBOUND",
    "amount": "1200.00",
    "currency": "EUR",
    "applicant": { "vendor_data": "user-123" },
    "counterparty": { "name": "Jane Doe" }
  }'
See the API Reference for the full payload schema.

​
Next steps

Submitting transactions

Full payload reference for the Create Transaction API.

Rules & scoring

How the rule engine works, built-in bundles, and custom rule creation.

AML blockchain screening

Wallet screening, source of funds, and network visualization.

Travel rule

Travel rule compliance data for virtual asset transfers.

Cases & investigations

Open cases, assign analysts, and manage investigation workflows.

Settings

Score thresholds, providers, and remediation configuration.