The account asked for a confirmation code, you wait — and nothing arrives. What makes this unpleasant is that there are exactly five causes and they all look identical: an empty waiting screen. The good news is that three of the five you close yourself in a minute if you know where to look. The bad news is the remaining two mean the account is unusable and goes for replacement. Let us walk the delivery chain link by link.
Where the chain actually breaks
A code passes through three stages: the platform generates it, a delivery channel carries it, you read it. The failure is almost always in the second or third link, not the first. So the first thing to establish is where the platform actually sent the code: to the linked email or by SMS to the registration number. The confirmation screen usually shows a masked address or the last digits of a number — that is your hint which way to look.
If the delivery included a 2FA secret, there is nothing to wait for at all: the code is generated on your side. More on that below.
Code to email
Confirm you actually have mailbox access
Some batches hand over the inbox along with the account. Then the mailbox login and password sit in the same delivery file as the account itself. Accounts that ship with email are grouped in the accounts with email category.
Spam and service folders
The most common mundane cause. Code emails land in spam or in a separate notifications folder, especially for mailboxes on non-standard domains. Check every folder, not just the inbox.
IMAP access
If you read the mailbox through a mail client or software rather than the web interface, IMAP access may be disabled on the provider side. The message is sitting in the mailbox but never reaches you. Verify by logging in through the web.
Code by SMS
The registration number is not handed to the buyer
This is the key point people stumble on most. Registration phones come from SMS-receiving services and are not retained with the batch. If the platform demands a code specifically to the original number, there is no legitimate way to get it.
Number geo and carrier
Even when a number exists, SMS delivery through receiving services is unstable and geo-dependent. Waiting for a code on a number you attached yourself from a disposable service is also a dead end: at the next check it will be gone.
A 2FA secret instead of waiting
The most predictable option. A secret is a string from which your authenticator app computes a one-time code itself every thirty seconds. Neither email nor carrier is in the chain, so there is nothing to break. How it works is detailed in our piece on the 2FA secret, and the accounts themselves are in the 2FA category. If you keep running into code waits, that is an argument for batches with a secret rather than ones relying on SMS.
Mini FAQ
How long before I decide the code is not coming?
A few minutes. Beyond that, repeat requests only add events to the account without changing the outcome.
Can I request the code again?
Once, yes. A run of back-to-back requests is itself read as suspicious activity.
No code and no email in the batch. Is that a replacement?
Yes, this is a routine case: confirmation demands data that was never in the delivery. The procedure is described in our article on guarantee and invalid replacement, and extended terms are in the guaranteed category.
Conclusion
The diagnostic order: identify the delivery channel, check mailbox access and every folder, rule out IMAP, and only then draw a conclusion. If the code goes to the original number, or a confirmation is required that never came with the batch, that is not a reason to hunt workarounds but a reason to claim a replacement. And to stop meeting this problem, buy accounts where the second factor ships as a secret.