Written by Matt Cooper
Number Verify 2.x:
why mobile authentication has just become far more interesting in the USA...
All of us have become very familiar with the unwelcome ritual that comes with logging in, opening an account or approving a payment. Enter your mobile number, wait for the text message, switch screens, copy the code, return to the original journey and hope nothing has timed out while you were doing it. It works, - most of the time - but it’s hardly a great experience.
Number Verify was created to make that process much simpler. Rather than asking someone to prove they control a mobile number by receiving and typing in a one-time code, the mobile network can confirm that relationship directly. The customer does less, the business gets a stronger signal, and the whole journey becomes much smoother.
That’s always been the attraction of Number Verify. There is no code for the customer to wait for, mistype, copy into the wrong screen or accidentally share with someone pretending to be their bank. The response passes securely between the mobile operator and the business, while the customer simply carries on with what they were trying to do in the first place.
Number Verify was already a strong idea. Number Verify 2.x is what makes it a genuine game changer…
Why Number Verify needed to evolve
Earlier versions of Number Verify worked most naturally when the customer was using mobile data on the phone containing the relevant SIM. In the right conditions, the experience was excellent because the operator could recognise the mobile connection, associate it with the subscription and return the verification result quickly and securely.
The difficulty was that customers do not spend their lives connected through mobile data. They use Wi-Fi at home, at work, in hotels, airports, cafés and almost everywhere else. They jump between apps and browsers, begin journeys on one device and complete them on another, and generally expect services to work without needing to understand which network connection is being used underneath.
That meant a very good authentication capability was limited by the circumstances in which it worked. Businesses could see the value, but they also needed something that fitted the way their customers actually behaved.
Number Verify 2.x closes that gap by extending network-based verification across Wi-Fi and browser journeys, while supporting both Android and Apple devices (the latter with an SDK used where required). The underlying principle remains the same because the mobile network is still confirming the relationship between the customer and the number, but the range of journeys it can support is considerably wider.
This is what makes Number Verify 2.x so important. It takes a strong network capability and makes it usable in the real world, where customers move constantly between different devices, connections and channels without giving any of it much thought.
What actually happens during a Number Verify 2.x check?
The exact journey will vary depending on the application, device and operator, but from the customer’s point of view it should remain refreshingly straightforward.
A customer begins an activity such as opening an account, signing in, recovering access or approving a payment, and the business either already holds their mobile number or asks them to provide it. The Number Verify process then begins, with any required consent built naturally into the journey.
The operator confirms whether the supplied number is associated with the mobile subscription being used and sends the result securely back to the business.
In many cases, the whole thing can happen with little more than a tap and may feel almost invisible. That is one of the most appealing things about it because customers rarely wake up wanting a more complicated authentication process. They simply want to access their account, make their payment or complete their application without unnecessary interruptions.
The operator doesn’t hand over personal subscriber information. The business receives the answer it needs, which is whether the number matches, without gaining access to the underlying mobile account details.
How is it different from SMS OTP?
The most obvious difference is the amount of effort required from the customer. There is also an important security difference. SMS codes can be intercepted, redirected or stolen through phishing and social engineering, and fraudsters have become very good at convincing people to share them. A customer may believe they are speaking to their bank, their mobile provider or a delivery company, when in reality they are handing over the final piece of information needed to access an account.
With Number Verify, there is no code for the customer to read aloud, forward or paste into a fraudulent website because the response moves between the operator and the business. That removes a familiar opportunity for fraudsters and makes the process much harder to manipulate.
There are operational advantages too. SMS delivery can be delayed, messages can be filtered and businesses generally pay to send them whether the customer completes the journey or not. A network-based response avoids that entire messaging process and gives the business a cleaner route to the answer it actually needs.
Number Verify does not have to replace every authentication method in every circumstance. There will always be higher-risk situations where an additional check makes sense, and every sensible deployment should include a fallback. The real value is that genuine customers can move through ordinary journeys with far less friction, while stronger checks are reserved for the moments when they are genuinely needed.
Where can Number Verify 2.x be used?
Authentication appears throughout the customer relationship, so Number Verify 2.x has much broader potential than login alone. It can support registration, onboarding, account recovery, payments, profile changes and other sensitive actions across financial services, fintech, e-commerce, marketplaces, gaming, social platforms and digital services.
During registration and onboarding, Number Verify can confirm that the customer controls the number they are providing. This can help reduce false registrations, automated account creation and the use of someone else’s number, while making the process noticeably easier for genuine customers.
That first authentication step is often more important than businesses realise. It usually arrives at the exact moment when a potential customer is deciding whether the service is easy enough to continue using. Asking them to wait for a message and move between screens introduces friction before the relationship has properly started.
Account recovery is another particularly useful application because it is such an attractive route for fraudsters. Someone who successfully resets a password or changes the registered contact details may be able to take over an account without ever knowing the original login credentials. Number Verify can help establish whether the person attempting recovery still controls the mobile subscription associated with the account before access is restored.
Banks, fintechs and payment providers can also use the same capability when customers add beneficiaries, change personal details, update payment information or approve higher-risk transactions. The business gains an additional level of assurance without forcing every genuine customer through another clumsy step.
Retailers and marketplaces can use Number Verify when customers create accounts, complete purchases or access stored payment details, while gaming, social media and online platforms can apply it to reduce duplicate accounts, promotional abuse, automated registrations and account takeover.
Why US coverage matters
A network-based authentication service only becomes genuinely useful when it reaches enough of the customer base to support a consistent experience.
For a business operating across the USA, integrating separately with individual mobile carriers can create a substantial amount of technical, commercial and operational work. Each carrier relationship may require a separate integration, different agreements and ongoing maintenance, leaving the enterprise to manage several authentication routes depending on which network its customer happens to use.
That may be manageable for a limited pilot, but it is much harder to justify for a service intended to support millions of customers across login, onboarding, payments and account recovery.
Common industry standards have helped create more consistency in how network APIs are defined and delivered, although standards alone do not remove the practical work involved in connecting to multiple operators. Businesses still need a route that turns carrier coverage into something they can deploy without taking on the burden of managing every relationship themselves.
That is where XConnect comes in.
Coast-to-coast coverage through one integration
XConnect is deploying Number Verify 2.x across AT&T, T-Mobile and Verizon, giving businesses access to all three major US carriers through a single integration.
For enterprises, that changes the proposition considerably. They can design one Number Verify experience for customers across the USA rather than building and maintaining a different route for each operator, while supporting journeys across Wi-Fi and mobile data, applications and browsers, and Apple and Android devices.
This is the point at which Number Verify 2.x moves from being an interesting network capability to something that can be considered for genuine national deployment.
A bank, fintech, marketplace, identity provider or digital platform can create a consistent authentication experience without asking its customers to understand which carrier they use, which connection they are on or why one journey behaves differently from another.
Coast-to-coast is therefore about more than putting three carrier logos on a coverage slide. It means making the same core authentication experience available across the country through one integration, without leaving the enterprise to manage the complexity behind it.
A genuine game-changer for authentication in the USA
Number Verify introduced a better way to confirm that someone controls their mobile number. Number Verify 2.x removes many of the practical limitations that previously made it difficult to use across the full range of customer journeys.
People move between Wi-Fi and mobile data, apps and browsers, and different devices without thinking about it, and they expect the services they use to work just as seamlessly. They do not want to repeatedly prove who they are through passwords, codes and unnecessary steps when the network can help provide that assurance in the background.
With XConnect providing access across AT&T, T-Mobile and Verizon through one integration, businesses can now consider Number Verify 2.x as a practical, coast-to-coast authentication capability rather than a specialist option for a narrow set of users.
For enterprises, that means stronger protection against phishing and account takeover, less dependence on SMS OTP and a much more consistent route to deployment. For customers, it means fewer codes, fewer interruptions and a faster journey to whatever they were trying to do in the first place.
That’s the kind of authentication experience people notice - mainly because it doesn’t get in their way.
Want to try it out? Talk to us and test-drive NV2.x for yourself in a proof of concept.