Case

Restriction after a MEXC P2P trade lifted: $120,000 in about 36 hours

MEXCP2P counterparty$120,00036 hours

The account was restricted after the client bought USDT from a counterparty on a blocklist. We distinguished the seller's risk from the buyer's conduct and submitted a package to the compliance team.

An anonymized case. A similar situation does not mean the same timeline or outcome.

Situation

What happened to the client

According to the client

The client regularly bought USDT through MEXC P2P. They accepted an order from a highly rated seller, and the trade completed normally. About 12 hours later, the account was restricted and about $120,000 could not be withdrawn.

Several days were spent responding to template document requests and opening repeat tickets. Social-media posts and support messages generated activity but no substantive progress.

Available evidence

What was documented

Documented fact
  • Platform and amount

    A MEXC account; about $120,000 was subject to a restriction after a P2P trade.

  • Trigger: blocklisted counterparty

    The case materials linked the restriction to the P2P counterparty: the seller appeared on the exchange's blocklist.

  • Case materials

    The materials included P2P history—trade identifiers, the counterparty's wallet, and timestamps—documents showing the source of fiat funds, KYC and account history, an on-chain analysis, and a structured compliance package.

Work completed

Steps toward resolution

Our analysis
  1. 01

    Identified the trigger: the counterparty blocklist

    We reviewed the trade and its on-chain trail. The risk appeared to arise from a 1-hop link to the blocklisted seller rather than from general concerns about the buyer.

  2. 02

    Separated the client from the counterparty risk

    We documented the client's good-faith selection of the order and the source of the fiat funds separately from the seller's conduct.

  3. 03

    Prepared a P2P compliance package

    We prepared an explanation of the trade, Source of Funds (SoF) evidence, and on-chain reasoning in terms suitable for MEXC compliance rather than repeating the same KYC materials in support tickets.

  4. 04

    Submitted through the specialist channel

    Instead of opening more first-line support tickets, we sent the package to the channel that reviews compliance materials.

  5. 05

    Brought the package to review

    The decision then depended on the exchange and the quality of the evidence. The period from our involvement to the lifting of the restrictions was about 36 hours.

OutcomeDocumented fact

How the case ended

The restrictions were lifted after the package was reviewed. The client withdrew the funds from the account. The period from our involvement to the decision was about 36 hours.

Account restrictions lifted and funds withdrawn by the client.

MEXC$120,00036 hours
What helped

Factors that influenced the outcome

Our analysis
  • A specific trigger—the counterparty and 1-hop risk—rather than emotional support messages.
  • Documents showing the buyer's good faith and the source of the fiat funds.
  • The compliance channel instead of another queue of template support tickets.
  • A focus on the P2P mechanics rather than a general request to lift the restriction.

Important limitations

  • This outcome does not promise the same result or timeline in another case.
  • The exchange's decision, the completeness of the evidence, and the details of the P2P trade all matter.
  • The client and personal data are not disclosed.
  • Not every P2P case is resolved within one or two days; timelines vary.
Free initial assessment

Describe what happened

Answer a few questions so we can assess the situation and suggest the next steps.

Do not send seed phrases, private keys, passwords, or 2FA codes. They are not needed for an initial assessment.

Do not send seed phrases, private keys, passwords, or 2FA codes.