A completed blockchain transfer does not always become a credited MEXC deposit. The token, network, destination address, MEMO or Tag, minimum amount and deposit availability must all match the live instructions for that asset. One incorrect field can leave funds visible onchain but absent from the exchange balance. This guide explains the most common MEXC deposit mistakes, how to diagnose an uncredited transfer and when to use the official recovery process.
Last reviewed: October 12, 2026. MEXC can change supported tokens, networks, addresses, minimums, confirmation requirements, recovery fees and regional availability. Always use the values displayed in your authenticated account immediately before a transfer. This independent guide is educational, is not affiliated with MEXC and is not financial, legal or tax advice.
How a MEXC deposit reaches your balance
The sending wallet or exchange broadcasts a transaction. The blockchain confirms it, the asset reaches an address controlled by MEXC, and MEXC detects and associates it with a customer before crediting the applicable account. Each stage can succeed independently. A transfer may be confirmed but use an unsupported network, or reach a shared address without the MEMO needed to identify its owner.
Diagnose the precise stage instead of repeating the payment. A sending platform’s “completed” label proves only that it processed its side. A successful explorer result proves the network included the transaction. Neither proves that every MEXC deposit requirement was satisfied.
Four details must match
| Field | Purpose | Check |
|---|---|---|
| Asset | Identifies the cryptocurrency or token contract | Compare the contract, not only ticker and logo |
| Network | Defines the blockchain route | Select the same network on both platforms |
| Address | Routes funds to MEXC infrastructure | Copy the current address and compare it after pasting |
| MEMO/Tag | Assigns a shared-address deposit to a user | Copy the complete identifier when shown |
Mistake 1: choosing the wrong network
If MEXC displays an ERC-20 deposit route, the sender must use Ethereum. Choosing BEP-20, TRC-20, Polygon, Arbitrum or another route merely because it is cheaper can produce an uncredited deposit. Compare the full network identity rather than an abbreviation.
Ethereum and many EVM-compatible chains use identical-looking 0x addresses. A wallet can accept the string as valid even when MEXC is not monitoring that token at that address on the selected chain. Address format is not proof of network compatibility.
Common network labels
| Label | Network | Frequent confusion |
|---|---|---|
| ERC-20 | Ethereum | Another EVM chain with the same address format |
| BEP-20/BSC | BNB Smart Chain | Ethereum or older BEP-2 routes |
| TRC-20 | Tron | Chosen for lower fees when the receiver expects another route |
| Arbitrum One | Arbitrum rollup | Ethereum mainnet |
| Polygon | Polygon PoS | Ethereum mainnet |
| Bitcoin | Bitcoin main network | Wrapped BTC on another blockchain |
Mistake 2: using an unsupported network
A token can exist on several chains while MEXC accepts deposits on only some. The ability to trade a ticker does not imply support for every network carrying it. MEXC’s Deposit FAQ says manual recovery may be attempted for some unsupported-network deposits and may incur a handling fee, but some assets and networks cannot be recovered.
Check that deposits are active for the exact asset and network before broadcasting. Do not infer support from an old transaction, a futures market or another exchange.
Mistake 3: omitting a MEMO or Tag
Some currencies use a common exchange deposit address. An additional identifier—MEMO, Tag, Message, Label or Payment ID—tells MEXC which account receives the credit. The address and identifier form one destination.
MEXC currently lists examples including XRP, XLM, ATOM, CRO, HBAR, EOS, BTS and TON, but the list can change. If the live deposit page displays an identifier, treat it as mandatory. Never copy one from an old screenshot or another user’s account.
Mistake 4: entering the wrong MEMO
An incorrect Tag may resemble another customer identifier. Do not attempt to repair the mistake by sending another transfer with a guessed number. Preserve the transaction hash, amount, network, destination and identifier actually entered, then submit the official uncredited-deposit request.
A confirmed transaction cannot be edited to add or replace a MEMO. Only MEXC can determine whether manual attribution or return is technically possible.
Mistake 5: trusting the ticker instead of the contract
A ticker is not unique. Anyone can issue a token with a familiar name and symbol. MEXC credits the supported contract, not every asset sharing its ticker. Compare the contract displayed by the official project, the sending wallet and MEXC, especially for new or less familiar tokens.
A token visible in a wallet is not necessarily listed or deposit-enabled. Likewise, a perpetual contract with the same symbol does not prove the underlying token can be deposited.
Mistake 6: sending below the minimum
MEXC can set a minimum deposit for each asset and network. Transfers below it may not be credited normally. Sender-side fees can reduce the delivered amount, so calculate the net value arriving at MEXC rather than only the amount entered.
A test transfer is useful only when it exceeds the current minimum and leaves margin for fees. Several below-minimum payments should not be assumed to combine unless the live instructions explicitly say so.
Mistake 7: reusing an old address
Deposit infrastructure can change after maintenance, network upgrades or token migrations. Open the authenticated deposit page for every meaningful transfer and copy what is shown at that time. Avoid relying on browser autofill, a notes file, an old QR code or a saved address book without comparing it to the current page.
If managing multiple accounts, verify the signed-in account too. A common exchange address paired with the wrong customer’s Tag can be especially difficult to resolve.
Mistake 8: sending from a smart contract
Some protocols, mining pools or DeFi contracts send through contract calls rather than ordinary transfers. Automated exchange systems may not recognize every method. If the source is a contract, bridge or reward distributor, confirm that direct exchange deposits are supported.
A safer route may be receiving into a compatible self-custody wallet first and then making a standard transfer. That adds a network fee but gives the user a chance to verify the asset and contract.
Mistake 9: ignoring a deposit suspension
MEXC can suspend deposits for maintenance, upgrades, token swaps or security review while trading remains available. Check the live deposit status. If suspended, wait for restoration; never search social media for an “alternative” address.
If a transaction was already sent, retain its hash and monitor both the explorer and official MEXC announcements. Do not resend automatically.
Mistake 10: expecting immediate credit
Networks reach finality differently, and MEXC can require multiple confirmations. A transaction visible in a block may remain pending. Use the hash in an explorer for the correct chain and compare the confirmation count with the current MEXC requirement.
If a self-custody transaction remains unconfirmed because its fee is low, use only the wallet’s supported speed-up or replacement process. A duplicate transfer can create a second payment rather than accelerate the first.
Mistake 11: confusing Spot and Futures balances
A deposit may be credited to Spot while the Futures interface shows no available collateral. Check Deposit History and every relevant wallet section before assuming funds are missing. Use MEXC’s internal Transfer control to move supported collateral from Spot to Futures.
An internal transfer is not a blockchain transaction: it needs no address, MEMO or miner fee. Verify source, destination, asset and amount. Move only the collateral intended for derivatives risk.
Deposit status troubleshooting table
| Symptom | Likely check | Next action |
|---|---|---|
| No explorer record | Sender has not broadcast or supplied a real hash | Contact the sending platform |
| Pending onchain | Confirmations or transaction fee | Wait or use the sender’s supported acceleration |
| Confirmed, no MEXC record | Network, contract, address and MEMO | Prepare an uncredited-deposit request |
| Deposit record processing | Required confirmations or maintenance | Monitor the official status |
| Completed, balance “missing” | Spot, Futures and other account sections | Use internal transfer if appropriate |
How to diagnose a missing deposit
- Open the sender’s withdrawal record.
- Copy the blockchain transaction hash, not an internal order number.
- Inspect it on the correct network explorer.
- Verify status, destination, token contract, amount and network.
- Compare the destination with the current MEXC address.
- Confirm the MEMO or Tag recorded by the sender.
- Compare confirmations with MEXC requirements.
- Check Deposit History, Spot and other account sections.
- Check for maintenance or suspension.
- Use official recovery if the details are wrong or credit remains absent.
How to inspect the transaction hash
A real hash identifies a public blockchain transaction and can be shared with verified support without exposing signing authority. Search it on an explorer for the actual network. Confirm that the explorer displays the expected token transfer and contract, not merely a native-coin value.
Waiting is appropriate when the transaction remains pending, confirmations are insufficient or MEXC reports processing maintenance. Waiting cannot correct a wrong network, wrong address, unsupported contract or missing Tag.
What is an Uncredited Crypto Deposit?
MEXC uses this process for transactions that reached an address but were not assigned automatically. Official materials describe examples including missing or incorrect MEMOs, unsupported tokens, unsupported networks and incorrect deposit details.
It is an investigation request, not a guarantee. Manual recovery may require technical work, supported infrastructure and a handling fee. For small amounts, the fee may exceed the recoverable value.
Evidence to prepare
- MEXC account identifier and verified contact details;
- token name and contract address;
- blockchain network and amount;
- transaction hash;
- sending and destination addresses;
- MEMO or Tag used, if any;
- the sender’s completed withdrawal record;
- screenshots showing complete relevant fields;
- a concise description of the mismatch.
No legitimate investigation needs a recovery phrase, private key, password or two-factor code. These secrets would grant account or wallet control and must never be submitted.
Submit recovery safely
- Open MEXC from a trusted bookmark or verified application.
- Navigate to the official Help Center or deposit-recovery form.
- Confirm the domain before uploading evidence.
- Review any disclosed handling fee and conditions.
- Save the case number and submission time.
- Follow updates only through authenticated messages or verified email.
Do not send another deposit to “unlock” the first. MEXC cannot necessarily recover assets sent to an unrelated external address or through unsupported infrastructure. The presence of funds onchain does not prove technical recoverability.
Avoid fake recovery agents
Public posts about missing deposits attract impersonators using MEXC logos. They may request screen sharing, remote-access software, a wallet connection or a payment to a private address. End the conversation and open support independently.
- Never disclose a recovery phrase, private key or verification code.
- Never install remote-control software for an unsolicited helper.
- Never connect a wallet to a “validation” page.
- Never pay an address supplied through private chat.
Complete pre-deposit checklist
- The website or app is official.
- The selected asset and contract are exact.
- The network matches on both services.
- Deposits are currently enabled.
- The current address was copied from MEXC.
- The exact MEMO or Tag is included when shown.
- The net amount exceeds the minimum.
- The source uses a supported transfer method.
- Address and Tag were checked after pasting.
- A qualifying test transfer is used when practical.
- The transaction hash will be saved.
Example: USDT network mismatch
MEXC displays USDT on TRC-20 with a Tron address. The sender must withdraw USDT through TRC-20. Selecting ERC-20 because the token is also called USDT creates a different onchain transaction. Before sending, check the minimum, fee and deposit status, then use a qualifying test.
Example: XRP without a Destination Tag
XRP reaches MEXC’s shared address but the Tag is missing. The blockchain shows success while MEXC cannot automatically associate the payment. Sending a second transfer with the correct Tag does not label the first. Save the evidence and submit the official request.
Example: credited to Spot, not Futures
Deposit History says complete and the Spot wallet contains USDT, but Futures shows no margin. Nothing is missing. Use the internal Spot-to-Futures transfer, verify the direction and move only the intended collateral.
Recordkeeping
Save the withdrawal record, blockchain hash, network fee, credited amount and timestamps. If recovery returns funds or charges a handling fee, retain that evidence. These records help reconcile exchange exports and self-custody histories.
Tax treatment varies by jurisdiction. A transfer, fee, loss and recovered amount may be treated differently. Consult a qualified professional rather than classifying the event from one interface label.
Frequently asked questions
Why is my MEXC deposit not showing?
Check broadcast status, confirmations, network, contract, address, MEMO, minimum, deposit suspension and whether funds are already in Spot.
Can MEXC recover a wrong-network deposit?
MEXC may assist with some cases for a fee, but some assets and networks cannot be recovered. Use the official form.
Can I add a MEMO after sending?
No. Confirmed blockchain data cannot be edited. MEXC must investigate possible manual attribution.
Does the network matter when the address is identical?
Yes. EVM chains can share an address format while keeping separate ledgers.
Can I deposit any token with a supported ticker?
No. The exact supported contract and network must match.
Why is a confirmed deposit still pending?
MEXC may require additional confirmations or still be processing the deposit.
Is a test deposit always useful?
Only when it exceeds the minimum, uses the correct route and accounts for fees.
Will MEXC Support ask for my recovery phrase?
No legitimate deposit investigation needs private signing secrets.
Final takeaway
Most MEXC deposit problems begin before broadcast. Match the exact token, network, current address and MEMO, then verify minimums and availability. These details cannot be edited after confirmation.
If funds are missing, find the real transaction, compare every field, check Deposit History and Spot, and use the official recovery process when necessary. Do not resend blindly or trust an unsolicited recovery agent.
Official MEXC references
These official pages explain the rules and recovery procedures used in this guide:
- MEXC Learn — How to deposit crypto: standard workflow and network selection.
- MEXC Learn — What are MEMOs and Tags?: additional customer identifiers.
- MEXC Help Center — Deposit FAQ: wrong networks, unsupported tokens and recovery limits.
- MEXC Support — Uncredited Crypto Deposits: cases needing manual investigation.
- MEXC Help Center — Deposit guides: current address, network and MEMO instructions.
- MEXC Learn — Deposit and withdrawal FAQ: minimums, limits and verification.
- MEXC Help Center — Crypto deposits and withdrawals: official transfer-support hub.