A2P SMS — PINHAN GROUP

What our customers send

Three traffic types, each with a different failure cost. We route them separately because treating them alike is how a bank's login codes end up queued behind a retail campaign.

TIME CRITICAL

One-time passwords

Login codes, payment confirmations and identity checks. Routed on dedicated OTP paths with the shortest hop count we can buy, and measured on median latency rather than average.

TRANSACTIONAL

Alerts and notifications

Shipment updates, appointment reminders, fraud warnings and balance alerts. Sent with registered sender IDs so the recipient sees your name, not a shortcode they do not recognise.

PROMOTIONAL

Campaigns

Bulk sends with local opt-out handling and quiet-hours rules applied per market, so a campaign that is legal in one country is not sent unchanged into one where it is not.

How a message actually travels

Most delivery problems are routing problems wearing a different name. This is the path your traffic takes with us, and the point at which each thing can go wrong.

What we will not do

Rewrite your sender ID to make a cheaper route accept the traffic.
Return a delivered receipt the operator never issued.
Move OTP traffic onto a grey route when a direct one gets congested.

Submission

You connect over SMPP with a bound session, or POST to the HTTP API. Both accept concatenated and Unicode messages, and both return our message ID immediately.

Route selection

Destination and traffic class decide the route, not price alone. OTP classes are pinned to direct paths; if the direct path is down the message queues rather than silently falling back.

Operator handover

The message is handed to the terminating operator on an interconnect we hold in our own name, which is what makes the sender ID and the receipt trustworthy.

Receipt

The delivery receipt comes back to you as the operator issued it, including the failure codes. Undelivered is reported as undelivered.

Deliverability by region

These are floors, not averages: the minimum we contract to and re-source below. Per-country figures come with the rate deck.

Region	Route type	Deliverability floor	OTP median latency	Sender ID
Western Europe	Direct to operator	99.0%	1.6 s	Alphanumeric, registered
North America	Short code and toll-free	98.6%	1.9 s	Campaign registered
Middle East	Direct to operator	97.1%	2.1 s	Alphanumeric, registered
Central Asia and Caucasus	Direct to operator	95.8%	2.4 s	Alphanumeric, registered
North Africa	Direct and aggregated	94.2%	2.8 s	Mixed by market
South and Southeast Asia	Direct and aggregated	93.5%	3.1 s	Registered, template rules apply

Connecting to us

SMPP 3.4

Transmitter, receiver or transceiver binds. Multiple sessions per account, concatenation and Unicode supported, delivery receipts returned on the same bind.

HTTP API

JSON over HTTPS for teams that do not want to hold an SMPP session open. Single and batch send, with receipts pushed to your callback URL.

Reporting

A dashboard showing submitted, delivered and failed by destination and by hour, plus a monthly reconciliation file you can check your own logs against.

Example submission

POST /v1/messages
Authorization: Bearer <key>

{
  "to":     "+447700900123",
  "from":   "ACME",
  "text":   "Your code is 481920",
  "class":  "otp",
  "dlr":    "https://acme.example/dlr"
}

201 Created
{ "id": "0f3a…", "status": "accepted" }

Full specification and test credentials are issued with your account. No sandbox signup wall.

Questions buyers ask first

Do you resell other aggregators?

For the destinations marked direct, no: the interconnect is ours. For destinations marked aggregated we buy from a named partner, and we will tell you which one before you send traffic there.

How long does sender ID registration take?

It depends entirely on the market, from same-day in most of Europe to several weeks where a local entity and template pre-approval are required. We give you the per-country timeline with the rate deck so it is planned rather than discovered.

What happens when a route degrades?

Monitoring compares live delivery against the floor for that destination. Below the floor, the route is withdrawn and traffic moves to the next qualified path. You are told what changed; you do not have to notice it from your own dashboard first.

What are the commercial terms?

Prepay to start, moving to weekly settlement or net terms once there is a payment history. Pricing is per destination and per traffic class; there is no minimum monthly commitment to open an account.

Send us a country list. We will send back a rate deck.

Destinations, monthly volume and traffic type are enough to price the work.

Request pricing

Messages that clear the filter