Verify Countersignature Phone with airSlate SignNow

Register number text

if you're a developer for an app you probably know the nightmare that would ensue if you let just anyone or anything create a new account without some sort of verification the simplest cheapest and most common option email verification someone signs up they get an email they click the link in the email and right away you know they're a real person except not really the problem is an email address is hardly an accurate one-to-one representation of a human all you've proved is the existence of an email address it's also really easy to create a new email account just to satisfy a verification requirement or lots of email accounts and just because someone's email address was legitimate at one point doesn't mean it hasn't since been hacked and/or become part of a botnet work so maybe you've tried defending against bad sign ups using a CAPTCHA good idea you just got rid of all the robots but this won't stop a human with criminal intentions let alone a whole workshop of them oh and CAPTCHAs generally frustrate people like crazy but there is another piece of information you can use that's a much better indicator of a real person accessing your business a phone number it's harder to fake and more expensive for a hacker to scale an attack it's now very common to see signup forms ask for a phone number so users are familiar with giving applications their number it might seem simple to implement phone verification yourself in theory just send the user a text containing a randomly generated pin code then make sure they retype this code into your application thereby verifying that they have access to the phone number they provided but of course it's not that simple first you have to fix potential deliverability issues what if someone's phone isn't capable of receiving a text message then there are the filtering rules did you know for instance that your message might not be delivered in Canada if the code comes from a USA ten digit number you'll need to know which filtering rules are in place all across the globe then there's the issue of translation you'll need to translate all the SMS messages for each region your business is in and all the voice messages on top of that the rules change constantly you'll have to familiarize yourself and stay up-to-date with all the rapidly changing filtering rules and regulations of carriers and the local regulatory requirements and that's to say nothing of all the security considerations but what if you didn't have to think about any of this what if all the regulatory and security issues carrier rules and language barriers just went away what if you could replace all those development hours with just two API calls what if you knew that the message would make it to the human user no matter where they are in the world and in the right language this might be closer...