Send SMS to DRC (Democratic Republic of Congo)
from $0.0200/msg

Mobile Operators: Vodacom, Airtel, Orange

Vodacom DRC (44% market share) is the largest and most reliable operator, with modern infrastructure in Kinshasa and other major hubs. Vodacom's SMS interconnection accepts messages to numbers prefixed +243 81 and supports both alphanumeric and numeric sender IDs after ARCEP approval. Delivery latency via Vodacom averages 240–290 ms p50.

Airtel DRC (31% market share) covers a complementary footprint across eastern and central provinces. Airtel's SMS platform accepts messages to +243 82 and has recently upgraded its regional peering to reduce latency. Airtel supports both sender ID types and has improved delivery throughput; p50 latency is typically 300–340 ms.

Orange DRC (25% market share) operates primarily in western and northern regions, with strong penetration in smaller cities. Orange's SMS gateway accepts +243 89 numbers and maintains separate registration for alphanumeric sender IDs. Latency via Orange is 320–380 ms p50, reflecting its smaller but geographically dispersed network.

All three operators are ARCEP licensees and participate in the regulator's sender ID and consent oversight. smsroute maintains dedicated interconnections with each, ensuring that a single API call to a +243 number is automatically routed to the correct operator based on the prefix (81, 82, or 89).

Pricing vs. Competitors

smsroute's $0.0200 USD per-SMS rate to DRC is substantially lower than legacy carriers and competing gateways. The table below compares smsroute to five major competitors on their published or list rates to DRC (prices in USD per SMS, as of Q1 2025).

At volume, the difference compounds rapidly. Sending 100,000 SMS to DRC via Twilio costs $5,000; smsroute costs $2,000—a $3,000 saving. Additionally, smsroute's minimum top-up is $5 USD (no monthly minimums or maintenance fees), making it accessible to startups and small-volume senders. Crypto-only payment eliminates currency conversion and international wire fees typical of traditional gateways.

Latency and Delivery Performance

smsroute maintains 99.9% uptime and 99% tier-1 delivery to DRC. Median (p50) latency from our PoP to recipient handset is 280 milliseconds. The 95th percentile (p95) is 520 milliseconds. These benchmarks include message queuing, operator routing, and device-side delivery confirmation; they do not include client library or application-level delays.

Latency varies predictably by operator and time of day. Vodacom DRC (largest operator) consistently delivers at 240–290 ms p50 during off-peak hours (22:00–06:00 WAT) and 280–350 ms p50 during peak (07:00–21:00 WAT). Airtel and Orange average 50–80 ms slower due to smaller backbone capacity but remain well within acceptable ranges for transactional and marketing SMS.

Delivery success is defined as receipt of a delivery confirmation (SMSc acknowledgment) from the recipient's operator within 24 hours. smsroute achieves 95.8% delivery success to DRC mobile numbers. Non-delivery (4.2% of messages) is caused by:

• Invalid or inactive numbers (60% of non-deliveries): recipient has closed account, number reassigned, or never existed.
• Network congestion (25%): temporary operator queue overflow during peak hours; messages eventually deliver after retry.
• Operator blocks (15%): recipient's account is suspended, or operator-side content filters reject the message (e.g., flagged as spam or malware).

All messages receive a delivery receipt (SMSc status code) in your dashboard. Codes like 0 (delivered), 1 (queued), 8 (undelivered) enable you to implement intelligent retry logic and identify problem numbers for removal.

Consent Framework: ARCEP Regulations + Law 2002-002

The Democratic Republic of Congo regulates SMS marketing under ARCEP's published regulations and Law 2002-002 (Telecommunications Law), most recently amended in 2023. The core requirement is explicit opt-in: before sending any marketing SMS, you must obtain and document affirmative consent from the recipient. A checkbox on a sign-up form, a confirmed email, or a dated SMS response ("SUBSCRIBE") all constitute valid proof of opt-in.

Transactional SMS—such as order confirmations, password reset codes, delivery notifications, or account balance alerts—do not require prior consent, provided they are directly related to a preceding action by the recipient. For example, an SMS sent immediately after an online purchase or a requested password reset is transactional and may be sent 24/7. Marketing SMS (promotions, newsletters, event invitations) requires explicit consent and must respect quiet hours.

ARCEP publishes enforcement actions and compliance guidance on its official website (https://www.arcep.cd/). The regulator has issued fines and suspension orders against senders who violate opt-in rules or abuse quiet hours. To stay compliant, maintain detailed records of consent (timestamps, channel, recipient confirmation) and audit your message scheduling before each campaign. smsroute provides delivery receipts and per-message logs to support your compliance records.

Frequently Asked Questions

Related

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+243812345678",
    "message": "Hello from smsroute!",
    "sender_id": "MYCOMPANY"
  }'

import requests

url = "https://api.smsroute.cc/send"
headers = {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json"
}
payload = {
    "to": "+243812345678",
    "message": "Hello from smsroute!",
    "sender_id": "MYCOMPANY"
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/v1/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+2435551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());