Document AI for Crypto & Web3

Screen wallets against sanctions lists and on-chain risk signals, check fiat bank statements for source of funds and read the IDs behind an account.

Request demo

How a compliance team uses it

1

Customer signs up

ID documents are read into fields and checked for format and expiry.

2

Wallet is screened

The deposit or withdrawal address is checked against sanctions lists and its on-chain history.

3

Funds are explained

For larger amounts, fiat statements are parsed and checked for edits.

4

Compliance reviews

Your team reviews sanctions matches and unclear results, with supporting evidence in the report.

What crypto teams check

Sanctions lists

OFAC on every tier. Enhanced adds UK, EU and UN lists on EVM networks.

On-chain risk signals

Mixers, exploits and sanctioned counterparties, each with a severity and the transaction behind it where there is one.

Six networks

Bitcoin, Ethereum, Base, Optimism, Arbitrum One and Polygon.

Source of funds

Large one-off credits, cash deposits and new borrowing flagged in the fiat statements a customer provides.

Edited statements

File history, editing software and a running balance that breaks on a specific row.

Business accounts

Trade license verification for UAE companies and domain age for any company website.

Four clear statuses

Every wallet screening ends in one status your flow can route on, with the matches and signals behind it.

  • BLOCKED_EXACT_MATCH: the address is on a sanctions list
  • MANUAL_REVIEW: risk signals a person should look at
  • INSUFFICIENT_DATA: not enough history to say
  • NO_KNOWN_RISK_SIGNALS: nothing known was found

Frequently asked questions

Have a question that is not here?

What does Enhanced add on each network?

On EVM networks, Enhanced adds UK, EU and UN sanctions lists. On Bitcoin, it adds known ransomware addresses. OFAC screening is included on every tier.

Which tier should we use for deeper exposure checks?

Pro adds third-party exposure analysis and a Bitcoin law-enforcement watchlist on top of the lower-tier checks. Choose the tier for the network and evidence your review process needs.

How should we route a sanctions match?

An exact official match produces BLOCKED_EXACT_MATCH. Other risk signals produce MANUAL_REVIEW. Your flow can route these outcomes differently and show the supporting findings to the reviewer.

Do we need to specify the network for an address?

Yes. A screening request contains both the wallet address and its network. If a customer uses the same address on several supported EVM networks, screen each relevant network separately.

What should we do with an insufficient-data result?

Review which required checks were unavailable before proceeding. INSUFFICIENT_DATA is distinct from a result with no known risk signals, so your flow should keep it open for follow-up.

Screen a wallet you know

Try a few addresses and a statement, and look at the evidence behind each status.

Request demo