OFAC-KYC Integration

Combining Know Your Customer verification with OFAC sanctions screening in a single compliance workflow.

TL;DR

TL;DR: OFAC-KYC integration runs identity verification and sanctions screening together, so a party is confirmed both real and not sanctioned before a transaction proceeds.

Two checks, one workflow

Know Your Customer (KYC) verification answers who a counterparty is: confirming identity, ownership, and sometimes beneficial owners. OFAC screening answers whether that party is blocked: checking the name, wallet, and jurisdiction against the SDN List. Running them together avoids the failure mode where identity is verified but the sanctions check is skipped, or vice versa. Skipping either half leaves a hole: identity without screening misses sanctioned parties, and screening without identity is easy to evade.

Why they belong together

The two controls answer different risks but gate the same transaction. A verified identity that is not screened can still be a sanctioned party, and a screen without identity is easy to evade with a fresh name. Integrating both into one pre-payment step gives a complete picture before funds move. Treating them as one step also produces a single audit trail, so a compliance review can see both the identity evidence and the sanctions result together.

Integration for agent payments

sanctionsai.dev pairs these checks for AI agent flows. The kya_verify tool confirms counterparty identity, while sanctions_check screens it against 19,218 SDN names, 947 OFAC-listed crypto wallets, and 16 jurisdictions. Clean returns ALLOW and flagged returns BLOCK, so an agent can run both controls in one flow before paying. For regulated businesses, this pairing is standard practice rather than an optional extra.