Route transparency
The sender type and number pool for your traffic are confirmed at onboarding.
A2P SMS
A2P SMS for platforms that check delivery on the handset
Send verification codes, notifications and opt-in marketing to 190+ countries on one connection, with a test route to your own handsets before live traffic.
- Coverage
- 190+ countries
- Connection
- SMPP 3.4 · HTTP
- Throughput
- 200+ TPS per bind
- Traffic types
- OTP · transactional · opt-in marketing
- Sender types
- VLN · short code · alphanumeric
- Delivery reports
- Per message, as SMPP receipts or HTTP callbacks
What you get on every route
One SMPP or HTTP connection and the sender type each market needs.
Template pre-testing
We test new message templates against local keyword and link filters before your campaign goes out.
Dedicated number ranges
Reserve number ranges for your traffic instead of sharing pools with unknown senders.
Test route
Send test messages to your own handsets on the destinations you choose before live traffic.
How we test routes
Named contracting entity
Your quote names the contracting entity for your location and destinations, with local invoicing where available.
Our entities
Traffic screening
We review sample content before a route goes live.
Traffic policyConnect
SMPP and HTTP JSON connection
SMPP 3.4 supports transmitter, receiver and transceiver binds. HTTP takes JSON requests and returns callbacks, and both carry delivery receipts per message. Endpoints are documented in your onboarding pack.
- SMPP
- v3.4 · transmitter / receiver / transceiver binds
- Throughput
- 200+ TPS per bind
- Encoding
- GSM-7 · UCS-2 · concatenated messages (UDH)
- Delivery reports
- deliver_sm receipts · HTTP callbacks
- HTTP
- JSON over HTTPS
Which sender type fits your traffic
Each market sets its own sender rules. We confirm the sender type, registration steps and lead time for your destinations in the quote.
| Sender type | Best for | What setup involves |
|---|---|---|
| Virtual long number (VLN) | High-volume OTP and notifications | Dedicated ranges registered for your traffic where local rules require it; we coordinate the registration. |
| Short code | Banking and large consumer brands | Per-operator or national registration; lead times depend on the market. |
| Alphanumeric sender ID | Brand name as sender | Sender ID registration where the market supports it; some operators do not. |
Sender types, registration steps and lead time are confirmed in your quote.
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
Fit
Who this is for, and when it is not the right fit
Wholesale A2P SMS is for businesses that send application messages and go through verification before activation. These are the limits we state up front.
Who this is for
- Businesses that send verification codes, account and order notifications, or marketing to recipients who opted in
- Teams that connect over SMPP 3.4 or HTTP JSON and want a test route before live traffic
- Companies that can pass company verification and content review before activation
When it is not the right fit
- Personal use: we serve businesses only, and we verify the company and its use case before activation
- Gambling, debt collection, unlicensed lending, political content, unsolicited promotions, or SIM-box and gray-route traffic
- Marketing to recipients who did not opt in; sending hours and opt-out wording are set country by country
- Application messages on person-to-person (P2P) routes: P2P has no sender registration or template approval, so it is not for application messages
- Testing your own app’s sign-in flow or your live customer traffic: route tests use test messages only
- A published price list: every route is quoted per destination, traffic type and volume
- RCS: this page covers SMS; ask us about RCS for your destinations
Route testing
How we test routes
A delivery report says the network accepted a message, not what the phone showed. Before live traffic, we set up a test route after we review your request, and you send test messages to your own handsets on the destinations you choose. We also test new message templates against local keyword and link filters.
What a route test checks
- Whether the message reaches your handset at all
- The sender your handset shows, and whether it was rewritten
- Content as received: accents, Unicode, long-message joins, links
- Time from submit to arrival, compared with the delivery report
- Delivery reports that say “delivered” when the phone got nothing
What a route test does not cover
- Every operator in every country: a result holds for the destination, networks and time you tested
- Your own app’s sign-in flow or your end users’ devices
- Your live customer traffic; route tests use test messages only
When a test fails
- A failed test leads to a route review.
- An anonymised sample route report is available on request.
Where you can send
A2P SMS to 190+ countries. Check a destination’s sender types and rules before you ask for a quote.
Industries that buy this
Fintech & banking
One-time passwords and transaction alerts that must reach the phone, with sender types chosen per market.
Learn moreE-commerce & marketplaces
Sign-in codes, order confirmations and delivery updates for marketplaces selling across borders.
Learn moreTravel, airlines & OTAs
Booking codes, flight alerts and check-in reminders to travelers worldwide, alongside travel eSIM data.
Learn moreFrom first message to live traffic
-
Tell us your traffic
Destinations, volumes, traffic type and sample content.
-
Agreement and KYC
Company verification, content review and a messaging agreement.
-
Connect and test
SMPP or HTTP credentials, then a test route with sends to your own handsets.
-
Go live
Ramp volume with delivery reports and one point of contact.
Tools for this product
Free, no sign-up. Your text stays in your browser.
Illustrative scenario, not a specific customer
A global CPaaS platform moves its OTP traffic onto verified routes
Delivery reports said its verification codes arrived; its users said they did not.
We moved OTP to dedicated number ranges, set up a test route so the platform could check each destination on its own handsets, and ramped volume in stages with one point of contact.
The platform now checks delivery on its own handsets before it moves a destination.
FAQ
Do you publish prices?
No. Rates depend on destination, traffic type and monthly volume. Send an inquiry with your destinations and volumes and we quote those routes.
Do you offer RCS?
Ask us about RCS for your destinations.
Can I send marketing messages, and at what hours?
Yes, to recipients who opted in. Sending hours and opt-out wording are set country by country; we confirm the rules for your destinations in your quote. This is general information, not legal advice.
Can I test a route before I commit?
Yes. Request a test route; once our team has reviewed your request, we set up test credentials so you can send to your own handsets on the destination you choose.
What traffic do you not carry?
Gambling, debt collection, unlicensed lending, political content, unsolicited promotions, and SIM-box or gray-route traffic. See our traffic policy.
How fast can we start?
We do not promise a fixed lead time. The agreement, company verification and, where a market requires it, sender registration set the pace, so the timeline depends on your destinations and sender types. Your quote sets it out.
Can we move traffic to you one destination at a time?
You can start with the destinations you choose; the quote confirms volume and terms per destination. One SMPP bind or HTTP endpoint to us covers every destination, while sender type and route change per destination, so keep the sender as a parameter in your template layer. Start with a test route on the destination you choose, set up after we review your request. Dedicated number ranges can be reserved for your traffic, and where a market requires sender registration we coordinate it, with the brand proof coming from you. A delivery report says the network accepted a message, not what the handset showed; if your current provider reports delivered but users get nothing, check app and template causes first with the content pre-check, the SMS segment counter and the SMPP and DLR code decoder.
Who signs an A2P SMS contract, and what do you check before activation?
A contracting company signs the messaging agreement, and your quote names which one; our entities lists our local contracting companies. We serve businesses only, and before activation we verify the company and its use case and review your sample content. Depending on your country, products and use case, we may ask for supporting documents; your quote lists what applies. Our sales, onboarding and support teams work in English; we do not run a Spanish or Portuguese support desk. Where a local company holds your contract, it can support you locally.
Do you offer an A2P SMS API?
We connect over SMPP 3.4 or HTTP JSON; the onboarding pack documents the endpoints.
Apps going global
If your app is expanding from China to other markets, see A2P SMS for apps going global and the A2P learning path.
Tell us your destinations and volumes
Our team replies with next steps or a quote.