For Cross-Border Payments agents

OFAC Sanctions Screening for Cross-Border Payments

Screen counterparties, jurisdictions, and wallets before cross-border transfers — agent-native compliance under 100ms.

Try the free checker  Get an API key

By ·

Answer: Cross-Border Payments agents screen counterparties against the OFAC SDN list (19,086 names, 782 crypto wallets, 16 embargoed jurisdictions) via a single API call before every payment. A "clean": true response means proceed; "clean": false means halt. The check runs in under 100ms and the free tier covers 5 checks/day with no API key.

Why do Cross-Border Payments agents need OFAC sanctions screening?

Cross-border payment agents handle transfers across jurisdictions and regulatory regimes. Every transaction touches counterparties that must be screened against OFAC sanctions.

Cross-border payments face the highest sanctions risk because they intersect with embargoed jurisdictions, sanctioned banks, and designated individuals. A single wire can result in civil penalties up to $300,000.

How does sanctions screening work for Cross-Border Payments agents?

Add sanctions checking to your payment-routing agent with a single API call. Free tier: 5 checks/day. Production from $19/mo.

Example: screen a wallet before paying

curl "https://sanctionsai.dev/sanctions?wallet=0x098B716B8Aaf21512996dC57EB0615e2383E2f96"

Real OFAC data. Free tier: 5 checks/day, no API key.

What exactly does agentmail screen for cross-border payments agents?

Related resources

Add compliance to your cross-border payments agents

MCP, HTTP, and CLI. Self-host free, or use the hosted API.

See pricing