OFAC screening within AML programs
AML spots suspicious activity, while OFAC screening identifies prohibited counterparties, and a sound program needs both.
TL;DR
TL;DR: OFAC screening is a required component of any AML program. AML identifies suspicious activity, while OFAC screening identifies prohibited counterparties on the SDN List, and both must run before a transaction completes.
AML and OFAC answer different questions
Anti-money-laundering controls look for suspicious patterns: structuring, unusual volumes, or red-flag behavior. OFAC screening answers a narrower question: is this specific counterparty on the Specially Designated Nationals and Blocked Persons List? A transaction can look completely normal and still violate sanctions, so AML monitoring alone will not catch it. OFAC strict liability means intent is not required, and penalties start at $356,000 per violation.
How the two fit together
Run OFAC screening as a hard gate before funds move, then layer AML monitoring on top. sanctionsai.dev provides the screening gate: one HTTP call that checks a wallet or name against 947 OFAC-listed crypto wallets and 19,218 SDN names, returning clean (ALLOW) or flagged (BLOCK) in under 100 ms, synced hourly from US Treasury data.
Program checklist
- Screen at onboarding and again at each transaction.
- Escalate flagged matches for review before any override.
- Document every screening decision for regulators and auditors.
AML catches the pattern; OFAC screening catches the person behind it.
Together, the two functions give a complete picture: the pattern of the activity and the identity of the counterparty behind it. Programs that skip the screening gate leave the most damaging case, a clean-looking transaction with a designated party, entirely uncovered.