# What a verification code costs to send in Rwanda

> A sign-in code is one SMS segment if you write it right and two if one character slips in. The bill for 1,000 codes either way, and how to keep it at one.

Source: https://sms.bweze.com/blog/what-an-otp-costs/ · Updated 2026-11-17

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](/learn/sms-basics/gsm-7-vs-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:

**1,000 sign-in codes, one segment each**

| What | Amount | Rate | Cost |
| --- | --- | --- | --- |
| "Your BWEZE code is 482913. It expires in 10 minutes." | 1,000 segments | 15 RWF per segment | 15,000 RWF |
| **Before the allowance** | | | **15,000 RWF** |
| **Month** | | | **15,000 RWF** |

Add a little text and one character outside GSM-7, and the same message crosses 70 characters in UCS-2 and becomes two segments:

**The same 1,000 codes, with one character that forces Unicode**

| What | Amount | Rate | Cost |
| --- | --- | --- | --- |
| A 72-character message with one "ê" or one emoji | 2,000 segments | 15 RWF per segment | 30,000 RWF |
| **Before the allowance** | | | **30,000 RWF** |
| **Month** | | | **30,000 RWF** |

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/preview` takes 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.

```json
{ "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:

**A month for a small fintech app**

| What | Amount | Rate | Cost |
| --- | --- | --- | --- |
| Sign-in codes, 6,000 one-segment messages | 6,000 segments | 15 RWF per segment | 90,000 RWF |
| Payment alerts, 3,000 messages of two segments | 6,000 segments | 15 RWF per segment | 90,000 RWF |
| **Before the allowance** | | | **180,000 RWF** |
| **Month** | | | **180,000 RWF** |

Every number on this page comes from BWEZE's published price list when the page is built. The [pricing page](/pricing/) has the current rate, and the [docs](https://docs.bweze.com/docs/messaging) have the full API.

## Sources

- [BWEZE price list (GET /v1/pricing)](https://api.bweze.com/v1/pricing)
- [BWEZE docs: Messaging](https://docs.bweze.com/docs/messaging)
- [3GPP TS 23.038: Alphabets and language-specific information](https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/)
