SMS gateways
An SMS gateway is the text-message service your organisation sends through. It decides whether a client’s SMS goes out, on whose account, and under which sender.
You see them under Settings › Correspondence › SMS.
Gateways
Each gateway row shows its type, who it sends for, its sender, its account, and whether its credential is set.
| Column | What it tells you |
|---|---|
| Type | The SMS service. Twilio sends for real. Simulator records each SMS as sent and delivers nothing; it needs no account SID and no credential. |
| Sends for | Whole bank, or one operating entity that sends under its own brand. |
| Sender | What the client’s phone shows as the sender: a number, a messaging service, or a name of up to 11 characters. |
| Account | The account at the SMS service that sends, and is billed. |
| Credential | Set once the service’s auth token is entered on the Secrets page. |
If a gateway’s credential is not set, it sends nothing. Select Secrets and enter the token there. Nobody can read a token back once it is entered.
Which gateway sends an SMS
- If the SMS belongs to an operating entity with its own gateway, that gateway sends it.
- Otherwise the whole-bank gateway sends it.
If the operating entity’s own gateway has no credential, the SMS is not sent through the whole-bank gateway instead. It is recorded as skipped, “channel not configured”.
If there is no gateway at all, your organisation sends no SMS. Clients are not offered SMS on their Delivery tab.
The Simulator gateway
A Simulator gateway lets a tenant with no SMS account send correspondence. Use it for demos, training and testing.
- It needs no account and no credential. Its channel counts as configured as soon as the row exists.
- It records every SMS exactly as a real send would. Nothing leaves the bank.
- Each SMS it records is badged Simulated in the client’s SMS history.
- The correspondence panel reads Sms (simulated) for each channel it sent.
- You open what it sent on the Simulator Outbox page, under Back office.
- A demo or test environment allows it. Your organisation’s live deployment refuses it: SMS reads “channel not configured”, even where a simulator row is configured.
The mobile number chosen decides the outcome:
| Number ends in | Outcome |
|---|---|
0001 |
Fails at once: “number not reachable”. |
0002 |
Fails on the first attempt, then sends on the first retry. |
| anything else | Sent. |
A number that is not a mobile number in international form still fails as “invalid mobile number” before the simulator sees it.
+27820000001 fails. +27820000002 fails once, then sends.
Which numbers are texted
An SMS goes only to a valid mobile number in international form, such as
+27821234567. Mobile numbers are stored that way when they are entered.
| Result | What happened | What to do |
|---|---|---|
| invalid mobile number | The number is not a mobile number, for example a landline. Nothing was sent. | Correct the client’s mobile number. |
| number refused by the gateway | The SMS service would not text the number. Its reason follows. | Check the number with the client. |
| sender refused by the gateway | The SMS service does not allow this sender on your account. | Register the sender with your SMS service, or change it. |
| credential refused by the gateway | The auth token was rejected. | Enter a current token on the Secrets page. |
If the SMS service times out, is unavailable, or asks you to slow down, the SMS is tried again later.
What an SMS costs
SMS services bill per segment, so each SMS records its segment count. The count follows the GSM 03.38 alphabet, from the standards register.
| Message | First segment | Each further segment |
|---|---|---|
| Plain letters, digits and common symbols | 160 characters | 153 characters |
| Any other character, such as an emoji or Cyrillic | 70 characters | 67 characters |
The characters € [ ] { } ^ ~ \ | are in the plain alphabet but count as two. An
emoji counts as two characters.
- A 200-character message in plain letters is two segments.
- The same message with its last letter replaced by an emoji is three segments.
The SMS carries the correspondence’s message only. Its title is not sent.
Standards
- Numbers are in the international telephone number format, ITU-T E.164.
- Segments are counted by the GSM 03.38 alphabet rules.
What your organisation configures
- Which SMS service your organisation uses, its account, and its auth token.
- The sender each gateway sends as.
- Whether an operating entity sends through a gateway of its own.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.