AML check before a P2P USDT trade
Buying or selling USDT TRC-20 directly with another person? Ask the counterparty for an AML report on their wallet before the transfer so you don't receive funds an exchange will freeze.
The main P2P risk: receiving tainted USDT
In a P2P trade you receive tokens from an address whose history you don't know. If the funds are linked to scams, mixers, or sanctioned addresses, an exchange may freeze your deposit and ask for proof of origin. The burden of explanation falls on you.
In AMLTrace a check is started by the wallet owner through WalletConnect, so you cannot screen someone else's address. The working approach is to ask the counterparty to check their own wallet in AMLTrace and send you the report as a PDF or a public link. It takes them a minute, and you see where their funds came from and which risk categories their wallet is connected to.
Steps before the trade
- Ask the counterparty to check the wallet they will send USDT from in AMLTrace and send you the report as a PDF or a public link.
- Compare the address in the report with the address the transfer will come from, and check the screening date.
- Review the total score and the categories: sanctions, scams, mixers, darknet, hacks.
- Low risk: proceed. Medium: ask for another address or reduce the amount. High: decline the trade.
What to look for
- A fresh address with no history is not proof of cleanliness: funds may have just arrived from a risky wallet.
- A high share in the P2P and exchanges category is normal for an active trader.
- Any non-zero share in Sanctions lists or Stolen funds is a reason to walk away.
If you are the seller
The report matters when selling too. If you send USDT to an address linked to illicit activity, your own wallet gains a risky connection in its history. Ask the buyer for an AMLTrace report on the wallet they expect the transfer to, and check your own wallet so you can show its report to counterparties.
P2P has both blockchain and payment risks
A P2P trade has a crypto leg and a payment leg. A wallet report cannot establish that the person named in an order made a bank payment, that a receipt is genuine or that a transfer cannot be disputed. Before trading, understand who transfers the asset, who pays, which platform rules apply and which evidence remains available if the transaction is challenged.
Unexpected third-party payments and new receiving addresses sent through an outside messenger need separate clarification. They may have an explanation, but that explanation should be established before releasing assets. Do not use an apparently reassuring report as a reason to bypass platform protections, confirm receipt prematurely or move dispute handling outside the required process.
A practical pre-release checklist
Compare the amount, currency, payer, reference and payment details against the agreed order. Verify the actual credit in your own bank or payment account rather than relying on an image of a receipt. Confirm the token destination through the agreed communication channel. Where the platform requires communication and dispute handling inside the order, preserve that record.
If you need the USDT sender's report, ask them to check their own wallet and share it. Match the reported address to the one that will actually send the payment. Check your own wallet from your own account. A seed phrase, private key or recovery code is not needed to read a report and should never be supplied as part of a supposed AML verification.
Example: the payment comes from someone else
Suppose a buyer asks for USDT after money arrives from a person not named in the order. Receipt of funds does not explain the relationship between those people or remove the possibility of a later claim. Preserve the order identifier, payment details and conversation. Check whether the platform permits that payment arrangement and use its dispute process before releasing the asset when necessary.
Do not accept a new refund address simply because it was supplied quickly in chat. A refund is another transaction and can introduce additional risk if its recipient is unrelated to the original payment. Establish the correct process through the relevant institutions. A wallet report may support the case, but it does not resolve a payment dispute or authorise a refund by itself.
Evidence to retain after a trade
Keep the order, agreed terms, trade identifier, transaction hash and confirmation of the actual payment. If a report was used, retain its address and date. These records should connect the bank payment and the token transfer to the same agreement. A collection of screenshots without dates or references is much harder to explain later.
For repeated trades, follow a consistent procedure and reconsider it when the payment method, amount or parties change. Previous successful transactions are not a guarantee for the next one. If a bank or platform asks questions, answer about the particular trade and provide only the necessary documents through its official channel, retaining a copy of your response.
Sources and scope
These sources describe general principles and technical data, not proof that a particular address was screened in AMLTrace. Examples are hypothetical; this article is not a legal opinion.
P2P screening questions
Do I need a report for every trade?
Yes. Counterparties change addresses and wallet histories grow. Ask for a fresh report right before the transfer and check its date.
What if the exchange has already frozen my deposit?
Keep the AMLTrace report the sender provided and your chat history with the counterparty. They help when answering the exchange's source-of-funds request.
Can I screen the counterparty's address myself?
No. A check is started by the wallet owner through WalletConnect. The counterparty screens their own wallet and shares the report as a PDF or a public link.
How much does a check cost?
One check after registration is free, so the counterparty only needs to register. For regular trades a plan with a check bundle is more convenient; see the pricing page.
