SMS integration checklist
Work through these lists before and during a messaging integration. They apply to any provider and help our team answer your request faster.
Educational guide. General information about messaging integrations. It does not describe a live Wise Network API, and examples are illustrative only.
Download this guide (PDF)Same content as this page, for offline reading and sharing.
1. Scope and business information
- Company name, registration details and the technical and commercial contacts.
- Traffic type: one-time passcodes, transactional notifications, alerts, or marketing where allowed.
- Destination countries and networks, and the expected monthly volume and peak rate.
- Sender IDs you plan to use, and whether registration is needed in each destination.
- How recipients gave consent, where consent is required.
2. Connection details to agree
| Item | SMPP | HTTP API |
|---|---|---|
| Address | Host name and port | Base URL |
| Credentials | System ID and password | Key, token or client credentials |
| Session or call settings | Bind type (transmitter, receiver or transceiver), number of binds, enquire_link interval | Request format (JSON or XML), timeouts |
| Limits | Messages per second and window size | Requests per second and batch size |
| Your public IP addresses | All addresses that will connect, including failover | All addresses that will call the API |
| Environments | Test and live connections | Test and live base URLs |
Exchange credentials only through an agreed secure channel, never in an ordinary email or chat message.
3. Security
- Credentials stored on servers only, in a secret store or protected configuration.
- A plan to rotate credentials and to revoke them quickly if they leak.
- Encrypted transport where the provider supports it (HTTPS; TLS or a VPN for SMPP).
- Your outbound public IP addresses documented. See IP access.
- Logs that record message IDs and errors without passwords, keys or full sensitive message text.
4. Message handling
- Destination numbers in international E.164 format.
- Encoding and length checked for each language you send. See SMS encoding.
- Long-message method agreed (user data header, message_payload or SAR fields).
- Validity period and, if used, scheduling with explicit time zones.
- Rules for duplicate prevention when your system retries.
5. Delivery reports and errors
- Delivery reports requested on every message you need to track.
- Receipts matched to your records by message ID, and late or duplicate receipts handled.
- The provider's list of statuses and error codes, and which errors to retry.
- For webhooks: an HTTPS address, signature verification and replay protection. See delivery reports.
6. Testing
- Agreed test numbers and test volume.
- Tests of each message type, language and sender ID.
- Tests of failure cases: wrong password, invalid number, throttling, disconnection.
- A record of test times, message IDs and results.
7. Go-live and operations
- Start with a limited volume and watch delivery rates and latency.
- Incident contacts on both sides, with hours and escalation steps.
- A process for changes: new IP addresses, new sender IDs, new destinations.
- Regular reconciliation of your records against the provider's statements.
Send us your request
When the scope is clear, request an SMS interconnection or email support@wisenetwork.co if you are already connected.
Related
Talk to our carrier team
Tell us which destinations, volumes or networks you are working with. A member of our team will reply by email.
- Email: sales@wisenetwork.co
- Phone: +961 3 085 999