OFAC compliance for blockchain developers
Blockchain developers can add OFAC screening to any payment path as a single API call.
TL;DR
TL;DR: Blockchain developers face strict OFAC liability for the payment paths they build, and can satisfy it by adding a single screening call that returns ALLOW or BLOCK before value moves.
Why developers are on the hook
Whoever builds the path that moves value also owns the responsibility to keep sanctioned parties out of it. OFAC liability is strict, meaning intent is not required, and penalties start at $356,000 per violation. A developer who wires up a payment feature without screening has created the exact gap OFAC penalizes.
The tools
- sanctions_check: the ALLOW or BLOCK decision.
- risk_score: a risk view for borderline matches.
- kya_verify: documentation of who the counterparty is.
- dispute_open: a review path for flagged addresses.
Get started
Screening is a single HTTP call under 100 ms, backed by live data of 947 OFAC-listed wallets, 19,218 SDN names, and 16 jurisdictions synced hourly. The free tier (5 checks per day, no signup, no key), the MIT self-hosting option, and the MCP server (pip install sanctions-mcp) make it straightforward to drop into any stack.