Does OFAC screening apply to testnet transactions?

Testnet transfers use no real value, but screening them still protects the patterns and code that later move real funds.

TL;DR

TL;DR: Testnet transactions generally carry no real value, so OFAC exposure is limited, but the screening logic you build for testnet is the same code that will run in production, so it is worth screening there too.

Why testnet is low risk

OFAC, the Office of Foreign Assets Control, targets property and transactions involving the SDN List, the Specially Designated Nationals and Blocked Persons List. Testnet assets have no real-world value, so a testnet transfer does not move blocked property in the same way a mainnet transfer does.

Why screening testnet still helps

The real reason to screen testnet is parity. If your agent screens in production but not in testnet, the test environment drifts from what actually ships. Screening both keeps the code path identical, so a clean (ALLOW) or flagged (BLOCK) decision behaves the same everywhere.

How to screen both environments

sanctionsai.dev (agentmail) screens a counterparty before an AI agent pays in one HTTP call under 100 ms, so the same integration can run against testnet and mainnet. The free tier offers 5 checks per day with no signup and no key, enough to verify the flow on testnet before enabling production traffic.

Parity in practice

Treat testnet and mainnet as one pipeline. If the screening call is part of the shared code path, enabling it on mainnet requires no extra work, and a change tested on testnet behaves identically in production. This is the simplest way to avoid a test environment that quietly diverges from what actually ships.