OFAC screening for CBDCs

Why central bank digital currency systems still need sanctions screening in their rails.

TL;DR

TL;DR: A central bank digital currency is a transfer of value, so its rails must screen participants and addresses against the SDN List. OFAC strict liability applies to CBDC systems just as it does to any payment network.

A CBDC is a payment rail

A central bank digital currency moves value between accounts and wallets, which puts it squarely within OFAC's reach. The Office of Foreign Assets Control enforces the SDN List (Specially Designated Nationals and Blocked Persons List) with strict liability: intent is not required, and a transfer to a blocked party carries penalties starting at $356,000 per violation.

Where screening sits in the system

The checkpoints are account and wallet onboarding and each transfer. The 50 Percent Rule extends blocks to entities 50 percent or more owned by a blocked person, so the participant identity behind an account matters, not only the account identifier. Screening at issuance and at transfer keeps the system from becoming a channel for blocked funds.

Composable screening for new rails

agentmail, the screening API at sanctionsai.dev, is rail-agnostic: one HTTP call under 100 ms returns clean (ALLOW) or flagged (BLOCK), checking 19,218 SDN names and 947 OFAC-listed crypto wallets across 16 jurisdictions, synced hourly. A CBDC pilot or wallet provider can call it before a transfer settles, the same way an agent or exchange would.