How to add OFAC screening to an existing application
Retrofit sanctions screening by finding every payment path, adding a screening call before each one, then testing and deploying.
TL;DR
TL;DR: Identify each place the app moves funds, insert a screening call immediately before payment, block flagged counterparties, then test and ship. SanctionsAI makes this a single HTTP call under 100 ms.
Step by step
- Map payment paths: list every point where the app pays a counterparty, including agent and API-driven payments.
- Add the check: call the screening endpoint before each payment; treat ALLOW as pass and BLOCK as stop.
- Handle flags: log the match, halt the payment, and route the case to a human or compliance step.
- Test and deploy: verify blocked and clean counterparties behave correctly, then roll out.
No rewrite required
The screening step is additive, so an existing app does not need a rebuild. It can be wired through existing integrations such as LangChain, CrewAI, the OpenAI Agents SDK, x402, or the MCP server installed with pip install sanctions-mcp. Pricing starts with a free tier of 5 checks per day, no signup and no key, scaling through a Dev plan at $19 per month for 10,000 checks and a Pro plan at $99 per month for 100,000 checks.