Wholesale SMS for aggregators & telcos
Buy SMS termination from WeZend over your own SMPP bind — multi-vendor routing with health-based failover, rates per destination country, prepaid or postpaid. Sales-assisted: you apply, we review the traffic, we issue the binds.
Everywhere else on this site, SMPP means bring-your-own-carrier: you attach your own SMSC and WeZend dispatches through it. This page is the arrow pointing the other way. You are the aggregator, reseller or operator; you bind to our SMPP server as a client, submit_sm, and buy SMS termination from us.
It is sales-assisted by design — nobody provisions a bind from a signup form. You apply, we look at the traffic profile (destinations, volume, content type), agree rates and prepaid or postpaid terms, and then issue a system_id and password pair. That is an application with a review, not a closed club: talk to us and you get an answer either way.
Why it works
You bind to us, not the other way round
Your ESME binds to our SMPP server with a system_id and password — transceiver, transmitter or receiver, enquire_link for keepalive, and a message_id back on every submit_sm_resp. Same pipe as bring-your-own-carrier, opposite direction.
Routing that scores delivery, not acceptance
Your traffic resolves to a vendor per destination country with a named fallback. A route that accepts everything and delivers nothing gets scored down from its own delivery receipts and skipped before you notice — accepted is not delivered, and only one of the two is worth paying for. Per-vendor rate limiting keeps a burst from tripping an upstream throttle.
Rates per destination country
Rates are set per channel and destination country on your account, and the country comes from parsing the E.164 MSISDN rather than a hand-maintained prefix list — so a Guernsey number is not billed as UK. Prepaid or postpaid is agreed up front, not discovered later.
A portal with three numbers on it
Balance (or current usage, if you are postpaid), SMS sent, delivered and failed for today and this month, the last 20 messages with status — plus the host and port to bind to. No campaigns, no journeys, no contact database, no AI. A wholesale account is not a marketing seat, and a menu of things you would never click is not a feature. There is a Broadcast tab if you ever need to paste a batch of numbers and fire a one-off without touching the bind.
Sender IDs pass straight through
The source_addr on your submit_sm goes out as submitted — no sender-approval queue between you and the SMSC, because on a wholesale route the sender belongs to your customer, not to us. The flip side is that the compliance for it in each destination market is yours too.
Features behind it
Frequently asked questions
Can I sign up for this online?
No — and the start-free buttons elsewhere on this site are for the marketing and CPaaS platform, not for a bind. A wholesale connection is provisioned by hand: you get in touch, we review the traffic profile and agree commercial terms, then an administrator issues your SMPP credentials. It is an application with a review, not an invite-only list.
How do the SMPP credentials work?
Your system_id is a key issued specifically for the bind, and the SMPP password is a separate secret. Both are hashed at rest and shown exactly once, at issue — there is no recovering them later, so rotation means a fresh pair. Test and live credentials are separate, so you can validate your ESME against a test bind before pointing production traffic at us.
Do you relay DLRs back over the bind?
Not today. submit_sm_resp returns our message_id immediately, and per-message delivery state is resolved from the upstream carrier's delivery receipt and shown in the portal — the delivered and failed counters plus the recent-message list. If deliver_sm relay into your own platform is a hard requirement, raise it when you get in touch; it is a routing conversation, not a checkbox.
What happens if a prepaid balance runs out mid-burst?
Submissions past a zero balance stop being dispatched and are recorded as failed with an explicit insufficient-balance reason, visible in the portal's failed counter — the stop-gate sits at the send chokepoint the bind goes through, not in an HTTP layer SMPP skips. Postpaid partners are exempt from the balance floor and invoiced monthly instead.
One platform. Every customer interaction.
Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.
Provisioned by hand after a commercial review · EU data residency