BWEZE SMS charges 15 RWF per segment, and a segment is what decides the bill. Most sign-in codes fit in one. Some take two, and nobody notices until the invoice.
One segment or two
An SMS travels as one of two alphabets. GSM-7 covers plain Latin letters, digits and common punctuation, and fits 160 characters in a segment. If a message contains a single character outside GSM-7, the whole message switches to UCS-2, which fits 70. Longer messages are split, and each part loses a few characters to the header that joins them back together: 153 per segment in GSM-7, 67 in UCS-2.
The guide GSM-7 or Unicode lists the characters that do this. The usual causes are an emoji, curly quotes pasted from a word processor, and accented letters that GSM-7 lacks, such as ê, â and ô. English and Kinyarwanda written in plain Latin letters stay in GSM-7.
The bill either way
A typical code message is well under 70 characters, so it is one segment in either alphabet:
| What | Amount | Rate | Cost |
|---|---|---|---|
| "Your BWEZE code is 482913. It expires in 10 minutes." | 1,000 segmentsat 15 RWF per segment | 15 RWF per segment | 15,000 RWF |
| The month | 15,000 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
Add a little text and one character outside GSM-7, and the same message crosses 70 characters in UCS-2 and becomes two segments:
| What | Amount | Rate | Cost |
|---|---|---|---|
| A 72-character message with one "ê" or one emoji | 2,000 segmentsat 15 RWF per segment | 15 RWF per segment | 30,000 RWF |
| The month | 30,000 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
That is the same message, sent to the same people, at twice the price.
Keeping a code to one segment
- Write it in plain text. Straight quotes, no emoji, no accented letters outside GSM-7.
- Keep it short. The code, what it is for and when it expires.
- Check before you send.
POST /v1/messages/previewtakes the same body as a send and returns the encoding and the number of segments without sending or charging anything. Run it in your tests so a template change that adds a segment fails the build.
{ "encoding": "GSM7", "segments": 1, "length": 52 }
What else is billed, and what is not
Only messages the gateway accepts are billed. Before a send, BWEZE holds its cost against your wallet; if the submit fails, the hold is released and nothing is charged. A send that your balance cannot cover is refused with 402 insufficient_balance instead of going out on credit.
Retries do not bill twice if you send an idempotency key. A retry with the same key returns the first result and does not send again, so a timeout on your side never becomes two codes on the user’s phone and two charges on your wallet.
A month of SMS for a small fintech app might look like this:
| What | Amount | Rate | Cost |
|---|---|---|---|
| Sign-in codes, 6,000 one-segment messages | 6,000 segmentsat 15 RWF per segment | 15 RWF per segment | 90,000 RWF |
| Payment alerts, 3,000 messages of two segments | 6,000 segmentsat 15 RWF per segment | 15 RWF per segment | 90,000 RWF |
| The month | 180,000 RWF | ||
Computed from BWEZE's published price list when this page was built. Memory is billed only while running; CPU only as used.
Every number on this page comes from BWEZE’s published price list when the page is built. The pricing page has the current rate, and the docs have the full API.