How to build an OFAC compliance culture

Practical steps to make sanctions screening a shared default across an engineering and product organization.

TL;DR

TL;DR: Build the culture by naming an owner, making screening a ship gate, and celebrating caught blocks as wins, not as friction.

Name an owner

Compliance culture starts with accountability. Assign a clear owner for sanctions screening who keeps the gate current and answers questions. Without a named owner, screening becomes everyone's secondary job and no one's priority, which is exactly how a flagged counterparty slips through.

Make screening a ship gate

Treat the check as part of the definition of done. No payment feature ships until sanctions_check runs before every transfer and blocked counterparties are stopped. The 4-Gate Agent Payment Protocol, SCREEN, SCORE, STOP, STAMP, gives teams a shared vocabulary for what complete looks like.

Reframe caught blocks as wins

When a screen blocks a sanctioned counterparty, treat it as a success, not a support incident. A BLOCK result means the system worked. Reinforce the message that strict liability carries penalties starting at $356,000 per violation, so an early catch is worth far more than the friction it causes.