Skip to main content
Configure application-level transaction monitoring settings from the Business Console to control scoring thresholds, provider preferences, and remediation behaviour.

​
General settings

SettingDefaultDescription
Monitoring enabledtrueEnable or disable transaction monitoring for the application. When disabled, submitted transactions are stored but not evaluated against rules.
Default currencyUSDCurrency used for rule threshold comparisons and currency conversion. All amounts are converted to this currency for consistent evaluation.

​
Score thresholds

Score thresholds determine how the cumulative risk score from matched rules maps to a transaction status:
SettingDefaultDescription
Review threshold60Transactions scoring at or above this value receive IN_REVIEW status
Decline threshold85Transactions scoring at or above this value receive DECLINED status
Transactions below the review threshold are automatically APPROVED. If a rule has an explicit change_status action, that status takes priority over score-based thresholds — DECLINED always wins.
Lowering the review threshold increases the volume of flagged transactions for analyst review. Adjust based on your team’s capacity and risk appetite.

​
Digital asset monitoring

Enable or disable automatic AML blockchain screening for cryptocurrency transactions. When enabled, Didit screens wallet addresses and transaction hashes against blockchain analytics providers for all transactions with currency_kind: "crypto".

​
Provider preferences

Select and configure your preferred blockchain analytics provider:
ProviderConfiguration
CrystalEnable with managed pricing or connect your own API key (BYOK)
Merkle ScienceEnable with managed pricing or connect your own API key (BYOK)
ChainalysisConnect your own API key (coming soon)
EllipticConnect your own API key (coming soon)
With BYOK (Bring Your Own Key), you use your existing provider agreement and pay a reduced per-screening fee through Didit.

​
Remediation workflow

Select which verification workflow to trigger when a transaction enters AWAITING_USER status. When a rule sets a transaction to AWAITING_USER:
  1. Didit automatically creates a linked remediation session using the configured workflow
  2. The remediation session URL is returned in the transaction detail
  3. You can redirect the user to complete the required verification steps
  4. Once the remediation session completes, the transaction status is re-evaluated
This allows you to collect additional KYC information mid-transaction without leaving the transaction monitoring flow.

​
Where to find

Navigate to Transactions > Settings in the Business Console to configure these options. Settings take effect immediately for all new transactions.

​
Next steps

Risk scoring

How score thresholds map to statuses.

AML blockchain

Wallet screening and provider details.

IP enrichment

What IP data is available to rules.