---
title: "Test sign-up for people in Pakistan · Proxy Mail QA"
description: "Names in English and Urdu, right-to-left fields, the father's name, CNIC fields, +92 phone sign-up and emails in Urdu, for apps used in Pakistan."
url: https://proxymail.qa/solve/pakistan-sign-up-testing
---

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

# Test sign-up for people in Pakistan

A Pakistani form may ask for the name in English and again in Urdu, then the father's name and a CNIC number, and sign people up with a +92 mobile. Test each with test accounts that have Pakistani names in both scripts.

Updated 13 November 2026

## Names in English and Urdu

Many Pakistani forms take the name in English letters. Some also ask for it in Urdu, for a certificate, a bill or a government record, and a form written in Urdu expects Urdu letters throughout.

Make the test account with Pakistan as its country, in the app’s **New address** or with `country: "PK"` for agents and tests. Its persona gets a name from Pakistani lists, and each name has its Urdu spelling: Ali Khan is علی خان. The app shows **Name in Urdu** beside the name, for copying.

- A field that asks for the name in Urdu, such as **Name (Urdu)** or **نام اردو میں**, gets the Urdu spelling.
- A field that asks for English, such as **Name (English)** or **نام (انگریزی میں)**, gets the Latin spelling.
- A field labelled in Urdu that asks for neither, such as **پہلا نام**, gets the Urdu spelling.

`form_values` follows these rules, and an Urdu full name box counts even beside English first and last name boxes.

Check that the app:

- shows Urdu right to left, in fields, on screen and in emails, and keeps an email address or a number left to right inside it
- accepts the letters Urdu uses and Arabic doesn’t, such as ہ, ے and ٹ: a check that allows only Arabic letters refuses عائشہ
- keeps the English and Urdu names together, so a search for either finds the person

The [unusual names](https://proxymail.qa/docs/unusual-names-and-passwords) list has Urdu values to paste.

## The father’s name

Pakistani forms often ask for the father’s name, or the husband’s for a married woman: **Father’s name**, **ولدیت**, **S/O** (son of) or **D/O**. Proxy Mail QA never puts the persona’s own name there. If your tests need one, teach the field once with a custom field, so every fill and every agent gives the same value.

Check that the form says which name it wants, and that it accepts one name there too.

## CNIC and other ID fields

A CNIC number has 13 digits, written 35202-1234567-1 with dashes. NADRA publishes no check digit and no specimen, so any well-formed number may be someone’s. Proxy Mail QA gives the shape and the all-zero placeholder 00000-0000000-0 only, and only when a lead adds the ready-made National ID number field in Project settings → Custom fields.

Test the CNIC field with and without dashes, with a space typed by mistake, and with 12 or 14 digits. If the app checks CNICs with a verification service, use that service’s test values. All formats are on [field formats](https://proxymail.qa/docs/field-formats).

## Phone-first sign-up

Many Pakistani apps sign people up with a +92 mobile number, 3xx then seven digits, and a code by SMS. Proxy Mail QA receives email, not SMS, and gives no Pakistani 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.
- Have a project lead add one to the project’s [Phone number](https://proxymail.qa/docs/custom-fields#ready-made-fields) as Pakistan’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 Pakistan.
- Check that the form takes the number as people type it: 03001234567, +92 300 1234567 and 923001234567.

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

## Addresses

A Pakistani address has a five-digit postcode, though many people leave it out. Make the address with Pakistan as its country and its postcode agrees with its city: 54000 is Lahore, in Punjab. The street is made up. Check that the postcode is optional unless the app really needs it.

## Emails in Urdu

Verification and reset emails in Urdu are read like any others: the code, the link, and how long it lasts (10 منٹ کے لیے درست). Check that the subject and body read right to left in common mail apps, and that numbers and links inside them stay in order.

## Automating this?

Make it a test: createAddress with country PK gives a Pakistani name (Ali Khan) and an address whose postcode and city agree, and formValues gives علی خان to a name field that asks for Urdu and Ali Khan to one that asks for English.

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

## Questions

### Where do the Urdu spellings come from?

Each Pakistani name in the persona lists has its Urdu spelling, so Khan is always خان. The names are combined from lists of common given and family names, never taken from anyone's record.

### What does an Urdu name field get for an account that isn't Pakistani?

Nothing. Proxy Mail QA leaves it empty and says why, rather than spelling an English name in Urdu letters. Make the address with Pakistan as its country, or add a custom field for the field.

### Does Proxy Mail QA fill the father's name?

Not with the persona's own name. It's someone else's name, so it's one of the form's other fields: teach it with a custom field if your tests need the same value every time.

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

No. NADRA publishes no check digit and no specimen, so any well-formed number may be someone's. Proxy Mail QA gives the shape and an all-zero placeholder only.

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