OFAC compliance for crypto payments

OFAC compliance for crypto payments means screening the recipient wallet and counterparty name before authorizing, logging each check, and blocking matches.

TL;DR

TL;DR: Before you authorize any crypto payment, verify the recipient wallet and counterparty name against the SDN List, log the result, and block flagged matches. Clean means allow, flagged means block.

The core loop

Every payment should follow the same sequence: screen, score, stop if flagged, and stamp the decision. This is the 4-Gate pattern used in agent payment screening: SCREEN, SCORE, STOP, STAMP.

• Screen: check wallet and name against the SDN List.
• Score: attach a risk score to the counterparty.
• Stop: block the payment when a match appears.
• Stamp: record the decision for audit.

What to check

Check the recipient wallet against listed crypto wallets and the counterparty name against SDN names. Remember the 50 Percent Rule: an entity majority owned by a blocked person is also blocked. That means ownership matters as much as the direct name or address.

Logging and proof

Keep a log of every screen, not just the blocked ones. OFAC applies strict liability, so intent is not required. A documented screen on every payment is your evidence of a reasonable compliance program, and it is the first thing a regulator will ask to see.

Automating the gate

For agents and automated payment systems, the same gate runs in code. The agent calls the screen before signing a transaction, and the response decides whether to proceed. This keeps every payment consistent, including the ones no human reviews, and the log of each decision becomes the compliance record you can show later.