What is the difference between this API and a simple number format validator?

A format validator only confirms that the structure of the digits is correct. Our API directly queries the mobile operator to confirm if the number is authentic, active, and matches the identity of the user in real-time.

What happens if the phone number is inactive or invalid?

If the number is inactive, invalid, or a VoIP number, the API will respond negatively. Your system can then block registration or trigger stricter identity verification methods.

How is user privacy protected?

The API operates under strict security protocols. The mobile operator only provides a binary Yes/No response regarding the match. No sensitive personal info like names or locations are ever shared.

Does the user need an active mobile data connection (3G/4G/5G) for it to work?

Yes. The user must be using the operator's mobile network to ensure the identity check is accurate, real-time, and network-based.

Does the Number Verification API replace the SIM Swap API?

No, they are complementary. SIM Swap API detects recent theft or cloning, while Number Verification verifies current user identity. Together, they provide up to 99.9% authentication security.

Number Verification API

In the digital economy, the mobile phone number has established itself as the main identifier of a customer's identity. However, how can your company be truly sure that the number it receives belongs to the user who claims to be?

Plusmo's Number Verification API offers a cutting-edge solution that validates the authenticity and validity of a phone number in real time. This ensures that the numbers provided by your users are not only correct, but also active and operational, and, most importantly, that they match the identity of the current user. This is an essential security layer that operates silently, without generating friction.

More information

Frictionless Authentication: Number Verification Without User Intervention

The key to success in modern digital security is the ability to protect users without complicating their experience. Our Number Verification API achieves this balance by operating without the direct intervention of the end user.

The Problem with Traditional Verification

Traditional verification methods (such as sending one-time codes or SMS OTPs) add a step to the customer experience.
If the number provided is incorrect or inactive, the user is frustrated and the cost of verification (for each failed SMS) accumulates.

The Plusmo Solution: Silent Verification

The Plusmo API eliminates these weaknesses. Its main objective is to verify if the phone number presented to it matches the user who is actively using your service at a given time, and all of this happens behind the scenes.

How Silent Validation Works
Our number verification process uses a secure and unique integration with mobile operators, ensuring maximum accuracy and speed

The 4-Step Verification Flow

1

Token generation and initial query

When a user attempts to access or perform a critical transaction, your backend application initiates the process. This application contacts the AuthServer to generate a one-time security token.

2

Call to the Verification API

The institution or company (you) generates a query to the Plusmo API, sending two crucial pieces of data: the security token and the phone number to be verified (e.g., $+5491145388773$).

3

Operator verification (MNO):

The Plusmo API, in collaboration with the mobile phone operator, performs a real-time query: "Does phone number $N$ match the user currently connected to this service or device?"

4

Binary response and authorization

The mobile operator responds securely, confirming with a "Yes" (TRUE) or a "No" (FALSE).
‍
- If the response is TRUE, your institution authorizes access or the operation, knowing with certainty that the number matches the active user.
‍
- If the response is FALSE, a risk policy is applied (e.g., access is denied, a stricter additional verification is requested).

This process guarantees the authenticity and operability of the number, preventing fraud and securing the customer's identity.

Critical Use Cases: Where Number Verification is Essential

The versatility of the Number Verification API makes it indispensable in various sectors that prioritize security and user experience.

1

Two-Factor Authentication (2FA) and Account Recovery:
Instead of relying solely on an SMS that could be intercepted, use the API for:

Trust validation:
Before sending an OTP, verify that the number is active and corresponds to the user. This is especially useful for countering SIM Swap attacks.

Password recovery:
‍Ensure that the person attempting to reset a password is the legitimate owner of the number associated with the account.

2

Onboarding Fraud Prevention:
‍Prevention begins the moment a new customer registers.

Account registration:
‍Prevent bots or scammers from creating accounts using false, inactive, or disposable prepaid phone numbers. Ensuring the validity of the number improves the quality of your database.
‍
‍Churn and spam prevention:
Reduce communication costs associated with inactive or invalid numbers, improving the effectiveness of your marketing and mailing campaigns.

3

Financial Institutions and Payments (Fintech): For any high-value transaction, certainty of identity is crucial.
‍
Transaction verification:
‍Run a silent verification before authorizing large transfers or changes to credit limits, ensuring the account is being operated by the owner of the associated number.
‍
Regulatory compliance (KYC/AML):
Strengthen your Know Your Customer (KYC) and Anti-Money Laundering (AML) processes by having irrefutable confirmation of the customer's digital identity.

Strategic Benefits for Your Company

Integrating Plusmo's Number Verification API provides tangible benefits that directly impact your operating costs and customer satisfaction.

Increased security

Provides a proactive defense against account takeover fraud and attacks that rely on SMS interception.

Cost optimization

Reduces expenses associated with sending failed OTP SMS to invalid or inactive numbers.

Improved user experience

Eliminate annoying extra verification steps or Captcha codes, resulting in faster and smoother onboarding and access.

High-quality data

Maintain a clean and verified customer database, improving contactability and the effectiveness of your communications.

FAQ’S

Number Verification API

Frictionless Authentication: Number Verification Without User Intervention

The Problem with Traditional Verification

The Plusmo Solution: Silent Verification

Critical Use Cases: Where Number Verification is Essential

Frequently Asked Questions