A2P SMS, OTP, and sender ID rules in Rwanda.
BroadNet delivers A2P SMS and OTP in Rwanda over direct connections to MTN Rwanda and Airtel Rwanda, with RURA sender ID registration in 5-7 business days. Direct termination into MTN Rwanda and Airtel Rwanda with RURA sender ID registration handled in-house.
From-rates by channel in Rwanda
- SMSfrom$0.0320per SMSIndicative list rate, reviewed September 24, 2026Volume pricing available
- OTPRequest a quote Channel list rate from $0.0120 per verification (all markets)
- WhatsAppRequest a quote Channel list rate from $0.0135 per template message (all markets)
- RCSRequest a quote Channel list rate from $0.0080 per session (all markets)
- VoiceRequest a quote Channel list rate from $0.0150 per minute (all markets)
Indicative list prices in USD, excluding taxes and sender-ID registration fees. Final per-operator pricing is confirmed in your quote.
The Rwanda A2P market at a glance.
Rwanda is served by 2 licensed mobile networks (MTN Rwanda and Airtel Rwanda) covering a subscriber base of 12M. Rwanda Utilities Regulatory Authority (RURA) regulates A2P messaging and sender-ID registration. RURA sender ID registration via operator. English, French, and Kinyarwanda supported. Rwanda Data Protection Law 2021 enforced. Pro-digital regulator with fast turnaround.
Technical facts for Rwanda
Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038).
| Mobile country code (MCC) | 635 |
|---|---|
| Dialling code | +250 |
| Operators (MCC-MNC) |
|
| SMS length, GSM-7 (Latin alphabet) | 160 characters in a single SMS; 153 per part when concatenated |
| SMS length, UCS-2 (Arabic, Cyrillic and other scripts) | 70 characters in a single SMS; 67 per part when concatenated |
| Regulator | RURA (Rwanda Utilities Regulatory Authority) |
| Sender-ID rules | RURA sender ID registration via operator. English, French, and Kinyarwanda supported. |
| Sender-ID lead time | 5-7 business days |
Channels live in Rwanda.
One contract, one contact model. Fall back between SMS, WhatsApp, and Voice with shared opt-in evidence and a single audit trail.
SMS
Operator-direct A2P with USSD/sender-ID fallback where alphanumeric is not permitted.
OTP
Sub-5-second median in metro areas; rural coverage gracefully degrades with retry.
WhatsApp Business API live — high market penetration makes it a strong OTP and engagement channel.
RCS
RCS not yet rolled out by local operators. SMS + WhatsApp remain the primary A2P channels.
Voice
Voice OTP recommended as fallback in low-bandwidth regions.
How do I register a sender ID in Rwanda?
Filed end-to-end by BroadNet's compliance team — KYC pack, operator approval, and renewal cycles handled on your behalf.
RURA · MTN Rwanda and Airtel Rwanda
- Format
- Alphanumeric, up to 11 chars (numeric long-code on select networks)
- Pre-registration
- Set by the operators; BroadNet confirms the current requirements during onboarding
- KYC documents
- Confirmed during onboarding
- Renewal cycle
- Confirmed during onboarding
- Common rejection causes
- Sender-ID rules are set by the operators; BroadNet confirms current requirements during onboarding.
What OTP delivery looks like in Rwanda.
Latency profile, peak-hour behaviour, recommended fallback chain, and the fraud signals our firewall watches in-market.
Typical latency window
Median 3.2 s with a 95th-percentile inside 8 seconds across operator-direct binds. Two-shot delivery confirmed by DLR.
Peak-hour behaviour
Operator throughput holds steady through local business peaks; throttling kicks in only during outlier mass-send events. BroadNet load-shapes per-MNO to avoid firewall blocks.
Fallback chain
Recommended fallback: WhatsApp OTP → Voice OTP after 30s. USSD fallback available on selected operators for feature-phone users.
Fraud signals we watch
Watch for SIM-swap fraud (banking and fintech), DND-list violations, and grey-route arbitrage attempts via foreign aggregators.
What you can — and can't — send.
Opt-in, opt-out, quiet hours, content restrictions, and the penalty regime for the Rwanda market.
Opt-in
Verifiable opt-in required, with timestamped consent records retained for at least 12 months and produced on regulator request.
Opt-out
Every promotional message must include STOP / opt-out wording. DND-registry suppression applied automatically where the regulator runs one.
Quiet hours
We have not found a regulator-published time-of-day window for promotional SMS in this market. Agree sending hours with the operator and schedule promotional sends for the recipient's local daytime; transactional traffic runs 24/7.
Content restrictions
Loan, gambling, and unlicensed pharma flows are blocked. Promotional and transactional traffic must stay on separate sender IDs.
Regulator penalties
RURA penalties for grey-route or unsolicited traffic — fines, sender-ID delisting, and aggregator-licence suspension for repeat offenders.
Termination,
network by network.
The route status column shows how each operator is reached — a direct BroadNet bind or a labelled partner route. No grey-route exposure. Route grades are indicative planning guides, not live measurements.
| Operator | MCC-MNC | Route status | Grade | A2P rate (typ.) |
|---|---|---|---|---|
| MTN Rwanda | 635-10 | Direct | A+ | USD 0.0343 |
| Airtel Rwanda | 635-13 | Direct | A+ | USD 0.032 |
Rates shown are typical pay-as-you-go for transactional traffic. Promotional traffic is priced separately, and volume tiers reduce both. See the rate-card section below for the full ladder.
| Tier | Transactional | Promotional | Notes |
|---|---|---|---|
| Pay-as-you-go | USD 0.0320 | USD 0.0390 | List rate up to 100K messages/month |
| Growth · 100K+ | USD 0.0282 | USD 0.0344 | Auto-tier discount |
| Volume · 1M+ | USD 0.0237 | USD 0.0289 | Includes quarterly route review |
| Enterprise | Custom | Custom | Direct operator pricing + signed SLA |
RURA sender ID registration: 5-7 business days.
Open the Rwanda rate cardCompliant
by default.
Every send is pre-screened against Rwanda Utilities Regulatory Authority (RURA) rules, the operator firewalls, and the local privacy framework. Where registration is required, BroadNet files the paperwork on your behalf.
Rwanda Data Protection Law 2021 enforced. Pro-digital regulator with fast turnaround.
Full regulatory deep-diveRURA sender ID
Sender IDs registered via operator route (fast turnaround).
DPL 2021
Rwanda Data Protection Law enforced.
EN / FR / RW
All three at parity.
Programmes that work well in Rwanda.
Where the BroadNet operator-direct footprint, the local regulator regime, and consumer messaging habits line up.
- 01
Fintech and mobile-money OTP, balance alerts, and transaction confirmations.
- 02
Agritech weather, price, and input-supply alerts to smallholder farmers.
- 03
E-commerce and logistics delivery tracking and rider-coordination messages.
- 04
Healthcare and public-health campaign messaging with local-language templates.
- 05
Education and edtech enrolment, attendance, and fee-payment reminders.
What we run for Rwanda senders.
The operator relationships, the compliance workflow, the routing position — all on a single contract and a single account team.
Operator-direct binds with MTN Rwanda and Airtel Rwanda — no aggregator hops, no grey-route exposure.
Sender-ID requirements confirmed during onboarding.
Live in 5–15 business days from test-access request to production, with a dedicated solution engineer through go-live.
Typical delivery rate 99.1% and typical OTP delivery time 3.2 s across the country.
African operator-team relationships maintained continuously — fast route remediation when a network flaps.
DND-registry and local-language template support included.
Buyer questions about Rwanda.
The questions BroadNet's sales engineers field every week from teams shipping into this market.
What's the typical sender-ID approval time with RURA in Rwanda?
Typical lead time: 5-7 business days. BroadNet confirms the current sender-ID requirements and documents during onboarding.
Are BroadNet's routes to Rwanda operator-direct?
Yes — every operator on the public coverage table is a direct A2P bind. No aggregator hops, no grey-route exposure. Route grades are indicative planning guides, not live measurements.
Can I send marketing SMS in Rwanda without prior consent?
No. Verifiable opt-in is required across every market BroadNet supports, with the consent source, timestamp, and channel logged. Transactional OTP and account-level alerts are exempt from marketing-consent rules.
Which channels do you support for Rwanda — SMS only, or also WhatsApp and Voice?
SMS, OTP, WhatsApp Business, and Voice OTP are all supported. RCS Business Messaging is available where the local operator has launched it. All channels run on the same contract and contact model.
Can I be billed in a currency other than USD?
Yes — billing is available in USD. Volume tiers apply automatically from 100K messages a month.
Do I need a local-language version of my templates for Rwanda?
Not strictly required, but in markets with multiple official languages a bilingual template materially improves engagement on marketing traffic. Transactional OTP is usually fine in English.
What happens if a route to Rwanda degrades?
BroadNet runs continuous DLR monitoring on every operator. If a route flaps, traffic is automatically re-shaped to the next-best operator on the same destination, and your account manager is notified with a remediation note within the hour.
Do you sign an SLA for traffic to Rwanda?
Yes — traffic to this market runs under BroadNet's standard SLA: 99.99% monthly platform uptime, with service credits on enterprise contracts. Support response targets and the credit schedule are published on our Support & SLA page.
A ready-to-adapt template for Rwanda.
In the local script alongside English. Copy, swap the brand, and we'll register it as part of your sender-ID onboarding.
- Mobile subscribers
- 12M
- Sender ID lead
- 5-7 business days
- Time-to-launch
- Live in 5–15 business days from test-access request to production
- Billed in
- USD
Your code is 471829. Valid 5 minutes.
RURA sender ID registration via operator. English, French, and Kinyarwanda supported.
Continue across the region.
See how enterprises put these operator-direct routes to work in banking and finance messaging and e-commerce and retail messaging, or weigh the options on the messaging platform comparison hub.
More on Rwanda
Request current route availability for Rwanda.
Live in 5–15 business days from test-access request to production. Sender ID filed with RURA on your behalf. Billed in USD from day one.
$ curl -X POST https://api.broadnet.me/sms/sendSms·mno = +250