Enterprise SMS

A2P SMS for banks, retailers and messaging platforms.

Transactional, OTP and marketing messages to 200+ countries. Sender ID registration and route setup are part of onboarding.

From €0.003/msg (India). Connect over REST API or SMPP 3.4. Rates depend on destination, route type and volume.

Built for

Who sends A2P traffic with us

Businesses that send application-to-person messages from their own systems. See enterprise messaging for industry detail.

Banks and fintech

Transaction alerts, one-time passwords and account notifications sent from a registered sender ID.

E-commerce and logistics

Order confirmations, delivery updates and appointment reminders triggered from your own systems.

Messaging platforms

CPaaS providers and aggregators that need additional A2P routes over SMPP.

Architecture

Messaging architecture: REST or SMPP in, delivery reports back

Two ways to submit traffic, one routing layer, and delivery reports for both.

A2P SMS architecture Submit messages over REST (JSON over HTTPS) or bind over SMPP 3.4. Each message returns a message ID and is routed per destination and message type with your registered sender ID, with rate limits and geo-restrictions on by default. Operators deliver to the handset; delivery reports come back to your webhook for REST traffic, or as deliver_sm PDUs on your SMPP bind. Submit over REST or SMPP 3.4 · routed per destination and message type · delivery reports for every message Your stack OmaxTelecom send → message ID SMPP 3.4 A2P routes delivery delivery reports Your application REST · JSON over HTTPS SMPP client SMPP 3.4 bind Webhook endpoint HTTPS REST API single & bulk sends SMPP gateway submit_sm · deliver_sm Routing & sender IDs per destination & type Fraud controls rate limits & geo-restrictions Mobile operators destination networks Recipient handset message delivered Sender ID registration is required in many countries; we handle registration as part of onboarding.SMPP bind credentials and throughput are agreed during onboarding. SMPP binds receive delivery reports as deliver_sm PDUs.
Reading the diagram Submit messages over REST (JSON over HTTPS) or bind over SMPP 3.4. Each message returns a message ID and is routed per destination and message type with your registered sender ID, with rate limits and geo-restrictions on by default. Operators deliver to the handset; delivery reports come back to your webhook for REST traffic, or as deliver_sm PDUs on your SMPP bind.

Technical details

Connection options: REST API · SMPP 3.4

SMPP connection details: smpp.omaxtelecom.com. API reference: developer documentation.

$ curl -X POST https://api.omaxtelecom.com/sms/v1/send \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "to": "+447700900000", "from": "YourBrand", "message": "Your order 10482 has shipped.", "type": "transactional" }' // Response{ "status": "sent", "message_id": "msg_abc123"}
REST API
JSON over HTTPS. Single and bulk sends, delivery reports by webhook.
SMPP
SMPP 3.4 bind to smpp.omaxtelecom.com. Bind credentials and throughput are agreed during onboarding.
Sender IDs
Alphanumeric (up to 11 characters) or numeric, depending on the destination.
Message types
Transactional, OTP and promotional. Each type is routed and priced separately.
Fraud controls
Rate limits and geo-restrictions are on by default. Traffic is monitored for artificially inflated traffic (SMS pumping).
Two-way messaging
Inbound replies on UK, Australian or Brazilian mobile numbers or SMS-enabled DIDs.

Sender ID registration is required in many countries; we handle registration as part of onboarding.

Prices

SMS rates by country

Per message, in EUR. Ask for the countries you send to and we will quote the full list.

Country Promotional Transactional
United Kingdom €0.035 €0.040
United States €0.008 €0.010
Germany €0.065 €0.075
France €0.055 €0.065
Spain €0.045 €0.055
Italy €0.050 €0.060
Netherlands €0.060 €0.070
Turkey €0.015 €0.020
India €0.003 €0.005
Brazil €0.012 €0.018

Indicative. Final rates depend on origin, volume and route type.

Onboarding

From first contact to production traffic

Production access is granted after KYC and sender ID registration.

  1. Step 01: KYC and agreement

    Company verification and signed agreement, including our Acceptable Use Policy.

  2. Step 02: Traffic profile

    Destination countries, expected volumes, message types and the sender IDs you plan to use.

  3. Step 03: Sender ID registration

    Registration in countries that require it. We handle this as part of onboarding.

  4. Step 04: Integration and test

    Connect over REST API or SMPP 3.4 and send test traffic to your own handsets.

  5. Step 05: Go live

    Production traffic with agreed throughput, rate limits and destination permissions.

FAQ

Technical questions

REST API (JSON over HTTPS) and SMPP 3.4. SMPP binds are issued during onboarding; connection details are at smpp.omaxtelecom.com.

Sender ID registration is required in many countries; we handle registration as part of onboarding. Lead times vary by country, so share your destination list early.

Each message returns a message ID. Delivery reports (DLRs) are sent to your webhook for REST traffic and as deliver_sm PDUs for SMPP binds.

Rate limits and geo-restrictions are applied by default and traffic is monitored for artificially inflated traffic. Additional destinations are opened on request after review.

Yes, when you send from a mobile number or an SMS-enabled DID. Alphanumeric sender IDs are one-way.

Many operators price and filter the two traffic types differently. Sending promotional content on a transactional route can lead to blocking, so each type is routed separately.

Ready to send A2P traffic with OmaxTelecom?

Tell us about your traffic and we'll come back within one business day with pricing and onboarding steps.

  • Business accounts only
  • KYC required before production
  • Prepaid wallet