Verify user mobile numbers using a simple REST interface

On: Mar 14, 2016    In: Product Updates

verify_safe.png

This week Dynmark adds a new service to its arsenal of SMS capabilities; Verify is a new REST interface that allows you to Verify that a user owns a mobile number they have provided. This service allows you to not only protect your business by ensuring the messages you send are delivered to the correct user, but also to protect your user by establishing a trusting relationship right from the moment the user signs up.

Add Dynmark Verify to your app to secure user data and authenticate new customers. Dynmark Verify allows you to easily setup a simple system to verify user phone numbers across the globe and improve security in your app. Our Dynmark REST APIs take care of the verification backend, from sending the code and managing the SMS, so you just need to tell us who to send it to.

Calling on over a decade’s experience and having communicated with nearly every country in the world, Dynmark has the experience to deliver a solution for verification that is fast to integrate, easy to use and reliable under load.

What does Dynmark Verify do?

The Dynmark Verify service is a secure REST based API that delivers a numeric code to a mobile number, which the user must then supply within a website or app, this code is then validated before the user can proceed. This ensures that mobile data is not only accurate, but the mobile number is owned by the user that provided it.

The Verify service will manage all the hard work for you, by validating the mobile number provided, generating the 6-digit code, sending the SMS and validating the code.

The Dynmark REST API is offered as HTTPS only to ensure data privacy. We use TLS 2048 bit encryption to protect messages in transit.

Verify use cases?

Businesses are more and more frequently using techniques like Verify to create a trusting relationship between them and their users, there are a lot of benefits for the business for doing this.  As spam and online fraud accelerate, the requirement to tie a user to a device leveraging the mobile number as the primary ID is also accelerating. Mobile only channels are replacing email as the trusted communication method. This is driving compelling business use cases.

  • Valid data: Businesses want to be sure they have the right information for a user before sending sensitive communications (e.g. bank balances, payment information)
  • SCV (single customer view): Utilising the verification process to capture the mobile number which can then be used across multiple channels to identify a user, replacing email
  • Trust: The number becomes a trusted piece of information once verified and can be used for account recovery, password reset etc. in place of email
  • 2FA: As part of a 2FA process, the mobile number can be used as “something you own” once validated
  • OTP: Once a confirmed mobile number is attached to a user account, the number can be used for OTP (one time passcodes) to confirm transactions, such as payments etc.
  • User benefit: Users will be motivated to provide the correct information, because there will be benefits for them if they provide their mobile number (e.g. delivery updates, account information etc.)

Creating a custom experience

When reaching out to users with Verify, it helps to be able to create a custom experience that fits in with all other communications coming from a business. To that end, when calling the Verify API, you are able to specify the following parameters to match your requirements:

ParameterDescription
Expiry Used to control how long the code is valid for once sent to the user, the default is 5 minutes, but can be anywhere from 30 seconds to 60 minutes.
Message The Verify API will have a default message, but the API will accept a custom message up to a maximum of a single segment (160 GSM characters) instead, including the field (6 characters)
From A valid sender ID
Country Code If a mobile number is provided in international format (e.g. 447000000000) they do not need to provide a country code, but if the mobile number is local (e.g. 415 555 2671) they must provide the country code (e.g. USA)

Converting customers

One of the most important things to be understood from any verification or authentication process is its success; which is in the case of Verify, the number of Verify calls that result in a successful verification of the code.

Dynmark provides a report for Verify that provides exactly that information. This report can be used to track the number of Verify SMS sent against the number of successful verifications. These numbers should be very similar, demonstrating a very high rate of success of SMS verifications of users.