How to Change Your Phone Number on Gate: Whether the Old Number Works or Not

Before you switch: is your old number still in your hands?

Before you do anything, answer one question for yourself: can you still receive that verification text on your old phone number? The whole difficulty of this hinges on that single point.

If you can — say you've only swapped in a new SIM but the old number isn't cancelled yet, or the old handset is still switched on and getting texts — then you're on the standard swap. The platform assumes you're the account holder, checks a code sent to the old number, and waves you through: a few minutes' work. If you can't — the old number was cancelled long ago, the SIM is lost, or you're abroad and can't receive a home-country text — then the platform has no way to confirm it's you through the old number, so you'll take a slower but steadier route to prove your identity.

So don't charge straight to the change-number page and start filling things in. Work out the state of your old number first. Guess wrong, get stuck halfway through the standard flow with no code coming, and you've made more work for yourself, not less.

If your old number still receives codes: the standard swap

This is the easy road, and it's roughly the steps below. What each menu is actually called varies between app versions — go by what's on your screen — but the order is much the same:

• Open the security center. After logging in, find the "Security" area from your profile picture or settings; one of the items in there governs your phone binding.
• Find the phone-number row and tap "Change / Edit." It usually sits alongside email and 2FA, showing the number you currently have bound (with the middle digits masked).
• Verify your old identity first. This is the crux: the platform makes you prove that the person operating right now really is the account holder. Typically it asks you to enter a code sent to your old phone number, and sometimes stacks on one or more of an email code, 2FA, or your fund password on top. How many checks, and in what order, goes by what the page tells you. Don't resent the hassle — this is exactly the barrier that stops someone quietly rebinding your number behind your back.
• Enter the new phone number. Pick the right country code, type the new number in, tap send, and enter the code that arrives on the new number to confirm.

Once you confirm, the binding switches over and every code from then on goes to the new number. The one spot that genuinely trips people up is this: during the old-identity check, one of the items won't pass — the 2FA authenticator app was uninstalled ages ago, say, or you've forgotten the fund password. So before you start, it's best to confirm you have all of these to hand and working.

When the old number is lost, deactivated, or won't receive codes

If your old number can no longer receive codes, the standard flow is a dead end — because you can't clear the "verify the old number" gate. At that point the core logic changes: since you can't prove it's you with the old number, you prove that the account really belongs to you some other way.

The path usually goes like this: on the change-number or login page, find an appeal entry along the lines of "Can't receive code / Change verification method / Not receiving SMS," or contact official support directly and explain the situation. From there the platform will most likely have you go through an identity review — effectively proving you're the holder all over again, commonly a face scan plus a document check, much like the one you did for identity verification (KYC) in the first place. So have the document you used back then ready, and the review will go more smoothly.

Two realistic expectations to set here up front. One, it takes time: a manual or system review isn't as quick as typing in a code, and how long it takes to get a result goes by the official process — we don't make up a specific duration. Two, your account may be limited during the review: some actions get held first, which is normal protection, not the account being banned. Work patiently through the process, and once it passes you can bind the new number.

Don't rush to withdraw: that cooling-off period is normal

Once the swap goes through, a lot of people's first instinct is "finally, let me try a quick withdrawal" — only to find withdrawals are blocked, and assume something's broken. Don't panic; this is by design.

Changing your phone number counts as a sensitive security change, in the same class as changing your password or turning off 2FA. After an action like this the platform will usually add a withdrawal cooling-off period (commonly around 24 hours, though the exact length goes by what Gate's page tells you), during which withdrawals are blocked or limited. This isn't a fault — it's protecting you, precisely.

The reasoning is simple: what if the person quietly changing your binding today isn't you, but an account thief? The moment they're done, they want to move the coins straight out. That cooling-off period deliberately carves out a window so the real account holder has a chance to notice — "wait, why did I get a rebind notification?" — and pull things back, by locking the coins so nobody can whisk them away in the first instant. So when your own routine swap gets held up by that same stretch of time, it's the small inconvenience you're carrying on behalf of every user.

The practical takeaway is a single line: if you need to withdraw, don't do it on the same day as the swap. If you've planned ahead, change the number a day early; otherwise wait out the cooling-off period after the swap before you move any money.

One aside: don't lean on SMS — 2FA is what actually holds

While you're changing your number, it's worth clearing up a common misconception at the same time: a lot of people think "SMS verification = a secure account," and that once they've swapped in a new number everything's sorted. In fact the SMS layer has a real weakness of its own — there's a technique called SIM swapping where a fraudster gets your number "re-issued" onto a SIM in their own hands, and from that point every SMS code you'd receive lands with them instead. It needs no malware on your phone at all; it's a social-engineering attack on your mobile carrier — someone impersonates you to a support agent, claims a lost or damaged SIM, and has the number ported over. Once they hold the number, an SMS code isn't a barrier — it's a delivery service straight to the attacker.

What actually holds up is 2FA from an authenticator app (Google Authenticator, for instance): it's tied to your device, doesn't rely on the carrier's SMS channel, and can't be re-issued out from under you. So the sensible role for a phone number is as a backup and recovery channel — don't expect it to carry your account security on its own.

While you're in here for the swap, check two things in passing: whether 2FA is still on and bound to the device you're actually using now; and if you lost the authenticator when you last changed phones, set it back up while you're at it. For which security settings to switch on and which to do first, see which account-security settings to switch on. For the whole picture of an account, from sign-up to daily use, head back to the complete Gate beginner's guide to follow along.

Common questions