// betting & igaming
USSD Betting in Africa: The Complete Operator Guide
How Betika, SportPesa, Bet9ja, and betPawa use USSD as a primary betting channel. Shortcode deployments, the 5-screen betting journey, booking code economics, and why USSD bettors have higher lifetime value than app users.
The Operator Shortcode Matrix
Deploying a USSD shortcode requires a direct commercial agreement with a national telco — creating a capital and regulatory moat that limits market entry to capitalised operators or deeply entrenched local brands.
| Country | Operator | Shortcode | Networks | Channel Role |
|---|---|---|---|---|
| Kenya | SportPesa | *790# | Safaricom, Airtel | Hybrid Primary / Fallback |
| Kenya | Betika | *644# | Safaricom, Airtel | Hybrid Primary / Fallback |
| Ghana | Betika Ghana | *263# | MTN, Vodafone, AirtelTigo | Primary Acquisition (Rural) |
| Ghana | NLA | *959# | MTN, Vodafone | Primary (National Lottery) |
| Uganda | betPawa | *255# | MTN, Airtel | High-Volume Fallback |
| Tanzania | Meridianbet | *149*10# | Tigo, Airtel | Primary Acquisition (Rural) |
| Tanzania | SportPesa | *15888 | Vodacom, Tigo, Airtel | SMS/USSD Hybrid |
| DRC | Premier Bet | #150*4*4# | Orange Money | Financial Bridge |
Primary vs Fallback: It Depends on the Market
In Tanzania and rural Ghana, USSD is the primary acquisition channel. Meridianbet's *149*10# is marketed as a complete standalone gateway — register, deposit, bet, withdraw, all without internet. In Kenya, operators run USSD alongside apps in a hybrid model. The "USSD-only operator" is functionally obsolete in 2026 — modern betting complexity requires a parallel digital platform for odds discovery and accumulator building.
The 5-Screen Betting Journey
160 characters per screen. 60-90 seconds before session timeout. Product managers must compress thousands of live odds into a minimalist text-tree hierarchy.
Screen 1: Gateway & Authentication
User dials the shortcode. The telco identifies the MSISDN. Backend cross-references with PAM. If recognised, bypass registration entirely.
Screen 2: Market Segmentation
Can't display 10,000 matches. Backend algorithmically curates highest-liquidity events — EPL, Champions League, domestic African football.
Screen 3: Event Selection
Pagination via universal commands: "98" for next page, "00" for back. Abbreviated team names to fit character limits.
Screen 4: Odds Display
The critical UX juncture. Must display Game ID, kickoff time, and 1X2 odds plus input prompt — all in 160 characters.
Screen 5: Confirmation & Receipt
Verifies wallet balance. In Kenya, legally mandated to display withholding tax calculations. The final screen IS the legally binding receipt.
The Booking Code Revolution
The most transformative UX innovation in African betting. An urban user builds a 20-leg accumulator on the app over Wi-Fi, generates a short alphanumeric booking code, shares it via WhatsApp or SMS. A rural user dials *644#, enters the code, and the entire accumulator loads instantly for staking.
Why This Changes Everything
- Crowdsources odds analysis to urban broadband users
- Executes the transaction via USSD for data-constrained rural users
- Replaces digital ad spend — Betway Zambia pays 4% commission on every booking code staked by others (5+ legs)
- Creates a decentralised affiliate network powered entirely by USSD execution
In-Play Betting: The "Freeze and Fetch" Architecture
Live odds can't push to USSD — it's synchronous request-response, not WebSocket. Operators implement a workaround: when a user navigates to a live match, odds are fetched and frozen for 10-15 seconds. If odds shift before bet confirmation, the system returns: "Odds changed to [New Odds]. 1 to Accept, 2 to Cancel."
Channel Economics: USSD vs App
| Metric | USSD | Mobile App |
|---|---|---|
| Reach | 100% of phones | ~55% (smartphones only) |
| User data cost | Zero | Downloads + background data |
| Deposit conversion | Near-zero abandonment (STK Push) | Multi-step redirect, high abandonment |
| Avg stake | $0.50-$2 (micro-bet volume play) | Higher individual stakes |
| Retention | Permanent in dialer. Zero updates. | Storage churn, APK friction, Play Store bans |
| LTV pattern | Lower ARPU but extreme long-term stability | Higher ARPU but app fatigue churn |
The LTV Paradox
USSD bettors have lower individual ARPU. But they never uninstall the shortcode — it lives permanently in the phone's dialer, requires zero storage, zero updates. The brand never gets deleted. App users face storage pressure on entry-level Android devices, APK sideloading friction (Play Store bans gambling apps in many African markets), and update fatigue. USSD retention metrics are consistently higher.
PAM Integration: Bridging SS7 and Cloud
Operators connect USSD shortcodes to their Player Account Management system via aggregation gateways (Africa's Talking, Infobip). The architecture runs on RESTful APIs with JSON payloads. When a user dials, the MNO routes to the USSD gateway, which parses numeric input into API calls that query the PAM database, retrieve odds, format into 160-char plaintext, and return — all within milliseconds to prevent timeout.
Session Timeout Recovery
If a session drops before bet confirmation, the middleware caches the betslip in Redis for 5-10 minutes. When the user redials, the PAM recognises the MSISDN, retrieves the cached state, and shows: "You have a pending betslip. 1: Resume. 2: Start Over."
Tax Automation
Systems like Digitain's Tax Engine instantly calculate jurisdiction-specific taxes — Kenya's 20% WHT on winnings, excise on stakes — and return compliant receipts to the handset without bottlenecking the database.
Responsible Gambling via USSD
USSD self-exclusion is remarkably airtight. Because the ecosystem is tied to the user's government-registered MSISDN (mandatory SIM registration across Africa), a problem gambler cannot bypass the block by opening incognito tabs, clearing cookies, or registering new email addresses. Users navigate to Account Settings and select numeric options to pause activity for 24 hours, 7 days, or permanently.
// ready to launch USSD betting?
We handle the shortcodes, session state, carrier routing, mobile money integration, and booking code flows. You handle the betting product.