THE LINUX FOUNDATION PROJECTS

Number Verification

API Description
Use Cases
  • App Onboarding and Account Registration: Applications can use Number Verification during registration to confirm that the phone number entered by the user matches the mobile number associated with the device being used. This helps replace SMS OTP in eligible journeys, reducing onboarding friction and abandonment while keeping a strong possession factor.
  • Login and step-up Authentication: Digital services can silently verify that the user is accessing the application from a device associated with the expected mobile number. This supports faster login and risk-based step-up authentication without asking the user to manually enter an OTP code.
  • Account Recovery and Password Reset: Applications can use Number Verification to confirm possession of the registered mobile number before allowing account recovery, credential reset or profile changes. This reduces reliance on SMS OTP and knowledge-based questions.
  • Transaction Validation: Banks, fintechs, wallets, e-commerce providers and other digital services can call Number Verification before sensitive actions such as payments, transfers, account changes or high-value transactions. If the mobile number is verified, the application can continue the journey with less friction; if not, it can trigger additional controls.
  • Device Binding and first Activation: Applications can use Number Verification during first activation or trusted-device registration to confirm that the device being bound to the account is associated with the expected mobile number.
  • Customer Support and assisted Journeys: Customer support channels can use Number Verification as an additional possession signal before performing sensitive actions such as account changes, credential recovery or fraud-related support operations.

See also GSMA Use Case Library for more information:

Benefits
  • Frictionless User Authentication: Removes the need for users to wait for, read, copy or manually enter SMS OTP codes during onboarding, login, account recovery or transaction validation.
  • Stronger mobile Possession Signal: Uses operator-backed network or SIM-based authentication to verify that the mobile number is associated with the authenticated device.
  • Reduced OTP-related Risk: Since there is no OTP code to intercept, phish or socially engineer from the user, Number Verification helps reduce exposure to common SMS OTP attack patterns.
  • Higher Conversion and lower Abandonment: Silent verification reduces friction at critical points in the user journey, helping businesses improve completion rates for registration, login and payment flows.
  • Developer-friendly Integration: Provides a standardized CAMARA API that developers can integrate into existing authentication, onboarding and fraud-prevention workflows.
  • Composable Fraud Prevention: Can be combined with other CAMARA APIs such as SIM Swap, Device Swap, Tenure or Device Location Verification to support stronger risk-based authentication and account protection.

API Portfolio: Authentication and Fraud Prevention

Sub Project Wiki: Number Insights
(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)
  • v1.0.0 (01.10.2024), Fall24 meta-release
  • v2.0.0 (20.03.2025), Spring25 meta-release
  • v2.1.0 (12.09.2025), Fall25 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.

Be part of a collaborative community driving the future of global Telco APIs.

Join Today