Frequently Asked Questions - Verify Now

Our support team is available 24/7 to help with any questions or issues you may have. You can reach out to us via: -

1. Website through the talk form
2. WhatsApp through the WhatsApp live chat on the website
3. Email us at support@messagecentral.com

You do not need Sender ID to use Verify Now. You can start sending OTPs through our sender ID and generic template for OTPs which are approved.

‍For US Users: In the US, you can start using our SMS verification APIs without any 10DLC. We already have an approved template for sending SMS verification codes i.e. OTP SMS.

For Indian Users: In India, you can start sending OTP SMS directly without any DLT registration in India. We have approved templates for sending OTP SMS. You can refer to our guide on how to get started without DLT registration in India for any further details.

To send SMS messages in India, compliance with Digital ledger Technology (DLT) registration is a must, as mandated by the Telecom Regulatory Authority of India (TRAI). You can also refer to our complete guide on DLT registration.

Effective September 1, 2023, A2P 10DLC has been made mandatory for all A2P campaigns in the US. A2P 10DLC enhances message delivery and improves trust and reputation. You can read more about the same in our guide on A2P 10DLC.

If you have your own sender ID and template which you wish to broadcast to your clients, you can use our SMS platform -Message Now. Please get in touch with us, and our team will guide you to the best solution tailored for you.

We are powered by direct operator connectivity across the globe. This helps us in automatic routing of global traffic to avoid outages ensuring the most premium routes and the highest delivery rate.

We have developed the entire Verify Now technology in-house and are the sole owners of it.

Yes, upon initiating the OTP request, if the OTP delivery is unsuccessful for any reason, you have the option to resend the OTP after a 60-second interval (can be changed).

However, once the OTP has been successfully delivered and verified, you will be able to send subsequent OTPs immediately. We also have our SMS retry algorithm working consistently to ensure successful delivery of every SMS.

Yes, you can change the 60-second interval to resend OTP SMS. Here are the details: -

1. Default: 60 seconds
2. Minimum: 20 seconds
3. Maximum: 300 seconds

You can adjust the “Validity Time” to make any effective changes to the default timer to resend OTPs.

You can set change the “Validity Time” to adjust the resend OTP SMS timings. For example: If you set the validity time to 30 seconds, your resend OTP SMS option will be enable after 30 seconds.

You can use postman to rewrite API calls in your preferred programming language. You’d need to use: -

1. POST method for sending SMS
2. GET method for validating OTP SM

You’d need to ensure that the endpoint URL for the Token API matches the one defined in the documentation.

The same has been mentioned below: -

1. Token API using GET method
2. Send API using POST method
3. Validate API using GET method

You can use Postman to test Message Central’s SMS verification APIs.

If you are getting Whitelabel Error page, you should check for the following errors: -

1. You are using incorrect API packet
2. You have not replaced placeholders with the actual values
3. API curl is incorrect
4. Curl location has not been changed to ‘production’ instead of ‘staging’

This could be because of incorrect API or token. Make sure you have followed our API documentation for the right token values.

There are multiple reasons for a “Bad Request” in Postman. You can check for the following probable reasons: -

1. Check if the authToken is correct
2. Check if any parameter is missing in API
3. Header should be passed in this format - application-x-www-form-urlencoded

In your Message Central login, you can find the authToken under “Try with Code” as shown below: -

Alternatively, in order to generate the authToken in Postman, you’d: -

1. Find a ‘key’ in GET API
2. You’d need to copy that key and encode the same using Base64 - https://www.base64encode.org/‍
3. Put the encoded password in ‘Key’ placeholder
4. Hit the GET API

You’d get an authToken.

You’d need to put the authToken in the header of SEND API.

You’d need to change country, customerid, email and key. Scope will always remain = “NEW”

You’d need to change country code, customerid, otplength, and mobilenumber.

There can be multiple reasons of this error. But in majority cases, your authToken parameter is missing in header.

Verify Now is a user authentication service provided by Message Central, which enables businesses to verify users' phone numbers using a One-Time Password (OTP) sent via SMS.

The process is simple: -

1. You can sign up for free through the website
2. Access detailed API documentation from within the platform
3. Test the service with the free credits in your account
4. Once satisfied, top Up your wallet and start using Verify Now

You can also refer to our video on API integration which explains the entire Integration process in detail.

We provide: -

1. The best delivery rates which are as high as 99% through intelligent routing

2. The best rates per OTP SMS which are on an average 40% lesser than other providers in the industry.

3. You do not have to go through the hassle of registering a Sender ID/ 10DLC (for US) or DLT registration (for India) for OTP SMS.

Verify Now offers global connectivity to enable you to send OTPs, to countries all over the world

User authentication is important to protect a business and its users from fraud, data breaches, and other security threats.

By confirming user phone numbers through OTP Verification, you can ensure that only legitimate users access your services.

When a user enters their phone number on your website or app, Verify Now sends an OTP via SMS. The user then enters the OTP to verify their phone number. This ensures that the user is a legitimate user and not a bot or fake account.