What the platform does not keep
Message content is not archived. What is kept is metadata — and among that metadata two fields are load-bearing, because without them a bill could not be reconciled.
Read the guide →Messaging for fintech and payments
In payments the message is often the product: a code that has to land before the session expires, an alert that proves a transaction happened, a reminder that keeps a subscription alive. Connect your own accounts, and the send path stops being the part you have to watch.
The messages you cannot afford to lose
These messages have hard deadlines. A code that arrives late is a failed login; a reminder that arrives twice looks like fraud. The platform therefore exposes pacing and per-number rate limits explicitly rather than hiding them behind a single auto-scaling counter.
- One-time passwords and step-up verification codes
- Transaction and balance alerts
- Payment-due and dunning reminders
- KYC and document-request follow-ups
- Subscription renewal and card-expiry notices
Throughput follows your numbers, not a hidden quota
Provider limits apply per sender number and per account, and a single application quota hides the constraint that actually blocks you. The console shows the limit that applies to each connected number, and pacing is applied at that granularity — so adding a second number genuinely doubles throughput instead of splitting the same allowance.
Regulatory duty stays with you
Regulatory obligations in financial services — record retention, disclosure wording, sector-specific rules — belong to you and to the provider carrying the traffic; they follow the duty, and the duty sits with you. On the SMS channel the platform’s part is the send path: routing, pacing, and a log that records what went out and what happened to it.
Questions this usually raises
- Can a duplicate code be prevented?
- Not by the platform. There is no idempotency key on the send API, so a retried request sends a second message. Duplicate prevention belongs in the caller — the guide on idempotency explains why and what to do instead.
- Are codes delivered on the fastest channel?
- You choose the channel by which provider account you send through. The platform does not silently switch channel for you; on SMS it can switch between your connected provider accounts when one stops accepting traffic.
- Does the platform store the content of the messages we send?
- No. The message log retains metadata only — time, destination, provider, sender identity, status and error code. Message bodies are not persisted, so content does not accumulate in a log you would later have to govern.
Keep reading
A timeout is not a failure
Sending is accepted asynchronously and there is no de-duplication key. Retrying a request you are unsure about sends a second message and bills for it.
Read the guide →E-commerce & retail
A storefront runs on the messages customers actually read: the confirmation, the dispatch note, the delivery window, the code after a failed payment. Send all of them over the SMS, email and WhatsApp accounts your store already pays for.
Open →Healthcare & clinics
Most clinic messaging is administrative, and a missed administrative message costs a wasted appointment slot. Send a confirmation at booking and a timed reminder before, on the number the patient gave you — and keep clinical detail out of it.
Open →Logistics & delivery
A delivery operation lives on contact attempts: the customer who is not home, the gate code nobody has, the parcel heading back to the depot. Each of those is a message that either saves a second trip or causes one.
Open →SaaS & online services
Your login codes, incident notices and renewal nudges sit on the critical path of someone else’s workday. Send them from your own service with a tenant API key, and read the outcome back through the same API.
Open →Education & training
Education messaging is about timing: a class that moved, a deadline that is close, an enrollment nobody confirmed. The failure mode is not a missing message — it is one that arrives after it mattered.
Open →Marketplaces & platforms
A marketplace messages two audiences about the same event for opposite reasons: the buyer wants it to arrive, the seller wants proof that it did. That makes the receipt the part worth getting right.
Open →Travel & hospitality
Travel messaging is shaped by the clock: a confirmation that has to arrive immediately, a reminder the evening before, a disruption notice that is worthless once the guest has left for the airport. Send each one from an account that is still accepting traffic.
Open →On-demand & field services
Field service messaging is measured in minutes: a technician twenty minutes away, a job that moved, a customer who will not be in. Send the ETA when the event happens and it saves a trip; send it late and it is worse than silence.
Open →Scope. Whaleal Platform sends over the CPaaS or BSP accounts you already hold. Your contracts, your rates and your sender identities stay yours, and nothing in the middle reprices them. Sector-specific rules — consent, records retention, industry obligations — stay with you and your provider.