SMS OTP API · South Africa

SMS OTP verification for your customer journey

Send a one-time code to a South African mobile number and let your customer confirm it inside your app. Keep signup and account checks in the experience your customers know.

API-only service. Access by arrangement.

Example verification message

Your verification code is 123456. It expires in 5 minutes. Do not share this code.

One code. One verification journey.

A phone check at the moment it matters

New account signup

Ask customers to confirm access to their mobile number before they continue with your onboarding checks.

Account recovery

Add a phone check to the recovery process your business controls, alongside the safeguards appropriate to the account.

Contact changes

Check that a customer can receive a code at their new mobile number before updating your records.

Sensitive account actions

Include a phone verification step where your business needs an additional confirmation from the customer.

You keep the customer relationship

Your app collects the number, displays the code-entry screen and decides what happens after verification. You retain customer account records and control account recovery.

Every SMS uses a fixed verification message. Send limits help control unwanted requests. Sends use your available prepaid credits without a daily spend cap.

Temporary data in South Africa

OTP processing payloads use encrypted storage in Cape Town. Codes expire after five minutes, with short retention periods for abuse prevention and safe retries.

SMS delivery partners and mobile networks maintain separate delivery records. Our OTP processing disclosure explains what is kept and for how long.

SMS OTP questions

What does SMS OTP verification confirm?

A correct one-time code confirms that the person can access messages sent to the supplied phone number. Your business decides what checks are needed before granting account access.

Can I use it in my own app or website?

Yes. The service is designed for API integration. Your team keeps the customer journey in your app and uses separate requests to send a code and check the response. Use your existing approved API key and available credits.

Which phone numbers are supported?

South African mobile numbers are supported. International destinations and non-mobile numbers are outside the current service.

What does the customer receive?

A six-digit verification code with a five-minute expiry and a reminder to keep it private. The message contains no marketing content or VerifyNow brand prefix. Its wording is fixed.

How is the service charged?

Each accepted SMS send or resend uses OTP credits. Checking the code is included. Unresolved sends are charged after ten minutes; confirmed rejection before acceptance is refunded. Delivery failure after acceptance remains charged. Full charging terms are available below.

Where is temporary OTP data stored?

Temporary OTP code hashes, recipient-derived tokens and retry payloads use Cape Town, South Africa storage. Raw numbers and codes are used for processing in memory. Account, billing and delivery-network records follow their own retention schedules.

Add phone verification to your application

Tell us about your customer journey and expected SMS volume. We’ll help you plan API access and the checks that fit your business.

Discuss your integration