SMS gateway pricing explained: what you actually pay per message
What you actually pay per SMS message is the sum of three separate line items—per-message termination, optional monthly platform fees, and number rental—scaled by destination operator rates and by how many segments your content produces. Advertised floor rates omit those multipliers; an all-in rate should fold delivery attempt and DLR into one figure with no hidden carrier surcharge.
Three line items buyers routinely conflate
Gateway price pages often present a single per-message figure as if it were the whole bill. In practice the invoice has up to three independent components, and mixing them up is the most common source of budget surprises. The first is the per-message charge: the amount assessed each time the gateway submits a segment toward a destination handset. The second is the monthly platform fee, if any—an account, API, or dashboard charge that does not scale with traffic and may exist even in months you send nothing. The third is number rental: the recurring cost of a long-code, toll-free, or short-code identity used as the sender, billed whether or not messages flow through it.
These items are priced and contracted separately because they cover different costs in the chain. Termination is paid onward to destination networks. Platform fees cover the provider’s control plane (routing, logging, retries, dashboards). Number rental covers inventory and, where required, registration with operators or registries. A buyer comparing only the per-message cell on two price tables is not comparing total cost of ownership. Ask explicitly which of the three appear on the contract, which are optional, and which are waived at which volume tiers—without assuming a low message rate implies a low monthly bill.
Prepaid and postpaid change cash timing, not the line-item structure. On a prepaid wallet you fund termination in advance; platform and number charges may still debit the same balance or appear as separate renewals. On postpaid, all three may land on one invoice. Either way, model them as distinct rows in your unit-economics sheet so a change in sender strategy (for example, moving from a shared route to a rented number) does not silently rewrite your per-notification cost.
SMSRoute publishes its per-message rates openly - United States $0.0125 all-in and rates from $0.004 - which is what makes this arithmetic checkable rather than promotional.
Why the same message costs different amounts per destination
The gateway does not set the underlying cost of reaching a handset. Destination mobile network operators set termination fees for inbound application-to-person traffic, and those fees vary by country, by operator within a country, and sometimes by traffic class or sender registration status. The gateway’s published per-destination rate is therefore a pass-through plus margin on a fee the gateway itself pays or has contracted upstream. Two deliveries of identical payload length to two different E.164 country codes can legitimately price apart because the far-end operators price apart.
E.164 numbers are at most 15 digits; the country code embedded in the destination is what selects the rate card row. Gateways that publish per-country rates are exposing that mapping. Rates also move when operators renegotiate interconnect, when registration regimes change, or when a route is replaced. Treat any country figure as dated, not eternal: the honest operational practice is to read the rate from a country fact sheet that states when it was last updated, then re-check before a large campaign or a new market launch.
Because termination is destination-specific, blended or “from” rates are not predictive of your bill. A floor rate describes the cheapest row on the card, not the weighted average of the countries you actually dial. To forecast, build a simple model: message volume per country code, times segments per message, times the current all-in rate for that country. If the provider only publishes a floor, ask for the full card or for a quote filtered to your destination mix. Variance across destinations is a property of the public telephony market, not a hidden markup trick—though markup still sits on top of termination and should be visible in the all-in figure you are offered.
Multipart messages multiply cost: segments, not “messages”
SMS is not billed by user-visible notification; it is billed by protocol segment. A single notification that exceeds the character budget of one segment is split into concatenated parts, and each part is submitted and charged as its own message toward the destination rate. If you budget one unit per notification while your template routinely splits into three segments, your real spend is triple the spreadsheet line you thought you had.
Encoding decides the budget. GSM-7 (the default 7-bit alphabet for basic Latin text and common European characters) allows 160 characters in a single-segment message. When concatenation is required, each segment carries a UDH header that consumes space, so the per-segment user-data budget drops to 153 characters. UCS-2 is used when the text needs characters outside GSM-7 (many non-Latin scripts, most emoji). UCS-2 allows 70 characters in a single segment and 67 characters per segment once concatenated. Crossing the single-segment ceiling by one character doubles the segment count; crossing the next ceiling triples it.
Practical measurement beats rules of thumb. Before you ship a template, encode it the way the gateway will (GSM-7 if the full body fits that alphabet, otherwise UCS-2), apply the 160/153 or 70/67 limits, and count segments. Do this for every localization, not only the English master: a translation can flip encoding or length enough to add a segment. Also count what you inject at send time—OTP codes, URLs, names—because variable tails are what push borderline templates over the limit. On the price page, verify whether “one message” means one segment or one API call; providers differ, and that definition error becomes a pure multiplier on every row of your forecast.
The SMSRoute country fact sheets carry each market's published rate with a source and a retrieval date.
| Encoding | Single-segment limit | Concatenated per-segment limit | When it applies |
|---|---|---|---|
| GSM-7 | 160 characters | 153 characters | Body fits default 7-bit alphabet |
| UCS-2 | 70 characters | 67 characters | Any character outside GSM-7 |
Advertised floor rate versus all-in rate
An advertised floor rate is the lowest per-segment figure on the provider’s public card—often the cheapest country or a promotional lane. It is a marketing minimum, not a quote for your traffic. An all-in rate, used carefully, is the amount you will be debited per billable segment for a stated destination with the ordinary success path included: submission, downstream delivery attempt, and delivery report (DLR) handling, without a separate carrier surcharge line that appears only after traffic runs.
“All-in” is only meaningful if the contract enumerates what is inside. At minimum, expect: the termination component for that destination, gateway margin, and DLR processing with no per-DLR add-on. Clarify edge cases in writing: failed attempts after submit, retries, unreachable handsets, and whether inbound MO (if you use two-way) is priced differently. If sender-ID registration, throughput tiers, or number rental sit outside the segment rate, they are not all-in for total cost—they are simply outside the segment line. Honesty here is definitional, not promotional: a low floor plus surcharges can exceed a higher all-in that truly bundles the attempt path.
SMSRoute’s published commercial frame is a concrete illustration of how these pieces can be stated without collapsing them into one opaque number. Per-message rates start from $0.004; the United States is published at $0.0125 all-in; coverage is listed across 149 countries; the account is prepaid with a minimum top-up of $5. Per-country rates are published and dated on the country fact sheets rather than only summarized as a floor. Use that pattern as a readability test elsewhere: can you find the dated country figure, see whether it is labeled all-in, and tell which of the three line items are included before you send traffic?
Checklist to run against any provider’s price page
Before you integrate, walk the public price page and contract draft against a fixed checklist. The goal is not to negotiate in the abstract; it is to force every multiplier into the open so two providers become comparable in the same units: billable segments to your real destinations, plus fixed monthly and number costs.
Worked reading order: (1) Is the headline figure a floor or a destination rate? (2) Is that rate labeled all-in, and does all-in explicitly cover delivery attempt and DLR with no separate carrier surcharge? (3) Is a segment counted as one billable message, and are GSM-7 160/153 and UCS-2 70/67 documented? (4) Is there a monthly platform minimum or platform fee independent of traffic? (5) Are DLRs charged, free, or only available on higher tiers? (6) Is there a sender-ID, registration, or branding fee per country? (7) Is number rental required for your use case, and is it itemized? (8) Prepaid or postpaid, and what is the minimum fund or invoice commitment? (9) Are per-country rates published with dates (fact sheets), and how do you retrieve the current card via API or dashboard before a campaign? (10) What happens on handset failures—second billable segment on retry, or not?
If any answer is missing from the page, treat it as unknown cost, not as zero. Replace unknowns with written clarification before you load production traffic. Build your forecast only from destination-level all-in segment rates times measured segment counts, then add platform and rental as separate rows. That model is what you actually pay per message—mechanics first, sticker second.
SMSRoute's comparison matrix quotes every provider's own published page, dated.
| Check | Pass criterion | Fail signal |
|---|---|---|
| Rate type | Destination all-in stated | Only “from” floor shown |
| All-in scope | Attempt + DLR, no carrier surcharge line | Surcharges TBD after send |
| Segment definition | GSM-7 160/153, UCS-2 70/67 documented | “Message” undefined |
| Monthly minimum | Fee or “none” explicit | Silent platform charge |
| DLR pricing | Included or priced per event | Unmentioned |
| Sender / registration | Per-country fees listed or waived | Required later in onboarding |
| Number rental | Optional and itemized | Bundled without a line item |
| Country card | Published rates with dates | Blended rate only |
| Billing mode | Prepaid/postpaid + minimum stated | Top-up rules absent |
Frequently asked
- Why does the same SMS cost different amounts to different countries?
- Destination mobile operators set termination fees for inbound traffic; those fees vary by country and sometimes by operator. The gateway’s per-destination rate passes that cost through with margin. Identical payloads therefore price differently by E.164 country code. Use dated per-country fact sheets and your real destination mix—not the advertised floor—to forecast.
- How many characters fit in one SMS segment?
- GSM-7 allows 160 characters in a single segment and 153 per segment when concatenated. UCS-2 allows 70 single and 67 per concatenated segment. Each segment is typically one billable unit, so templates that cross a limit multiply cost. Encode the final localized body—including variables—before you estimate spend.
- What should an all-in SMS rate include?
- An all-in per-segment rate for a stated destination should cover the delivery attempt path and DLR handling with no separate carrier surcharge discovered after traffic runs. Platform fees, number rental, and sender-ID or registration charges may still sit outside that figure; they must be itemized so total cost remains calculable.