Understanding USSD in Africa
USSD (Unstructured Supplementary Service Data) remains important for African mobile money, banking, airtime, data collection and account-service flows because it is session-based, real time and does not require a data connection. Gateway providers such as Africa's Talking describe USSD as a way to run interactive services on both feature phones and smartphones.
For developers, the hard part is usually not drawing the menu. It is keeping each screen short, handling invalid input, reaching terminal screens quickly, avoiding sensitive-data exposure and confirming provider rules before launch. Some markets have strict menu-length and timeout constraints, so a prototype should be checked against the exact telco or USSD gateway you plan to use.
This simulator models the menu as a local state machine: the user chooses a preset or custom JSON flow, enters responses, and watches the phone-style screen update. It does not dial a real short code, collect live fees, connect to a wallet or validate provider credentials. Use it for product, QA and engineering handoff before implementation.
Before production, confirm short-code ownership, shared-code routing, callback payloads, session timeout, character limit, user billing, compliance review and support escalation directly with the mobile network operator or gateway provider.
Frequently Asked Questions
Does this send live USSD requests?
No. The simulator is local and offline. It models menu logic only, so short-code availability, callbacks, pricing, session duration and gateway approval must be validated with the provider.
What should I check before launch?
Confirm the provider's shared or dedicated code model, session timeout, character limit, callback payload, billing model, production credentials, support path and compliance requirements.