What is OFAC screening for gaming and virtual worlds?

Games with tradeable items or tokens act like payment rails, so screening counterparties matters there too.

TL;DR

TL;DR: OFAC screening for gaming and virtual worlds means checking players and counterparties against the SDN List before they buy, sell, or transfer items that hold real value, so listed parties are blocked.

Why virtual economies are in scope

OFAC, the Office of Foreign Assets Control, enforces the SDN List, the Specially Designated Nationals and Blocked Persons List. When a game lets players trade items for real money or transfer tokens, those flows can create sanctions exposure just like a payment rail. Enforcement is strict liability.

What to screen in a game

Screen the counterparty behind a purchase, sale, or withdrawal. sanctionsai.dev (agentmail) screens a counterparty before an AI agent pays, returning clean (ALLOW) or flagged (BLOCK) in one HTTP call under 100 ms. The dataset covers 947 OFAC-listed crypto wallets and 19,218 SDN names, synced hourly.

Where this fits in practice

Game marketplaces and in-game agents can use the same 4-Gate sequence: SCREEN, SCORE, STOP, STAMP. Integrations with Base/USDC, x402, and MCP (pip install sanctions-mcp) let a game add the check without replacing its marketplace logic.

Where the check sits in a game

Put the screening call in the transaction layer, not in the game logic. Marketplaces, item transfers, and withdrawal flows should all pass through the same check, so a listed player cannot bypass screening by using a different menu path. One API call under 100 ms keeps the check fast enough for real-time play.