Open Receive in your destination wallet, confirm the account and network, and copy its address into the exchange's withdrawal form. Match the exact asset and network, review the net amount, then follow the withdrawal and transaction records until the funds arrive.
Prepare the receiving side before opening Withdraw
Start with a wallet you have already set up and backed up correctly. Confirm you can reopen the intended account. If it is a hardware-wallet account, use the device's supported method to check the receiving address.
Choose the network on which you need the asset. Receiving a token on an inexpensive chain is useful only when that is a network your wallet and intended application support. The same-looking address on another chain does not make balances interchangeable.
Obtain the asset identity as well as the ticker. Where a token has several versions or representations, compare the contract information with official material and the exchange's withdrawal description. A symbol and logo are insufficient when multiple assets share them.
If the destination is another exchange rather than a personal wallet, use its deposit page. Check the supported transfer type, minimum credit, and any memo or tag. The receiving platform's requirements determine which withdrawal route will work.
Match the exchange's available withdrawal routes
Open the exchange's withdrawal section and select the asset. Inspect the list of networks and their current status. A market being open for trading does not prove that its withdrawal route is available.
Select a route that matches the destination instructions exactly. If a needed network is absent or suspended, do not choose another network merely to get past the form. Review supported alternatives as a complete route, including any conversion or bridging required.
Paste the address and compare the entire result with the wallet's receive view. Add the memo or tag if required. If the exchange automatically proposes a network from the address, verify it independently because address format can be shared by several networks.
Read any address-book or allowlist procedure before relying on it. Saving an address can reduce manual entry later, but a saved label is not evidence that the current destination still supports the same asset and network.
Review the amount you will actually receive
Enter the amount and inspect the fee, total deduction, and net delivery. Interfaces can let you enter either a total withdrawal or a target receipt. Identify which mode you are using so you do not misinterpret the fee.
Check the exchange's minimum withdrawal and any destination minimum. A transfer can satisfy one requirement while missing the other. A test amount must be large enough for both after deductions.
If you need the token for an immediate application, ensure the net amount is sufficient. You may also need a fee asset on the receiving network for the next transaction. Receiving a token does not automatically supply ETH, BNB, or another required fee balance.
Some funding methods can create a temporary withdrawal hold even after a purchase appears in the exchange account. Inspect the withdrawable balance and any account notice. Buying again may increase the commitment without removing the original restriction.
A withdrawal quote should be refreshed if you change the amount, network, or recipient. Review the final numbers immediately before approving the security check. Keep the confirmation for later reconciliation.
Follow processing before looking for a blockchain result
An exchange can perform internal checks before broadcasting. At that stage, you may have a withdrawal reference without a transaction hash. Use the account's withdrawal history to understand the current stage.
Once a hash is available, open the linked explorer and verify the network. Kraken's withdrawal documentation, for example, distinguishes internal stages from broadcast and confirmation. Other providers can use different status labels, so read their definitions.
A request held for review requires the provider's documented action. A receiving wallet cannot speed up a transfer that the exchange has not broadcast. Contact the sending exchange through an official channel when its internal stage needs clarification.
Do not treat every use of the word pending as the same problem. A payment hold, an exchange queue, and an unconfirmed network transaction have different evidence and different parties able to help.
Prove arrival from the receiving account
- Open the transaction on the correct network. Check the status, destination, and relevant asset-transfer details.
- For a native-asset transfer, inspect the transferred value. For a token, inspect the contract and token movement rather than relying only on the native-currency Value field.
- Open the same account and network in the wallet. Refresh the view and check whether the asset needs to be displayed through a verified token entry.
- If the destination is custodial, inspect its deposit record and current confirmation rules. On-chain success and an available platform balance can occur at different times.
- Retain the sending exchange's withdrawal reference, transaction hash, network, and amount received. These connect the provider's process with the public transfer.
Resolve a missing balance without repeating the withdrawal
If no hash exists yet, investigate the exchange's request status. If a hash is pending, monitor that record. If the record succeeded but the wallet is empty, compare the receiving address and account before changing anything.
When tokens have arrived at the correct self-custody address, a display issue does not require sending them again. Use reliable contract information and the wallet's official instructions to inspect the balance. Avoid following a link embedded in an unexpected token's description.
If the asset or network does not match a custodial destination's support, contact that destination with the public record. Recovery availability and any charges depend on the case. The sending exchange can establish what it sent, but it cannot necessarily credit the receiving platform.
If you suspect a wrong address, preserve the original data and stop repeating the route. A confirmed transfer cannot be undone by editing the saved address for future requests. Any practical recovery depends on who controls the actual destination.
Once the result is clear, update your route notes with the verified asset, network, and receiving account. Recheck those details for future transfers, particularly after a platform changes support or a wallet account changes.
When reconciling the receipt, use the token quantity rather than only the portfolio total. Market prices can change while a withdrawal is processed, and a wallet may use a different valuation source from the exchange. A lower displayed fiat value does not establish that fewer tokens arrived. Compare the requested amount, fee deduction, and confirmed net quantity first.
Reader questions
Does the exchange need my seed phrase to send to my wallet?
No. It needs supported receiving details, such as the public address and any required memo. Keep recovery material private.
Can the hash identify which exchange customer funded the withdrawal?
The public record shows on-chain activity. A custodial exchange may use shared sending infrastructure, so customer-level ownership requires its internal records.
Is the block explorer's fee always the amount deducted from my account?
Not necessarily. A provider can batch withdrawals or charge under its own withdrawal rules. Compare your account record with the on-chain delivery.