testingphone-numberswoocommercecheckout
International Test Phone Numbers for Form & Checkout Testing (2026)
July 27, 202614 min read·ShopMonitor Team
Loading…
Need a phone number to test your checkout form, registration page, or SMS verification flow — without triggering real messages or flagging fraud systems? Here's every test phone number you need, organized by country and provider.
Pair this with our Stripe test cards reference for full checkout testing.
Every WooCommerce store, SaaS signup form, and booking system asks for a phone number. But when you're testing, you can't just type random digits:
The solution: use officially designated test numbers, fictional number ranges, and provider-specific sandbox numbers. This guide collects all of them in one place.
Animated diagram: a fictional phone number passes format validation but never connects to a real subscriber.
If you're in a hurry, here are the most commonly needed test numbers:
| Use Case | Number | Format |
|---|---|---|
| US form testing (generic) | +1 (555) 555-0100 | US fictional range |
| UK form testing (generic) | +44 20 7946 0123 | UK Ofcom test range |
| Stripe phone field | +1 (555) 555-0123 | Any valid-format number works |
| PayPal Sandbox | — | Use your sandbox buyer account email |
| Twilio test SMS | +15005550006 | Twilio magic number (valid) |
| Google reCAPTCHA phone test | — | Use reCAPTCHA test keys instead |
| Firebase Auth test | — | Configure in Firebase Console → Test phone numbers |
Most countries designate specific number ranges for fictional use in TV, film, and software testing. These numbers are guaranteed to never be assigned to real subscribers.
The +1 country code covers both the US and Canada (NANP). The FCC reserves 555-0100 through 555-0199 in every US/Canadian area code for fictional use.
Pattern: Pick any valid US/Canadian area code + 555-01XX (where XX = 00–99).
| Number | Notes |
|---|---|
| +1 (213) 555-0100 | Los Angeles area code |
| +1 (212) 555-0100 | New York area code |
| +1 (415) 555-0100 | San Francisco area code |
| +1 (416) 555-0100 | Toronto area code (Canada) |
| +1 (800) 555-0199 | Toll-free fictional number |
Ofcom reserves specific ranges explicitly for testing and drama use. The mobile range (+44 7700 900XXX) is especially useful for SMS verification flows.
| Number | Notes | Range |
|---|---|---|
| +44 20 7946 0123 | London (020) | 0000–0999 |
| +44 29 2018 0456 | Cardiff (029) | 0000–0999 |
| +44 113 496 0789 | Leeds (0113) | 0000–0999 |
| +44 7700 900123 | UK mobile | 900000–900999 |
The Bundesnetzagentur designates these ranges for testing and dramatic use. For SMS verification, use Twilio or Firebase test numbers instead.
| Number | Notes | Range |
|---|---|---|
| +49 152 28817386 | Mobile (Vodafone test) | — |
| +49 172 0000001 | Mobile test range | 0000000–0000009 |
| +49 30 23125 456 | Berlin landline | 000–999 |
| +49 69 90009 789 | Frankfurt landline | 000–999 |
| +49 89 99998 234 | Munich landline | 000–999 |
ACMA reserves fictional number ranges for testing and drama.
| Number | Notes | Range |
|---|---|---|
| +61 2 5550 0042 | NSW/ACT landline | 0000–0099 |
| +61 3 5550 0017 | VIC/TAS landline | 0000–0099 |
| +61 491 570 006 | Mobile (fictional) | — |
ARCEP reserves a block for fictional use.
| Number | Notes | Range |
|---|---|---|
| +33 1 99 00 00 12 | Paris landline | 00–19 |
| +33 6 39 98 00 42 | Mobile | 00–99 |
Common toll-free and mobile test formats.
| Number | Notes | Range |
|---|---|---|
| +31 800 0004 | Toll-free test | 0000–0009 |
| +31 6 98765432 | Mobile (commonly used test) | — |
Standard mobile test number.
| Number | Notes |
|---|---|
| +46 70 000 00 00 | Mobile test |
Japan does not officially publish fictional number ranges. Use provider sandbox numbers for any testing that could trigger outbound communication.
| Number | Notes |
|---|---|
| +81 90-0000-0000 | Commonly used mobile test (090 prefix) |
| +81 3-0000-0000 | Tokyo landline test format |
For Indian phone verification, Firebase Auth test numbers or Twilio test credentials are the safest option.
| Number | Notes |
|---|---|
| +91 00000 00000 | Generic test (may fail strict validation) |
| +91 98765 43210 | Commonly used test format |
Common São Paulo mobile test format.
| Number | Notes |
|---|---|
| +55 11 99999-9999 | São Paulo mobile test |
When you're testing SMS verification, OTP delivery, or phone-based authentication, you need provider sandbox numbers — not just numbers that pass format validation.
Twilio
Twilio provides "magic numbers" for testing without sending real SMS or making real calls. Use with your Test Account SID and Test Auth Token — no real messages, no charges.
| Number | Behavior |
|---|---|
| +15005550006 | Valid number — test succeeds |
| +15005550001 | Invalid number — returns error |
| +15005550007 | Cannot route — returns error |
| +15005550008 | Blocked number — returns error |
| +15005550009 | Non-mobile — SMS fails |
Firebase Authentication
Firebase lets you register up to 10 test phone numbers with predefined verification codes. Best option for phone auth in mobile apps and SPAs.
Vonage (Nexmo)
Use Vonage test mode by setting sandbox=true in API calls.
| Number | Behavior |
|---|---|
| +447700900000 | Valid UK test number |
| +14155550100 | Valid US test number |
AWS SNS
AWS SNS does not provide specific test numbers, but the SMS sandbox (enabled by default for new accounts) restricts sends to verified numbers only.
Add verified phone numbers to your sandbox to prevent accidental sends to real customers.
I just need a number to fill a required phone field (no SMS sent)
Use your country's fictional range from the tables above. For the US, that's any area code + 555-0100 through 555-0199.
I'm testing SMS verification / OTP delivery
Use your SMS provider's test credentials. Twilio magic numbers or Firebase test phone numbers are the most common options.
I'm testing international phone validation (does my form accept +44 numbers?)
Use the Ofcom (UK), ACMA (Australia), or other country-specific test ranges from the tables above. These will pass libphonenumber validation.
I'm testing WooCommerce checkout with a phone field
Most WooCommerce checkout forms validate format, not deliverability. Use fictional numbers above. If Twilio/SMS plugins are active, use Twilio test credentials.
I need to test phone formatting across 20 countries
Use one number from each country's fictional range in this guide. For countries without an official range, use the libphonenumber demo to generate a valid-format example.
Using +1 (000) 000-0000 or all-zeros
Using +44 7911 123456 for UK testing
Testing with real coworker phone numbers
Hardcoding test numbers in production
Assuming fake numbers won't be validated
Manually entering test phone numbers into your checkout form is fine for one-off tests during development. But what about after launch?
Every WooCommerce update, plugin update, or theme change can break your checkout form — including the phone field validation. A field that accepted +44 numbers yesterday might reject them today after a Checkout Block update.
ShopMonitor runs automated end-to-end checkout tests on your WooCommerce store, filling in all form fields (including phone numbers) and completing the full purchase flow. If the phone field breaks, or any other part of your checkout stops working, you get an alert within the hour.
ShopMonitor runs real test purchases through your checkout around the clock and alerts you the moment anything breaks — phone validation, payment fields, or the full order flow.
No credit card required. Set up in 5 minutes, no code changes.
Last updated: July 2026. Phone number allocations verified against FCC, Ofcom, Bundesnetzagentur, and ACMA current registers. Provider test numbers verified against current Twilio, Firebase, and Vonage documentation.
About the author
Written by the Winning Solutions team — the agency behind ShopMonitor, automated WooCommerce checkout monitoring.