Crypto exchange withdrawal checklist: test transfers, addresses, networks, and fees
Financial disclaimer, not financial advice. This article is general information and education only. It does not recommend buying, selling, or holding any crypto asset, fund, or product, and it is not personalised financial, tax, or legal advice. Crypto assets are volatile and speculative and can lose all of their value. Consider your own circumstances and, where appropriate, speak with a qualified professional in your jurisdiction before making any financial decision.
An on-chain withdrawal is one of the few routine actions in crypto with no undo. Exchange help documentation states the consequence without softening it: assets withdrawn to the wrong address or an unsupported network may be permanently lost, and the exchange cannot recover them. That single fact should organise the entire task. A withdrawal is not a form to complete quickly; it is a sequence of checks that happen before the confirm button, because after it there is nothing left to check. This checklist is exchange-neutral, the screens differ by platform, but the gates below are the ones official exchange and wallet documentation keep returning to.
Why withdrawals are decided before the confirm button
Three failure modes account for nearly every preventable withdrawal loss, and each is invisible at the moment it happens. The address can be wrong, mistyped, pasted from the wrong place, or swapped for a look-alike. The network can be wrong, the same asset exists on several blockchains, and the address alone cannot prove the right one was chosen, because compatible networks share address formats. And the amount can be wrong in a quieter way, below a minimum, or reduced by a fee the sender never read. The procedure that follows is built to catch each failure at the cheapest possible moment: the first two before anything is sent, the third with a deliberately small test transfer.
Before starting: the preparation gates
- Open the receiving side first. In the receiving wallet or account, select the exact asset and the exact network, and display its deposit or receive address. Bitget Wallet's official transfer help follows this order, token, then network, then copy the address, and recommends choosing the network the funds will actually be used on, so a second cross-chain move is not needed later.
- Copy the address from that screen, and nowhere else. Not from transaction history, not from an old screenshot, not from a message. Trezor's knowledge base names the reason: address poisoning, in which scammers send small amounts from an address designed to look similar to a real one, hoping the fake will be copied from history next time. The defence is procedural, always copy the receive address directly from the original source, and verify it before sending.
- Compare the pasted address in full. After pasting on the exchange, compare the whole string against the receiving screen, not only the first and last few characters. Look-alike addresses are built to match exactly those characters, and the middle is where the difference hides.
- Check for a memo, tag, or reference requirement. If the receiving side displays one alongside the address, it is part of the address for practical purposes. If it displays none, do not invent one. The receiving screen is the authority either way.
The withdrawal procedure
- Start the withdrawal on the exchange and select the asset. Coinbase's documented sequence is representative: sign in, open the trading view, select Withdraw under the wallet balance, then search for and select the asset. Asset first, network second, amount last, the order matters because each choice narrows the next.
- Paste the receiving address and confirm the pairing. Coinbase's help instructs users to confirm they are withdrawing the correct asset into the correct address. Do this as a deliberate read-back: asset name, first and last characters of the address, and the receiving account or wallet it belongs to.
- Select the network, the same network, on both sides. Where an exchange offers multiple networks for an asset, select the supported network that matches the receiving side, and complete any confirmation the exchange presents about withdrawing on that network. Trezor's guidance is explicit about the trap: do not simply choose the cheapest option, because choosing a network the receiving wallet does not support can result in permanent loss of funds. Its example deserves emphasis. Ethereum and Avalanche C-Chain addresses in a wallet can be identical while belonging to different networks, so an address that looks right proves nothing about the network.
- Read the minimum and the fee on the confirmation screen. Every withdrawal sits above a minimum and carries a fee; the details are covered in the next section. If the intended amount is anywhere near the minimum, resolve that now, not after submission.
- Send a small test transfer to any new address-and-network combination. Trezor's documented method is to select the minimum amount allowed by the exchange and send that amount as the test. Then wait, for the assets to actually appear on the receiving side, not merely for the exchange to mark the withdrawal as sent.
- Verify arrival, then repeat for the main amount. Once the test assets appear in the receiving wallet or account, the documentation's conclusion applies: the network and receive address were selected correctly, and a larger amount can follow the identical path. Re-verify the address for the main transfer anyway; addresses are checked per transfer, not once per wallet. Complete any verification step the exchange requires. Coinbase notes 2-step verification may be required before a withdrawal completes.
- Keep the record. Save the transaction identifier, the asset, the network, the amount, and the fee shown at confirmation. Completed withdrawals can be reviewed afterwards in the exchange's portfolio or history view, but a personal record made at the time is what makes a later discrepancy provable.
Fees and minimums: read them the documented way
Kraken's official support page states the structure that applies across exchanges: there is a minimum requirement for each withdrawal, along with a fee to cover the transaction costs of moving the cryptocurrency out of the account, and its table lists those minimums and fees per cryptocurrency. Two documented caveats should change how any fee figure is used. First, fees and minimums are properties of the asset and the network, not of the exchange in general, the same coin on a different network is a different withdrawal with a different cost. Second, Kraken warns that withdrawal fees are subject to change and may differ from any published table, and that the final fees are accurately shown at the time of confirmation. The confirmation screen is therefore the only fee quote that counts. Any guide, including this one, that printed a specific fee as a lasting fact would be printing an expiry date as a promise, so this checklist deliberately quotes none: check the asset, check the network, read the screen.
The fee also bears on the test-transfer step. A test costs a withdrawal fee of its own, so the total cost of a careful withdrawal is two fees, not one. That is the correct comparison, not against the single fee of a rushed withdrawal, but against the full amount that a wrong network or a poisoned address would cost. On any meaningful sum, the second fee is the cheapest insurance in the process.
When the receiving side is an exchange, not a wallet
The same gates apply, with two direction reversals worth noting from the documentation. When sending to an exchange, Trezor advises checking the exchange's minimum deposit before sending anything, because each exchange sets its own rules, and sending that minimum amount as the test: a deposit below the minimum may not be credited even if the transfer itself succeeds on-chain. And the address to copy is the deposit address the receiving exchange displays for that asset and network at that moment, deposit addresses and their requirements are set by the receiver, and an address saved from a previous deposit deserves the same suspicion as one copied from history.
What success looks like at the end of this checklist is concrete: the test amount has arrived on the receiving side, on the intended network, in the intended account; the main transfer has followed the identical, re-verified path; and a record exists showing the asset, network, amount, fee, and transaction identifier for both. A withdrawal that ends any other way, sent but not arrived, arrived on an unexpected network, arrived short of an unexplained amount, is not finished, and the next step is investigation with the records in hand, not a second, larger attempt.
FAQ
Can a withdrawal sent on the wrong network be recovered? Plan on no. Coinbase states that assets withdrawn to a wrong address or unsupported network may be permanently lost and that it cannot recover them. Recovery stories exist as exceptions handled case by case by platforms; a checklist exists so that no withdrawal depends on being an exception.
Is the cheapest network the right choice if the address matches? No, the address matching is not evidence, because compatible networks share address formats. The right network is the one the receiving side supports for that asset, which is also, per Bitget's help, ideally the network the funds will actually be used on.
How large should a test transfer be? The documented method is the exchange's minimum withdrawal amount (or, toward an exchange, its minimum deposit). Large enough to prove the path and be credited; no larger than the loss that could be accepted if the path turned out to be wrong.
Reminder: Crypto Investing is educational content only, not financial advice. Crypto assets are volatile and can lose all value. Product terms, fees, and rules change, read the current documentation for any exchange, wallet, or product you use.