Bitcoin Forum
November 14, 2024, 02:05:38 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Planning to start a SMS Verification API  (Read 172 times)
Coin Dropper (OP)
Member
**
Offline Offline

Activity: 151
Merit: 10


View Profile
March 27, 2018, 10:54:40 AM
 #1

I am planning to create a SMS Verification Service with API. What is the best price should I charge per SMS?
OmegaStarScream
Staff
Legendary
*
Offline Offline

Activity: 3668
Merit: 6444



View Profile
March 27, 2018, 11:10:03 AM
Last edit: March 27, 2018, 02:04:52 PM by OmegaStarScream
 #2

It really depends on so many things. If your numbers are unique and are going work with Twitter, Facebook, Google, Whatsapp etc. If you're planning to charge users for each verification or based on a monthly subscription. There is a service called smsverify.club that charge 0.6$ per verification for example. You will need to make competitive rates and still make it profitable for you.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
AdolfinWolf
Legendary
*
Offline Offline

Activity: 1946
Merit: 1427


View Profile
March 27, 2018, 11:24:58 AM
 #3

It really depends on so many things. If you're numbers are unique and are going work with Twitter, Facebook, Google, Whatsapp etc. If you're planning to charge users for each verification or based on a monthly subscription. There is a service called smsverify.club that charge 0.6$ per verification for example. You will need to make competitive rates and still make it profitable for you.

Indeed, a site i used in the past charged just 0.1$/0.05$ for the verification of google/twitter accounts, but it seems that a lot of their numbers have stopped working/ are blocked by google.

See http://smspva.com/ if you're interested in looking into the rates of some of your competitors.

I am planning to create a SMS Verification Service with API. What is the best price should I charge per SMS?

I'd be more than happy to pay 0.3-0.5$ for twitter/google if your number would actually work instantly. ( Which is still 3x more expensive than what smspva charges, but i've found their service to be barely working currently.)

Coin Dropper (OP)
Member
**
Offline Offline

Activity: 151
Merit: 10


View Profile
March 27, 2018, 03:22:18 PM
 #4

I will have a number that works on most sites and cannot be blocked. Should 0.1$ per website is good? I am planning to sell it for different websites instead of a monthly or a per number basis.
Coin Dropper (OP)
Member
**
Offline Offline

Activity: 151
Merit: 10


View Profile
March 27, 2018, 03:27:55 PM
 #5

I think 0.1$ is good per website and will be credit based. Bulk credits will have discounts. And I currently have thousands of numbers available and should crush the competition.
Coin Dropper (OP)
Member
**
Offline Offline

Activity: 151
Merit: 10


View Profile
March 27, 2018, 03:30:43 PM
 #6

It really depends on so many things. If your numbers are unique and are going work with Twitter, Facebook, Google, Whatsapp etc. If you're planning to charge users for each verification or based on a monthly subscription. There is a service called smsverify.club that charge 0.6$ per verification for example. You will need to make competitive rates and still make it profitable for you.

The numbers are unique to the website they'll gonna use it for. And can be added to almost any programs for automation. That should be good right?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!