Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


Real-name verification in China, often searched as real-name authentication, happens inside the official app or service, and you should not pay a third party to pass it: the National Immigration Administration says its travel-document identity-authentication service is provided free of charge[3]. It is also not one universal screen shared by Chinese apps. A service may verify a phone number for registration, legal identity for an account, a live person or face, the physical document, or eligibility for a specific payment, ticket, publishing, or regulated function. Identify the layer before uploading anything. The correct outcome may be successful online verification, manual review, an official offline route, or a clear conclusion that the feature does not support your document.
Key Takeaways
- Separate phone/SMS registration, account real-name verification, liveness or face checks, document reading, and transaction-specific verification.
- Confirm the official app, domain, operator, privacy notice, purpose, and supported document list first.
- Enter identity data exactly as the document and current form require; do not guess a Chinese name or substitute another person's details.
- Classify failure before retrying: document support, data mismatch, capture, liveness, duplicate account, risk control, expiry, outage, or manual review.
- Never borrow an identity, forge a document, rent an account, or send identity images to an unofficial chat contact.
- This is general operational information, not legal advice. Current platform and authority instructions control.
For network preparation before real-name verification, see the Best VPN for China guide. Connectivity does not change document support, identity eligibility, or a platform decision.
Layer 1 is phone/SMS registration. It proves control of a phone number at a moment in time. The CAC rules identify mobile numbers as one possible basis for real identity information in services such as information publishing and instant messaging[1]. A successful SMS code does not prove that the account's legal name, passport, face, or payment eligibility has been verified.
Layer 2 is account real-name verification. The platform links the account to identity attributes such as name and document type or number. It may unlock posting, messaging, payment, ticketing, or account-recovery functions. The accepted documents and name format are platform-specific.
Layer 3 is a liveness or face check. The app may ask the current user to turn, blink, speak, or align their face. This is intended to check presence and compare the user under the platform's rules. It is not the same as photographing the identity page, and a successful document upload does not guarantee that face matching will succeed.
Layer 4 is physical-document capture or document reading. A service may photograph the identity page, scan a code, read a chip, use an authority-backed identity service, or route the document to manual review. China's National Immigration Administration describes an identity-authentication platform intended to make travel documents more usable in public and internet services, but that does not mean every app or every foreign document is connected to the same route[3].
Layer 5 is transaction- or feature-specific verification. A verified account may still need passenger identity for a train ticket, payer identity for a regulated payment, guest details for a hotel, or extra review for a high-risk transaction. The necessary-personal-information rules list different data for instant messaging, shopping, payment, transport ticketing, tourism, and hotels, illustrating why app category and function matter[2].
Write down the exact trigger: creating an account, posting content, adding a card, buying a ticket, receiving money, booking a hotel, changing a security setting, or recovering access. Do not repeatedly complete the wrong layer.
Begin from the official app store, official website, or a verified service entry. Check the operator name, domain, privacy notice, user agreement, and support route. Scam pages can copy a logo and ask for a passport, face video, SMS code, or payment before they provide any real service.
Read the document selector before taking a photograph. Look for the exact category: foreign passport, mainland identity card, Mainland Travel Permit, permanent residence card, or another named document. A generic “ID” label in an English translation may hide a narrower Chinese field. If your document type is absent, do not choose the closest-looking option.
Check whether the service supports online automatic review, manual review, or an offline counter for that document. A Shanghai Government transport example describes a foreign-passport manual-review route in one specific service[4]. It is evidence that such a route can exist, not proof that every Chinese app accepts foreign passports or uses the same review time.
Understand the purpose and requested data. The CAC rules state that personal-information processing should be lawful, justified, necessary, purpose-specific, and publicly explained, and that a user should not be denied basic functions merely for refusing non-essential information[1]. The necessary-information rules then define different basic-function data by app category[2]. These rules do not mean every verification request is invalid or that every optional feature must work without identity; they are prompts to check purpose and scope.
If the request appears in a message from a seller, driver, landlord, or “support agent,” stop and locate the same requirement inside the official service. Never send a document to an unofficial chat contact.
Use the document that the official selector supports. Check validity dates and physical condition. Enter the name, document number, nationality, date of birth, issue date, expiry date, and gender only where requested, following the document and field instructions exactly.
Name order is a common mismatch. A passport may separate surname and given names, while a form may ask for full name in the same sequence as the machine-readable zone or visual page. Preserve spaces, hyphens, and middle names when the field permits. Do not invent a Chinese name unless the official service explicitly asks for one and explains how it is linked to the passport.
Use Latin letters, capitalization, and document number exactly as required. Distinguish zero from O and one from I. Do not add spaces to a document number unless the original and field require them. For nationality, choose the official option rather than typing an informal country name.
Compare the data with any existing profile, ticket, card, or prior verified account. A new submission can fail because the account already contains a different spelling or an old document. If a passport was renewed, use the official update or support route rather than replacing values randomly.
Before submitting, review every field and the stated purpose. Do not store the complete details in an ordinary note, clipboard manager, public cloud folder, or shared translation service longer than necessary.
For a document photograph, use a clean lens, even light, a plain background, and the full requested page. Keep all four corners visible when required. Avoid glare, blur, fingers over text, deep shadows, filters, beauty modes, screenshots, and edited composites. Submit only through the official capture or upload control.
For NFC or chip reading, remove a thick case if the official instructions recommend it, place the phone at the indicated passport position, and keep both still. Not every phone, document, or app supports chip reading. A failed read should not be “fixed” by sending a full document to a stranger.
For liveness or face checks, use neutral lighting, remove accessories only when the official instructions require it, keep the camera at the requested distance, and follow one prompt at a time. Stop if the process asks you to record unrelated speech, display payment credentials, share an SMS code, or move to an unofficial video call.
For manual review, save the official case number and submitted-document description. Review time is service-specific. Do not open many duplicate cases or repeatedly upload different spellings unless official support tells you to correct a field. If the service provides an in-person counter, bring the original document and the exact reference requested.
Treat approval as layer-specific. A “verified” badge may apply to the account but not to a bank card or passenger. Read the final status and test only the function you intended to unlock.
Unsupported document: the selector or official rule does not list your document. Seek manual or offline support; do not choose a false category.
Data mismatch: name order, spelling, nationality, document number, date, or an existing profile differs. Compare the original and official field rules. Ask support to update locked historical data.
Capture or read quality: glare, blur, cropped corners, low contrast, damaged page, camera permission, NFC position, or an unsupported device prevents reading. Correct one physical cause and retry once.
Liveness or face mismatch: lighting, framing, camera quality, appearance change, or the platform's comparison fails. Follow official retry limits and request manual help. Do not use another person's face or an altered image.
Duplicate account or identity: the phone, document, or identity may already be linked. Recover or close the original account through official support instead of creating more accounts.
Risk control: unusual device, repeated attempts, inconsistent data, account history, or transaction context may trigger review. Stop changing networks and details. Preserve the notice and ask official support what evidence is accepted.
Expired or replaced document: update the record through the service's document-change process. Do not submit an expired document as current.
Service outage or manual-review delay: check official notices and case status. Wait for the stated window rather than generating duplicate submissions. A pending review is not a rejection.
Record the exact error text, date, time, app version, document type selected, and case number without exposing the full document number. This gives official support a useful diagnostic trail.
Open support from the verified app, website, order, ticket, or government page. Ask one precise question: “Does this function accept a [document type] issued by [country], and is manual or in-person review available?” Include a masked error and case number, not an unsolicited full passport image.
If support asks for a document, confirm why it is needed, which fields are required, where it will be uploaded, and how the request can be verified inside the official service. Use an official secure form. Do not continue in a personal messaging account merely because the person knows your error text.
An offline route can be the correct outcome. A station, bank, merchant, hotel desk, ticket office, or public-service counter may support documents that the app cannot read. Verify hours, location, appointment rules, original-document requirements, and payment options before traveling.
Choose a legitimate alternative rather than a bypass. A trusted companion may book or pay with their own account only if the service permits it and the actual passenger, guest, payer, and beneficiary details remain accurate. Never borrow identity details, buy a pre-verified account, rent an account, forge records, or use someone else's face.
If the function is unavailable to your document, preserve that answer and change the plan. A VPN cannot alter the supported-document list, authority record, face match, or platform decision.
Use a trusted device with an updated operating system and screen lock. Avoid submitting identity data on public Wi-Fi when a trusted mobile or private network is available. Check that you are in the official app or HTTPS domain and that no remote-control or screen-sharing session is active.
Close unrelated apps and notifications before a face or document capture. Do not save extra photographs “just in case.” If the official service allows a copy to be masked, follow its exact masking instructions; never cover a field required for validation. If it requires an unmasked original, decide whether the service and purpose are legitimate before proceeding.
After submission, confirm the receipt or case record, then delete stray camera-roll, download, scan, and message copies that are no longer needed. Empty recently deleted storage if appropriate, while preserving only the official case number and privacy-safe evidence needed for support.
Monitor the account and linked payment methods for unexpected changes. If you believe identity data was sent to a scammer, contact the affected platform and relevant financial or public authorities promptly using independently located contact details.
This guide is general operational and privacy information, not legal advice. Laws, platform rules, accepted documents, and review systems change. The official service and competent authority for the exact transaction are the final source.
Handle Chinese app verification as a decision tree. Identify the layer and function, verify the official service, confirm document support, enter exact data, follow the correct capture or review branch, and classify failures before retrying. Use official support or an eligible offline alternative when online automation cannot handle your document. Never turn a compatibility problem into identity fraud or unsafe document sharing.
No. SMS generally proves control of a phone number. An account may separately require legal identity, document, face, or transaction-specific checks.
No. Accepted documents and review routes are service- and function-specific. Look for an explicit foreign-passport option or obtain an official support answer.
Check surname and given-name order, spaces, hyphens, middle names, capitalization, nationality, document number, and any existing profile. Follow the field's current instructions exactly.
It is a legitimate route in some services, including specific foreign-passport examples, but not a universal entitlement or timeline[4]. Use only the case path shown by the official service.
No. Do not borrow an identity, face, phone-linked account, or document. It can violate law and platform rules, expose both people to fraud, and make recovery impossible.
Only use a verified official secure route after confirming the request inside the service. Do not send identity images to an unofficial or personal chat contact.
You should not need to pay anyone to complete it. The National Immigration Administration says its travel-document identity-authentication service is provided free of charge[3]. The ticket, purchase, or payment being verified may still cost money, but sellers of “verification services,” pre-verified accounts, or ID numbers are fraud signals.
No. It may affect network reachability, but it cannot make a document supported, correct authority data, pass liveness, or override manual review.
Sources checked 4 October 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.