Getting started · VERIFICATION CODES
The Code Never Arrives: Check These in Order Before Hitting Resend
Registration stalls on the last step, or you need to withdraw and cannot get in. The page says the code was sent. The inbox and the messages app say otherwise. Most people then do the same thing: hit resend, hit it again, hit it again.
That is the least useful move available, and it makes the wait longer. A missing code never has one cause; it has two completely separate delivery paths that break in different places. Email codes travel the mail system. SMS codes travel routing between carriers. Search the wrong path and a hundred resends will not produce the code. This piece gives a fixed order that usually locates the problem in two minutes, then covers the documented self-checks and reset routes on Gate.
Work out which code you are missing
Several different things are called a verification code, and they come from very different places:
- Email and SMS codes are issued by the platform and delivered through a third party. They can be lost in transit, and they are what this article is about.
- The six digits in an authenticator app cross no network at all — the app computes them from a stored secret and the current time. They cannot fail to arrive; they can only fail to match, and a mismatch is nearly always a phone clock that has drifted. If the authenticator itself is gone, that is a different route entirely: see recovering a lost authenticator.
Email codes: six places, in order
Ordered by how often each one turns out to be the answer. Do not skip ahead:
- Spam and the promotions tab. This accounts for most cases, and the code is usually sitting there untouched. Mark the sender as not spam while you are there so it stops happening.
- A typo in the address. A missing letter, .con instead of .com, gmial instead of gmail — the code was sent, just to somebody else. Go back to the form and read the address character by character.
- A full mailbox. Once a free mailbox hits its quota, new mail bounces silently and you see nothing at all on your side.
- Forwarding or filter rules. Rules you set years ago, or an extension you installed once, can archive or delete anything matching a keyword.
- A work or school address. Institutional mail gateways frequently block overseas senders wholesale and do not bounce. This is the classic "everything is correct and nothing arrives" case.
- Switch to a mainstream mailbox. If the first five come up empty, stop digging. Retry with a common public provider; it usually works first time.
The order matters. The first three take a minute and you can do them yourself; four and five mean digging into settings; six is the fallback. People who work backwards tend to switch mailboxes first, end up registering a second account, and create a bigger problem than the one they started with.
SMS codes: usually not your fault
The SMS path is far longer than the email one: platform, messaging provider, international routing, your carrier, your handset. Any hop can drop the message without notifying anyone. Five common break points:
| Break point | What it looks like | What you can do |
|---|---|---|
| Wrong number | Never arrives, no matter how many resends | Read it back digit by digit |
| Country code or leading zero | Same, and the hardest to spot yourself | Pick the country from the dropdown, drop the leading zero |
| Security app on the handset | Other texts arrive, this one does not | Check the app's blocked list |
| International routing | Intermittent; sometimes arrives hours later | Switch to email rather than waiting it out |
| Coverage itself | Never arrives, and nothing explains why | Read the platform's current SMS coverage note |
The last one is the one people miss. Exchanges support SMS verification in a defined set of countries and regions, and that set changes with regulation and operations. If your region is not currently covered, the page will normally not explain that; you just see "sent" and then nothing. The only effective response is to use email instead.
Why resending slows you down
Hammering the button is not merely useless — it actively works against you:
- It trips rate limiting. A burst of requests in a short window gets throttled, which moves you further back.
- The old code may be voided. Issuing a new one usually invalidates the last one — including the one that was still in transit.
- SMS queues. International delivery can take minutes by design. Five taps in one minute does not speed up a queue.
The right rhythm is: send once, wait one to two minutes, spend that time checking spam and spelling, then resend if it still has not landed. Use the wait to investigate, not to press the button.
A two-minute checklist
| Symptom | Check first | Still nothing |
|---|---|---|
| Email code missing | Spam and promotions | Read the address back → switch mailbox |
| Mailbox always worked, suddenly does not | Quota, and any new filter rule | Try a different address once to confirm it is this mailbox |
| SMS code missing | Number, country code, leading zero | Handset security app's blocked list → move to email |
| You are abroad | Roaming, and whether other international texts arrive | Move to email; do not gamble on routing |
| Authenticator code rejected | Phone system clock | Enable auto sync; if it persists, treat it as a lost authenticator |
Documented checks and reset routes on Gate
Gate's guide to binding and unbinding a phone number gives three self-checks when an SMS does not arrive: whether the number was entered correctly, whether the phone has normal signal, and whether a security app on the handset intercepted it; contact support if none of them resolve it. The same page also states that once a number is unbound you can bind a new one immediately, with no waiting period.
On coverage, there is a separate note on the countries and regions where SMS verification is supported, which opens by saying the supported list may change with regulatory or operational adjustments and that you should go by the latest official announcement. We are not reproducing the list here — it moves, and a copy will eventually mislead someone. Open that page and read the current version.
If the number genuinely cannot receive codes and needs resetting, the documentation splits it three ways. If you can still sign in, submit the request from the security reset page. If you cannot sign in, the web interface will not accept the submission — open the app, reach the security verification screen, and tap the unable-to-verify option at the bottom (it only appears once you are on that screen). If you have also forgotten the password, start from forgot-password on the app's login page, enter the phone or email, then choose the option for not receiving the code and reset the verification method. All three note that review is normally completed within 24 hours with the result sent by email — check the spam folder too.
If you simply want a different number and the old one still receives codes, the flow is shorter and lives in changing your phone number. Interfaces get redesigned and menu names change, so treat what is on your screen as authoritative. We checked this against Gate's published help documentation on 2026-09-03.
Three things not to do
- Do not register again with a different email. That leaves you with two accounts, and the first one may already hold your documents or a balance. Run recovery and reset instead of creating something new.
- Do not go looking for a code-receiving service. Handing someone else the ability to receive your verification codes is handing them the account. Any message asking you to forward a code, however reasonable the framing, is the standard script of a scam.
- Do not bind only one channel. Email and phone back each other up. With only one bound, a failure leaves you waiting on a review; with both, you usually fix it yourself in five minutes.
Editorial check
What our editors checked
Two things are worth calling out after reading the official documentation. First, SMS coverage is a real constraint and a moving one — the platform itself notes the supported list changes with regulatory or operational adjustments. Most "code not arriving" articles never mention this layer, which leaves readers hunting for a fault in their own handset that is not there. Second, the reset route does not work from the web while you are logged out: it has to be the app, and the entry point only appears once you are on the security verification screen. Not knowing that leads people to conclude the platform offers no path at all. If you have already decided to change the number, go to changing your phone number; if what you lost is the authenticator rather than the phone, go to recovering a lost authenticator.