Quick Answer: The receiving exchange must support the exact asset and network being sent; the destination address and any required tag or memo must match its deposit instructions. Check the minimum deposit and current deposit status before signing. A confirmed blockchain transaction proves a transfer occurred on that chain, but it does not guarantee the exchange will credit the account.
Check the receiving instructions: Open Phemex's deposit guide, then obtain the current coin, network, address and memo from your own signed-in deposit screen.
Which four fields must agree?
Match the coin, chain, destination and any secondary identifier. A ticker alone does not identify a token uniquely: USDT, for example, exists on more than one network. The sending wallet's network selector must describe the same blockchain as the exchange deposit screen. If the exchange shows a token contract, verify that contract against the sending asset before proceeding.
| Field | Check at the exchange | Check in the sending wallet |
|---|---|---|
| Asset | Exact coin or token and, where shown, contract | The asset actually held and selected |
| Network | Supported deposit chain for that asset | Withdrawal or send chain |
| Address | Current address in the signed-in deposit screen | Destination pasted into the transaction |
| Tag or memo | Whether required and its exact value | Separate tag/memo field, if requested |
Do not infer network compatibility from similar address formats. An EVM-style address can look the same on several chains; that does not mean the receiving exchange credits all those chains. For XRP and other assets that may use a destination tag or memo, the address can identify a shared receiving wallet while the tag identifies the customer account. Phemex's incorrect-deposit guidance states that a missing or incorrect memo may prevent automatic credit.
Why are ticker and network checks separate?
An asset label is a human-readable shortcut. A network is the ledger on which a transaction will settle. Two tokens can share a ticker but have different issuers or contracts; one token can exist on several networks. An exchange may support a token on one network and reject the same named token on another. Therefore, a check that stops at “both screens say USDT” is incomplete. The receiving screen must list the specific network, and the sending wallet must use that network for the selected asset.
For a token with a contract or mint address, compare the full identifier against a reliable source. A copied ticker from a social post is weak evidence; a contract on the wrong chain is a different asset even if its label matches. Do not assume a bridge is built into an ordinary exchange deposit. Bridging, if available, is a separate transaction with separate risks and fees.
What else should be checked before sending?
Check whether deposits for that asset and network are enabled now. Exchange maintenance, delisting, or network incidents can change availability. Read the minimum deposit amount and expected confirmation requirement in the current interface; amounts below a minimum may not credit automatically. Review the sending wallet's network fee and the amount that will arrive after any withdrawal fee. A large quoted transfer amount is not the same as the net amount received.
If a platform requests source-of-funds or counterparty information under a travel-rule workflow, complete that process through the official platform. Requirements vary by region and transfer type. Phemex's Travel Rule FAQ explains its applicable procedure; do not use an old screenshot as a substitute for current account instructions.
How do minimums and fees interact?
The amount typed into a wallet is not necessarily the amount the exchange credits. A sending platform may deduct a withdrawal fee from the amount, while a self-custody wallet may display a network fee separately. Confirm which convention the sending interface uses. Then compare the expected net amount with the receiving exchange's minimum for that asset and chain. A test transfer that arrives below the minimum may be an invalid test because the exchange may not credit it automatically.
Minimums and confirmations are operational policies, not fixed properties of a token. They may change with network conditions or an exchange's risk controls. Record what the receiving screen shows at the moment of transfer. A screenshot can help explain a later dispute, but it does not override the actual chain transaction or the platform's current terms.
What is a safe pre-send sequence?
- Open the receiving exchange directly and sign in. Select Deposit, then the exact asset and network.
- Confirm that the deposit method is active. Record any minimum, memo, and warning shown on that screen.
- In the sending wallet, select the same asset and chain. Copy the address through the exchange's copy button or QR code. Compare the full address after pasting, especially if clipboard software or a browser extension is present.
- Enter the tag or memo in its separate field when required. Do not append it to the address unless the receiving instructions explicitly say to do so.
- Review the final screen: asset, chain, destination, memo, net amount and fee. For a first transfer or a large one, a small test can reveal a mismatch, provided the test is above the receiving minimum and the extra fee is acceptable.
- Save the transaction hash and wait for both blockchain confirmation and the exchange's deposit credit. Treat those as separate states.
A test transfer reduces some operational risk but does not guarantee the next transfer will succeed. Deposit addresses, network status, and rules can change between transactions; repeat the checks each time.
Should you reuse a saved address?
Treat saved addresses as a convenience, not proof of current validity. Some services rotate deposit addresses, retire old ones, or change supported networks. A saved address can also be modified by malware or copied from a spoofed site. Open the receiving platform yourself, compare the address and memo with the current account screen, and confirm the domain before sending. If an address changes, find an official explanation rather than assuming either the old or new address is safe.
A QR code reduces manual typing but does not authenticate the source. Scan only a code displayed inside the signed-in deposit flow, and review the decoded address before approving the send. If the wallet auto-fills a network based on the code, verify it against the exchange screen. The final wallet confirmation is the last practical place to catch a mismatch.
What if the chain shows success but the balance does not?
Start with the transaction hash, asset, network, destination address, amount, and memo. Compare them with the deposit record and current minimum. If the fields match, check whether the exchange still requires confirmations or review. If something differs, do not send another transaction to “fix” it. Contact the receiving platform through its official help route. Phemex describes deposit recovery scenarios, but recovery depends on the asset and chain and is not guaranteed.
Never share a wallet recovery phrase, private key, or login code with anyone claiming to recover a deposit. A legitimate support process can investigate a transaction hash without asking for control of the sending wallet.
How do you diagnose the most common outcomes?
Use the transaction hash and the correct chain explorer first. If the sending wallet shows a pending transaction with no confirmed block, the problem is still on the sending network. If the explorer shows a confirmed transaction to the expected address, compare the asset contract, memo, amount and number of confirmations with the deposit requirements. If the explorer shows a different destination, the exchange may never have received the asset. Do not confuse “transaction successful” with “credited to my customer balance.”
| Observation | First check | Practical next step |
|---|---|---|
| No transaction hash exists | Whether the wallet actually submitted the send | Review wallet status; avoid blind duplicate sends |
| Hash exists but transaction is pending | Chain congestion and fee settings | Follow the wallet's supported replacement or cancellation process, if any |
| Confirmed to the right address, no credit | Memo, amount, contract, confirmation count, deposit status | Gather evidence and contact the exchange's official support |
| Confirmed on a different network | Actual chain and recipient address | Ask the receiving platform about recovery; do not assume it is possible |
| Sent below the minimum | Net amount received and minimum policy | Follow the exchange's published process; another send may not combine automatically |
The table is a diagnosis path, not a recovery promise. A platform may be unable to retrieve an asset sent to an unsupported contract or chain. Where recovery is offered, it may involve manual review, fees, time, or a return rather than credit. Phemex's self-service recovery page identifies some supported scenarios, but each case depends on its facts.
When should you stop the transfer altogether?
Stop if the receiving screen and sending wallet disagree on the network, if a required memo is missing, if the contract cannot be verified, or if the deposit method is suspended. Also stop if a person is pressuring you to transfer to an address that is not your own exchange deposit address. No fee saving or deadline justifies sending to an unverified destination. Resolve the mismatch before signing, because blockchain settlement may be irreversible even when the intended exchange credit never occurs.
FAQ
Is a successful blockchain transaction enough for an exchange deposit?
No. The exchange must recognize the asset, network, destination and memo, then meet any confirmation and account checks before crediting a balance.
Can I send on a cheaper network if the address looks identical?
Only if the exchange deposit screen lists that exact network for the selected asset. Address appearance alone does not establish support.
