Binance withdrawals: TRC20, ERC20 or BEP20?

Start a withdrawal with the receiving account's current deposit instructions. You need the asset, network and receiving address, plus a tag or memo if required. A low fee is useful only after both sides support the same transfer.

Match the asset, network and address

1. Choose the exact asset the receiver accepts.
2. Match the receiving network with the sending platform's network option.
3. Copy the address from the receiver's current instructions and compare it after pasting.
4. Enter the tag or memo when the receiver requires it.

A matching prefix is not enough. Ethereum and BNB Smart Chain addresses can both begin with 0x. Recheck the full destination information whenever you change networks.

USDT balances exist on separate networks

The balances do not automatically move between chains. See USDT network comparison for how to compare supported options and costs.

Confirm what the receiver means by BTC or ETH

A Bitcoin deposit and a wrapped representation on another chain are different destinations. Likewise, a receiver asking for ETH may specify Ethereum mainnet or a supported layer-two network. Match the actual network, not just the asset symbol.

Standards and network documentation can explain the labels, but the receiving service decides which deposits it supports. A network appearing in your withdrawal list does not mean the destination accepts it.

Build one destination record before opening the form

Keep the receiving service, intended recipient, asset, network, address and required tag together while preparing the transfer. An address saved under a familiar person's name can become misleading if that person sends new instructions for a different service or asset. Confirm the current purpose of the payment as well as the address. Avoid combining an old address from a contact list with a network name from a new message.

Compare the full address after pasting or scanning it. Matching the first and last characters is a useful initial check, but it is not a substitute for comparing the complete destination. If a QR code fills an address automatically, inspect what was filled and which required fields remain empty. A QR code does not confirm network support or fill in a missing tag.

Read the expected received amount

Before confirming, check the withdrawal fee, minimum withdrawal and expected received quantity. Determine whether the fee is deducted from the entered amount or shown separately. Then compare the received quantity with the destination's minimum deposit.

Exchange withdrawal charges are not necessarily identical to the underlying chain's transaction cost. Use the sending platform's quote for this withdrawal. Internal transfers between Funding and Spot are a different operation.

A hypothetical minimum-deposit calculation

Assume the sending screen deducts a fee of 2 units from the amount entered, and the receiver requires at least 10 units to credit a deposit. Entering 10 would leave 8 to receive, so it would not meet that receiving minimum. Entering 12 would leave 10 under these assumptions, but it still needs to satisfy the sender's separate minimum and every other destination condition. These are invented numbers explaining the calculation, not a quote for any asset or network.

Some confirmation screens may present the entered amount and fee differently. Read the displayed received amount rather than assuming the subtraction above always matches the form. Record the fee asset too: a charge stated in one token cannot be subtracted numerically from another token's quantity. Recheck the actual quote immediately before submission if you have changed the amount or network.

If you already used the wrong network

Save the withdrawal record, actual sending network, address, amount and transaction ID. Query that ID on the explorer for the network actually used. A missing result on a different explorer does not prove that the transfer disappeared.

If the transaction succeeded but an exchange balance did not credit, check confirmation requirements, supported deposits, minimums and tags before contacting the receiving service. Recovery depends on the destination and transfer details; sending another transaction will not repair the first.

Treat a tag or memo as a separate requirement

A network identifies the chain. A required tag or memo may identify a user sharing a receiving address. Correct network and address with a missing tag can therefore reach a platform without reaching the intended user's balance.

Copy the required value and verify it separately. Do not assume a QR code includes every field. If the destination requires a tag but you have none, ask before sending; if none is required, do not invent one.

Use the transfer method the receiver requested

An internal platform transfer may identify another user through account information and use platform records rather than a public transaction ID. An on-chain withdrawal uses a blockchain address and network. Do not place a UID into a blockchain-address field.

Moving your own balance from Funding to Spot is another internal operation. Confirm the source, destination account, asset and amount, then check the transfer record.

Make a test that can actually credit

A small test must satisfy the sending minimum and, after fees, the receiving minimum. Success means the intended receiving account actually shows the deposit; a transaction ID on its own is not that.

After a successful test, recheck the network status and destination details before the remainder. If a network is paused, wait, or agree on a different network both sides support and get its current receiving instructions.

Identify which stage is still pending

Keep the record of the first request when contacting support. The sender is the relevant starting point for a request that has not progressed through its withdrawal process; the receiving service needs the on-chain and deposit details when a completed transfer has not been credited.

Use the checklist to organize unanswered questions

The withdrawal-network checklist highlights checks for your asset and concerns. It does not read the account, quote live fees or choose a network for the receiver. Complete every unresolved destination check before submitting.

Check the remainder as a new request

A test shows only that one particular transfer credited under its recorded conditions. It does not reserve network availability, guarantee the next fee or remove account limits for a larger request. Compare the remainder with the balance available after the test and its charge. If the next request exceeds a limit or introduces a new security prompt, handle that prompt rather than changing destination details to make the form accept it.

Keep the test and remainder as separate entries when reconciling the recipient's total. Two withdrawals can incur two charges, and the receiver may see two deposit records. Agree whether the requested payment amount means the total you send or the net amount the recipient must receive. That agreement affects the amount calculation; it does not change the need for a supported network.