Skip to main content
This chapter of the Didit Academy fraud rule engine lesson picks up at wallet risk and what the score bands mean. The rule-engine Academy lesson reaches wallet risk at 3:00: what the score bands mean and how a wallet’s exposure feeds the transaction risk score. Wallet Screening checks blockchain risk for $0.15 per wallet or transaction-hash screening. Screen wallets before a transfer, screen transaction hashes after the fact, and send the results to the Transaction Monitoring rules engine. Wallet Screening is part of Didit’s Monitoring lifecycle stage — checks that run continuously, post-onboarding, on every flow of funds in or out of your platform.

​
How it works

  1. Connect a provider. In Transactions → Settings → Provider Preferences in the Business Console, choose managed pricing or connect an existing provider API key from the console Marketplace. The default provider is Merkle Science, the only provider with managed pricing.
  2. Submit a transaction with crypto details. Set transaction_details.currency_kind: "crypto" and provide a wallet address in the participant matching the transfer direction. Didit screens the wallet (pre-transfer) or the transaction hash (post-transfer) automatically.
  3. Receive a standardised result. Risk score 0-100, severity (LOW, MEDIUM, HIGH, CRITICAL), a source-of-funds breakdown, an exposure table, and a network graph. The result feeds the rules engine and triggers any matching webhooks.

​
Supported blockchains

Managed wallet and transaction-hash screening supports 13 networks: Bitcoin (BTC), Ethereum (ETH), Litecoin (LTC), XRP Ledger (XRP), Bitcoin Cash (BCH), Dogecoin (DOGE), Tron (TRX), Solana (SOL), Polygon (MATIC), BNB Smart Chain (BNB), Base (BASE), Optimism (OP) and Arbitrum One (ARB). Use the actual network for each lookup. The same address can have different activity and risk on different chains. Celo, Mode and Plume are not currently supported by the managed integration. Connected providers have their own coverage, and Lightning requires a supported connected provider. For tokens, including USDT and USDC, keep the asset symbol in transaction_details.currency and set the network in transaction_details.crypto_params.crypto_chain. Custom-token transfer coverage depends on whether the token contract is indexed on that network. See wallet screening and chain coverage and asset and network selection.

​
Risk signals

Every screening produces a standardised payload regardless of which provider sits behind it:
  • Risk score (0-100) — higher means greater exposure to risky entities.
  • Severity — LOW, MEDIUM, HIGH, CRITICAL derived from the score.
  • Source of funds — percentage breakdown across 14+ categories (sanctioned, terrorist financing, child exploitation, ransomware, stolen funds, darknet markets, mixers, scams, high-risk exchanges, gambling, regulated exchanges, P2P, unidentified services).
  • Exposure table — counterparty entities with direct vs. indirect hop distance, received and sent amounts, per-entity risk level.
  • Network graph — node-edge view of the wallet’s transaction relationships with centrality and depth metrics. Visualised in the Business Console.
  • Sanctions, darknet, and mixer flags — surfaced as discrete signals so rules can decline instantly.

​
Providers

Connecting your provider key lets you use an existing commercial agreement with a blockchain analytics provider. Didit charges a $0.02 infrastructure fee for each screening routed through a Didit workflow.

​
Pricing

**Wallet Screening costs 0.15percheckwithmanagedMerkleSciencepricing.∗∗Ifyouconnectanexistingproviderkeyforanylistedprovider,Diditchargesa0.15 per check with managed Merkle Science pricing.** If you connect an existing provider key for any listed provider, Didit charges a 0.02 infrastructure fee per screening. No minimums or contracts apply. See the pricing page for volume pricing.

​
Integration

The full API surface — request payloads, direction rules, pre-transfer vs. post-transfer screening, and the rule-engine integration — lives on the Transaction Monitoring AML Screening page. Wallet Screening is enabled by setting currency_kind: "crypto" on the transaction and toggling the application-level default in the Console.

API: crypto screening

Pre-transfer vs. post-transfer payloads, required fields, response shape.

Rules & scoring

How wallet-screening results feed the real-time rule engine.

Cases & SAR workflow

Triage high-risk wallet hits, draft SARs, keep an audit trail.

Travel Rule

FATF Travel Rule support for VASPs and crypto exchanges.