ChatGPT / OpenAI Phone Verification Guide
OpenAI is the strictest common verification flow: number type, IP, device fingerprint and account history are all scored. That is why the same steps work for one person and fail ten times for another. Here is how the flow actually behaves.
When OpenAI asks for a phone
- New account signup in most regions;
- Logins from a new device or country;
- Abnormal behaviour or rapid node switching;
- Some product lines (Codex, API platform) in specific cases.
Why VoIP numbers fail
OpenAI screens carrier type. VoIP ranges, public pool numbers and heavily abused lines are refused — usually as 'this phone number is already in use', or by silently never sending a code.
We rent US T-Mobile carrier numbers (non-VoIP), which is why they pass far more often. But the number is only half of it: IP and account environment matter just as much.
Step-by-step verification
- Lock your network first — clean US node, ideally residential;
- Buy the number (2-10 days to test, 11-30 days for accounts you keep);
- Enter it with +1, no spaces;
- Request the code once, wait 30-60 seconds, read it in your private link;
- Submit and finish verification;
- Keep the same IP and device for the next 24 hours.
Will it ask again later?
- New country or new device logins;
- After clearing browser data;
- Subscription or payment changes;
- Rapid switching between devices.
Keep and renew the number for accounts you care about.
One number per account
OpenAI records number-to-account binding: reusing a number for a second account is normally refused. For multiple accounts, use a separate number, browser profile and egress IP each.
Code missing or number refused
- Refresh the SMS center;
- Wait 1-2 minutes;
- Switch to a clean US node — IP first, then number;
- Swap the number to a different prefix;
- If it says 'already in use', move to a fresh number;
- Contact support for the prefixes working best that day.
Do API users need a number?
API keys are created inside a verified account, so the account itself must pass phone verification once. For automation, keep one number per account and maintain an account ↔ number ledger so renewals never break a login.
Tier and environment matrix
| Goal | Tier | Environment |
|---|---|---|
| Single test account | 2-10 days | Clean US node, leave it alone |
| Primary ChatGPT account | 11-30 days + renewal | Fixed residential IP and browser |
| Codex / API business accounts | 21-30 days + renewal | Isolated profiles, one doc per account |
| Bulk signups | One number per account | One environment and IP per account |
Top up with USDT or Alipay/WeChat, buy the number in the market and read the code in your private SMS link. Check live prices and stock (US T-Mobile real SIM, non-VoIP, 2-30 day tiers with renewal).
Open the marketContact supportFAQ
Is a phone number required?
In most regions yes, and new devices can trigger it again.
Why does it say the number is already in use?
That number already verified an OpenAI account. Use a fresh one.
Do VoIP numbers work?
Practically never — OpenAI screens carrier type. Use a US carrier number.
How many accounts per number?
One.
The code never arrives — what now?
Refresh, wait 1-2 minutes, switch to a clean US node, then swap the number.
Which tier should I buy?
2-10 days to test; 11-30 days with renewals for accounts you keep.
Do I need a number for the API?
The account needs verification once; API keys are created inside it.
Does Codex use the same flow?
Same account system — the same number works.