Blog
8 min readPublished August 12, 2026

Pre-P2P Stablecoin Freeze Checklist

Before you share a P2P receive address for freezeable USDT or USDC, name the chain, read the sender blacklist, screen labels, save a scan, then settle.

Sanctions & Wallet Screening
Stablecoins & Freezeable Assets
Wallet Operations
#wallet-screening
#exchange
#stablecoins
#USDT
#Tether
#freeze-risk
#wallet-monitoring
#compliance
Pre-P2P Stablecoin Freeze Checklist

P2P stablecoin tickets usually fail in the last twenty minutes: a chat quote, a wallet you never screened, and a “send it, I’m in a hurry.” By then you are either in received frozen USDT desk IR or you are explaining a venue hold you imported yourself. This post is the freezeable-asset screen before you share a receive address. It does not replace the academy owner for records, P2P and OTC stablecoin documentation, or the general OTC process, How to run a safe OTC crypto deal. Desk-sized OTC with a named counterparty still belongs on the OTC USDT pre-settle checklist.

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

A retail checkout counter — stand-in for a P2P quote that should be screened before anyone sends freezeable USDT or USDC.

Check a wallet before you act

Run a FreezeRadar scan for issuer-freeze signals, sanctions exposure, counterparty risk, and freezeable asset sensitivity before moving funds.

Scan a wallet

Direct answer

Before you accept freezeable USDT or USDC in a P2P chat, name the chain and official contract, collect the sending address, read that issuer’s live restriction flag, run sanctions and source-backed labels as their own pass, save a FreezeRadar scan, and only then share your receive address. If the sender is already blacklisted, stop. If they switch wallets after you screened a different one, it is a new trade. A screenshot of a wallet app is not a transfer.

Who owns which query

QuestionOwner page
Which invoices, chats, and hashes to keepAcademy: P2P and OTC documentation
Three-moment OTC process (screen, verify, watch)Academy: safe OTC checklist
Named-desk USDT settleOTC USDT pre-settle checklist
Chat-app / retail P2P freeze screenThis post

Do not publish a second thin /guides landing for “P2P stablecoin freeze.” Link academy for documentation. Use this blog when the failure mode is a last-minute address in Telegram, WhatsApp, or an exchange P2P thread.

How P2P differs from OTC (and why the freeze layer still looks similar)

OTC desks usually have a name, a chat archive, and a compliance person who can say “no.” P2P often has a handle, a rating, and a timer. That does not change the contract. Tether’s Token Terms still allow freeze or confiscation and blacklisting of a Digital Tokens Address when Tether determines or suspects Prohibited Use. Circle’s USDC Terms still describe Blocked Addresses and blocklisting. OFAC’s virtual-currency industry guidance is still about sanctions compliance for U.S. persons and firms, not a global P2P license.

What changes is how often the sending address is wrong:

  • The counterparty withdraws from an exchange at the last minute and pays from a different from than the one in chat.
  • They split one invoice across fresh wallets “for fees.”
  • They ask you to receive on Tron after you screened Ethereum, or the reverse.
  • They want you to sweep into a CEX before you have a hash.

Those are documentation events on the academy page. They are also freeze-import events if you skip the issuer flag.

Hard stops vs review vs proceed

Write three buckets so a trader cannot invent a fourth called “they have good reviews.”

Hard stop (do not share a receive address, do not send the other asset):

  • Official-contract blacklist / blocklist true on the sending address (read USDT yourself; USDC: the Circle getter for that chain)
  • Direct sanctions match on a primary list, not a forwarded screenshot (SDN addresses are not exhaustive)
  • Direct one-hop mixer on freezeable USDT/USDC (mixer detection)
  • Sender will not name chain, or switches sending address after you screened a different one and will not wait for a re-screen
  • Sender asks you to use a lookalike ticker that is not the official contract in FreezeRadar’s contracts registry

Review (recorded decision, not a vibe):

  • High-risk exchange, scam, or ransomware labels at one hop
  • Strong two-hop freeze-adjacent paths with intact attribution (tainted USDT without overclaim)
  • Brand-new wallet, concentrated inbound, rapid pass-through into you
  • “My friend will pay” / third-party sender
  • Chain change after quote (ETH screen, TRON pay)

Proceed with records:

  • Restriction flag false at the stated time
  • No direct high-severity finding your policy treats as blocking
  • Scan URL saved with the chat export
  • You still verify the actual hash before you release the other side (verify payment if your plan includes it)

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

The pre-P2P sequence (about ten minutes when they cooperate)

  1. Write the rail in the chat. USDT-TRC20, USDT-ERC20, USDC-ERC20, USDC-Solana — whatever you actually support. Address format is a sanity check: Tron typically T…, Ethereum 0x…, Solana base58.
  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. Pause.
  3. Official contract restriction flag on that sender. If true, stop. Do not quote. Do not share a receive address. Do not “take it and petition later.”
  4. Sanctions / official lists as their own pass. An empty address match is not a freeze clearance.
  5. Source-backed counterparties. Mixer, high-risk exchange, scam, ransomware: only with a source and confidence. A Telegram name tag is not a finding.
  6. Run scan on the sender. Save URL, score category, top findings, coverage note.
  7. Screen your own receive wallet if it has been reused. You do not want to publish an address that is already flagged.
  8. Share receive address only after 3–7. Put scan ID and chain in the same chat thread as the quote.
  9. On send: verify hash, asset, amount, destination. Screenshots lie. Pending is not done. Wrong token with the same ticker is a classic fail.
  10. After credit: do not sweep into a CEX until before CEX deposit. P2P → exchange is how other people’s problems become venue holds.

Academy’s documentation page still owns invoices, identity as you actually know it, and chat export. This sequence is the freeze layer inside “before the trade.”

People reviewing a laptop together — the P2P deal pack is a chat export, a sending address, and a scan URL.

Chat-app failure modes that look like “just P2P”

Last-minute from. The hash arrives from an address that is not the one you screened. It is a new trade. Re-run steps 3–6. If you already released cash or another asset, you are in IR, not in pre-screen.

Split payment. Several small sends from fresh wallets to “look smaller” is a structuring conversation for your policy, not a fee optimization. FreezeRadar does not treat hop count as a laundering verdict; it also does not treat ten new wallets as a courtesy.

Escrow theatre. Some P2P platforms hold funds on their own books. That is a venue ledger, not an issuer freeze. If the user cannot withdraw, run exchange hold vs issuer blacklist before you open a Tether or Circle ticket.

Lookalike assets. A token named USDT that is not Tether’s official issuance is someone else’s risk model. FreezeRadar’s discipline is the registered asset and chain. If you cannot identify the contract, do not settle.

Wallet segmentation for people who actually do P2P

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

  • Recv: rotating intake for this week or this counterparty
  • Personal / treasury: no surprise P2P senders
  • Stage-CEX: only after the deposit workflow
  • Investigate: quarantine only

Sweep Recv → treasury only with a saved screen artifact. Naming a wallet “P2P Alice” in the address book does not change the score.

Deal pack (minimum)

  • Platform or chat handle as you actually know it
  • Chain, asset, amount, rate, timestamp
  • Sending address and receiving address
  • Restriction-flag read (true/false) plus explorer URL
  • Scan URL
  • Tx hash after send
  • Full chat export, not a cropped rate screenshot
  • Who approved a Review-bucket trade, if anyone did

If the counterparty refuses any record, that is already a risk signal on the academy page. It is also a reason not to share a receive address for freezeable USDT.

What you should refuse in writing

  • “Screen my ETH address, I’ll pay on Tron.”
  • “It’s coming from Binance / an exchange, so it’s clean.” Screen the actual from.
  • “We’ll split across ten new wallets.”
  • “Just take it, Tether almost never freezes.” Tether’s terms and on-chain addBlackList history say otherwise (can Tether freeze USDT).
  • “Send first, I’ll verify after.” You verify the hash before you release the other side.

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 P2P freezeable receives with a saved scan URL
  • Count of last-minute sender-address changes caught before you shared receive or released cash
  • Count of tickets that were venue holds mis-tagged as issuer freezes
  • Time from first chat quote → restriction-flag read (should be minutes, not after the hash)

If receive addresses go out before blacklist reads, the SOP exists only in a pinned message.

USDC, Solana, 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. Sequence stays. Function names and explorers change. Token-2022 freeze and clawback on other Solana mints is a different control plane (Token-2022 freeze and clawback); canonical Solana USDC still uses the Solana USDC freeze check landing.

Honest limits

Public screening does not see the issuer’s unpublished case file or an exchange P2P internal 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.

Map it onto your policy and counsel. OFAC’s brochure is not a worldwide P2P license. FreezeRadar scores are explainable assessments, not legal determinations.

Key takeaway

Pre-P2P screening for freezeable stablecoins is a named sending address, a live issuer-flag read, a sanctions/label pass, and a saved scan, in that order, before you share a receive address. Keep academy as the documentation owner. Use this page when the trade lives in a chat timer. If you skipped the screen, you already know which IR post to open.

Sources (5)

Continue exploring FreezeRadar knowledge content.