Red flags
OFAC red flags for AI agents
The transaction patterns that trigger OFAC scrutiny, bank freezes, and enforcement actions — and the screening control that catches each one before the payment signs.
What a red flag actually is
A red flag is a fact about a transaction that demands extra scrutiny before money moves. For payment agents, the red flags that matter cluster into three groups: the counterparty (a wallet or name on the OFAC SDN list, or owned 50 percent or more by someone who is), the pattern (repeated payments to fresh addresses, amounts just under review thresholds, bursts at odd hours), and the destination (high-risk jurisdictions and mixing services). Under strict liability, noticing a red flag and paying anyway is the expensive version of not noticing at all.
How to use this list
Each red flag page explains what the pattern looks like in agent logs and payment flows, why it triggers OFAC scrutiny or a bank freeze, and the control that neutralizes it. Treat the list as a review queue design: anything matching a red flag should route to a human or halt outright, and everything else should clear the same automated screen.
The single control that catches most of them
Almost every red flag on this list is caught by one pre-transaction check: screen the wallet, name, or jurisdiction against the live SDN list before the payment is signed. That is what SanctionsAI does: one HTTP call, under 100 milliseconds, returning ALLOW or BLOCK, with 5 free checks a day.
- 5 crypto payment red flags that trigger OFAC scrutiny
- AI agent sanctions compliance red flags
- The #1 red flag: an agent paying a sanctioned wallet
- Stablecoin payments to sanctioned entities
- Cross-chain sanctions evasion
- Payments to high-risk jurisdictions
- PEP & adverse-media red flags
- When your own agent bypasses the screen
Block every red flag before payment
Pre-transaction OFAC screening in under 100ms. Free tier: 5 checks/day.
Screen a wallet free → See pricing