OFAC red flags
Stablecoin Payments to Sanctioned Entities: The Compliance Red Flag
Stablecoins are not a sanctions loophole. Circle and Tether have frozen hundreds of millions in USDC and USDT at law-enforcement request. A stablecoin payment to a sanctioned entity is both an OFAC violation and a frozen-asset event.
| Red flag | Why it triggers OFAC scrutiny | Risk level |
|---|---|---|
| Stablecoin transfer to a listed SDN | Major issuers operate blocklists. A payment to a sanctioned address can be frozen at the issuer level within hours, locking your funds and creating an audit trail. | Critical |
| Stablecoin rail used to bypass a blocked fiat path | Using USDC to complete a payment you could not make in fiat because of sanctions is itself a sanctions evasion pattern. OFAC treats the underlying transaction, not the rail. | Critical |
| Stablecoin payment to a mixer-adjacent address | Addresses one hop from Tornado Cash and similar mixers are flagged by issuers. Stablecoins sent there are frequently frozen pending review. | High |
The control: every red flag above is caught by pre-transaction OFAC screening.
SanctionsAI checks the wallet, name, or jurisdiction against the live SDN list in under 100ms,
before the payment is signed. There is no pattern so clever that it bypasses an address check.
What to do if you see one of these
- Stop the transaction. Do not let the agent retry around the screen.
- Log the event with timestamp, subject, and SDN list version (the audit trail is your defense).
- If a payment already executed, preserve evidence and assess voluntary self-disclosure — it can reduce a penalty by up to 50%.
- Review the agent's control path: was the screen on the actual execution path, or only on the happy path?
Block every red flag before the payment signs
Pre-transaction OFAC screening in under 100ms. Free tier: 5 checks/day, no signup.
Screen a wallet free → See pricing