OFAC sanctions screening best practices 2026

Current best practices: real-time screening, multi-parameter checks, hourly list sync, audit logging, and agent-specific controls.

TL;DR

TL;DR: In 2026 the bar is real-time screening with hourly data sync, multi-parameter checks, full audit logs, and explicit controls for autonomous agents.

Real-time and multi-parameter

Real-time screening is now the baseline. The check should run at the moment of payment and return in under 100 ms, so a BLOCK result stops the transaction rather than flagging it after the fact. Multi-parameter means checking more than a name: wallet addresses, jurisdiction, and the 50 Percent Rule all matter, since OFAC lists 947 crypto wallets that a name search would miss.

Fresh data and audit logs

Fresh data is non-negotiable. A list that syncs hourly keeps pace with new designations, while a stale list silently misses them. Equally important is the audit log: record every check with a timestamp, the counterparty, and the outcome. Under strict liability, that log is your evidence that screening was performed.

Agent-specific controls

Agent-specific controls are the new requirement. As AI agents gain the ability to pay, screening must sit inside the agent's flow, since tools such as x402, AP2, ACP, and Coinbase AgentKit move money but do not screen. Screen the counterparty before the agent pays, then log it.

The four-gate protocol

These practices come together in a four-gate protocol: SCREEN the counterparty, SCORE the risk, STOP on a flag, and STAMP the decision into the log. The protocol gives autonomous payments a deterministic path, so a payment either clears through the gates or is halted with a record of why.