Which network for USDT? Start with the recipient’s deposit page

Start with the receiving side

Choose USDT on the recipient's deposit page and inspect its supported networks. Compare them with the sender's withdrawal page. Matching the coin name alone is insufficient: the networks must match too. Binance warns against choosing an incompatible option simply because it costs less. [1]

In this exercise, the recipient uses Ethereum, so selecting Tron on the sending side fails the check. Think of the asset as what you send and the network as the route. ERC20 and TRC20 commonly identify token transfers on Ethereum and TRON respectively; always read the platform's full label.

Separate the token contract, recipient address and memo

A token contract identifies the asset; a recipient address identifies where it goes. Do not paste a token contract into the recipient field. OKX's web deposit details include Token contract, which helps check that a similarly named token is actually supported. [4]

Copy the receiving details from the recipient's current deposit page, then compare the complete pasted address. Include a memo or tag when that page requires one; not every asset does. Passing an address-format check does not establish that every other detail is correct. [3]

Check whether transfers are available now

Check withdrawal availability at the sender and deposit availability at the recipient separately. Maintenance or network upgrades can suspend services. An older screenshot cannot establish current availability; consult the platform's present notice. [5]

Before confirming, check again that the route remains available, the selected asset and network have not changed, and the address matches the recipient's current instructions. Resolve any uncertainty before submitting.

Compare the received amount with the minimum

The sender's withdrawal minimum and recipient's deposit minimum are separate checks. Binance displays the current withdrawal fee and minimum on its withdrawal page; OKX shows its deposit minimum on the deposit page. Check the selected asset and network. [2][3]

Our fixed example deducts 1 USDT from 10 USDT, leaving 9 USDT. With a fictional deposit minimum of 5 USDT, 9 ≥ 5 passes this amount check. These are teaching values, not live quotes or a promise that any real platform will credit a transfer.

An exchange's withdrawal charge need not equal actual on-chain gas. OKX notes that its charge can differ and may come from additional balance instead of the entered amount. Read the final received amount and total debit rather than applying 10−1 universally. [6]

Compare two invented fee methods with a 1 USDT charge: “send 10, receive 9” debits 10 in total; “receive 10, fee 1 extra” debits 11. Entering 10 therefore does not tell you what arrives. Write down the entered amount, fee, total debit and expected receipt together. Compare the receipt with the deposit minimum. These are our own examples; actual field labels vary.

What can a small test establish?

A small test can help establish whether a checked route credits successfully. It does not replace the earlier checks or guarantee safety. An amount can be too small to meet the deposit threshold, and repeated transfers add costs. A successful test does not remove the need to check every subsequent transfer.

Try the simulated exercise first: select a mismatched network, read the explanation, then choose the matching route and review the amount. The exercise creates no real deposit address and broadcasts no transaction.

Investigate a missing deposit in three steps

Do not rely solely on the sender's completed label. Keep the network, transaction hash (TxID), amount, time and recipient address. OKX's troubleshooting guidance distinguishes an on-chain lookup, confirmations and account crediting. [7]

• Start with the sending record: transfer method, status and TxID. If you only have a platform order number, or no record appears on the correct network, ask the sender to check broadcasting. An internal order number is not the transaction hash. [8]
• Check the correct network's explorer for the transaction result and confirmations. A different blockchain's result does not verify this transfer. [7]
• Check the recipient's deposit history. If confirmations are sufficient but credit is missing, contact its official support with the details and check the asset, address, memo, minimum and service status. [4]

Does having a TxID mean it worked? Read the result and confirmations separately

Open the blockchain explorer link from the withdrawal record. Check the network, then the execution result. Binance’s status guide shows that a TRON transaction can be CONFIRMED with a FAIL result. Reading only the confirmation label can send you down the wrong path. [9]

• Fail / Reverted: execution did not succeed. A failed Ethereum transaction can still spend gas. For an exchange withdrawal, ask the sending platform to check its withdrawal record and account debit; a failed on-chain result does not establish that your exchange balance has already been restored. [10]
• Success: check the asset, recipient and amount in the token transfer details. Ethereum token movements appear under Token Transfer. A successful transaction headline alone does not verify receipt of the particular USDT transfer you are tracing. [11]
• Too few confirmations: compare with the recipient’s current requirement. Deposit credit and permission to withdraw again can have different thresholds. If a credited balance cannot yet be withdrawn, check the applicable confirmation requirement. [7]
• Dropped & Replaced: obtain the new TxID from the sender and look up the replacement. Refreshing the old hash does not establish the replacement’s progress. [9]

Withdrawal completed, deposit missing: work through one fictional record

Record N-01 is an example written for this guide, not a platform transaction. All amounts, fees, thresholds and statuses are invented. It contains no real address or searchable transaction hash. The question is whether a completed withdrawal should already appear in the receiving account.

• Sending record: platform A → platform B; USDT on Ethereum; entered amount 12 USDT, fee 1 USDT deducted from it, expected receipt 11 USDT; total debit 12 USDT; status Completed; a TxID link is available in the record (no real hash is shown here).
• Receiving conditions: platform B accepts the same USDT contract and Ethereum network in this example; the complete recipient address matches; no memo is required here; minimum deposit 5 USDT, credit threshold 12 confirmations, deposits available.
• Checked at 10:00 UTC+8 on 2026-09-08: transaction result Success; token transfer details show the matching recipient and 11 USDT; 3 confirmations so far; platform B’s deposit is awaiting confirmations.
• Diagnosis now: 11 ≥ 5 passes the fictional amount check, but 3 < 12 does not meet the confirmation requirement. Save the record and follow its progress. Sending again to hurry the deposit would create another transfer.
• Next branch: suppose it later reaches 12 confirmations but platform B still has not credited it. Provide the latest check time, confirmation count and both records to the receiving platform. Meeting this example’s threshold alone does not prove it has lost the account entry.

Put the useful records in one support request

State where the transfer stopped, then attach the records. This avoids starting with only “my funds are missing.” The checklist below helps organize a request; it is not a platform’s acceptance policy. Binance identifies the TxID as useful information when contacting support. [8]

• Identity: sending platform, receiving platform, asset, network and TxID. If no TxID is available, say so and include the sending platform’s order reference.
• Amounts and timing: entered amount, fee and fee asset, expected or on-chain receipt, submission time with time zone, and latest check time.
• Checks: execution result, confirmation count and required threshold, and current deposit status. Record whether the address, token contract, memo/tag and minimum match. State discrepancies as found; do not rewrite the records to make them match.
• Keep attachments limited to this transfer. Submit through support you open from the official site or app, rather than posting account records publicly. Do not send passwords, verification codes, private keys or seed phrases. OKX says it will not ask for your seed phrase. [12]

Keep learning