Global OTP delivery
One connection for verification codes, account notices and opt-in marketing, routed per destination.
A2P SMSApps going global
Verification codes that reach your users in every new market
Send sign-up and login codes to 190+ countries over one SMPP or HTTP connection, with a test route to your own handsets and sender types chosen per country.
What you get
One connection carries verification codes, account notices and opt-in marketing. The sender type, registrations and rate are set per destination, and you can test a market before you commit volume to it.
Test routes
Send test messages to your own handsets in the markets you choose and check what the phone shows, not only the delivery report.
How we test routes
Sender types per country
Each market decides whether you send from a long number, a short code or a brand name. We confirm the type your market needs.
Sender typesExamples, not legal advice
Sender types and compliance points: two examples
Rules differ in every market. Two examples of what an app has to plan for; we confirm the current rules for your destinations in the quote.
| Example market | Sender types | Points to plan for |
|---|---|---|
| Mexico | Confirmed in your quote | People on the national no-advertising register (REPEP) must stop receiving advertising texts, so plan consent and opt-out handling. |
| Brazil | Short codes, long numbers | LGPD applies to the phone numbers and personal data you send; opt-in and opt-out rules apply to marketing. |
This is general information, not legal advice. Check each market with your counsel.
SMPP integration
Connect once, send everywhere
A bind is a session between your application and our messaging center. You submit the destination and the sender the market expects, and each submit can return a delivery report. Sender type and route are confirmed per destination at onboarding; encoding is a per-message choice in your application.
- Protocols
- SMPP 3.4 · HTTP
- Throughput
- 200+ TPS per bind
- Encoding
- GSM-7 · UCS-2, for Chinese and other scripts
- Delivery reports
- Per message, by deliver_sm or HTTP callback
- Concatenation
- UDH; 153 GSM-7 or 67 UCS-2 characters per part
- Destination address
- E.164 digits: country code first, no plus sign in the SMPP address
- Registrations
- Sender IDs, short codes and number ranges where the market requires them, confirmed before launch
Traffic policy
What we carry
- Verification codes (OTP)
- Account and order notifications
- Marketing to recipients who opted in
What we do not carry
- Gambling
- Debt collection
- Unlicensed lending
- Political content
- Unsolicited promotions
- SIM-box and gray-route traffic
When we are not the right fit
Limits worth knowing before you plan a new market on our routes.
A fit for
- Apps that send sign-up and login codes, account notices and opt-in marketing from one connection
- Teams that want to test a market on their own handsets before committing volume to it
Not a fit for
- Marketing to users who did not opt in, or traffic outside our traffic policy
- Testing your app’s own sign-in flow or your live user traffic: route tests use test messages only
FAQ
Can we test before we sign?
Yes. Request a test route; after we review your inquiry we set up test credentials so you can send to your own handsets in the markets you choose.
Do you publish prices?
No. Rates depend on destination, sender type and volume, so we quote per request.
Can we send codes in Chinese characters?
Yes. Messages in Chinese use UCS-2 encoding, which fits fewer characters per segment. Count segments before you send with the SMS segment counter.
How long can an OTP be before it costs two messages?
GSM-7 fits 160 characters in one segment, or 153 once a concatenation header is added; UCS-2 fits 70, or 67 with the header. A six-digit code is never the problem; the template around it can be. Check the count with the SMS segment counter before you change wording, and read concatenation if your messages split.
What has to be registered before we send to a new market?
It depends on the market: alphanumeric sender IDs, short codes and dedicated number ranges may need registration, and some destinations review template content first. We confirm what applies, and the lead time, in your quote. Sender registration explains what is usually asked for, and sender IDs in Mexico and Brazil shows how two markets differ.
How do we know a code reached the phone?
A delivery report says the network accepted and delivered the message; it does not prove the handset showed the right sender or text. On a test route, send to your own handsets and check the sender, accents, long-message joins and links on each one. Route testing and OTP delivery fraud explain the failure modes worth watching.
Can we keep one integration while we add markets?
Yes: the SMPP bind or HTTP endpoint stays, while sender type and route change per destination. Keep the sender as a parameter in your template layer rather than hardcoding it per country, so a market change does not need an app release. SMPP or HTTP sets out the trade-offs.
Learn
Learning path: A2P SMS, from first code to production
Related solutions: A2P SMS for apps going global
Tell us your markets and monthly volumes
Our team replies with next steps or a quote.