---
title: "Fill phone, ID and tax number fields in sign-up tests without real people's details · Proxy Mail QA"
description: "What to put in a sign-up form's phone, national ID, passport, VAT and tax number fields when you or your coding agent test it, and how ready-made fields keep every test account safe."
url: https://proxymail.qa/solve/phone-id-and-tax-number-fields
---

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

# Fill phone, ID and tax number fields without real people's details

A made-up phone number can reach a stranger, and random digits in an ID field can be a real person's. When a test or a coding agent signs up again and again, those values add up. Ready-made fields give every one of them values that can't belong to anyone. Where there's no such value, the field stays empty with a note.

Updated 15 November 2026

Sign-up forms in finance, marketplaces and B2B software ask for more than an email: a mobile number, a national ID or tax number, a passport for an identity check, a VAT number for invoices. Testing them means typing something into each, every time, often from a coding agent that signs up dozens of times a day. What goes in matters.

## Why made-up numbers aren’t harmless

- **A phone number can reach someone.** If your app sends a code or a welcome text, a number someone made up may be a stranger’s. Do it in every test run and you’re texting real people.
- **Random digits can be a real ID.** Many ID numbers have a short check digit, so random digits with the right one are often a real person’s number. Saving them in test accounts, logs and screenshots is handling someone’s identity number.
- **An agent will make one up.** Asked to get past a required field, a coding agent fills it with something plausible. Without a safe value to use, plausible means a number that might be real.

## Ready-made fields

In **Project settings → Custom fields → Add ready-made field**, a project gets Proxy Mail QA’s own values for these fields, for every agent and test on it:

| Field                                                                         | What goes in                                                                                                                                                                                                                                                                                             |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Phone number                                                                  | A number set aside for fiction in the UK (07700 900xxx), Australia (ACMA’s 0491 57x xxx) and the US and Canada (555-01xx), in the form the field asks for. For other countries, your app’s own test number, one per country, or nothing.                                                                 |
| National ID, personal tax and passport numbers                                | A published test value or a shape that’s never issued, for the account’s country, and a passport of Utopia, ICAO’s made-up state, where a country has none. A field with no such value, such as Japan’s My Number or any personal tax number, stays empty with a note. Or a KYC vendor’s sandbox values. |
| VAT and business tax numbers                                                  | The same, never matching a real business. Proxy Mail QA has no safe VAT number, so a VAT number field stays empty with a note saying what to do, unless a KYC vendor’s sandbox values have one.                                                                                                          |
| Gender, language, role, team size, business type, how someone heard about you | One of the field’s own options, the same one for the same account.                                                                                                                                                                                                                                       |
| The terms box                                                                 | Ticked, or unticked to test what your form says when it isn’t.                                                                                                                                                                                                                                           |

Every project has the Phone number from the start. Phone numbers are never guessed: without it, or with it off, a phone field is left for your test. ID and tax number fields stay empty until one of the project’s leads adds their ready-made fields. Each ready-made field finds its field by what it asks for, in nine languages, so “Mobile number”, “Telefonnummer” and “USt-IdNr.” all match. A custom field of your own for that field, by its test ID, name or ID, still comes first.

## With a coding agent

Your agent sends each screen’s fields to `form_values` on the [MCP server](https://proxymail.qa/docs/mcp). A field a ready-made field fills comes back as `kind: "custom"`, with the field’s name and a note on where the value came from. A field with no safe value comes back empty with a note, so the agent asks you instead of inventing one.

JSON

```json
{
  "values": [
    {
      "id": "mobile",
      "kind": "custom",
      "value": "07700 900736",
      "rule": { "id": "…", "name": "Phone number" },
      "note": "A number set aside for fiction, which reaches nobody."
    },
    {
      "id": "passport",
      "kind": "custom",
      "value": "U89634324",
      "rule": { "id": "…", "name": "Passport number" },
      "note": "A shape that’s never issued, a passport of Utopia: …"
    }
  ]
}

```

When your app is used in a country with no fiction numbers, give the agent your SMS provider’s test number and ask it to add it: `save_custom_field` with the Phone number’s `phones`. Only a lead’s agent can save it; anyone else’s asks a lead on a locked project. The `sign-up-form-setup` [skill](https://proxymail.qa/skills) proposes ready-made fields for the phone, ID and choice fields it finds, and saves only the ones you agree to.

## For an identity check in test mode

If your sign-up sends ID details to a KYC vendor, its sandbox wants its own test values. Set **Values from** on the ID fields to that vendor, such as Stripe, Plaid or Onfido, or pass `kyc_sandbox` to `form_values` for one call. The values pass the vendor’s checks in test mode and nowhere else. The [field formats](https://proxymail.qa/docs/field-formats) page lists every country’s format and what Proxy Mail QA gives for it.

## What to test

- The phone field takes the number in each form your users type it: spaces, a leading 0, the country code.
- An ID field’s check refuses a number with a wrong check digit, and says why.
- A VAT check that calls a government service is mocked in tests, as no fake number passes it.
- A sign-up without the terms box ticked is refused with a clear message.
- The confirmation email arrives and works: Proxy Mail QA waits for its code or link.

## Automating this?

Make it a test: formValues fills a phone field with the project's ready-made Phone number, and ID and tax number fields with their ready-made fields, as kind custom with a note saying where the value comes from, or why there's none. Add per-country test numbers with saveCustomField on the Phone number (leads only).

[Node.js client](https://proxymail.qa/docs/node) [Python](https://proxymail.qa/docs/python) [Set up your coding agent](https://proxymail.qa/docs/api#agent-setup)

## 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-id-and-tax-number-field)

## Questions

### Can't I just type 555-1234 or a row of zeros?

Outside North America's 555-01xx range, a made-up number can belong to someone, and a row of zeros fails most forms' checks. A number set aside for fiction looks real and reaches no one, but only the UK, Australia, the US and Canada have them. For other countries, use your SMS provider's test numbers and add one per country to the Phone number.

### Will the ID numbers pass my form's checks?

They follow the format, and the check digit where the country publishes one, so a form that checks the pattern takes them. A form that asks a government or KYC service whether the number is real will refuse them, as it should. For that path, choose a KYC vendor's sandbox values, which pass that vendor's checks in test mode.

### Why can only leads add ID fields?

An ID number field applies to every account on the project, so the project's leads decide whether it's filled at all and with whose values. Members, and the agents they use, ask a lead on a locked project.

### Do my agent and my tests get the same numbers?

Yes. Ready-made fields belong to the project, and their values come from the test address, so the same account gets the same phone and ID numbers from form\_values and the API.

### Can Proxy Mail QA receive the SMS code?

No. Proxy Mail QA receives email only. For phone-first sign-up, see the guide on test numbers and test-mode codes.

## 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 phone-first sign-up without real SMS](https://proxymail.qa/solve/phone-first-sign-up-testing): Test numbers with fixed codes, a test-mode code kept out of release builds, and why virtual numbers usually fail.
- [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.
- [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)
