Payment confirmations
Instant receipt after mobile money or card payment. Include amount, reference, and support contact.

Transactional SMS
Receipts, alerts, and account notices should arrive fast and show your brand. Taysend routes transactional SMS to MTN, Telecel, and AT with prepaid GHS billing, approved sender IDs, and a delivery report on every message id.
Patterns
Instant receipt after mobile money or card payment. Include amount, reference, and support contact.
Dispatch notices, rider assigned, and delivered confirmations for e-commerce and logistics.
Clinic, salon, and service bookings — sent hours before the slot with a named sender ID.
Balance changes, login from new device, or password reset notices (pair with OTP where needed).
Meter readings, bill ready, and payment-due reminders for estates and service providers.
Transfer status and limit warnings. Use type: transactional and keep copy factual.
Integration
Send from your backend with POST https://api.taysend.com/v1/messages — include Authorization: Bearer sms_live_..., an Idempotency-Key, and type: "transactional". The dashboard composer uses the same pipeline for manual sends. For login codes, use OTP endpoints instead.
Explore
Each page answers a different question. They are not copies of this one.
FAQ
If something here is product behaviour, it matches the dashboard and the API.
Transactional messages relate to an action the recipient already took or expects — a purchase, booking, or account event. Marketing promotes products. Set type: "transactional" in POST /v1/messages.
Yes. POST /v1/messages handles single sends with to or bulk with recipients. Transactional traffic typically sends one message per event rather than a large campaign list.
HTTP 200 on send means accepted. Poll GET /v1/messages/:id or subscribe to webhooks for DELIVERED, FAILED, EXPIRED, or REJECTED states.
GHS 0.04 per billed unit unless a contract rate applies. Encoding and message length determine segment count.
Developers