- App onboarding (banking app, social media, ride share, mobile wallet, …): One Time Password SMS is widely used to prove that the user is in possession of the mobile device associated with the mobile number used for registration. However it adds friction to the user journey. The application can instead request a seamless authentication of the mobile device via the Number Verification API.
- App login: In place of username/password, the application can request seamless authentication of the mobile device.
- Application password reset: The user journey often relies on One Time Password SMS. As in the app onboarding use case, the application can instead request a seamless authentication of the mobile device via the Number Verification API.
- Customer support
- 2FA
- Device Binding
Number Verification
Two mechanisms are leveraged to obtain the information:
- Network-based: Network operator knows to which subscriber a network-connected mobile phone belongs and what its associated phone number is or,
- SIM-based: Authentication mechanism based on the identification of the subscriber’s SIM installed in the user’s device.
This API ensures that the phone number provided or obtained matches the one associated with the user’s device, enabling secure and reliable authentication. This API eliminates the need for manual inputs, such as SMS codes, simplifying processes like account creation, login, or transaction validation. It offers a practical solution for industries requiring accurate phone number verification and retrieval, enhancing both user experience, fraud prevention and operational efficiency.
- Streamlined User Authentication and Onboarding: The Number Verification API simplifies user authentication by automatically verifying the phone number associated with a device, removing the need for manual inputs like SMS codes. It also allows businesses to retrieve a user’s mobile number directly, enabling faster and more seamless onboarding processes for applications.
- Enhanced Security and Fraud Prevention: By leveraging mobile network mechanisms, the API ensures reliable authentication without relying on vulnerable methods like One Time Password SMS. This reduces risks such as phishing, SIM swapping, and other account takeover attacks, providing a more secure environment for digital transactions.
- Improved User Experience and Conversion Rates: The API eliminates friction in key processes like account creation, login, and transaction validation. Its transparent operation ensures users enjoy a smooth experience without interruptions, leading to higher conversion rates and reduced abandonment during critical interactions.
- Versatile Integration Across Use Cases: Designed for various scenarios, the API supports industries such as banking, e-commerce, and healthcare. It facilitates secure account recovery, fast logins on new devices, and validation of sensitive transactions, making it a flexible solution for businesses aiming to enhance both security and user satisfaction.
- Operational efficiency for the API customer (cost savings).
API Portfolio: Authentication and Fraud Prevention
SubProject Wiki: Number Verification
(incl. how to meet the team)
API Wiki: Number Verification
API Repository: Number Verification
API Repository Status: Incubating
API Status: Stable
API Version(s) and Release Date(s):
- v0.3.1 (17.11.2023), initial release
- v1.0.0 (01.10.2024), Fall24 meta-release
- v2.0.0 (20.03.2025), Spring25 meta-release
API availability: Information which APIs are available in which country and network, and how to get access can be found on the GSMA public launch status page.