Screening fundamentals

USDT Blacklist, OFAC Sanctions and AML Risk: What’s the Difference?

By TRON Checker · Published

A USDT blacklist result describes issuer-controlled token restrictions. An OFAC result describes a match against sanctions data. An AML risk score summarizes observed signals under a defined model. These answer different questions and must remain separate in a P2P or OTC review.

The USDT blacklist: a token-contract fact

Tether can restrict addresses through its USDT contract controls. TRON Checker reads the TRON USDT blacklist state through the contract and cross-checks TronScan's index. A displayed wallet balance does not establish that its USDT can move.

Tether announced a voluntary wallet-freezing policy connected to the OFAC SDN List in December 2023. That policy explains a relationship between sanctions and issuer action; it does not make an OFAC dataset lookup interchangeable with a current contract-state check. See Tether's announcement in the sources below.

OFAC screening: an exact match within a dataset

The OFAC field checks the address against the locally cached OFAC TRON dataset. Read the dataset freshness alongside the result. No exact match means this address was not matched in that dataset; it is not a determination that the counterparty is outside every sanctions restriction.

OFAC explicitly says its digital currency address listings are not likely to be exhaustive (FAQ 562). Address screening cannot replace identification, ownership review, or other checks your business requires. Any legal conclusion depends on the applicable facts and rules, beyond this guide's screening workflow.

AML risk indicators: evidence interpreted by a model

The risk score is a deterministic 0–100 indicator with a named scoring version. Direct blacklist and sanctions findings can drive severe results; other supported evidence, such as exposure or particular flow patterns, can add points under the methodology. The score is not a percentage probability of crime or a future freeze.

Balance, raw transfer volume, and transaction count provide context. High volume alone does not add points. A flow or concentration signal has its own eligibility rules, and a sampled history has limits. Read the signal evidence instead of inferring misconduct from a busy wallet.

Core facts are available without an account. Deep analysis uses credits and can add available exposure and pattern checks. Some evidence can remain unavailable because of provider failures or coverage limits even when access is unlocked.

Use a three-part review note

Write the freeze fact, sanctions fact, and model assessment separately, including each source's availability. Then add your own decision and rationale. This prevents a single color or number from obscuring why the result was reached.

  1. Record the direct freeze result and any source disagreement.
  2. Record the exact sanctions result and dataset freshness.
  3. Record score, confidence, coverage, and the signals that need review.
  4. Apply the desk's policy and preserve the report; repeat screening when circumstances change.

Sources and product references

Editorial review: September 7, 2026. Features and source availability can change; check current product controls before relying on a workflow.

Put the guide into practice

Create an account to organize your review workflow. Core checks are free; deep analysis uses credits. Enable report saving in Settings when you need a stored record.