An Interesting Alternative to Captcha & One Time Password ( For Customer Identity Verification & Transaction Authorization )

With the traditional approach we usually go for Captcha OR SMS Based OTP, for validating user identity. But How about using missed call to authorize website users?

I personally feel, it would not just help us in validating user identity but also can be used to build a clean userbase with valid customer contact details

I came across this new platform as a service, and so thought of sharing here...really exciting. ( http://dial2verify.in )

Knowledge-base on Dial2Verify API, http://kb.dial2verify.in

It can be very well used as an alternative to captcha and OTP ( one time password over sms )
for
1. authenticating user identity
2. for building a clean user-base

Browse sample code and live examples at
http://sample.code.dial2verify.in

I agree that there needs to be improvements to the likes of Captcha, I personally use the Math hook on my formit forms which works 100% and can honestly say if a site asked me for my phone number there is no way I would sign up, so personally think this would put people off

Very well explained Paul.

But for the ecommerce sites ( specially in india ) which provide cash on delivery option , verifying customer mobile before accepting COD order is must. As the spam orders might lead to wastage of supply chain efforts and fuel costs as well.

With the traditional approach, websites dispatch a one time password ( OTP ) on customer mobile. but such OTP is a costlier option to business owners when compared with Missed Call Based implementations

It is true that most ecommerce checkouts and some business sites do require a phone number anyway. So for that kind of site this might be useful. I wasn't able to determine on the quick glance I gave it whether or not this is a service where the information is stored on their servers. That would definitely be a show-stopper for me; adding my users to somebody's list of phone numbers is not my idea of a Good Thing.

No, Information isnt stored with Dial2Verify, It just sends a notification ( Acknowledgement ) to the 'notify' url set while calling its API.

Acknowledgement is nothing but a GET URL call made to the remote url set in the 'notify' parameter of the API call.

Then the web owner can record the results of verification, sent in GET call, on its local db

Please have a look at the http://kb.dial2verify.in/?q=16 for more details on 'how it works'.