USSD Applications: The Complete Guide for Africa (2026)

For all the noise about apps and AI, the workhorse of African digital services is still USSD applications. From M-Pesa to school fees, from SACCO loans to election results, USSD quietly powers trillions of shillings of value every year — on feature phones, smartphones, basic Nokias, and the latest Samsung flagships. This comprehensive guide explains what USSD applications are, how they work, who needs them, how they are billed, and how non-developers can build one using a no-code platform like HelloDuty.

What Is a USSD Application?

USSD stands for Unstructured Supplementary Service Data. It is a GSM protocol — the same family as SMS — that opens a real-time, session-based dialog between a mobile subscriber and a service running on a server. Unlike SMS, which is store-and-forward, USSD is interactive: dial a short code like *544# and a menu appears within milliseconds, even on a 2G network with no internet.

USSD vs SMS vs Apps: What's the Difference?

SMS is one-way and asynchronous. Smartphone apps require data, storage, and OS compatibility. USSD sits in the sweet spot: instant, two-way, network-resident, and device-agnostic. It works on every phone made since 1996, in any region with mobile coverage, with or without data, with or without a smartphone.

Why USSD Still Wins in 2026

Even with rising smartphone penetration, USSD remains dominant for high-frequency financial services. M-Pesa reports that of its 66.2 million customers, only 3.6 million regularly use the smartphone app — the rest transact via *334#. When Safaricom raised its KES 20 billion green bond in 2025, 59% of applications came in via USSD, paid directly through M-Pesa. USSD is the rails on which African digital finance runs.

Anatomy of a USSD Session

Understanding the session model is the key to designing a useful USSD application. A session is a short-lived, server-mediated dialog with strict timing and screen-size constraints.

The Session Lifecycle

A USSD session typically follows this sequence:

1. The subscriber dials a short code (e.g., *544#) from their mobile.
2. The mobile network operator (MNO) routes the request to the USSD gateway.
3. The gateway forwards an HTTP request to the application server, passing a unique session ID, the subscriber's phone number, and any text the user has typed.
4. The application returns a screen — plain text up to 182 characters — plus a flag indicating whether the session continues or ends.
5. If the session continues, the subscriber sees a menu and chooses an option; the app receives the choice in the next request and responds again.
6. The session ends after a fixed timeout (typically 20–60 seconds) or when the application sends an end signal.

Menu Trees and UX Constraints

Each USSD screen is a text-only menu of up to 182 characters across roughly 7 visible lines. Designers must collapse complex flows into 3–5 menu items per screen, use short verbs, and minimise round-trips. The best USSD UX feels like a slick command-line: predictable shortcuts (e.g., *544*amount#), consistent back-navigation with 0, and emergency exits with #.

Billing Models: Who Pays for the Session?

USSD pricing is the part that surprises most product managers. There are two main billing models in Africa:

Per-Session Billing (Subscriber Pays)

The MNO charges the end user per session — typically KES 1–5 in Kenya, NGN 5–20 in Nigeria, UGX 50–150 in Uganda. This is common for entertainment, content, and competitions. The MNO collects the fee; the service provider shares revenue.

Reverse-Billed (Business Pays)

The service provider absorbs the per-session cost (typically KES 0.50–2 per session in Kenya) so the user pays nothing. This is the model used by banks, SACCOs, mobile-money services, and most government services. It removes the friction barrier for high-volume engagement.

Hybrid Pricing

Some MNOs offer a tiered structure where the first 20 seconds are free (the gateway eats the cost) and subsequent extension is billed. Good USSD design respects this by completing common flows under the free threshold.

MNO Partnerships: Safaricom, Airtel, MTN and Beyond

Every USSD short code must be provisioned by, or through, an MNO. In Kenya, that means Safaricom (~66% market share), Airtel, and Telkom. In Nigeria, MTN, Glo, Airtel, and 9mobile. In Uganda, MTN and Airtel. There are two approaches:

Direct MNO Application

Apply to each MNO individually for a dedicated short code. Pros: prestige, lower per-session cost at scale, branded codes (e.g., *334#). Cons: long lead time (3–12 months in Kenya), high deposits (KES 100,000+), and ongoing compliance reporting.

Shared Short Codes via Aggregators

Use a USSD aggregator like HelloDuty or Africa's Talking that already owns a short code and rents you a sub-code (e.g., *384*1234#). Pros: live in days, no MNO paperwork, instant multi-country coverage. Cons: longer dial string, shared brand visibility.

Cross-Network Coverage

Beware: a short code provisioned with Safaricom does not automatically work on Airtel or Telkom. True cross-network reach requires either separate MNO applications or an aggregator that has stitched the relationships together. Aggregators are usually the pragmatic choice for SMEs.

Use Cases: What USSD Powers in Africa

The breadth of USSD use cases is the strongest argument for considering it as a primary channel for African markets.

• Mobile money — M-Pesa (*334#), Airtel Money, MTN MoMo, EcoCash. The original killer app.
• Micro-lending — Tala, Branch, KCB M-Pesa loans, Fuliza. Instant credit decisions delivered in 4–6 screens.
• Banking — Account balance, mini-statements, fund transfers, cardless ATM withdrawals.
• SACCOs and chamas — Member balance lookup, loan applications, dividend statements.
• Insurance — Policy purchase, premium payment, claim notification.
• Agriculture — Commodity prices, weather alerts, input vouchers, e-extension.
• Health — Appointment booking, medication reminders, vaccination records.
• Voting and surveys — Talent shows, opinion polls, NPS surveys.
• Education — KCSE results, school fee balances, e-learning quiz access.
• Government services — eCitizen lookups, KRA TOT filing, social cash transfers.

For a deeper dive, see our guide on how USSD can grow your business in Nairobi and our list of popular USSD codes Kenyans use daily.

Building a USSD Application: A No-Code Walkthrough

You do not need to write a single line of code to launch a USSD service on HelloDuty. Here is the typical workflow using the Click-and-Configure Studio:

1. Provision your short code. Choose a shared sub-code for fast launch or apply for a dedicated short code if you have the budget and time. Most pilots start on a shared code.
2. Design the menu tree. In the visual studio, drag-and-drop screens: a welcome screen, then up to 5 menu options per screen. Each option links to either another screen, an API call, or a session end.
3. Define dynamic placeholders. Use variables like {{phone}}, {{name}}, {{balance}} so each screen can be personalised at runtime.
4. Connect to your backend. Point any menu option at a webhook — a URL on your CRM, ERP, or mobile-money platform — that returns the value to display. The studio handles authentication, retries, and timeouts.
5. Add input validation. For amount entry, ID number capture, or PIN entry, configure regex-based validation so users get a friendly error before the call to your backend.
6. Test on a sandbox. Use the platform's simulator to walk through every branch before going live.
7. Publish and go live. Once approved, the short code becomes dialable across networks. Live analytics show session counts, drop-off points, and average session time.
8. Iterate. Most USSD applications are tuned weekly in the first 90 days to lift completion rates from 40% to 70%+.

For Developers: API Building Blocks

If you prefer to build from scratch, every USSD platform exposes a webhook API. Your application server receives an HTTP POST with the session ID, phone number, network code, service code, and the cumulative text the user has typed (separated by *). Your response is plain text prefixed with CON (continue session) or END (terminate session). The pattern is stateless on your side, with the platform handling session state via the session ID.

FAQ: USSD Applications in Africa

How much does a USSD short code cost in Kenya?

A dedicated 4-digit short code from Safaricom carries a one-off setup fee (KES 100,000+) plus monthly rental (KES 30,000–100,000) and per-session charges. A shared sub-code via an aggregator can start under KES 10,000 per month.

Can USSD work without internet?

Yes. USSD runs entirely over the GSM signalling channel — the same lane as voice and SMS — so it works on 2G networks, in rural areas, and in places with zero mobile data coverage.

How long can a USSD session last?

Operators set per-session timeouts, typically 20–60 seconds per user input. Total session length is capped at 180–300 seconds depending on the MNO. Design for completion within 60 seconds.

Is USSD secure for payments?

USSD itself runs over the GSM signalling channel, which is considered reasonably secure. Sensitive flows like PIN entry use additional encryption between handset and MNO. M-Pesa, with billions of dollars flowing monthly, is the proof point.

How do I integrate USSD with M-Pesa or mobile money?

Most USSD platforms expose direct integration with M-Pesa STK Push, Airtel Money APIs, and MTN MoMo — so a customer can authorise payment inside the same session. See our USSD integration guide for examples.

Launch Your USSD Application With HelloDuty

Whether you are a Kenyan SACCO digitising loan applications, a Nigerian fintech rolling out micro-savings, or a Ugandan agri-business pushing weather alerts — HelloDuty's USSD platform lets you launch in days, not months. Our no-code Click-and-Configure Studio, multi-MNO coverage, M-Pesa STK Push integration, and per-session analytics dashboard make USSD accessible to product teams that have never written a line of Erlang. Talk to us for a free short-code consultation and a 14-day sandbox.