OFAC compliance for crypto wallet developers
Wallet developers should screen the destination address in the send flow before a transaction is signed.
TL;DR
TL;DR: Wallet developers should screen the counterparty address in the send flow, verify who the counterparty is, and record each decision, using tools that plug into wallet code as a single call.
Screen in the send flow
The natural place for screening is the moment a user enters a destination address. A single HTTP call checks the address against OFAC-listed wallets (947 are tracked) and returns ALLOW or BLOCK in under 100 ms, so the wallet can warn or refuse before the user signs. Because the list syncs hourly, the check reflects current designations.
Know your counterparty
Beyond the address, kya_verify documents who the counterparty is, which matters because OFAC liability is strict and a blocked party is not always obvious from an address alone. risk_score adds a view of how risky a given counterparty looks, so the wallet can show context rather than a bare yes or no.
Tools for wallet developers
- sanctions_check: the ALLOW or BLOCK decision.
- risk_score: a risk view for flagged or borderline cases.
- dispute_open: a review path when a legitimate address is flagged.
- MCP server: pip install sanctions-mcp for agent-style integrations.