01 / PAYMENTS
Payment-triggered automation
Configured M-Pesa and SMS signals can create requests, match amounts to offers and move work into the right transaction state.
v1.3.2 now available
Safaricom Bingwa Sokoni agent automation
Speed that wins. Automation that stays accountable.
Bingwa Flash helps agents turn paid customer requests into controlled fulfilment. It can read permitted payment and SMS signals, match them to your configured offers, run the correct USSD path, retry safely when allowed, and keep the final response visible in your transaction history.
Payment-triggered requests
Dual SIM offer routing
Web order pages
Retry and recovery tools
Live automation feed
Automation on
KSh 50 airtime
Daily bundle
Held request
USSDMapped paths
WebPaid orders
LogsAudit trail
Features
Everything an agent needs to serve faster.
The app is built for the full day-to-day flow: receive payment, match the offer, execute the right path, detect the response, recover from blocks, and keep the customer or agent informed.
02 / USSD
Multi-step USSD mappings
Build offer flows with specific menu responses, SIM assignment and fallback paths when carrier menus or responses change.
03 / WEB ORDERS
Agent order pages
Agents can expose selected offers online, collect STK payments and route paid web requests into the same fulfilment queue.
04 / RETRIES
Retry and alternative USSD
Failures that are safe to retry can use configured rules or an alternative USSD path while preserving one visible transaction trail.
05 / RELAY
SMS relay workflows
Sender and receiver relay modes help partner agents pass work between devices when that workflow is enabled and configured.
06 / CLIENTS
Client tools
Manage client registration, saved contacts, blacklist actions and customer lookup tools where supported by your messages.
07 / ALERTS
Agent alerts
Important events such as failures, automation interruptions, reversals or low readiness can be surfaced so the agent acts quickly.
08 / BALANCES
Airtime and token safeguards
Track airtime usage, watch token access, and use enabled emergency purchase flows when supported by the configured offer.
09 / HISTORY
Searchable transaction logs
Every important request keeps status, phone details, selected offer, response text, failure reason and recovery action in one place.
How it works
From customer payment to final response.
Bingwa Flash is not just a button that dials USSD. It is a controlled transaction flow that checks readiness, runs the selected path, records the result, and gives the agent a decision when automation should not continue blindly.
STEP 01
Detect
A payment, SMS, web order or relay event is received through enabled permissions and configured rules.
STEP 02
Match
The amount, offer, SIM, customer and receiver details are matched before execution starts.
STEP 03
Execute
The mapped USSD flow runs through the selected SIM and captures carrier dialog responses.
STEP 04
Recover
If blocked, the transaction can fail nicely, wait on hold, retry, skip or ask for agent confirmation.
STEP 05
Report
The final status, response, airtime impact, commission and alert trail remain auditable.
Built for
The agents who keep moving.
Whether you run a small till, a busy shop, online bundle orders or a partner relay setup, the app is meant to reduce manual work without hiding what happened.
Safaricom agents
Serve airtime and bundle customers faster while keeping final transaction outcomes visible.
High-volume till operators
Let matched requests queue and execute while you focus on customers who need attention.
Web-enabled sellers
Receive paid orders from your public link and fulfil them through your configured app setup.
Relay networks
Use controlled sender and receiver modes where partner fulfilment is part of the workflow.
Agent control
Setup matters. Recovery matters more.
Android permissions, Safaricom menus, SIM state, airtime balance and network prompts can change. Bingwa Flash gives the agent clear setup controls and recovery states instead of crashing or silently losing the request.
Before going live
Configure the phone properly
Reliable automation starts with the right permissions, SIM selection, offer mappings and tested USSD paths.
- SMS, phone and accessibility permissions enabled
- Offers mapped to the correct USSD code and SIM
- Enough airtime or token access for the selected offer
- Retry, verifier and alert rules reviewed
When something blocks
Fail clearly and recover safely
When execution cannot continue, the app should show why and give the agent a sensible next action.
- Held requests remain visible for confirmation
- Failures keep their response and reason
- Retry paths stay tied to the same transaction trail
- Customer-facing web order screens fail gracefully
What clients ask
The questions agents hear every day.
Customers usually care about speed, proof, and whether a delayed request has been lost. Bingwa Flash is structured around those practical worries.
Has my bundle gone through?
Final carrier text and transaction status stay visible so the agent can answer from history instead of guessing.
Can you serve me now?
Matched payments move into a controlled queue, so busy agents can keep selling while requests run in order.
What happened to my pending order?
Held, failed, retried and verified states stay separate, which makes follow-up clearer when network prompts delay the flow.
Can I order without calling?
Agent web order pages let selected offers receive paid requests and route them into the same fulfilment trail.
Frequently asked questions
Got questions? Quick answers.
Brief answers to common questions customers and agents ask before trusting Bingwa Flash with a real order flow.
General
What is Bingwa Flash?
Bingwa Flash is an Android tool for Bingwa Sokoni agents. It helps match paid customer requests to configured offers, run guarded USSD fulfilment, and keep the final result in transaction history.
Who is it built for?
It is built for agents and bundle sellers who receive many customer requests and need a traceable way to serve them faster without losing control of the phone.
Does the agent still control the process?
Yes. Automation follows the agent's saved offers, SIM choices, retry rules, and review decisions. A request can still be held, checked, retried, or handled manually.
Automation
What happens after a customer pays?
When the signal matches a configured offer, Bingwa Flash can create a transaction, queue the correct fulfilment flow, and record the carrier response when it arrives.
What if a USSD menu changes?
The app should fail clearly, hold the request, or use a configured recovery path. It should not silently guess through a changed menu.
Can failed orders be retried?
Yes, when the agent has enabled safe retry rules. Retry notes stay attached to the same transaction so the history remains easy to audit.
Web Orders
Can customers order from a link?
Yes. When web orders are enabled, selected offers can appear online and paid requests can enter the same fulfilment trail.
Can I choose what appears online?
Yes. The agent controls which offers are published and how those offers are fulfilled.
What does a customer see when something fails?
The customer-facing flow should show a clear failure or pending state, while the agent keeps the detailed transaction record for follow-up.
Security and Privacy
Why does the app need SMS, phone, and accessibility permissions?
Those permissions are used for enabled automation paths such as reading allowed payment signals, placing USSD requests, and capturing final carrier dialogs.
Can Bingwa Flash access my M-Pesa account?
No. It reads supported SMS signals and works with configured fulfilment steps. It does not log into or control your M-Pesa account.
Are transaction records kept?
Yes. Records keep the customer, offer, status, response text, retry notes, and recovery action together so the agent can review what happened.
Support
Where should official questions go?
Email support@bingwaflash.co.ke or bingwaflash@gmail.com for account, setup, web order, or transaction recovery questions that need a written trail.
What should I include when reporting a transaction issue?
Share the customer number, amount, offer name, time, and the visible transaction status. That helps support trace the issue faster.
Can I ask before going live?
Yes. Ask first if you are unsure about permissions, SIM setup, offer mapping, or web order readiness.
Need a clear answer before setup?
Email support for account questions, web order readiness, offer mapping concerns, or transaction recovery cases that need a written trail.