Withdrawals · WITHDRAW

Gate Withdrawal Guide: Steps, 24-Hour Holds, Wrong Chains

Gateway Guide editors Updated 2026-10-14 About 11 min
Gate withdrawal walkthrough: a step-by-step look at picking the coin, choosing the network, pasting the address and entering the fund password
At this step, the one field worth a second look is "network."

The order, first. On the assets page tap Withdraw, pick the coin, paste the receiving address, choose the network the receiving side supports, enter the amount, check the fee and the amount that will arrive, then confirm with your fund password and two-factor code. Sending to a new address for the first time? Send a small test amount.

Button greyed out, or a message saying you can't withdraw? Think about the last 24 hours. Gate's withdrawal FAQ says withdrawals are restricted for 24 hours after you first complete KYC, change your authenticator or update your phone number, and crypto bought through P2P can only be withdrawn after 24 hours (checked October 2026; the help centre's current wording is final). How to work out when the hold ends, and who to contact if it doesn't lift, is covered in withdrawals disabled for 24 hours.

After you submit, the withdrawal record shows a status. Processing means Gate is still handling it. Sent and waiting for blockchain confirmation means it is on-chain, so take the transaction ID to a block explorer. Canceled means it was not sent, for example because the address was wrong, and the coins go back to your account. The steps below go into detail, with most of the weight on choosing the network and on tracing a withdrawal that hasn't arrived.

Get these few things ready before you withdraw

Lay the groundwork before you touch anything, and you'll dodge most of the "stuck halfway through a withdrawal" awkwardness. Three things, in order:

  • Finish identity verification. If you haven't passed KYC, the withdrawal function is most likely greyed out, or your limit is squeezed down to almost nothing. It's an anti-money-laundering requirement you can't route around, so get it sorted first.
  • Save the addresses you use in the address book (the “whitelist”) — worth doing. Gate’s help center calls it a withdrawal address whitelist, but what you actually get is an address book on the withdrawal page: open Address Book, add a new address, save your regular receiving addresses, and next time pick from the list instead of pasting by hand — fewer typos, and less room for clipboard malware to swap an address. It does not restrict withdrawals to the list, and it isn’t insurance if your account is taken over. When you add an address there’s an option to mark it as trusted so later withdrawals to it skip the fund password and other checks; if someone gets into your account, that leaves them one check fewer, so as a beginner leave it unticked. The steps are in Gate’s help article How to Whitelist Withdrawal Addresses; for which security settings come first, see which Gate account-security settings to switch on.
  • Have your fund password and two-factor ready. Beyond being logged in, withdrawals usually ask you to enter the fund password again, along with a two-factor code (authenticator app or SMS). If you set one but can't remember it, recover it ahead of time; if you've changed phones since setting up 2FA, confirm it still produces codes. A fund password you just set or changed also starts a 24-hour hold on withdrawals.

Of these three, the address book is an optional convenience, while verification, the fund password and two-factor are hard gates. If you haven't even set up your account's basic protections, don't rush to withdraw — go back through the security section of the beginner guide first, then come back.

Step by step: from picking the coin to the fund password

Once you're set, open your assets page and find "Withdraw" (some versions call it "Withdrawal"). The order of the steps below is essentially the same for every coin — only the middle few fields change:

  • Pick the coin. First choose which coin you're withdrawing — USDT, BTC, ETH, and so on. Get the coin wrong and everything after it is wasted, so settle this field first.
  • Paste the receiving address. Copy the address from your wallet or the other platform and paste it straight in — don't type it by hand. After pasting, check the first and last few characters against the source. If you can scan a QR code, do that; it's less error-prone.
  • Choose the network (chain). This is the heart of the whole piece. The same coin often supports several networks, and the one you choose has to match the network the receiving address supports, exactly. There's a whole section on this below, but for now: don't just coast on the default value.
  • Enter the amount. Type in how much you want to withdraw, and watch the minimum withdrawal and your available balance shown on the page. If you want to send everything, note that the fee comes out of the withdrawal amount.
  • Check the fee and the amount that arrives. The page usually shows the withdrawal fee for that network, plus how much actually lands after the fee is taken out. How high the fee is, and how long confirmation takes, vary a lot by coin and by network — go by what Gate's withdrawal page shows at the time, not some number written down elsewhere.
  • Enter the fund password / two-factor. The last step is identity verification: enter the fund password, the authenticator or SMS code, and possibly an email confirmation. This is the platform's last chance to let you stop, so before you submit, scan every field above one more time.
Tip Some coins and networks add an extra memo / tag field, especially when you withdraw to an exchange's internal address. Leave it blank or get it wrong and the coins may never reach the other account. If the receiving side asks for it, fill it in — and go by the information they give you.

Why choosing the network is the make-or-break step

A lot of people can't see the problem: I pasted the address correctly, so why can't I just pick any network? Because the address and the network are bound together. The same recipient on a different network either has an entirely different address format, or — even when the address looks the same — is only recognized on one specific network.

Take USDT as the most common example: it exists on TRC20 (Tron), ERC20 (Ethereum), and several other chains. If you pick ERC20 on Gate and send it out, but the address the other side gave you is a TRC20 address, that transfer has gone onto a chain where they can't receive it. The address "looked" accepted, the money genuinely left your account — but it went somewhere wrong.

So the right approach is always to work backwards: look first at what network the receiving side (your wallet, or the other platform's deposit page) says it supports, then go back to Gate and set the network to match it exactly. You don't pick whichever is convenient for you — you pick the one the other side can actually receive on. For how to weigh fee and speed across different chains for the same coin, and which one a beginner should reach for first, see which chain to use for USDT withdrawals.

Which way to check Remember the rule: the network is decided by "what the receiving side supports," not by "what's cheapest for you." Confirm which chain they receive on first, then choose it on Gate.

What happens if you pick the wrong chain or mistype the address

This is the section to read most carefully. On-chain transfers have a trait that's completely unlike a bank transfer: once confirmed on the chain, they're usually irreversible. There's no "cancel" button, and Gate's support can't claw back a transaction that's already on the chain — not because they don't want to, but because the blockchain simply doesn't support it. The outcomes fall into a few cases, in rising order of severity:

  • Wrong address, sent to a nonexistent address or someone else's: the money has gone somewhere you don't control. If that address has an owner, getting it back comes down to their goodwill; if it's an invalid address, it's usually unrecoverable.
  • Wrong network, sent to an incompatible chain: this is the most dangerous case. Send coins to a network the other side doesn't support at all, and the assets may be permanently lost. In a few cases, if the two chains happen to be compatible and the recipient is able to recover them on the other chain, there's a sliver of hope — but that's luck, not something to count on.
  • Sent to the right platform but missing the memo / tag: this one's relatively less hopeless. Sometimes the receiving platform can help recover the funds using the transaction hash, but the process is a hassle, takes time, and isn't guaranteed.

As you can see, none of these is an "easy undo." Which is why this piece keeps hammering on checking, and on the small test in the next section — both are really about trading a few minutes for an outcome you won't be kicking yourself over after you hit confirm. For how to drive down the risk of both fumbles and theft at the account level, pair this with Gate account-security settings.

Always send a small test amount first

If you take just one line away from this piece, take this one: the first time you withdraw to a new address, send a small amount first.

The logic is plain. On-chain transfers are irreversible, as covered above, so rather than betting a large sum all at once on "I didn't get anything wrong," send a small amount ahead to scout the route. Once that small amount actually lands in the other account and the network confirms cleanly, you've personally verified the whole set — right coin, right address, right network, right memo — and you can withdraw the rest with peace of mind.

Yes, a test costs you one extra withdrawal fee, but that's nothing next to losing the entire transfer. It's all but mandatory the first time you send to a new address, or when you're using a network you're not familiar with. For later withdrawals to the same address over the same network, you don't have to test every time — but the first one is worth it.

Nothing arrived? Troubleshoot in this order

After you submit, if the money is slow to reach the other account, don't panic — and definitely don't rush to fire off the same withdrawal again (that's how things spiral). Work through the order below and you'll locate the problem in most cases:

  • Check the status on Gate's side. Go back to your withdrawal record and look at this transaction's status. If it's still "processing" or "under review," the platform hasn't sent it to the chain yet — just wait. Large or unusual withdrawals can sometimes trigger a risk-control review that needs manual clearance; in that case all you can do is wait, so don't resubmit.
  • If the status shows sent, check the chain. Copy the transaction hash (TXID) and look it up on the block explorer for that network. For Ethereum, you can paste the hash into Etherscan and see how many confirmations the transaction has and whether its status is successful. This step tells you which end the problem is actually on.
  • The chain shows it's not confirmed yet: most likely network congestion — a lot of transactions queued on that chain at the time, so it needs more confirmations. The money isn't lost; wait until it has enough confirmations and it usually arrives.
  • The chain shows it's confirmed but the other side still hasn't received it: the problem is usually at the receiving end — possibly the wrong network (sent to a chain they can't receive on), a wrong address, or a missing memo / tag. At this point, take the transaction hash to the receiving platform to sort it out, rather than going back to Gate.

Put simply: if it's stuck on Gate's side, wait on the platform; if it's already on the chain, check the explorer; if the chain says success but it hasn't landed, go to the receiving side. Working out which end the problem is on is what keeps you from waiting for nothing or flailing around. Gate has also documented the various sticking points; for the withdrawal-related entries, see the Gate Help Center.

Checked against Gate's docs

Worth flagging after checking it

We checked these steps against Gate's withdrawal help pages. Three fields deserve a second look: the network (chain), because the one selected by default isn't necessarily the one you want, so set it to the one the receiving side supports; the receiving address, pasted or scanned, never typed, with the first and last characters rechecked; and the memo / tag, which you can't skip when sending to an exchange's internal address. Withdrawal fees and minimums change by coin and network, so there's no table here; read the line on the withdrawal page before you submit.

Common questions

The withdrawal shows as successful but the other side never got the coins. What now?
First copy the transaction hash (TXID) from your withdrawal record and check the transaction's status on the block explorer for that network. If the chain shows it confirmed, the problem isn't on Gate's end — go check with the receiving platform whether the address and network were entered correctly. If it's still unconfirmed, that's usually network congestion, and it generally arrives once it has enough confirmations.
Do I need to fill in the memo / tag field when withdrawing USDT?
It depends on the network and the receiving side. When you withdraw to an exchange's internal address, or use a network that requires a memo / tag, leaving this field blank or wrong can mean the coins never reach the other account. Go entirely by the information the receiving side gives you — if they ask for it, you must fill it in; don't leave it empty.
What's the minimum withdrawal amount, and how long does it take to arrive?
The minimum withdrawal, the fee and the confirmations required all differ by coin and by network, and they change with platform policy — go by what's shown on Gate's withdrawal page at the time. Arrival time also depends on how congested the network is, so go by the actual network conditions; there's no fixed standard duration.

Gateway Guide editors

This is the site's byline on its Gate sign-up, funding, fee and security guides; it does not refer to a verifiable team of real people. We don't give investment advice; data is marked "see the official page" and re-checked regularly. Spot an error? See corrections.