USSD in Nigeria: How It Works and What It Takes to Run a Service That Reaches Every Phone

People keep writing USSD off as legacy technology. The numbers say otherwise. In 2025, USSD banking transactions in Nigeria rose about 21 percent to 669.55 million, according to the Central Bank of Nigeria's 2025 annual report. That is not a channel on its way out. That is core payment infrastructure that happens to run on a technology most people assume died with the feature phone.

If you are building a service that needs to reach every phone in Nigeria, not just the ones with data plans and current Android versions, USSD is still the shortest path there. Here is how it works, why it holds up, and what actually separates a USSD service that runs from one that keeps dropping sessions.

What USSD actually is

USSD stands for Unstructured Supplementary Service Data. In plain terms, it is the technology behind the codes you dial that start with a star and end with a hash, like *123#.

A few properties make it different from anything app-based:

It is session-based. When a user dials your code, the network opens a live, two-way session between their phone and your application. Menus load, the user picks an option, your system responds, and the exchange continues until someone ends it or the session times out. Nothing is stored on the phone.

It needs no internet. USSD rides on the signalling channel of the GSM network, the same layer that sets up voice calls. That means it works on 2G, on a ten-year-old handset, with zero airtime data and no app installed. If the phone can make a call, it can run your USSD service.

It is instant and text-only. No download, no login screen, no loading spinner. The user dials, the menu appears in a second or two, and they are in.

That combination is why USSD carries so much weight in a market where smartphone and data penetration still leave millions of people out.

Why the channel still wins here

The case for USSD in Nigeria comes down to reach and friction.

Reach, because a huge share of transactions happen on phones and in places where a data-hungry app is not an option. USSD does not care about the handset, the operating system, or whether there is a signal strong enough to load a webpage. It works where apps quietly fail.

Friction, because there is almost nothing between the user and the action. No onboarding funnel, no forgotten password, no 40 MB update. Someone can open a bank account, send money, buy airtime, check a balance, or vote in a poll in under a minute, on a phone that cost less than a tank of fuel.

This is also why USSD sits underneath so much of Nigeria's instant payment activity. It is one of the channels that feeds NIBSS Instant Payments, alongside apps, POS, and QR. The interface looks basic. What it plugs into is not.

What businesses actually build on USSD

USSD is not only a banking tool, though banking is where the volume is. The pattern that makes it useful is simple: any service that can be expressed as a short menu can run on it.

Common builds include:

• Banking and fintech. Balance checks, transfers, bill payments, account opening, card control, and loan requests. This is the highest-volume use case in the country by a wide margin.
• Airtime, data, and VAS. Self-service top-ups, bundle purchases, subscription management, and content menus.
• Agent and distribution networks. Field agents in areas with poor data coverage can register customers, log sales, and check stock over a code.
• Customer engagement. Surveys, competitions, promo redemptions, and voting, run at scale without asking anyone to install anything.
• Service delivery and queries. Utility balance checks, exam result lookups, delivery tracking, and order placement.

If your users are on the ground rather than on Wi-Fi, USSD is often the only channel that reaches all of them.

How a USSD service is actually put together

This is where most of the real work lives, and where the choice of provider decides whether your service runs well or limps.

There are three pieces:

A short code. The star-hash string your users dial. Codes are a regulated, finite resource. You either own a dedicated code or you rent a slot behind a shared one, and that distinction matters more than it sounds. A dedicated code is your brand, your menu, your session behaviour, with nobody else's traffic competing for it.

A USSD gateway with network connectivity. This is the plumbing that carries sessions between the mobile networks and your application. For a code to work on MTN, Airtel, Glo, and 9mobile, there has to be a live connection into each of those networks. The quality and directness of those connections is the single biggest factor in how your service performs.

Your application logic. The menus, the responses, and the connections into your own systems, usually over an HTTP or SMPP-style interface that your developers integrate with. This is the part you control.

Put simply: you write the menus, but whether those menus reach every subscriber, respond fast, and hold the session without dropping depends almost entirely on the connectivity sitting underneath.

What to look for in a USSD provider

Most USSD problems are not application bugs. They are connectivity problems wearing an application costume. Sessions that time out, menus that work on one network and fail on another, latency that makes users give up halfway through. All of that traces back to how the provider connects to the mobile networks.

So the questions worth asking are blunt:

Are the network connections direct, or resold? Every hop between your code and the subscriber adds latency and another point of failure. A provider running direct interconnects into the mobile operators gives you shorter, more reliable sessions than one reselling capacity bought from someone else. This is the difference that shows up as reliability under load, and it is the one to press hardest on.

Do you get a dedicated code, or a slot on a shared one? A dedicated code means your service is not sharing session capacity or brand recognition with anyone. It also gives you room to build a proper menu tree rather than squeezing into a sub-option.

Who handles the billing side? Since June 2025, Nigeria has run on an end-user billing model, where the session charge is deducted directly from the subscriber's airtime rather than billed to the service. That changes how you design flows and how charges are disclosed to users. A provider who understands the current regime saves you from launching a service that surprises people with charges.

What is the uptime commitment, and who answers when it breaks? USSD sessions are live and unforgiving. A dropped session is a lost transaction. You want operator-grade availability and a support line that reaches an engineer, not a ticket queue.

Where Ruach fits

We run USSD as a licensed Nigerian operator, not as a middleman. That means direct interconnects into the mobile networks, owned short codes, and gateway agreements that put your sessions on the shortest path to the subscriber. Fewer hops, faster menus, and connectivity we control rather than rent.

For a bank, a fintech, a VAS provider, or any business that needs to reach the whole market rather than the slice with a smartphone and a data plan, that is the part that decides whether the service works on launch day and every day after.

If you are scoping a USSD build, or you are already live and fighting dropped sessions, talk to us. We will tell you plainly what your setup needs, and whether we are the right people to run it.