SMPP v3.4
SMPP v3.4 bind
An SMPP v3.4 bind is the standard way to move A2P SMS at volume. Transmitter, receiver or transceiver, with real end-to-end delivery receipts.
Get test credentialsSMPP is the protocol A2P messaging is built on, and for sustained volume it remains the right choice: persistent sessions, low per-message overhead, and delivery receipts that come back on the same connection rather than through a webhook you have to keep available.
How binds are issued
You receive a system ID, a password and an IP allow-list entry. Most platforms open a transceiver bind; separate transmitter and receiver binds are supported where your architecture prefers them. Throughput per bind is agreed with your account engineer and can be raised as your traffic establishes a pattern.
Delivery receipts
Receipts are end-to-end, meaning they reflect handset delivery rather than acknowledging that we accepted the submission. This matters: a receipt that fires on submit will show you a delivery rate that has no relationship to whether anyone read the message.
- Bind types Transmitter, receiver, transceiver
- Encoding GSM 03.38, UCS-2, concatenated / long SMS
- Delivery receipts End-to-end DLR on the same session
- Authentication System ID, password and IP allow-list
- Throughput Per-bind TPS agreed with your account engineer
Get credentials
Credentials are issued with your test account, on the same routes production will use.