Common use cases

Phone verification has many applications and use cases; we can only imagine what you can do with Veriph.One's capabilities. However, if you need help understanding how to make the most out of it, here are some of the common uses for phone verification services.

Account creation (sign up) and fraud prevention

Even though email has become the most common way of creating an account for a new online service, it has the downside that users can create an almost infinite amount of emails and sign up for as many new accounts on your product.

This exploit can be especially worrying for companies that offer freemium services, first-time-user promotions, and referral programs. To combat this, one can ask users for a phone number to create their accounts. This way, although not a silver bullet, most users will be discouraged from acquiring multiple phone numbers just for this purpose. Additionally, you can run phone numbers through blacklists to detect the ones previously related to fraud.

Usually, phone verification for account creation is done by asking for the user's phone number and then sending a one-time password (OTP) via SMS or WhatsApp to confirm the existence and possession of the number. This traditional method, however, has its difficulties when it comes to deliverability rates, especially in developing countries and smaller carriers. An unreliable verification method can hurt the activation and conversion rate of a product and, in turn, make it lose potential business with interested users.

Getting to a 100% deliverability rate can be extremely expensive or require complex software solutions; that's why Veriph.One devised a new method to perform reliable phone verification without breaking the bank and ensuring a verification rate that only leaves fraudsters out. Fixing leaky funnels is our specialty, so you don't have to become an expert.

Know your customer (KYC)

In financial services, some laws and regulations compel companies to gather and keep a sufficiently comprehensive profile of the customers for money laundering prevention and vulnerable operations. This mandate is commonly known as a know-your-customer (KYC) process. In many countries, regulations rule that the company must ask for the customer's phone number and ensure that they have possession over it. To do so, many financial institutions rely on phone verification, just like the one described before, for account creation. This process can happen through completely digitalized onboarding or an in-person procedure at a bank or branch.

We designed Veriph.One with financial services in mind and security is a top priority for us, especially in enterprise environments where scale and performance are critical.

Two-factor authentication (2FA)

Finally, neither of the previous use cases end at signup; users will log back in at some point, and you can implement two-factor authentication (2FA) to secure their accounts. Passwords can be guessed and stolen, and emails are insufficient to protect your users' data; that's why many companies rely on a second layer of security that shields the most sensitive transactions from external tampering.

Usually, 2FA differs slightly from simple phone verification, mainly because the latter requires the user to input their phone number to receive an OTP. 2FA, however, does the process with a number already linked to the customer profile, meaning it mustn't change mid-transaction. You want to ensure that the owner of the phone you have in file is the one doing the operation. In this case, Veriph.One supports 'pre-filled' phone verification, which skips the step of asking the user for a phone number and ensures that one is verified.