---
title: "Test phone-first sign-up without receiving real SMS · Proxy Mail QA"
description: "Sign-up by phone and SMS code is the norm in China, India, Pakistan and South-East Asia. How to test it with test numbers and a test-mode code that never ships."
url: https://proxymail.qa/solve/phone-first-sign-up-testing
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# Test phone-first sign-up without receiving real SMS

In China, India, Pakistan and much of South-East Asia, people sign up with a phone number and a code by SMS. Testing that with real messages is slow and costly, and in some countries hard to set up at all. Test numbers with fixed codes do the same job without a message being sent.

Updated 13 November 2026

Phone-first sign-up is common across Asia: an 11-digit number and an SMS code in China, a mobile number and a one-time code in India and Pakistan, and in Indonesia often a code by WhatsApp. To test it you need codes that arrive every time, quickly, for numbers you control. Real SMS gives you none of that reliably.

## Why real SMS is hard to test with

- **Registration before sending.** India requires businesses to register their sender ID and message templates (DLT) before SMS are delivered. In mainland China, SMS signatures and templates are approved by the provider before use.
- **Real-name SIMs.** In China and Pakistan a SIM card is registered to a person’s ID, so a team can’t simply buy a stack of test numbers.
- **Cost and delays.** Every test run pays for messages, and delivery can take seconds or minutes.
- **Virtual numbers refused.** Lookup services can tell a virtual (VoIP) number from a mobile one, and many apps refuse virtual numbers before sending a code, as bots use them. Online SMS services hand out exactly those.

## Option 1: your auth provider’s test numbers

Most auth providers let you register test numbers that take a fixed code and never send a message:

- **Firebase Authentication:** add up to 10 fictional numbers, each with a 6-digit code, under Phone numbers for testing in the Phone provider’s settings. No SMS is sent.
- **Supabase Auth:** add test numbers and their codes under **Authentication → Sign In / Providers → Phone**, in Test Phone Numbers and OTPs, with a date they stop working. An SMS provider must still be set up, but no SMS is sent.
- **Clerk:** in development, numbers from +1 (XXX) 555-0100 to 555-0199 take the code 424242.

Keep these in development and staging projects. A production project should have none.

## Option 2: a test-mode code in your own backend

If you send SMS yourself, a test mode with a fixed code is the usual answer. In China it’s often called a universal code (万能验证码). Done carelessly, it is a way into every account. Done carefully:

1. **Limit it to listed numbers.** The fixed code works only for numbers on a short test list, never for any number.
2. **Turn it on by setting, off by default.** Read it from an environment variable that only development and staging set.
3. **Leave it out of release builds.** In a mobile app, keep the code path behind a build flag the release build doesn’t include. Check the release build refuses the code before it ships.
4. **Check production refuses it.** Add a test to your release checks that signs in to production with a test number and the fixed code, and expects it to fail.

## What to test in the flow

- A wrong code is refused, and the number of tries is limited.
- An expired code is refused, and asking again sends a new one.
- After a resend, an older code works or doesn’t, as you decided, and the app says which.
- The number is stored in one format (with the country code) whatever the person typed: spaces, a leading 0 or +86.
- Someone who signs up with the same number again is sent to sign-in, not given a second account.
- If the app also asks for an email address, the confirmation email arrives and works. Proxy Mail QA covers that step: create an address, sign up with it, and wait for the code or link.

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-phone-first-sign-up-testing)

## Questions

### Can Proxy Mail QA receive SMS codes?

No. Proxy Mail QA receives email only. Real-name rules for SIM cards in China and Pakistan, and India's registration rules for business SMS, make shared test numbers impractical, so we don't offer them. Use your provider's test numbers, and Proxy Mail QA for the email steps.

### Can I use a free online number to receive the code?

Don't. Anyone can read the messages on those sites, so anyone can take over an account made with one. Many apps also refuse virtual numbers.

### Is a fixed test code safe?

Only when it's limited to a short list of test numbers and can't work in a release build. A fixed code that works for any number in production is a way into every account.

### My form needs a phone number but never sends an SMS. What should I type?

A number from a range set aside for fiction: 07700 900000 to 07700 900999 in the UK, ACMA's list of 0491 57x xxx numbers in Australia, or 555-0100 to 555-0199 after any area code in North America. They look real and reach no one. Elsewhere, add one of your app's own test numbers per country to the project's ready-made Phone number: in Project settings → Custom fields, or with save\_custom\_field for agents.

## Related guides

- [Test sign-up and email verification](https://proxymail.qa/solve/email-verification-testing): A fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.
- [Test OTP and one-time login codes](https://proxymail.qa/solve/otp-code-testing): Codes pulled out of the email with a Copy button and a countdown when the email says how long they last.
- [Test magic links and passwordless sign-in](https://proxymail.qa/solve/magic-link-testing): Single-use links that are never opened or prefetched on our side, so they still work when you click them.
- [Test password reset emails](https://proxymail.qa/solve/password-reset-testing): Request, receive and use reset links, and keep the new password saved next to the test account.
- [Stop sharing one Gmail inbox for QA](https://proxymail.qa/solve/shared-test-inbox): Private, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.
- [Stop using Gmail for test codes](https://proxymail.qa/solve/gmail-test-inbox): Why reading codes from Gmail over its API or IMAP keeps breaking your tests, and how one address per test removes the inbox from the problem.
- [Email limits in auth providers while you test](https://proxymail.qa/solve/auth-email-limits): Supabase's 2 an hour, Firebase's 5 email links a day, Auth0's 10 a minute and Clerk's 100 a month, and how to send your own.
- [Let test addresses through a disposable-email block](https://proxymail.qa/solve/disposable-email-blocks): Keep the block for real users and let your test domains through in development and staging, with one setting you can't ship by mistake.
- [CAPTCHA, Google and Apple sign-in in tests](https://proxymail.qa/solve/captcha-and-social-sign-in-tests): Published test keys for reCAPTCHA, hCaptcha and Turnstile, and what to test instead of automating Google and Apple sign-in.
- [Take QA notes by voice with Wispr Flow](https://proxymail.qa/solve/voice-notes-wispr-flow): Dictate what each test account is for, its state and what you found, straight into its notes, in seconds.
- [Test sign-up for people in China](https://proxymail.qa/solve/china-sign-up-testing): Real-name rules, a 姓名 field and province menus, a safe test code, and 身份证 numbers that can't be anyone's.
- [Test sign-up for people in Japan](https://proxymail.qa/solve/japan-sign-up-testing): Furigana fields, 全角 and 半角, postcode lookups and LINE sign-in, with test accounts that have Japanese names.
- [Made-up test accounts, not masked production data](https://proxymail.qa/solve/synthetic-test-data): A masked copy of production still holds real people. Test sign-up with made-up accounts that no one owns instead.
- [Test sign-up for people in India](https://proxymail.qa/solve/india-sign-up-testing): Test accounts with one name, PIN codes that agree with the city, phone-first sign-up, Hindi labels, ID fields and card mandates.
- [Test sign-up for people in Pakistan](https://proxymail.qa/solve/pakistan-sign-up-testing): Test accounts with Pakistani names in both scripts, CNIC fields that never hold a real number, and phone-first sign-up.
- [Fill phone and ID fields safely](https://proxymail.qa/solve/phone-id-and-tax-number-fields): Numbers set aside for fiction, your app's own test numbers, ID values that never match a real person, and KYC sandbox values, filled the same way by agents and tests.
- [Verification link points to localhost:3000](https://proxymail.qa/solve/localhost-links): Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.
- [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): Emails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.
- [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): Missing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.
- [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): The login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.
- [Check that one user can't see another's data](https://proxymail.qa/solve/vibe-coded-app-data-leaks): A curl with the anon key for tables anyone can read, and two signed-up accounts for policies that let every user read every row.
- [Triage sign-up and login bug reports with an agent](https://proxymail.qa/solve/bug-report-triage): An agent signs up with a new test address, watches the inbox, and answers replicated, not replicated or inconclusive, with the evidence.
- [A self-improvement loop for agents that build sign-up](https://proxymail.qa/solve/agent-self-improvement-loop): The agent builds, signs up with a test address, reads what the email did, fixes its own work and runs again. Proxy Mail QA is the tool it checks with.
- [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests): A complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.
- [Test sign-ups over several screens](https://proxymail.qa/solve/multi-step-sign-up-testing): One test account across every screen of the sign-up, with your form's own questions filled the same way each time.
- [Test sign-up emails in Cypress](https://proxymail.qa/solve/cypress-email-tests): A complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.
- [Test sign-up emails with pytest](https://proxymail.qa/solve/pytest-email-tests): A complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.
- [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing): The coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.
- [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing): The unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.
- [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse): Versions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.
- [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): Let an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.
- [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): An agent tries every field with values made for it, then finishes the registration through the email.
- [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): A checklist for your browser and phone, in the order that finds the most problems.
- [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): 12 checks for a form with an email, a password and perhaps a name.
- [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): One test account across every screen, and the verification email wherever it comes.
- [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): The emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.
- [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): A new, real address for every registration try, with the code or link ready to use.
- [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): Test accounts with saved passwords and an inbox for codes, magic links and resets.
- [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST's numbers for password length and rules, and test passwords to check yours.
- [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): The eight usual causes of a silent password field, and how to tell which one it is.
- [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): A whole-site check in an afternoon, in the order that finds the costliest problems first.
- [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): A toolkit by area, most of it free and none of it ours, except for account emails.
- [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): The full list, then which parts a simple site can skip.

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)
