OFAC screening for cross-border payments

Cross-border payments carry the highest OFAC exposure, so every international transaction should be screened before funds move.

TL;DR

TL;DR: OFAC screening for cross-border payments checks the sender, recipient, and any intermediary against the SDN List before money crosses a border. A clean result means the payment can proceed; a flagged result means it should be blocked.

Why cross-border payments are riskier

When money crosses a border, it can touch counterparties, banks, and wallets in several jurisdictions at once, and each hop is another chance to brush against a blocked party. OFAC applies strict liability here: intent is not required, and civil penalties start at $356,000 per violation. A payment that routes through a blocked entity, even indirectly, can trigger that exposure, and reversing it later is hard.

What screening actually checks

Screening compares the counterparty against the SDN List, the Specially Designated Nationals and Blocked Persons List. The 50 Percent Rule also applies: an entity that is 50 percent or more owned by a blocked person is treated as blocked. SanctionsAI screens 19,218 SDN names and 947 OFAC-listed crypto wallets across 16 jurisdictions, synced hourly so the check always runs against current data.

How it fits into agent payments

For an AI agent moving money, the flow is a single HTTP call that returns ALLOW or BLOCK in under 100 ms. Clean means the agent can pay; flagged means the payment stops before funds move. Screening first is cheaper than unwinding a blocked transfer later, and it keeps the agent compliant without a human reviewing every wire.