---
title: "A2P SMS Wholesale: How to Choose a Provider and Test Routes"
description: "A2P SMS wholesale explained: who buys it, how SMPP binds work, what DLR and latency tell you about a route, and the KYC and fraud controls to demand."
canonical: "https://omnichannels.ai/blog/a2p-sms-wholesale-provider-guide/"
language: "en"
updated: "2026-10-16"
publisher: "BroadNet Technologies"
brand: "OmniChannels.ai"
category: "sms"
primaryQuery: "a2p sms wholesale"
keywords: ["wholesale sms provider", "a2p sms wholesale", "sms termination", "smpp bind", "sms routes quality", "sms aggregator selection", "wholesale sms kyc", "sms dlr rate"]
published: "2026-10-16"
author: "OmniChannels.ai Editorial Team"
reviewer: "BroadNet Messaging Solutions Team"
readingMinutes: 9
answer: "A2P SMS wholesale is the sale of SMS termination capacity, per destination and usually over SMPP, to aggregators, platforms and large senders who then deliver to end clients. Choose a wholesale provider on route quality you can measure (delivery receipts, latency, sender ID preservation), the KYC and anti-fraud controls it enforces on its own traffic, transparent per-route reporting, and settlement against records both sides can check."
takeaways: ["Wholesale buyers include CPaaS platforms, aggregators, resellers, banks and large enterprises; each wants per-destination rates and a technical interconnect.", "The SMPP bind is the contract in code: bind type, window size, throttling and delivery receipt handling decide how well traffic flows.", "Judge routes by delivery receipt rate, latency distribution and sender ID preservation, measured on your own test traffic per destination.", "A good wholesaler runs KYC on upstream clients, filters content and watches for pumping fraud, because one abusive customer damages routes for all.", "Run a staged evaluation: paper checks, a sandbox test per destination, a limited live ramp, then a settlement reconciliation."]
faq: 
  - q: "What is wholesale A2P SMS?"
    a: "It is the supply of application-to-person SMS termination capacity to businesses that resell or embed it, rather than to message senders directly. The buyer connects over SMPP or an HTTP API, sends traffic to many destinations and pays per message according to a destination rate card. The provider handles the operator or downstream routes."
  - q: "Who buys wholesale SMS?"
    a: "Typical buyers are CPaaS and messaging platforms, aggregators serving smaller resellers, white-label resellers with enough volume to bind directly, and large enterprises such as banks or marketplaces with their own sending infrastructure. Operators also buy, sell and swap A2P capacity through hubs for destinations they do not reach directly."
  - q: "What is an SMPP bind?"
    a: "A bind is the authenticated SMPP session between your system and the provider's SMSC. The SMPP 3.4 specification defines transmitter, receiver and transceiver bind types. The bind carries your messages in submit_sm PDUs and returns delivery receipts. Credentials, IP allow-lists, window size and throttling limits are agreed per account."
  - q: "How do I measure the quality of an SMS route?"
    a: "Send controlled test traffic to numbers you control on each target operator and compare results over time. Track the share of messages that reach a final delivered state, the time from submission to receipt, whether the sender ID arrives intact, and how many receipts stay pending. Repeat tests at different hours, since quality can vary through the day."
  - q: "Why do wholesale providers ask for KYC?"
    a: "Operators hold the provider responsible for the traffic it sends. If a client sends phishing, spam or fraud, routes and sender IDs can be blocked for everyone. KYC, content rules and fraud monitoring let a wholesaler identify who sent what and suspend a client quickly."
  - q: "Is the cheapest wholesale SMS rate the best?"
    a: "Rarely. A very low rate on a destination often indicates a grey or SIM-based route, which operators filter and which can return false delivery receipts. Compare the cost of a delivered, correctly attributed message, not the cost of a submitted one."
sources: 
  - title: "SMPP Protocol Specification v3.4 (Issue 1.2) — SMPP Developers Forum"
    url: "https://smpp.org/SMPP_v3_4_Issue1_2.pdf"
  - title: "Resource Hijacking: SMS Pumping (T1496.003) — MITRE ATT&CK"
    url: "https://attack.mitre.org/techniques/T1496/003/"
  - title: "Secure networks: the key to A2P monetisation — GSMA-hosted whitepaper (2015)"
    url: "https://www.gsma.com/get-involved/gsma-membership/wp-content/uploads/2015/10/2015-10-whitepaper-secure-networks-key-to-a2p-monetisation.pdf"
---

# A2P SMS Wholesale: How to Choose a Provider and Test Routes

Canonical: https://omnichannels.ai/blog/a2p-sms-wholesale-provider-guide/
Language: en
Publisher: OmniChannels.ai by BroadNet Technologies

This guide is for carriers, aggregators, CPaaS teams and large senders who are buying or evaluating wholesale A2P SMS. It explains what you are actually buying, how to read the technical interconnect, which numbers reveal route quality and which controls a serious supplier should apply to its own traffic.

## What is wholesale A2P SMS, and who buys it?

Wholesale A2P SMS is the sale of SMS termination capacity in bulk, priced per destination, to companies that deliver messages for others. The message still ends up on a handset through an operator network, but the buyer is a platform, aggregator or reseller, not the business that wrote the message.

Typical buyers:

- **CPaaS and messaging platforms** that expose an API to developers.
- **Aggregators** that serve smaller resellers and want better coverage than they can negotiate alone.
- **Resellers** whose volume justifies a direct bind rather than a web console.
- **Enterprises** (banks, marketplaces, super-apps) with their own sending infrastructure and SMPP-capable systems.
- **Operators** that hand off international A2P traffic to a hub instead of keeping bilateral agreements with every network.

If you are earlier on that path, our guide to [starting an SMS reseller business](/blog/start-sms-reseller-business/) covers the retail side. If you need background first, read [what is A2P SMS](/blog/what-is-a2p-sms/).

## How does a wholesale SMS interconnect work?

Your platform opens an authenticated SMPP session to the provider, submits messages, and receives delivery receipts on the same session. The SMPP 3.4 specification defines three bind types: transmitter (send only), receiver (receive only) and transceiver (both on one connection).

The settings that matter in practice:

| Setting | What it controls | What to agree |
|---|---|---|
| Bind type | Whether sending and receipts share one session | Transceiver for simplicity; separate binds for isolation at high volume |
| Window size | How many unacknowledged submissions may be in flight | A value both sides can sustain without timeouts |
| Throttling | Provider's response when you exceed the allowed rate | The ESME_RTHROTTLED (0x00000058) error means you sent faster than allowed; your client must back off and retry |
| Enquire_link interval | Keep-alive that detects dead connections | A fixed interval and a reconnect policy |
| Registered delivery | Whether the provider returns receipts | Always on, so you can bill and troubleshoot |
| Encryption and access | TLS and IP allow-listing | TLS and a named source IP list |
| Source address handling | TON/NPI and sender ID format | How alphanumeric and numeric senders are submitted |

Binds are provisioned per account, so ask who configures them and how quickly changes are made. Our [SMPP gateway](/channels/sms/smpp-gateway/) page describes the options and the [SMPP developer guide](/developers/smpp/) covers connection details. For when HTTP is the better choice, see [SMS API vs SMPP](/blog/sms-api-vs-smpp/).

## How do you measure route quality?

Measure what happens to your own test traffic, destination by destination. Rate cards say nothing about quality. Four measurements matter.

### Delivery receipt rate

The SMPP specification defines delivery receipt states such as DELIVRD, EXPIRED, DELETED, UNDELIV, ACCEPTD, UNKNOWN and REJECTD. Count the share of messages that reach DELIVRD against those that end in the failure states, and also the share that never receive a final receipt. A high pending share is a warning, since some routes never return one.

A delivery receipt is only as honest as the route. Receipts that look perfect for numbers that are switched off point to false receipts, a classic symptom of a [grey route](/blog/grey-route-vs-direct-route-sms/). Use controlled test handsets to check that receipts match reality.

### Latency

Compare the time from submission to final receipt, and look at the slow tail (the slowest 5 percent of messages), not only the average. OTPs fail on the tail: a code that arrives after two minutes is a lost login.

### Sender ID preservation

Send with an alphanumeric sender ID and see what arrives. A route that replaces your sender ID with a random number is a quality failure for any brand that depends on recognition.

### Consistency

Repeat the test across hours and days. Routes that perform at 10:00 and degrade at peak hours cost you in production. Our explainer on [message delivery status](/blog/message-delivery-status-explained/) and the delivery report decoder help you read the receipts.

## What KYC and fraud controls should a good wholesaler apply?

A good wholesaler controls who sends, what they send and where it goes, because operators hold the wholesaler responsible for all of it. Ask for specifics in these areas.

1. **Customer KYC.** Company registration, beneficial owner, business address, expected volumes and destinations, and use case. Without it, nobody can say who sent a phishing campaign.
2. **Content and sender ID rules.** Blocked content categories, sender ID registration where a country requires it, and a process for template or content approval on strict routes.
3. **Traffic monitoring.** Alerts on sudden volume spikes, new destinations, unusual conversion and prefix concentration. These are the signs of SMS pumping, which MITRE ATT&CK catalogues as technique T1496.003.
4. **Destination controls.** The ability to restrict or throttle destinations per account, so a compromised client cannot send to expensive ranges.
5. **SMS firewall compatibility.** Operators increasingly filter A2P traffic through firewalls; traffic with an agreement is visible and monetised, while traffic without one is not. The GSMA-hosted whitepaper on A2P monetisation makes this argument about operator visibility.
6. **Fast suspension.** A named contact and a documented time to block an account or destination when abuse is detected.

These controls also protect you. If your supplier does not police its other customers, the routes you share with them degrade.

## What should you ask in the commercial and reporting terms?

Ask about the following before signing:

- **Rate card structure:** per destination (and, where relevant, per operator), currency, validity and how changes are notified.
- **Billing basis:** whether you pay for submitted, accepted or delivered messages, and how failed or expired messages are treated.
- **Reporting:** per-route and per-destination quality, delivery outcomes and cost, available through a portal, an API or exports.
- **Settlement:** records both sides can reconcile (per-message CDRs), a clear dispute window and invoice currency.
- **Support:** a 24-hour NOC contact, an escalation path and who handles operator-side investigations.
- **Exit terms:** notice period and how prepaid balances are returned.

We do not print rates in articles. Wholesale rates are quoted per destination and tiered by committed volume, so request a quote against your real traffic mix.

## How should you evaluate a wholesale provider, step by step?

Use a staged evaluation so that nothing reaches production traffic before you have data.

1. **Paper check.** Licences where the provider operates, company details, references you can contact, operator coverage by destination, fraud policy.
2. **Technical onboarding.** Receive bind credentials, connect from your staging system, send a handful of messages and confirm receipts, encodings and sender ID handling.
3. **Destination test.** For each priority destination, send to test numbers on each operator at different hours. Record delivery, latency and sender ID results.
4. **Failure tests.** Exceed the throttle on purpose, drop the connection, submit invalid numbers. See whether error codes are correct and the provider reacts sensibly.
5. **Limited live ramp.** Move a small share of real traffic, with a hard daily cap, and compare against your current supplier.
6. **Reconciliation.** After a billing period, compare your submitted, delivered and billed counts. Differences should be explainable line by line.

## Worked example: a CPaaS adds Gulf and Africa coverage

"Nimbus Platform" (synthetic) sells an SMS API to developers and wants direct coverage for the Gulf and East Africa. It shortlists two wholesalers. On paper both look similar, so it runs the staged test. Provider A delivers nearly every test message with sender IDs intact, but its tail latency grows in the evening. Provider B is cheaper on one destination, but many of its receipts never arrive, and sender IDs are replaced by numbers.

Nimbus uses A for OTP traffic, adds a cap, and keeps B out of production. The cheaper rate was not cheaper once undelivered OTPs were counted.

## What are the common mistakes when buying wholesale SMS?

- **Buying on price per submitted message** instead of cost per delivered message.
- **Skipping destination-level tests** because the provider shows a global success figure.
- **Ignoring the tail latency** of OTP traffic.
- **Accepting receipts at face value.** A receipt reports what the route said, not necessarily what the handset saw.
- **No fraud limits on your own side,** so a client of yours can run up charges at your expense.
- **No exit plan.** Keep a second supplier tested on your top destinations.

## How OmniChannels.ai helps

BroadNet Technologies has direct connections to more than 1,000 operators and aggregators and offers wholesale interconnect over SMPP 3.4 with TLS or an HTTP API. You receive delivery receipts on every message, per-route quality reporting and settlement against per-message CDRs, and traffic passes through firewall-protected routes. Binds are provisioned per partner. See the wholesale programme and [contact our team](/contact/) with your destination list for a quote.