Crypto Sanctions Screening vs Issuer Freeze: Desk Decision Matrix

A sanctions screening hit and an issuer on-chain freeze are different control planes. OFAC (and peer lists) tell you who/what is blocked under sanctions law and which digital-currency addresses they have chosen to publish—explicitly not an exhaustive map of every wallet a sanctioned person may control. Tether or Circle freeze functions change whether a specific stablecoin contract will process transfers for an address. Exchange holds are a third plane. Desks need a matrix, not a synonym list.

Educational only. Not legal advice. Not a sanctions-evasion guide. Not a promise that any screening vendor is complete. Lawful escalation and records only. Glossary anchor: sanctions screening. Operator how-to for the OFAC wallet lane: OFAC wallet screening check.

Direct answer

Screening hit?	Issuer freeze on asset?	Typical ticket	First move
Yes (exact SDN / list address)	Yes	SANCTIONS + ISSUER_FREEZE	Stop activity; preserve evidence; counsel / sanctions playbook and issuer plane notes
Yes	No	SANCTIONS_HIT_NO_ISSUER_FLAG	Sanctions policy (block property / escalate)—do not tell the customer “you’re fine, not frozen”
No	Yes	ISSUER_FREEZE_NO_LIST_HIT	Issuer blacklist ops; do not invent an OFAC story; still screen related addresses
No	No	Continue under policy	Still watch venue hold risk; re-screen at settlement

Add venue hold as a parallel column whenever funds sit on a CEX or custodial app (exchange hold vs issuer USDT blacklist).

Why the SERP collapses three words into one panic

Queries like “crypto sanctions screening,” “OFAC crypto screening,” and “OFAC vs Tether blacklist” rank a mix of:

• Government FAQ pages (what OFAC publishes)
• Issuer freeze explainers (what addBlackList does)
• Vendor blogs that map SDN addresses onto USDT freezes

All three are real. None is a drop-in replacement for the others. FreezeRadar already covers “SDN digital currency addresses are not exhaustive” as a dedicated post—OFAC SDN digital currency addresses not exhaustive—and broader OFAC screening context in OFAC screening crypto. This article is the ops matrix: what to do when the lights disagree.

Plane A; Sanctions screening

OFAC FAQ 562 states that OFAC may add digital currency addresses to the SDN List to alert the public of identifiers associated with a blocked person, and that those listings are not likely to be exhaustive. If you identify identifiers you believe are owned by or associated with an SDN and hold such property, OFAC’s FAQ directs blocking and reporting steps with ownership details—not “wait until Tether freezes it.”

Operational consequences:

• Exact match on a published address is a hard compliance event under a sanctions program.
• Absence of a published address is not clearance that the counterparty is unsanctioned.
• Indirect exposure (hops, clusters, shared funding) is a model/policy question—document vendor, date, and reason codes.
• Other jurisdictions’ lists (EU, UK OFSI, UN, local) may apply depending on your nexus; this matrix uses OFAC as the primary worked example because of FAQ 562’s clarity, not because other lists are optional for every desk.

Guide CTA: OFAC wallet screening check.

Plane B; Issuer freeze

Stablecoin issuers enforce address-level restrictions inside token contracts. For USDT, public reads include isBlackListed / getBlackListStatus; privileged paths include addBlackList, removeBlackList, and destroyBlackFunds. For USDC, Circle documents allow/block-list behavior as a contract capability. These actions are visible on-chain and are about movability of that token, not a full sanctions determination.

Critical mismatches:

• Many issuer freezes are not mirrored as a one-line SDN digital-currency field (industry analyses routinely show SDN-tagged crypto addresses as a minority of all USDT freezes—treat third-party percentages as secondary, dated, and non-FreezeRadar metrics).
• An SDN hit can exist while a particular stablecoin on a particular chain is not yet frozen—or never will be if the person holds non-freezeable assets.
• Freezing USDT does not freeze ETH, BTC, or every other token at the same address.

Blacklist how-to: Tether blacklist check.

Plane C; Exchange / VASP hold

Venue risk engines can lock an account or deposit without any issuer transaction and without your personal self-custody address appearing on a freeze list. Evidence lives in the app ticket, not in isBlackListed. Misrouting venue holds into “OFAC froze my MetaMask” or “Tether froze my Binance” wastes the only hours that matter. Keep exchange hold vs issuer USDT blacklist in the template library.

Desk decision matrix (printable)

Step 0; Name the object. Chain, asset, address, whether funds are self-custody or venue ledger.

Step 1; Sanctions screen. Exact list hit? Indirect-only? Which list? Timestamp the result (OFAC guide).

Step 2; Issuer freeze read for each freezeable asset you care about (Tether blacklist check; USDC counterpart guides as needed).

Step 3; Venue status if any balance is custodial.

Step 4; Classify using the four-box table above + venue flag.

Step 5; Act

• Sanctions exact hit: follow your sanctions playbook / counsel—blocking, escalation, reporting as applicable. Do not invent technical bypasses.
• Issuer freeze without list hit: issuer evidence packet; no fake OFAC narrative to the customer.
• Both: parallel tracks; compliance owns sanctions language; ops owns contract evidence.
• Neither, venue hold: venue packet only.
• Neither, self-custody clear: proceed under policy; re-screen at settlement.

Step 6; Record vendor outputs, explorer URLs, and decision rationale. Audit trails matter when intent is not a defense to civil sanctions exposure under many US fact patterns—counsel defines your program; this blog does not.

Worked composites

SDN address, USDT not yet frozen. Screening flags an exact published digital-currency address. USDT isBlackListed still false on ETH. Correct: sanctions escalation immediately; optional monitoring for a later issuer freeze; do not credit “we can still send USDT so compliance is optional.”

Frozen USDT, no SDN field. Contract true; OFAC search clean for that string. Correct: issuer freeze ops; screen neighbors and funding graph anyway; avoid claiming “OFAC listed you” in customer email.

Clean screen, clean freeze, CEX hold. Classic Plane C. Correct: exchange hold packet.

Clean everything at T0, freeze at T1. Settlement without a second blacklist read. Correctable process bug—not a mystery.

Copy/paste ticket fields (L1)

asset_chain:
address:
sanctions_lists_checked: OFAC SDN [+ others]
sanctions_exact_hit: true|false
sanctions_indirect: none|suspected|vendor_code
sanctions_vendor_or_manual:
sanctions_checked_at:
issuer_asset: USDT|USDC|other
issuer_blacklist: true|false|n/a
issuer_checked_at:
venue_hold: true|false|n/a
classification:
next_owner: sanctions_compliance|issuer_ops|venue_support|treasury
customer_language_approved_by:

Forbidden customer phrases without counsel review: “OFAC cleared you,” “Tether says you’re innocent,” “move funds to avoid the freeze,” or any mixing/structuring suggestion.

Interaction with travel rule and VASP obligations

Sanctions screening and issuer freezes sit beside—not inside—Travel Rule / originator-beneficiary messaging. A Travel Rule packet can be complete while the beneficiary address is issuer-blacklisted; the send will still fail on-chain. Conversely, a perfect freeze read does not satisfy sanctions screening. Keep the controls on separate checklist lines when you onboard a new VASP rail. FreezeRadar’s compliance academy and glossary entries exist so training decks stop treating “compliance” as one button (glossary: sanctions screening).

Secondary literature—how to cite without overclaiming

Industry posts that cross-map OFAC-listed crypto addresses to USDT freezes are useful for intuition: they often show that almost all published OFAC ETH/TRON addresses end up frozen, while most USDT freezes are not simple SDN digital-currency rows. Use that pattern in training. Do not paste a blog’s percentage into a regulator letter as if it were your attested statistic. If the board wants a number, derive it from your own date-stamped joins of primary lists and primary freeze events—or commission counsel/forensics to do so.

Honest limits

OFAC’s published crypto addresses are incomplete by FAQ 562’s own words. Issuer freezes can precede, follow, or never match a public designation. Screening vendors differ on indirect exposure. FreezeRadar helps operators separate sanctions screening from issuer freeze evidence; it does not file your OFAC reports, does not practice law, and does not help anyone evade sanctions or freezes. Secondary industry “X% of freezes are non-SDN” charts are directional only—recompute from primaries if you need a board number.

Related FreezeRadar surfaces

• OFAC wallet screening check
• OFAC SDN digital currency addresses not exhaustive
• OFAC screening crypto
• Tether blacklist check
• Exchange hold vs issuer USDT blacklist
• Glossary: sanctions screening
• Scan · Methodology

Key takeaway

Screening hit ≠ on-chain issuer freeze ≠ exchange hold. Use a four-box matrix (plus venue) so L1 stops merging OFAC FAQ language with addBlackList receipts. Deep-link the OFAC wallet screening check for the list plane and the Tether blacklist check for the contract plane, then confirm material cases on /scan.

References

1. OFAC FAQ 562 — How will OFAC identify digital currency-related information on the SDN List? — https://ofac.treasury.gov/faqs/562
2. OFAC — Specially Designated Nationals And Blocked Persons List (SDN) — https://ofac.treasury.gov/specially-designated-nationals-and-blocked-persons-list-sdn-human-readable-lists
3. Etherscan — Tether USD Read Contract — https://etherscan.io/token/0xdac17f958d2ee523a2206206994597c13d831ec7#readContract
4. Circle — How the USDC Token Contract Works — https://www.circle.com/blog/how-the-usdc-token-contract-works
5. Tether — Legal / Token Terms — https://tether.to/en/legal/
6. FreezeRadar — OFAC SDN digital currency addresses not exhaustive — https://freezeradar.com/blog/ofac-sdn-digital-currency-addresses-not-exhaustive

Cover: Unsplash photo-1529107386315 — Unsplash License — https://unsplash.com/photos/1529107386315-e1a2ed48a620. Light resize long edge 720px. Zipic pending. Not a U.S. government endorsement.