Number Verification

Allows to check if the provided mobile phone number is the one actually used in the device
Available in flag-for-spain

Eliminate SMS OTP friction. Increase trust in phone-based onboarding.

Enhancing security with seamless authentication

The service verifies that the user is using a device with the same mobile phone number as the one which is declared for this user.

It also makes it possible for the application consuming this API to get the number itself by returning the phone number associated with the authenticated user’s access token.

As the CAMARA compliant Number Verification API uses the Orange mobile network, it offers strong authentication with enhanced security with minimum user friction. It also makes it possible for the application consuming this API to get the number itself by returning the phone number associated with the authenticated user’s access token.

As the Number Verification API uses the Orange mobile network, it offers strong authentication with enhanced security with minimum user friction.

Coverage that matters for production use cases

Number Verification API is currently available in France and Spain on Orange Developer. If you operate multi-country, you can design a progressive rollout: enable Number Verification where supported, and fall back to your existing method (e.g., SMS OTP) elsewhere while keeping a consistent user journey and risk policy.

Benefits

Enhanced Security and Fraud Prevention

By utilizing mobile network mechanisms, the API provides reliable authentication without depending on vulnerable methods like One Time Password SMS. This minimizes risks such as phishing, SIM swapping, and account takeover attacks, creating a safer environment for digital transactions.

Improved User Experience and Conversion Rates

The API reduces friction in essential processes like account creation, login, and transaction validation. Its seamless operation allows users to have an uninterrupted experience, resulting in higher conversion rates and lower abandonment during critical interactions.

Versatile Integration Across Use Cases

The API is designed for various applications, supporting industries like banking, e-commerce, and healthcare. It enables secure account recovery, quick logins on new devices, and validation of sensitive transactions, making it a flexible solution for businesses looking to improve both security and user satisfaction.

Google Firebase Phone Number Verification on Orange France (now live)

Firebase Phone Number Verification is now generally available, and Orange France is a core launch partner. For companies that rely on phone numbers for onboarding, login, and account recovery, this is a practical way to modernize verification without staying locked into SMS OTP constraints.

SMS OTP is not just a security topic, it directly impacts revenue and operating cost. OTP delivery and user handling issues create avoidable abandonment during sign-up and recovery. Industry figures referenced by Google highlight the scale of the problem:

23% account abandonment linked to OTP issues, and
up to 37% lost business opportunity when onboarding journeys are too complex and error-prone.

With Orange France, verification can be performed silently through the mobile network, using background cryptographic validation rather than a user-entered code.

The expected outcome is a materially faster and cleaner user journey:

fewer steps (from 23 to 6),
faster completion (around 2 minutes down to ~30 seconds), and
elimination of user input errors because there is no OTP to type.

This approach is positioned on a CAMARA-aligned model, with the intent to extend availability across additional Orange European networks, Spain, Poland, and Romania are next targets, while keeping integration effort stable as coverage expands.

Learn more

Use cases

App onboarding (banking apps, social media, ride-sharing, mobile wallets, etc.)

One Time Password (OTP) SMS is commonly used to verify that the user has the mobile device linked to the registered phone number. However, this can complicate the user experience. Instead, the app can utilize the Number Verification API for a smoother authentication process.

Application password reset

The user experience typically depends on OTP SMS. Similar to the onboarding process, the app can use the Number Verification API for a more seamless mobile device authentication.

App login

Rather than using a username and password, the app can opt for seamless authentication of the mobile device.

Step-up verification for risky actions

Use Number Verification as a “step-up” check when risk increases (new device session, unusual behavior, or high-value operation), while keeping the normal journey lightweight for low-risk users.

Case study

How DQE leverages Orange’s CAMARA APIs to protect users

DQE, a leading French fraud-prevention specialist, partners with Orange to strengthen digital identity checks for high-risk sectors such as banking, insurance, and e-commerce.
By combining Orange Network APIs (including Number Verification) with its own verification stack, DQE helps enterprises reduce exposure to identity theft, SIM swap-related attacks, and document fraud.
Results reported by DQE for client deployments include 50% reduction in document fraud and net fraud, 30% higher conversion for targeted users, and 40% of prospects no longer needing proof of address, simplifying onboarding and reducing operational workload.
This illustrates a pragmatic model: use network-backed number verification to reduce user friction while increasing assurance at the moment of onboarding or step-up checks.

Used APIs

Number Verification

SIM Swap

Partners

Read the article

Test and explore our APIs with API Playground

Discover the API Playground: your interactive environment for testing and exploring Network APIs with ease! Prototype, validate, and experiment in real-time without impacting your live systems.

Get started today and bring your projects to life!

Test in API Playground

Explore documentation

Frequently Asked Questions

It checks whether the phone number provided by the user matches the phone number associated with the SIM currently used on the device, based on the mobile network signal.

For many mobile journeys, yes: it can remove the OTP step and reduce friction. In practice, many customers implement progressive verification (Number Verification where available, fallback to OTP elsewhere) to keep full coverage.

No. Number Verification is not a phone-number lookup database. It is a network-backed match check between the declared number and the SIM on the device (and it can return the number tied to the authenticated token).

You can start with the Network APIs Playground, which is a mocked version of the production API and supports predefined +990 test numbers as well as configured user-defined numbers.

Orange France is integrated into Firebase Phone Number Verification, enabling Firebase developers to benefit from Orange’s network-backed capabilities thanks to Number Verification 2.1 API