Deposits and transfers

Crypto deposit minimums, fees and transaction tracking

There is no universal minimum deposit or fee across assets and networks. Read the receiving platform's current deposit screen, check the net amount after deductions, and use a TxID to distinguish broadcasting, confirmation and exchange crediting.

1. Find the minimum at the receiving end

Open the recipient platform's deposit flow and select the asset and network. Read the minimum, contract details, confirmation requirements and maintenance notices. A familiar ticker alone is not enough.

Do not rely on an old screenshot or address when deposits are paused. Below-minimum deposits may not credit automatically. Recovery and aggregation rules differ; do not assume a second transfer will fix the first.

2. Separate the costs

A receiving deposit fee, a sending exchange's withdrawal fee and a personal wallet's network fee are different costs. OKX's crypto-deposit guide describes no receiving fee for that service, while the sender may still pay charges. This does not mean card purchases or every payment route are free.

For exchange withdrawals, read the confirmation screen's fee and expected received amount. For personal wallets, the network may require its native asset for gas. Never choose an unsupported network solely because it appears cheaper.

3. Calculate what will actually arrive

Hypothetical example: a receiving page requires more than 5 USDT. You request 6 USDT, but the sender deducts 2 USDT, leaving only 4 USDT to arrive. That fails the requirement. These numbers illustrate arithmetic, not a current exchange fee or minimum.

Check whether fees are charged separately or deducted, and whether the rule says 'at least' or 'more than'. Even a small test needs enough room to satisfy the actual requirement. If deductions are unclear, do not send yet.

4. Run a final sending checklist

  1. Asset: verify the actual supported token and contract where relevant, not just its abbreviation.
  2. Network: both ends must support the chosen network; address appearance is not proof.
  3. Address: copy from the current verified deposit screen and recheck for substitution.
  4. Memo or Tag: include it whenever the receiving flow requires it.
  5. Amount and status: verify the net amount and that deposits are currently enabled.

5. Locate the transaction stage

No TxID and the sender shows 'processing' or 'under review': inspect the sending withdrawal order; it may not yet have been broadcast. Internal transfers may use an internal order identifier rather than an on-chain hash.

With a TxID, use the correct network's trusted explorer to inspect execution, recipient and confirmations. An exchange order number is not necessarily a transaction hash, and searching the wrong explorer does not establish that funds are lost.

If the chain shows success but the balance is unchanged, check required confirmations, minimums, Memo/Tag and maintenance. Exchange crediting is a separate stage. Inspect deposit history and relevant funding or trading balances.

6. Escalate with useful evidence

If sufficient confirmations have passed, or you suspect an address, network or memo error, contact support through the official application. Prepare the asset, network, amount, time, TxID, receiving address and relevant order screenshots, hiding unrelated personal data.

Do not repeatedly send larger amounts as a test. Do not provide recovery phrases, private keys or login codes to a tracker or helper. Whether recovery is supported, how long it takes and whether it costs anything depend on the actual case.

Frequently asked questions

Is a 1 USDT test always safe?

No. It may be below the minimum or reduced by a sending fee. Check the live receiving requirements first.

Why has a successful transaction not credited?

The exchange may need more confirmations or there may be a minimum, memo or maintenance issue. Check these, then contact official support with the TxID.

Can I top up to meet the minimum?

Do not assume separate deposits are combined. Confirm the platform's specific rules before sending again.

Official references