SMS Gateway vs SMPP, Pricing & Delivery Reports Explained
Choose the right SMS connection, estimate costs accurately, and interpret delivery statuses — gateway vs SMPP, pricing models, and DLR fields.
Short answer: An SMS gateway gives you a REST API — send SMS with one HTTP POST. SMPP is a raw telco protocol for direct SMSC connections. Most apps and businesses should use a gateway; SMPP is for carriers and extreme volume. Pricing is per segment; delivery reports track queued → sent → delivered/failed.
SMS Gateway vs SMPP
Both deliver SMS to mobile networks, but they sit at very different layers of the stack.
| Feature | REST SMS Gateway | SMPP |
|---|---|---|
| Protocol | HTTPS / JSON REST API | Binary TCP (SMPP v3.4/v5) |
| Integration time | Minutes to hours | Days to weeks |
| Best for | Apps, SaaS, e-commerce, OTP | Telcos, aggregators, 1M+ msg/day |
| Authentication | API key in request body | System ID, password, bind types |
| Delivery reports | Dashboard + API logs | receipt PDUs you must parse |
| Infrastructure | Provider handles routing & retries | You manage connections & failover |
SMS Provider is a REST SMS gateway. You POST to https://api.smsprovider.net/api/send-sms and we handle operator routing, retries, and delivery tracking — no SMPP bind configuration required.
Which Should You Choose?
Choose REST gateway if…
- You build web/mobile apps or SaaS products
- You send OTP, alerts, or bulk SMS under ~500K/day
- You want pay-as-you-go with no infra overhead
- Your team knows HTTP, not telco protocols
Consider SMPP if…
- You operate as an SMS aggregator or MVNO
- You need sub-second bind-level control
- You already run 24/7 NOC for telco connections
- Volume justifies dedicated SMPP infrastructure
SMS API Pricing Guide
SMS Provider uses pay-as-you-go pricing in Bangladesh Taka (BDT). No monthly subscription — you top up balance and pay per message segment at the rate tied to your sender ID.
Non-Masking SMS
BDT 0.40 / per SMS
Standard SMS without a custom sender name. Great for OTPs and alerts.
Masking SMS
BDT 0.80 / per SMS
Send SMS with your brand name as the sender ID. Ideal for marketing.
What affects your bill
- Sender ID type — masking (brand name) and non-masking (numeric) have different rates.
- Message length — long messages split into multiple segments; each segment is billed separately.
- Non-masking prefix — non-masking SMS prepends
[SenderID]to the billable text, which counts toward segment length. - Segment size — SMS Provider uses 150 characters per segment (same rule for English and Unicode).
- Failed messages — after gateway retries fail, charges are refunded automatically.
Check live rates on your Sender IDs dashboard page — rates are assigned per sender ID when approved.
Understanding Message Segments
One SMS segment is not always one message. The API accepts up to 1000 characters, but billing uses150 characters per segment — matching the rate shown in your dashboard and API docs.
| Route | Billable text | Segment rule |
|---|---|---|
| Masking | Your message as written | ceil(length ÷ 150) segments |
| Non-masking | [SenderID] your message | ceil(length ÷ 150) segments |
Example: A 160-character OTP on a non-masking route with a 12-character sender ID becomes 172 billable characters → 2 segments → 2× your per-SMS rate. Keep OTP messages short.
SMS Delivery Reports Explained
When you send SMS via API, the immediate response includes a message_id and initialstatus: "queued". Delivery reports (DLRs) update as the message moves through the network.
Lifecycle
- queued — API accepted the message; balance deducted; waiting to dispatch.
- sent — Message handed to the mobile operator or downstream gateway.
- delivered — Operator confirmed delivery to the handset (terminal success).
- failed — Delivery failed after retries; charge refunded; reason logged (terminal failure).
View all reports in Dashboard → SMS Logs. Filter by status, date, or phone number for reconciliation and support tickets.
Status Meanings & Troubleshooting
| Status | Meaning | Action |
|---|---|---|
| queued | Accepted, pending dispatch | Wait — usually resolves in seconds |
| sent | Submitted to operator | Monitor — delivery pending |
| delivered | Reached recipient device | None — success |
| failed | Could not deliver | Check phone validity; retry if appropriate |
Common failure causes: invalid or switched-off number, DND restrictions, operator timeout, or incorrect sender ID. Store message_id in your application logs to correlate API sends with dashboard reports.
Frequently asked questions
What is the difference between SMS gateway and SMPP?
An SMS gateway exposes a simple REST or HTTP API — one POST sends a message. SMPP is a low-level binary protocol (TCP) connecting directly to an SMSC. Gateways are easier to integrate; SMPP suits telcos and very high-volume senders with dedicated infrastructure.
Do I need SMPP to send SMS in Bangladesh?
No. Most businesses use a REST SMS API through an SMS gateway provider. SMPP is only necessary when you operate at carrier scale or need custom SMPP bindings — otherwise a gateway saves weeks of integration work.
How is SMS API pricing calculated?
Pricing is per message segment at the rate assigned to your sender ID. SMS Provider counts 150 characters per segment (including the [SenderID] prefix on non-masking routes). Longer messages split into multiple billable segments. You pay only for sent segments — no monthly fee on pay-as-you-go plans.
What is an SMS delivery report (DLR)?
A delivery report confirms what happened to a message after the API accepted it. Statuses include queued, sent, delivered, and failed. The message_id returned by the API lets you match reports to individual sends in your SMS logs.
What does 'delivered' vs 'sent' mean?
Sent means the message left the gateway toward the mobile network. Delivered means the operator confirmed handoff to the recipient's handset (or final failure reason if not delivered). For billing reconciliation, delivered and failed are the terminal states that matter most.
Am I charged if an SMS fails?
With SMS Provider, balance is deducted when the message is queued. If delivery fails after all gateway retries, the cost is automatically refunded and the failure reason appears in your SMS logs.
Ready to integrate? Read the full API documentation, create a free account, or contact us on WhatsApp.