OFAC Screening False Negative
The dangerous error: your screening tool says clean but the counterparty IS on the SDN list. Caused by outdated lists, exact-match-only algorithms, or integration bugs.
TL;DR
TL;DR: A false negative happens when a screening tool reports a counterparty as clean even though they are on the SDN List. Outdated data, exact-match-only matching, and integration bugs are the most common causes, and the result is an undetected sanctions violation.
What a false negative looks like
An agent prepares to pay a wallet or account. The screening call returns clean, so the agent sends the funds. Later it turns out the counterparty was listed, and the transaction has violated sanctions without anyone realizing it at the time. Because OFAC liability is strict, the fact that the tool reported clean does not by itself remove responsibility.
Why false negatives happen
- Stale list data: the counterparty was added to the SDN List after the screening data was last refreshed.
- Exact-match-only logic: a name that differs by a single character or spelling variant slips through.
- Integration bugs: the screening call is skipped, fails silently, or is misconfigured.
How to reduce them
Use a source that refreshes list data frequently. sanctionsai.dev syncs its data hourly and screens 19,218 SDN names and 947 OFAC-listed crypto wallets across 16 jurisdictions. Configure the integration to fail closed so that an error stops the payment rather than letting it pass, and test the pipeline against known listed names to confirm it actually blocks them.