Skip to content
Intracent
Log in Talk to sales Start building
Verify (OTP & 2FA) Products Virtual numbers Wholesale SMS Industries Developers API reference Pricing Compliance Log in
Talk to sales Start building
Verify for OTP and 2FA

One-time passcodes that arrive.

Add phone verification to sign-up, login and checkout. Codes travel on transactional routes worldwide, with number checks before you send and a receipt the moment they land.

Each code is one SMS, priced by destination country. See the rate for your users' country

Check your phone
We sent a 6-digit code to +1 415 •••• 0142
4 1 8 2 0 9
Verify
send_sms · accepted0.03s
dlr · DELIVRD1.32s
Illustrative example

Verify at the moments that matter.

Sign-up
Confirm a real person owns the number before the account goes live.
Your Acme code is 418 209. It expires in 10 minutes.
Login & 2FA
A second factor that every phone already supports.
Acme sign-in code: 552 019. Never share this code.
Checkout & payments
Step up before high-value orders, transfers and payouts.
Approve your A$1,240 payment with code 771 304.
Account changes
Protect email, password and payout-detail changes.
Code 306 118 to change your bank details. Not you? Call us.

Three calls. Your logic stays yours.

Your app generates and checks the code, so your security rules never leave your stack. We handle getting it to the phone, fast. Prefer a managed flow? Ask us about the Verify API.

Read the quickstart
1
Check the number (optional)
HLR lookup tells you if the number is live, ported, and which network serves it. Coverage varies by country.
curl 'http://hlr.intracent.com:42081/hlr/mccmnc_request?login=$LOGIN&password=$PASS&dnis=61412345678'
→ {"mccmnc":"505003","result":0,"ported":0}
2
Send the code
Generate a 6-digit code, store a hash with a short expiry, and send it.
curl -X POST -H "Authorization: Bearer $TOKEN" \
  "https://api1.intracent.com/rest/send_sms?acc_id=$ACC_ID&from=Acme&to=61412345678&message=Your%20Acme%20code%20is%20418209"
→ {"message_id":"…"}
3
Confirm delivery, then the code
The receipt arrives at your webhook. When the user types the code, compare it with the stored hash.
POST https://your-app.com/dlr
{"msg_id":"…","state":"DELIVRD","to":"Acme","mcc":"505","mnc":"03"}

Fast for real users. Hard for everyone else.

Transactional routing
Codes travel on routes built for time-sensitive traffic, with dedicated routing for enterprise volumes.
Number intelligence
HLR and MNP lookups flag dead, ported or unexpected numbers before you spend a credit. Coverage varies by country.
Registered sender IDs
Your brand name on every code. As an ACMA-approved telco, we register Australian sender IDs for you.
IP-bound API tokens
REST tokens only work from the IP address that requested them, and expire after 2 hours by default.
Real-time receipts
Know the moment a code is delivered, or not, so you can offer a resend at the right time.
Throughput for spikes
Up to 300 messages a second, and SMPP binds for very high volumes.

An OTP checklist that stops SMS pumping.

SMS pumping is when bots trigger codes to premium numbers so someone else collects the revenue. Most of it is stopped by a few rules in your app.

  1. Rate-limit every request
    Cap code requests per phone number, per IP and per session, with a cooldown between resends.
  2. Check numbers before you send
    Use HLR lookup to skip landlines, invalid and unexpected numbers.
  3. Only allow countries you serve
    Block destinations where you have no users. Most pumping targets unusual countries.
  4. Keep codes short-lived
    6 digits, valid for 5 to 10 minutes, single use, and stored hashed.
  5. Never put links in OTP messages
    A code, the brand and the expiry. Links make codes look like phishing.
  6. Watch the numbers
    Alert on spikes in sends without matching verifications, by country and by hour.

Questions

How much does an OTP cost?+

Each OTP is a standard SMS, priced by destination country; look up any country on our pricing page. Long or Unicode messages use more segments, so keep codes short and in plain characters.

Which countries can I send codes to?+

Intracent delivers SMS to mobile networks worldwide. Some countries require a registered sender ID or a specific route for one-time passcodes; tell us where your users are and we'll set up the right route.

Do you generate and check the codes?+

With the SMS API, your app generates and checks the code, which keeps your security logic in your hands. If you'd prefer a managed flow, ask us about the Verify API.

How do I reduce SMS pumping fraud?+

Rate-limit code requests by number and IP, check numbers with HLR lookup before sending, block destinations you don't serve, and watch for sudden spikes in traffic to unusual countries.

Ship verification this week.

Free account, pay as you go. Tell us your countries and volume and we'll recommend the right route.