---
title: "Test sign-up for people in Japan · Proxy Mail QA"
description: "姓 and 名 with their フリガナ, full-width and half-width fields, an address filled from the postcode, and LINE sign-in, for apps used in Japan."
url: https://proxymail.qa/solve/japan-sign-up-testing
---

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

# Test sign-up for people in Japan

A Japanese sign-up form asks for the family name first, then how the name is read, often in a set width, and fills the address from the postcode. Many apps also offer LINE sign-in. Test each with a test account that has a Japanese name.

Updated 13 November 2026

## Names and their readings

A Japanese form asks for the family name first: 姓 then 名, or one 氏名 field written 山田 直樹. Most also ask how the name is read, as furigana, because the same kanji can be read in more than one way:

- **フリガナ** or **カナ** asks for katakana: ヤマダ ナオキ.
- **ふりがな** or **ひらがな** asks for hiragana: やまだ なおき.
- **セイ** and **メイ** are the family name’s and the given name’s readings, in two boxes.
- **半角カナ** asks for half-width katakana: ﾔﾏﾀﾞ ﾅｵｷ.

Make the test account with Japan as its country, in the app’s **New address** or with `country: "JP"` for agents and tests. Its persona gets a name from Japanese lists, and every reading field gets that name’s reading in the kana and width it asks for. The app shows the reading beside the name, for copying.

Check that the app:

- keeps the family name first wherever it shows the name, in emails too
- sorts and searches by the reading, not the kanji, where it lists people
- accepts a long reading, such as ササキ ショウタ, and a short one, such as アヤ

## Full width and half width

Japanese text comes in two widths. Full-width (全角) letters and digits, such as ２２０, are what the Japanese keyboard types by default. Half-width (半角) ones are the usual 220\. A field often says which it wants: 全角, 半角数字 or 半角英数字.

Proxy Mail QA follows what the field says, in names, readings and guessed details such as the postcode and building: a 郵便番号（全角） field gets ２２０－００１１. For your own tests, try the width the field doesn’t ask for as well:

- **Full-width digits in a postcode or phone field.** Many forms convert them when the field loses focus. Check that the app stores the half-width form, or explains what it wants.
- **A full-width space between names.** Check that 山田 直樹 is stored the same as 山田 直樹, or the app treats them as two different people.
- **Half-width katakana in a フリガナ field.** Either accept it and convert it, or say the field wants full-width katakana.

The [unusual names](https://proxymail.qa/docs/unusual-names-and-passwords) list has full-width letters, half-width katakana and a full-width space between names as values to paste.

## The address from the postcode

Most Japanese forms fill 都道府県 and 市区町村 from the 郵便番号 as it’s typed, with a library such as yubinbango or ajaxzip3\. The test account’s address agrees with its postcode: 220-0011 is 神奈川県 横浜市西区 高島, from Japan Post’s data, with a made-up block number and building, so nothing is ever sent to a real door.

For agents and tests, type the postcode before the rest of the address, then fill 番地 and 建物名. `form_values` says this beside a Japanese postcode field.

Test what happens when the lookup can’t run as well: a postcode the library doesn’t know, a slow network, and a person who types the address before the postcode.

## LINE sign-in

LINE is widely used in Japan, and many apps offer **LINEでログイン**. LINE Login uses OpenID Connect: ask for `openid profile email` to get an ID token with the person’s LINE profile ([LINE Login documentation](https://developers.line.biz/en/docs/line-login/integrate-line-login/)).

**Testing before release.** A new LINE Login channel starts in Developing status, and then only people with the channel’s Admin or Tester role can sign in with it ([roles](https://developers.line.biz/en/docs/line-developers-console/managing-roles/)). Invite your testers by email from the channel’s Roles tab. Each one signs in to the LINE Developers Console with a LINE account, so use LINE accounts your team controls for testing, never a customer’s. Each environment’s callback URL must be registered on the channel’s LINE Login tab, and the `redirect_uri` your app sends has to match one. If the console doesn’t take your local address, use an HTTPS tunnel.

**The email address.** LINE gives an email address only to channels that have applied for the email permission (Basic settings, OpenID Connect, Apply, with a screenshot of the screen that tells people why you collect it), and only when the request includes the `email` scope. Not every LINE account has an email address registered, either. So an app that needs an email after LINE sign-in should ask for one and confirm it. That’s the step to test with Proxy Mail QA:

1. Sign in with a test LINE account.
2. When the app asks for an email address, give it a Proxy Mail QA address.
3. Fill the code or open the link from the email, in the page with Chrome or with `wait_for_code` for an agent.
4. Check the account now has that address, and that signing in with LINE again finds the same account rather than making a second one.

**Also test:**

- **Cancel on LINE’s consent screen.** The app should come back to its sign-in page with a clear message, not an error page.
- **The add friend option.** With `bot_prompt`, LINE offers to add your LINE Official Account as a friend, on the consent screen (`normal`) or on a screen after it (`aggressive`) ([add friend option](https://developers.line.biz/en/docs/line-login/link-a-bot/)). Sign in once adding the account and once without: the app should work the same both ways.
- **The profile after sign-in.** A LINE display name is a nickname, not a legal name. If the app needs 姓, 名 and their フリガナ, it should ask for them after LINE sign-in, and the test account’s Japanese persona fills them.

## Email in Japanese

Verification and reset emails in Japanese are read like any others: the code after 認証コード or 確認コード, the link, and how long it lasts (10分以内). Check that the subject and sender name read well in Japanese mail apps, and that the email isn’t only an image.

## Automating this?

Make it a test: createAddress with country JP gives a Japanese name (山田 直樹) and an address whose postcode, prefecture and city agree, and formValues fills 姓, 名, セイ, メイ and フリガナ fields in the kana and width each asks for.

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

## Questions

### Where do the readings come from?

Each Japanese name in the persona lists has its reading, so 山田 is always ヤマダ. The names are combined from lists of common family and given names, never taken from anyone's record.

### What goes in a フリガナ field for an account that isn't Japanese?

Nothing. A field that takes only kana refuses a Latin name, so Proxy Mail QA leaves it empty and says why. Make the address with Japan as its country, or add a custom field for the field.

### Can Proxy Mail QA sign in with LINE?

No. Test LINE sign-in with LINE accounts your team controls. Proxy Mail QA receives the email your app sends before or after it, such as a code to confirm an email address.

### Should the form accept full-width digits?

It should, or say clearly that it wants half-width ones. Many people type a postcode or phone number in full width with the Japanese keyboard still on. Test both.

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