Unibeam tops camara number verify with a simple, reliable mobile authentication solution

The Camara Number Verify API, launched in 2022, is an initiative designed to help mobile network operators (MNOs) play a bigger role in online user authentication. Traditionally, MNOs were involved in user authentication through one-time passwords (OTPs) via SMS and other legacy systems. With the Number Verify API, MNOs aimed to become more directly involved in user authentication – which could give them more reach and generate additional income.

The Number Verify API works by allowing applications to verify the mobile phone number being used by a given smartphone. It answers two key questions:

1.    Is the phone number provided by the user the actual number linked to the smartphone being used to access an online service via the smartphone app?
2.    What is the phone number associated with a specific access token issued from the app on a smartphone?

In theory, service providers can easily and securely integrate this API, helping them verify user identities. The API is supposed to be a simple and secure way to confirm a smartphone’s phone number authenticity. However, even though the idea has strong support from major mobile operators in Europe, the Number Verify API has not been widely adopted yet. Why is this?

The Reasons for Slow Number Verify API Adoption

The Camara Number Verify API faces several challenges that are slowing its wide-scale adoption by MNOs.

A key limitation is that the API only functions over cellular networks and does not natively support Wi-Fi connections. Since many users regularly switch between cellular and Wi-Fi networks, especially in urban areas or at home and work, this makes the API far less useful. Users cannot rely on it when they are on Wi-Fi – and this weakens its practical value for MNOs looking for seamless authentication.

What’s more, there are no standard solutions to mitigate the impact of the Wi-Fi issue. GSMA and the Open Gateway Initiative simply mandate that the user turn off Wi-Fi. Some API aggregators have even developed their own SDKs or code that force a smartphone to route a Number Verify API request through the cellular data channel, even if Wi-Fi is available. Yet these solutions, too, have serious drawbacks:

1.    The SDKs are not standard. They are proprietary to each aggregator. This means that an enterprise cannot switch between vendors without redeveloping and deploying a new SDK for all their end user applications.
2.    The SDKs cannot be installed in all smartphones and may exclude older phones. It does not address users trying to login via PC or tablets.

Another challenge facing Number Verify API is that it is not reliable if a user has multiple SIMs (for example one for voice/SMS and one for cellular data), or if the user has an eSIM. What’s more, Number Verify cannot itself prevent SIM swap – forcing enterprises to purchase another API alongside Number Verify.

For these reasons and more, businesses are hesitant to adopt the Number Verify API. Instead, enterprises prefer legacy authentication methods like two-factor authentication (2FA) and other mobile-based verification systems – despite their known security and usability drawbacks.

A Better Alternative: Unibeam’s SIM-Based Authentication

Unibeam’s SIM-based authentication solution is a better alternative to the Camara Number Verify API (and legacy authentication methods like 2FA) for a number of reasons.

Firstly, Unibeam works on any device – from 20 year-old feature phones through the latest smartphone and including tablets and PCS, without adding code to apps. And it works over any type of connection – Wi-Fi, cellular or roaming. This makes the solution far more accessible to everyone.

Unibeam is also much easier to use. While the Number Verify API requires enterprises to train their users on its limitations and workarounds (turning off Wi-Fi, disabling travel SIMs, etc.), Unibeam is seamless and self-explanatory for the user. It works automatically, with no user setup or training.

Finally, Unibeam is more reliable and secure. It works even when users are roaming. And it prevents SIM swap fraud without extra API calls, providing better security. Overall, Unibeam is a more flexible, user-friendly, and secure solution compared to the Camara Number Verify API, making it a stronger choice for businesses.

	Camara Number Verify	Unibeam
Works over GSM network	+	+
Works without GSM data connectivity	–	+
Works natively over Wi-Fi	–	+
Works reliably while roaming	–	+
Works for any mobile OS	–	+
Works on old feature phones	–	+
Works over PC or tablet	–	+
Prevents SIM swap	–	+
No special user training or usage limitations	–	+

Better for Enterprises, Better for MNOs

The Camara Number Verify API was created to help mobile network operators play a bigger role in user authentication, but it’s many issues are slowing adoption by both enterprises and MNOs.

For the enterprise, Unibeam’s SIM-based authentication is a better option because it works on any device, over both Wi-Fi and cellular connections, and doesn’t require any special SDK apps or user setup. Its simplicity, wide compatibility, and strong security make Unibeam a much more attractive solution for businesses looking for reliable and easy-to-use authentication.

For MNOs competing in a crowded space for user authentication revenues (while their SMS OTP margins are quickly shrinking), Unibeam is the best way successfully monetize authentication. Easy-to-deploy and easy-to-use, Unibeam is better underlying technology that relies on the mobile (e)SIM owned by MNOs. It does not depend on the mobile phone OS, vendor or model. And it can be easily implemented with a single API.

With its universal compatibility, seamless operation across networks, and built-in security features, Unibeam offers both enterprises and MNOs more reliable, scalable, and profitable authentication.