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 must arrive before a session expires, an alert that proves a transaction happened, a reminder that keeps a subscription alive. Latency and duplicates matter here more than anywhere else.
The messages that carry real weight
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
Why the rate limit is the whole story
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.
How the send path is handled
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 is mostly a messaging operation that happens to have a checkout. The confirmation, the dispatch note, the delivery window, the code for a failed payment — these are the messages customers actually read, and they run on the same few send paths every day.
Open →Healthcare & clinics
Most healthcare messaging is administrative, and administrative is exactly where a missed message costs a wasted appointment slot. The discipline is to say just enough to be useful and nothing that belongs in a clinical record.
Open →Logistics & delivery
A delivery operation lives on contact attempts: the customer who is not home, the gate code nobody has, the parcel going back to the depot. Each of those is a message that either saves a second attempt or causes one.
Open →SaaS & online services
For a SaaS product, messaging is infrastructure with a product surface: the login code, the incident notice, the trial-expiry nudge. These messages sit on the critical path of someone else’s workday, which sets a higher bar than marketing ever has.
Open →Education & training
Education messaging is overwhelmingly about timing: a class that moved, a deadline that is close, an enrolment that has not been confirmed. The failure mode is not a missing message, it is a message that arrives after it matters.
Open →Marketplaces & platforms
A marketplace sends to two audiences who care about the same event for opposite reasons: the buyer wants it to arrive, the seller wants proof that it did. That makes receipts and auditability the interesting part of the problem.
Open →Travel & hospitality
Travel messaging is time-zone-shaped: a confirmation that must arrive immediately, a reminder that should arrive the evening before, and a disruption notice that is worthless if it arrives after the guest has left for the airport.
Open →On-demand & field services
Field service messaging is measured in minutes: a technician is twenty minutes away, a job has moved, a customer will not be in. Every one of these messages exists to avoid a wasted trip.
Open →Scope. Whaleal Messaging is an orchestration layer 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.