I am using a free server of parse.com for my database
I need to verify phone number of user without spending any money, because I don't want to buy an sms gateway, or mobile no. verification by using miss call service.
Any idea?
How is sending verification codes to a user's email address going to verify their phone number? The only way to verify that a user owns the phone number that they're giving is to actually call or text it and have the user respond (usually by entering a one time passcode that's in the text message or spoken in the phone call).
Parse already supports e-mail verification, so if you want to do that then you can check it out here: http://blog.parse.com/2012/04/03/introducing-app-email-settings/
Some - but not all - mobile networks let you send SMS messages via e-mail address, but support for this is rather variable. For near-certain delivery and the best user experience you'll need to use a service that lets you send SMS messages through an API, such as Twilio.
Related
I'm planning to create an app and I do not want multi-account, is SMS verification the best way? I've thought with email verification, but for me it does not make sense since I can create fake emails and then sign up with that one. That's why I ended up thinking SMS verification could do the "trick", I know to avoid multi-account is hard, but I can avoid it with SMS because phone number is uniq.
I've been reading Firebase Phone-Auth, but I'm seeing I only can verify 10k users per month (free), from now is ok, but when growing it will be a problem, is there any other api to use OTP?
Edit
Is it safe to create my own service? Let's say this would be the flow.
User puts the phone number on Android phone
Android sends that phone number to server
Server uses an API to send SMS
Server knows then the SMS is sent or not, so it will store the code
Android receives the SMS (without permissions in manifest) then is sent to backend to do the verification
It's possible to send an e-mail which a phone receives as an SMS by sending to (in the case of Verizon) 2125551212#vtext.com, and when I use the SMS app to send to an e-mail address, that's what shows up as the sending account. (This site has a list of the "#telcoName.com" addresses for various other carriers.) Is there a way for an app to know that "2125551212#vtext.com" address of the phone that it is on, WITHOUT having to send out an e-mail over SMS first and then be told whom its sent message came from?
Is there a particular permission that a developer would use to determine this info?
With some other research, it appears that the answer is NO: the phone does NOT "know" the email address that will reach its SMS app. This info can be determined by asking the user his phone number and cellular carrier (looking up the "#whatever.com" part in the website I posted in the question), OR you can have the app send an SMS to an email address on a cooperating code server, which then "tells" the app what email address it just got a message from.
But the Android operating system in the phone doesn't have this information available itself, so the app can't get it from the OS.
I am making a messaging application and we need to verify the user mobile number by sending short code through SMS from users mobile(user will be charged for outgoing SMS ).
We are able to send sms and even able to verify but the message is going from user's name so how to change this user's name to custom name as it is done in whatsapp or other application.
DW-Whatsapp
AM-Telegram
Please advice.
I am trying to make an app which requires WhatsApp like validation of number, as heard from many people I sent a SMS from the same number to same number and check if the number is same and in message I sent a hashid generated from number and IMEI number and send the same to Server.
Now when the use receives the SMS and put the hashid on an input field and it got stored to Shared Preference and sent to server to match.
Is this the right way and same way WhatsApp doing?
See these links
SMS registration like in the mobile app: whatsapp
How to verify the phone number similar to Whatsapp?
As it says
Send the phone number to be verified, receive a unique hash.
The verification system sends a unique code to the user.
Once the user passes that code to your application, the original hash and the code are sent to the verification system to be validated.
Flow for MSG verification is:
User sent a request for a verification over a particular mobile
number.
Server sends an SMS to that mobile number with verification code,
along with device IMEI number sent by the phone while asking for
verification [Must be encrypted].
SMS broadcast receiver receives an incoming SMS checks if it's
type and if it's an verification SMS, Decrypt the contents,
validates the IMEI number, gets the verification number and sends
this verification number back to the server.
Our Android application is a Visual VoiceMail application which communicates with IMAP server to doownload voicemail mails and play it on user handset. As an autentication method application implements sending/receiving OOB SMS from this client. For sending SMS for this application we have following queries
Will our application be allowed to host on playstore as the application is supposed to send OOB SMS whitout letting the user know about it as it is a part of standard authorization method. In reply to this SMS server will response back to this client with an SMS over specific port which will have the credentials for user and client will start working.
If above is not allowed then what are the norms with which we can implement the same behaviour. Please not we cannot ask the user every time to allow sending messages from application.
Will it be ok if we take consent from user at the time of installation that this application will send authorization/validation messages from backend.
Any other suggestion and norms which we need to take care.
The Visual VoiceMail application is limited to users of a particular operator.
This SMS will not charge any cost to the user, It will be free.
Is this possible and allowed for application to be published on Google Play. If not, please suggest a way to achieve this.
Thanks in advance.