SMPP connectivity for high-volume business SMS
Connect your SMS platform, aggregator software or core banking system to VASbay over SMPP 3.4. Keep a persistent bind, push high volumes at your agreed throughput and receive delivery receipts in real time – on DLT-compliant transactional, OTP and promotional routes.
- SMPP v3.4 standard
- Transceiver, transmitter & receiver binds
- Per-account TPS control
- IP whitelisting
- DLT TLV parameters
- Real-time delivery receipts
# your SMPP account host shared securely on activation port shared securely on activation system_id ACME_OTP password •••••••• bind transceiver version 3.4 throughput as agreed (TPS) # submit_sm source_addr TXAAVY dest_addr 9198950XXXXX registered_delivery 1 TLV 0x1400 DLT entity ID TLV 0x1401 DLT template ID
Why businesses choose SMPP
SMPP (Short Message Peer-to-Peer) is the protocol operators and SMS gateways use between each other. One open connection carries thousands of messages without the overhead of a new HTTP request each time.
Built for volume
A persistent bind with windowed submits sends large campaigns and OTP bursts at the throughput agreed for your account.
Real-time receipts
Delivery receipts arrive on the same bind as deliver_sm, so your platform updates message status the moment the operator reports it.
Works with your software
Any SMPP 3.4 client connects: Kannel, Jasmin, jSMPP, OpenSMPP, Cloudhopper, smpplib, aggregator panels and banking middleware.
DLT ready
Send the DLT entity, template and telemarketer IDs in standard TLV parameters, or let VASbay match your approved templates automatically.
Priority queues
OTP and alert accounts are queued ahead of bulk traffic, so one-time passwords are not held back by a large campaign.
Secure by default
Every account is locked to your server IPs, limited to a set number of binds and throttled to its TPS. Passwords are stored hashed.
Technical specifications
What the VASbay SMPP service supports.
| Feature | Details |
|---|---|
| Protocol | SMPP v3.4 over TCP |
| Bind types | Transceiver (recommended), transmitter and receiver; several simultaneous binds per account |
| Throughput | Set per account (TPS); submits above it are answered with ESME_RTHROTTLED so your client can slow down |
| Operations | submit_sm, deliver_sm (receipts), query_sm, enquire_link, unbind |
| Encodings | GSM 7-bit / ASCII / Latin-1 text and UCS-2 for Unicode (Hindi, Tamil, Malayalam, Kannada and other Indian languages); flash SMS |
| Long messages | Concatenated SMS with 8-bit or 16-bit UDH reference, or message_payload |
| DLT parameters | Entity ID, template ID and telemarketer ID as TLV optional parameters |
| Delivery receipts | Standard receipt text (id: sub: dlvrd: submit date: done date: stat: err:) with receipted_message_id and message_state |
| Routes | Transactional, OTP, promotional and international – one SMPP account per route |
| Security | IP whitelisting, bind limits, per-account credentials, idle-connection timeout |
| Reporting | Every SMPP message also appears in your VASbay delivery reports and credit usage |
Go live in four steps
Register on DLT
Your entity, sender IDs (headers) and content templates, approved on your operator's DLT portal.
Request your SMPP account
Tell us your routes, expected TPS and the public IPs of your SMPP client.
Receive credentials
We share the host, port, system ID and password securely – one account per route.
Bind and send
Connect your client, send a test message and watch its receipt arrive. Then scale up.
SMPP or HTTP API?
Both send on the same DLT-compliant routes with the same reports. Choose by how your system works.
| SMPP | HTTP SMS API | |
|---|---|---|
| Best for | SMS platforms, aggregators, banks and telecom software sending steady high volumes | Websites, apps, CRM and ERP sending on events |
| Connection | One persistent TCP bind | One HTTPS request per send |
| Delivery status | Pushed to you as receipts on the bind | Fetched with the status API or callback |
| Integration effort | An SMPP client library or gateway | A few lines of code in any language |
Who uses SMPP connectivity
Banks & fintech
Transaction alerts and OTPs straight from core banking and payment switches.
SMS aggregators
Resell VASbay routes inside your own SMS platform.
E-commerce
Order, payment and delivery updates at peak-sale volumes.
SaaS & CPaaS
Messaging inside your product, with receipts fed back to your users.
Frequently asked questions
submit_sm, deliver_sm receipts, query_sm and enquire_link.submit_sm (tags are given in the SMPP documentation). If they are missing, VASbay matches the message to the approved templates of your account.data_coding 8 (UCS-2) for Unicode, and UDH concatenation or message_payload for long messages. Each part gets its own message ID and receipt.ESME_RTHROTTLED. Your SMPP client should pause briefly and retry; most clients do this automatically.Ready to send your first message?
Create a free VASbay account, register your DLT details and start sending in minutes. Our team helps you with sender IDs and templates.