USSDbet by AlgoStack Africa
Add USSD betting to the sportsbook you already run
USSDbet's standalone USSD offering lets you discuss adding a dial-in betting channel without replacing the whole sportsbook. We begin with your current platform, target country and mobile networks.
From there, we establish how USSD will connect to your accounts, wallet, betting and payment services, including any work that needs another supplier's agreement.
Agree the boundary before designing the menu
Before designing the menu, establish which system holds the customer's account and balance, accepts the bet and records the payment. That division of work determines what the channel can safely ask the customer to do.
| Area | Decision to make during integration scoping |
|---|---|
| Player identity | How a phone number relates to an account, and which checks are required |
| Wallet | Which system is authoritative and how available funds are determined |
| Bet acceptance | Where current odds, limits and acceptance decisions are applied |
| Payments | Which service initiates a collection or payout and records its eventual result |
| Session handling | What happens when the customer times out, repeats a step or reconnects |
| Support | Which identifiers help the team investigate a customer complaint |
Writing down these decisions gives the integration team a clear starting point and the operating team a clear owner when something goes wrong.
Design for the task, not for the website layout
USSD uses short text menus, so the next action and its result need to be clear. Trying to reproduce the whole website can make a simple task harder to complete.
Choose the tasks that belong on USSD and decide how a customer returns after an interruption. Start with the steps you can explain and demonstrate reliably before adding more menu options.
Make network access and charges explicit
A demonstration does not mean a production shortcode has been approved on every network. Confirm the intended country, code arrangement, participating networks, activation dependencies and commercial terms.
USSD does not require an internet data session on the handset, but that does not make the service cost-free. The customer, the business or both may face charges under the relevant arrangement. Record the payer, unit of billing and any recurring fees in the proposal.
Evaluate the interrupted journey
Before launch, agree how the integration will demonstrate a timed-out session, repeated input, a balance change during the journey and an unresolved payment. The important question is whether the financial record stays unambiguous and the customer receives a useful outcome.
The integration checklist gives your technical and operating teams a common starting document.
What remains with the existing sportsbook?
The answer depends on the agreed architecture. Your existing platform may remain responsible for accounts, wallet, trading, settlement and controls. Those responsibilities must be explicit; adding a channel should not silently change them.
What to send us
Share the target country and networks, the current platform, available integration documentation and the journeys you want to support. Avoid sending production credentials or customer records with an initial enquiry.
With that starting information, we can discuss what remains in your current platform, what the USSD channel needs to do and which supplier connections need further work.