Missed-Call Verification

OTP is great, but it shouldn’t be your only form of user verification. Since we think missed-call verification is essential to your business, we’re going to break down what it is, how it works and, why, when combined with OTP it can save your money and win you verified leads.

What exactly is missed-call verification and how does it work?

Missed-call verification is an easy way to verify a mobile number through a missed call from the user’s phone. The concept is pretty simple – the users enter their phone number during the in-app verification process then will receive a number on their app screen and will make a call to that number in order to get the user verified.

What is 2 Factor Authentication via Missed Call?

An authentication factor which uses Missed/Dropped Call initiated from user’s registered phone. Dropped/Missed Call is a call which gets disconnected by dedicated phone number before getting answered. You can Authenticate users using Dropped/Missed Call service.

Advantages of 2 Factor Authentication via Missed Call.

• Password-less Authentication.
• Low operational cost.
• Cheaper than OTP SMS Authentication.
• Cheaper than OTP Voice Authentication.
• Simple and secure HTTPS API based integration with your applications.

Most Commonly Used

• Sign up Verification.
• Leads Generation.
• Transaction Authorization.
• Member Account Verification.
• Cash on Delivery (COD) shipments.

Requirements

You need to avail dedicated missed call number.

Integrate our 2 Factor Authentication API.

API Work Flow

Our API handles all the authentication infrastructure. We have written a detailed documentation on 2 Factor Authentication via Missed Call which you can forward to your development team.

Step 1: Your user will appear on your login or registration page, fill your details then click on submit or login button.

Step 2: If the information given by the user is correct, then to verify the mobile number of the customer, a call has to be made on the given number like Screen – 2A.

Step 3: After the missed call, the user clicks on the “Done” button or after the time given on the timer ends, our web server will hit by passing the user number to our missed call API.

Step 4: Our web server will get a response code after hitting the API.

A) If our response code is 000. it means your user is authenticated

B) If our response code is 001. This means your user is unauthenticated.

Step 5: If, you have received response code 000, then take your authenticated user for further transactions.

Note: Callback parameter is mandatory, the response will be forwarded to this URL whether customer dialed the missed call number or not.

API Document

http://YourDomain/api/MissedCallReport/getmissedcallhistory?channelNumber=1800XXXXXXX&mobileNumber=XXXXXXXXXX&timeInterval=XX

Response: Missed Call Received

<MissedCallReportController.MissedCallSmsResponse xmlns:i=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”http://schemas.datacontract.org/2004/07/SmartTech.IMissedCall.Web.Controllers”>

<ErrorCode>000</ErrorCode>

<ErrorMessage>Received</ErrorMessage>

<MissedCallID>4477</MissedCallID>

<Number>8052128888</Number>

</MissedCallReportController.MissedCallSmsResponse>

Missed Call Not Received

<MissedCallReportController.MissedCallSmsResponse xmlns:i=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”http://schemas.datacontract.org/2004/07/SmartTech.IMissedCall.Web.Controllers”>

<ErrorCode>001</ErrorCode>

<ErrorMessage>Not Received</ErrorMessage>

<MissedCallID>0</MissedCallID>

<Number>8052128888</Number>

</MissedCallReportController.MissedCallSmsResponse>