Wallet Screening, KYT, and Crypto Compliance

Wallet screening, KYT and identity checks answer different questions. Wallet screening assesses an address's on-chain exposure. KYT examines transaction activity. KYC verifies the person or business, while identity AML screening checks relevant names and risk information. A useful compliance workflow connects those results without treating one as a substitute for the others.

Bring your provider key, or start with pay-as-you-go screening

Didit customers can bring their own Chainalysis API key into Didit and orchestrate it inside their Didit workflows, or choose any other wallet-screening provider available in Didit. Read the wallet-screening documentation for configuration and coverage.

If you want to start without a separate provider key, use Didit's pay-as-you-go wallet screening at the published price of $0.15 per check. Start in the Business Console without a sales call. From 1 November 2026, the free plan includes $10 of credit per month. See the November pricing update.

Both routes fit a developer-first workflow: use the API, connect an agent through the MCP server, and use Didit's SDKs for the surrounding customer journey. Wallet screening runs in the same workflow as KYC, AML and transaction monitoring. Check the selected provider's network coverage before sending an address.

Where the check belongs

Before a withdrawal, screen the destination address on its actual network. When recording a crypto transaction, use transaction screening to attach the result to monitored activity. Route uncertain or high-risk results for review according to your policy, and keep evidence of the decision. Screening supports that process; it does not guarantee compliance or establish wallet ownership. Crypto-screening integration.

Read the result before making a decision

A completed address screen returns a normalized risk_score, severity, screening status, risk factors, and source-of-funds and destination-of-funds breakdowns. Inspect status first: a pending or failed screen is not a completed assessment. Response reference.

UNKNOWN is the lowest score band, not an affirmative pass. A zero score means the provider returned no adverse assessment; a nonzero score below 10 still represents a signal. A sanctions_hit can reflect the screened address or exposure through counterparties, so examine the evidence rather than treating every hit as direct attribution. A wallet result does not establish who owns the address.

The on-demand wallet endpoint does not create a transaction, run transaction rules, or return a transaction network graph. To attach screening to monitored activity, submit a transaction using the transaction-screening integration. Missing information, including a null PEP field or unknown hop count, must remain unknown in your application.

Connect screening to the review work

Didit's Investigator agent reviews items at $0.20 per reviewed item. The support agent starts from $0.02 per message. Copilot helps teams build workflows, while the MCP server lets their own agents work with Didit. These are separate capabilities from the wallet-screening check; keep the review and messaging charges separate in your estimate. Investigator documentation; agent and Copilot updates; MCP documentation.

Start in the console

Open the Business Console, choose your application, and configure Transactions > Settings > Provider Preferences. Choose the pay-as-you-go route, or connect an available provider key through Marketplace. Then test a wallet on its actual network and inspect the returned screening status. Follow the integration guide.

Choose the route that fits your team: keep a supported provider relationship, or pay as you go at $0.15 per check and start in the console without a sales call.