One‑Click Mobile Number Authentication and Verification Services from China Mobile, China Telecom, and China Unicom
The article explains how carrier‑based one‑click login and mobile‑number verification work across China Mobile, China Telecom, and China Unicom, detailing SDK functions, network requirements, token handling, and security scenarios for iOS, Android, H5 and mini‑programs.
Many apps now support a "one‑click login with the device's own number" feature, which leverages the carrier's unique gateway authentication capability to let users register or log in using their SIM‑bound phone number, offering a smoother experience than traditional SMS‑code verification.
Numerous vendors provide three‑network verification services that essentially wrap the three major carriers' capabilities; detailed technical principles can be found in the carriers' own documentation.
China Mobile
China Mobile's number authentication service supports Mobile, Unicom, and Telecom networks and offers two main functions:
One‑click login: Uses carrier communication gateways to obtain the device's phone number via a network‑gateway number‑retrieval technique. After user consent, the app (iOS/Android) can log in without a password.
Device‑number verification: Through the SDK/JSSDK, the app can verify whether a user‑entered or backend‑bound phone number matches the SIM‑bound number, ensuring the device and number are not separated. This feature works on iOS, Android, H5, mini‑programs, and quick‑apps.
Number retrieval method
The SDK calls Android's getPhoneInfo or iOS's getPhoneNumberCompletion to silently perform network checks, cellular data switching, and gateway number retrieval, returning a success flag.
Network requirement: Number retrieval needs an active data connection; disabling data or weak signal reduces success rate.
Timeout: Default 8000 ms; Android can adjust via setOverTime , iOS via setTimeoutInterval .
Carrier detection: SDK can query network type ( getNetworkType on Android, networkInfo on iOS) to select appropriate carrier SDK or login method.
Cache handling: After a successful retrieval, a temporary credential is cached locally to improve success rate and latency, even when cellular data is off. Cache can be cleared immediately via Android's delScrip or iOS's delectScrip for higher security.
Device‑number verification
Calling Android's mobileAuth or iOS's mobileAuthCompletion obtains a token without launching an authorization page; the token can only confirm that the device number matches the target number, not reveal the full phone number.
Pre‑retrieval: Cached credentials from the number‑retrieval step can be reused to speed up token acquisition.
Use case: Silent verification of device number consistency for risk‑control scenarios that rely on phone numbers.
China Telecom
China Telecom's Tianyi Account Open Platform provides password‑free login, mobile number authentication, and secondary‑card verification, currently limited to Telecom users.
Password‑free authentication: Utilizes carrier data networks, communication‑gateway pre‑login, and SIM identification to accurately obtain the user's phone number for one‑click login, reducing SMS‑code leakage risk.
Mobile number verification: Confirms whether the device's current number matches the user‑provided number using the same carrier‑based technologies.
Secondary‑card verification: Detects whether a number has been recycled (a “second‑hand” number) by consulting the carrier's exclusive secondary‑number database, helping prevent privacy and security issues when users change numbers without unbinding old accounts.
China Unicom
China Unicom's Innovation Platform offers number authentication (one‑click login), anonymous device ID, anonymous user ID, empty‑number detection, secondary‑number verification, and three‑element verification services.
Number authentication: Provides one‑click registration/login and number verification for apps and H5 pages across all three carriers, with a patented, high‑performance SDK that reduces empty‑number registrations and password‑theft risks.
One‑click login (App): Automatically obtains the phone number when cellular signal is present (Wi‑Fi is temporarily switched to cellular), enabling fast, password‑free login.
One‑click login (H5): Users input a four‑digit local number to log in quickly when on cellular network.
Device verification: Automatically checks if the entered number matches the SIM‑bound number, useful for binding, payment confirmation, and loyalty points.
Anonymous device identification: Generates a unique, carrier‑provided device ID for iOS and Android without relying on manufacturer IDs, supporting fraud detection, precise marketing, and anti‑abuse measures.
Anonymous user identification: Returns a unique pseudocode derived from the user's public/private IP, protecting the actual phone number while enabling user‑level analytics for Unicom users.
Empty‑number detection: Identifies whether a phone number is active, offline, or in a “sleep” state within one second, supporting large‑scale concurrent queries for marketing and user‑maintenance tasks.
Secondary‑number verification: Checks if a number has been re‑issued after cancellation, helping prevent privacy leaks and financial loss in registration, login, or password‑recovery flows.
Three‑element verification: Validates the consistency of name, ID card number, and phone number for real‑name authentication in financial, lending, and other high‑risk scenarios.
PS: If you find this sharing useful, feel free to like or watch.
Java Captain
Focused on Java technologies: SSM, the Spring ecosystem, microservices, MySQL, MyCat, clustering, distributed systems, middleware, Linux, networking, multithreading; occasionally covers DevOps tools like Jenkins, Nexus, Docker, ELK; shares practical tech insights and is dedicated to full‑stack Java development.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.