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. 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.
{
"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 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 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.