Documents to Prepare for a Frozen Stablecoin Wallet Review
A document checklist for users and businesses preparing to explain frozen USDT, USDC, PAXG, or other issuer-controlled asset balances.

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.
Documents for a Frozen Stablecoin Wallet Review
When a stablecoin wallet is frozen, the first useful task is documentation. The reviewer may be an exchange, issuer, lawyer, investigator, or internal compliance team. Each one needs a coherent story backed by records.
Identity and ownership
Prepare proof that you control or own the wallet or account:
- exchange account email or user ID
- KYC profile information
- business registration documents if funds belong to a company
- wallet address and signed message if requested through a safe official process
- device or wallet screenshots that do not reveal private keys
Never send private keys or seed phrases.
Source of funds
Prepare records showing where the stablecoins came from:
- exchange purchase receipts
- bank transfer or card payment records
- OTC or P2P trade agreements
- invoices and contracts
- payroll, settlement, loan, refund, or customer payment documents
- transaction hashes for each relevant transfer
Transaction timeline
Create a table with date, chain, asset, amount, sender, receiver, transaction hash, and reason for transfer. A clear timeline can reduce confusion and shows you are not hiding the path.
Communications
Save support replies, law-enforcement case numbers, issuer emails, exchange tickets, and counterparty messages. Preserve full conversations where possible.
Risk explanation
If the funds touched a risky counterparty, do not ignore it. Explain what you know, what you do not know, and why the transaction happened. If the issue involves sanctions, court orders, or large balances, involve qualified counsel.
FAQ
Should I send screenshots or original files?
Send what the official channel requests. Keep originals, and avoid edited screenshots that remove important context.
Is a transaction hash enough?
No. A hash proves movement, not ownership, purpose, or source of funds.
What should I never include?
Never include seed phrases, private keys, login codes, passwords, or remote-access permissions.
Sources
Help improve this guide
Share a freeze case note, issuer response, missing document, or support-step correction. Do not include seed phrases, private keys, login codes, or exchange passwords.
On this page
By FreezeRadar Team
Research and product team behind FreezeRadar.
Related reading
Continue exploring FreezeRadar knowledge content.