OTC USDT Pre-Settle Screening Checklist

Most painful OTC tickets start as a price lock, not as a freeze. Someone agrees size and rate, a Tron USDT send lands, and only then does anyone read getBlackListStatus. By that point you are in incident response: received frozen USDT desk IR. This post is the hour before you agree: a freezeable-USDT pre-settle screen. It does not replace the academy owner for general OTC process, How to run a safe OTC crypto deal, or the documentation habit page, P2P and OTC stablecoin documentation. Glossary owner for the term: OTC risk screening.

Educational only. Not legal advice. Not a guide to evade issuer, venue, or lawful-order controls. Not instructions to complete a trade that screening says you should refuse.

Direct answer

Before you lock price or share a receiving address for freezeable USDT, identify chain and official contract, read issuer blacklist on the sending wallet, run sanctions and source-backed labels separately, capture a FreezeRadar scan, and only then settle. A screenshot is not a transfer. A clean score is not a legal opinion. If the sender is already blacklisted, stop. If one-hop mixer or a direct sanctions match appears, escalate under your policy; do not “just take it and sort it later.”

What this checklist is for

Academy already owns the three-moment story: screen before price, verify payment before you release the other asset, watch after the deal. This blog is the USDT-freeze layer inside moment one.

Use it when:

• the asset is USDT (or you might be paid in USDT after quoting another ticker)
• settlement is self-custody or a desk hot wallet, not an exchange omnibus you do not control
• size is large enough that a later issuer flag or venue hold would hurt

If the trade is P2P retail with a different mess of chat apps, use the companion pre-P2P freeze checklist. Documentation still lives on the academy page above.

Hard stops vs review vs proceed

Write these three buckets into the SOP so traders cannot invent a fourth bucket called “vibes.”

Hard stop (do not settle USDT here):

• Official-contract blacklist true on the sending address (read it yourself)
• Direct sanctions match on a primary list, not a Telegram screenshot
• Direct MIXER_INTERACTION (one-hop mixer label) on freezeable USDT; see mixer detection
• Sender refuses to name chain, or switches sending address after you screened a different one

Review (compliance/ops, recorded decision):

• High-risk exchange or scam/ransomware labels at one hop
• Strong two-hop sanctions or freeze-adjacent paths with intact attribution (tainted USDT without overclaim)
• Brand-new wallet, concentrated inbound, rapid pass-through into you
• Last-minute chain change (ETH screen, TRON pay)

Proceed with records:

• Restriction flag false at stated time
• No direct high-severity finding your policy treats as blocking
• Scan URL saved with the deal pack
• Payment verification still required before you release the other side (verify payment if you are on a plan that includes it)

Unknown labels and truncated history lower confidence. They do not, by themselves, invent a freeze. That is methodology, not a loophole.

The pre-settle sequence (about 15 minutes when the sender cooperates)

1. Write the rail. USDT-TRC20 or USDT-ERC20 (or another official deployment you actually support). Address format is a sanity check: Tron typically T…, Ethereum 0x….
2. Collect the sending address before you share yours. If they will only send from “whichever wallet has gas,” you do not have a screenable object.
3. Official contract blacklist on that sender. If true, stop. Do not quote. Do not share a receive address.
4. Sanctions / official lists as their own pass. An empty SDN address match is not a freeze clearance (SDN addresses are not exhaustive).
5. Source-backed counterparties. Mixer, high-risk exchange, scam, ransomware, OTC-desk labels: only with a source and confidence. Name tags without a source do not become findings in FreezeRadar.
6. Run scan on the sender. Save URL, score category, top findings, coverage note (window, truncation).
7. If they will pay you, screen your receive wallet too. You do not want to publish a receive address that is already flagged.
8. Quote only after 3–7. Put scan ID and chain in the chat or ticket, not only in someone’s head.
9. On send: verify hash, asset, amount, destination. Screenshots lie. Pending is not done. Wrong token with the same ticker is a classic fail (payment verification).
10. After credit: do not sweep into CEX until you run the before CEX deposit workflow. OTC → exchange is how other people’s problems become venue holds.

Wallet segmentation that makes the checklist real

If receive, treasury, and “CEX stage” are one address, one toxic inbound contaminates all three jobs.

• Recv: rotating intake for this counterparty or this week
• Treasury: no surprise OTC senders
• Stage-CEX: only after the deposit workflow
• Investigate: quarantine only

Sweep Recv → Treasury only with an explicit screen artifact. FreezeRadar’s address book is for aliases, not for scoring. Naming a wallet “market maker A” does not change the score.

Deal pack (minimum)

• Counterparty name or desk ID as you actually know it
• Chain, asset, amount, rate, timestamp
• Sending address and receiving address
• Blacklist read (true/false) + explorer URL
• Scan URL
• Tx hash after send
• Chat/email export
• Who approved a Review-bucket trade, if anyone did

Academy’s documentation page lists invoices and proof of commercial purpose. Use it. Chat screenshots that only show the rate are not a source-of-funds file.

Last-minute sender changes

If the hash comes from an address you did not screen, it is a new trade. Re-run steps 3–6. “My friend paid for me” is a documentation event, not a courtesy. If you already released the other asset, you are in IR, not in pre-settle.

After the deal

A clean settle can still go bad weeks later when a counterparty is listed or frozen. That is why academy includes ongoing watch. FreezeRadar watchlist/alerts are entitlement-gated; they do not consume this blog. Log the sending address. If your policy uses retroactive counterparty alerts, this is the address that belongs there.

If monitoring later flags the same sender, use OTC counterparty turned risky after the deal for the after-action, not a panic sweep through mixers.

What traders try that you should refuse in writing

• “Screen my ETH address, I’ll pay on Tron.”
• “The USDT is coming from an exchange, so it’s clean.” Exchange withdrawals can still be another customer’s residual risk; screen the actual from.
• “We’ll split across ten new wallets so it looks smaller.” That is a structuring conversation for compliance, not a fee optimization.
• “Just take it, Tether almost never freezes.” Tether’s terms and on-chain addBlackList history say otherwise. See can Tether freeze USDT.

None of those refusals are “how to evade screening.” They are how not to import a freeze.

Metrics that tell you the checklist is real

• Percent of USDT OTC receives with a saved scan URL
• Count of last-minute sender-address changes caught before release
• Count of tickets that were venue holds mis-tagged as Tether
• Time from first quote request → blacklist read (should be minutes, not after the hash)

If quotes go out before blacklist reads, the SOP exists only in Notion.

USDC and other freezeable assets

If the counterparty switches to USDC, do not reuse a USDT Tron runbook blindly. Circle’s blocklist dialect and Solana token-account freezes differ; start from USDT vs USDC desk view and the academy comparison. The sequence (name rail, read issuer flag, sanctions, labels, scan, then quote) stays. The function names and explorers change.

Honest limits

Public screening does not see the issuer’s unpublished case file or an exchange’s private cluster. A flag can land after you settle. This checklist reduces avoidable self-inflicted freezes and improves records. It does not purchase a withdrawal right at a CEX and it does not unfreeze anyone.

OFAC’s virtual-currency guidance is about sanctions compliance for U.S. persons and firms, not a global OTC license. Map this checklist onto your policy and counsel, not onto a blog.

Related FreezeRadar surfaces

• Academy: safe OTC checklist · OTC pillar
• Received frozen USDT desk IR
• Before CEX deposit
• Scan · Methodology

Key takeaway

Pre-settle screening for freezeable USDT is a named sending address, a live issuer-flag read, a sanctions/label pass, and a saved scan, in that order, before price lock. Keep academy as the general OTC owner. Use this page when the asset can actually be blacklisted out from under you. If you skipped the screen, you already know which IR post to open.