---
title: "Test sign-up for people in India · Proxy Mail QA"
description: "One-name people, PIN codes, +91 phone sign-up, Hindi forms and emails, Aadhaar and PAN fields, and subscriptions under RBI's e-mandate rules, for apps used in India."
url: https://proxymail.qa/solve/india-sign-up-testing
---

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

# Test sign-up for people in India

Many people in India have one name, and a form that insists on a surname turns them away. Sign-up is often by phone, the address hangs on a six-digit PIN code, and a subscription renews only after the bank's notice. Test each with test accounts that look like your Indian users.

Updated 13 November 2026

## People with one name

In parts of India, and in Indonesia, many people have one name and no family name. A sign-up form that requires both first and last name leaves them typing their name twice, a dot, or giving up.

Make a test account with one name: **One name only** in the app’s **New address**, or `one_name: true` for agents and tests. Its persona has a first name and no family name, and `form_values` gives a last name field no value and a note saying why.

Check that the app:

- accepts an empty family name, or offers one name field
- greets the person by the one name in emails and on screen, with no stray space or “null”
- still makes a sensible username and display initials from one name
- searches and sorts people who have one name

With a family name too, Indian names come given name first: Priya Sharma. Also try names written with initials, such as K. S. Ramesh, and long names from the [unusual names](https://proxymail.qa/docs/unusual-names-and-passwords) list.

## PIN codes and addresses

An Indian address ends in a six-digit PIN code, and many forms fill the city and state from it. Make the address with India as its country, and its PIN code agrees with its city: 400001 is Mumbai, Maharashtra, India Post’s head post office. The house and street are made up, so nothing is ever sent to a real door.

Test a PIN code the lookup doesn’t know, a lookup that’s slow or down, and a person who picks the state before typing the PIN code. Check that the form takes a PIN code typed with a space in the middle (400 001), which people often do.

## Phone-first sign-up

Many Indian apps sign people up with a +91 mobile number and a one-time code by SMS. Proxy Mail QA receives email, not SMS, and gives no Indian phone numbers: there’s no range set aside for fiction, so any number could be someone’s.

- Use the test numbers your SMS or sign-in provider lets you set, each with a fixed code. Firebase Authentication has these, for example.
- Have a project lead add one to the project’s [Phone number](https://proxymail.qa/docs/custom-fields#ready-made-fields) as India’s test number, in **Project settings → Custom fields** or with `save_custom_field` and its `phones`, so `form_values` puts it in every phone field for a test account from India.
- Test an email step after the phone, if the app asks for one: the code or link reaches the Proxy Mail QA address.

More in [phone-first sign-up](https://proxymail.qa/solve/phone-first-sign-up-testing).

## Forms and emails in Hindi

Proxy Mail QA reads Hindi labels, such as पहला नाम, उपनाम, ईमेल and पासवर्ड, so a Hindi form fills as an English one does. Verification emails in Hindi are read too: the code, the link, and how long it lasts (10 मिनट के लिए मान्य).

Check that the app’s Hindi pages fit their text, since Hindi is often longer than English, and that emails render Devanagari in common mail apps.

## Aadhaar, PAN and other ID fields

Never type a real Aadhaar number or PAN in a test. For Aadhaar, Proxy Mail QA gives UIDAI’s staging test number or a number starting with 0 or 1, which is never issued, with a correct check digit. For PAN it gives the format rule only, because any well-formed PAN may be someone’s. It fills these only when a lead adds their ready-made fields in Project settings → Custom fields. For tests that need a PAN that passes a check, use your verification provider’s sandbox values: Proxy Mail QA’s KYC sandbox mode lists Setu’s and Cashfree’s. All formats are on [field formats](https://proxymail.qa/docs/field-formats).

## Subscriptions and card renewals

Under the Reserve Bank of India’s rules, a renewal on an India-issued card needs an e-mandate. The customer approves it with 3D Secure when they subscribe. Before each renewal the bank sends a notice at least 24 hours ahead, with the amount and a way to cancel, and renewals over 15,000 INR need the customer to authenticate again ([Stripe’s India recurring payments guide](https://docs.stripe.com/india-recurring-payments)). With Stripe, card renewals are collected about 26 hours after they’re requested.

Check that the app:

- doesn’t cut access at the renewal time, while the payment is still waiting
- handles a customer cancelling from the bank’s notice
- tells the person, by email, when a renewal fails, and how to pay

The receipt and failed-payment emails reach a Proxy Mail QA address like any other.

## Personal data

India’s Digital Personal Data Protection Act, 2023 covers data about a person who can be identified by it. Test accounts that identify no one keep real people’s data out of staging altogether. More in [made-up test accounts](https://proxymail.qa/solve/synthetic-test-data).

## Automating this?

Make it a test: createAddress with country IN and oneName true gives a persona with one name (Priya) and an address whose PIN code, city and state agree, and formValues leaves a last name field empty with a note, so the test can check the form accepts it.

[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-india-sign-up-testing)

## Questions

### What should a form do with a person who has one name?

Accept it. Make the family name optional, or offer a single full name field. If a later step needs two names, such as a payment or an ID check, say so there and say what to type.

### Does Proxy Mail QA give a +91 phone number?

No. India has no range of numbers set aside for fiction, and a made-up 10-digit number can be someone's. Use the test numbers your SMS or sign-in provider gives, which take a fixed code, and have a project lead add one to the project's Phone number for India, so form\_values puts it in every phone field.

### Can I use a real Aadhaar number in a test?

No. The Aadhaar Act forbids displaying one. Proxy Mail QA gives UIDAI's staging test number or a number that can't be issued, and only when a lead adds the ready-made ID fields.

### Are personas personal data under the DPDP Act?

They aren't about anyone: names are combined from lists and the addresses are fictional. Real customers' records copied to staging still are, which is why made-up test accounts are the safer choice. A test aid, not legal advice.

## 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 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)
