Quick Answer
When a Bingwa automation app fails, identify the exact stage: did it detect the payment, match the offer, choose the correct recipient, open the USSD menu, receive a response, and save the final status? Check the correct SIM, SMS or notification permissions, sender filters, battery restrictions, accessibility service, network signal, offer mapping, and whether Safaricom changed the live menu.
First classify the failure
Symptom
Payment arrived but app did nothing
Likely area
SMS or notification detection, sender filter, background service
Symptom
Wrong package selected
Likely area
Amount-to-offer mapping or stale catalogue
Symptom
USSD opened on wrong SIM
Likely area
SIM-slot routing
Symptom
USSD stopped halfway
Likely area
Accessibility, timeout, screen state, or menu change
Symptom
Order says pending after success
Likely area
Result parsing or logging
Symptom
Same order ran twice
Likely area
Duplicate protection or retry logic
Check payment detection
- Confirm the payment notification or SMS actually reached the phone.
- Confirm the app recognizes the current sender ID and wording.
- Confirm SMS or notification permission remains enabled.
- Confirm Android has not stopped the background service.
- Test with one controlled small transaction.
Check order and offer matching
Confirm the paid amount maps to only one active package, and confirm the recipient source. If payer and recipient can differ, an M-Pesa message alone may not contain enough information to fulfil safely.
Check USSD execution
Test the same recommendation manually. If manual access fails, the automation app is not the first problem.
- Correct operational SIM is active and selected.
- The line has signal and can manually open the Bingwa menu.
- Accessibility or required service is running.
- No call, popup, or screen overlay interrupts the flow.
- The live menu still matches the configured sequence.
Check Android battery and background controls
Review battery optimization, auto-start, background-data, notification, and foreground-service settings. Phone brands use different names. Change one control at a time and retest rather than disabling every protection blindly.
Stop unsafe automatic retries
If the result is unknown, pause the job and verify before retrying. Repeated USSD attempts can produce duplicate recommendations or trigger an already-recommended response.
Prepare a useful support report
Do not send PINs, OTPs, full M-Pesa messages, or customer data to an unverified support contact.
- App name and exact version.
- Phone model and Android version.
- SIM slot used.
- Exact time and masked order reference.
- Last successful stage.
- Exact error or screen response.
- Whether manual USSD worked.
Official References
Use Safaricom's official pages for current service terms and account-specific support.
- Safaricom Care guidance to access Bingwa Sokoni through *180*5#
- Safaricom guidance on who can join Bingwa Sokoni
- Safaricom M-PESA Business Till information
- Safaricom M-PESA Business Till guide
- Safaricom M-PESA Business channels and portals
- BingwaOne official website and agent tools
- BingwaOne Bingwa agent guide library
Frequently Asked Questions
Why did the app stop after a phone update?
Android may have reset permissions, battery exemptions, accessibility, or background-service behaviour.
Why does payment detection fail?
The sender ID or message format may have changed, permission may be disabled, or the app may be stopped in the background.
Should I reinstall immediately?
No. First preserve logs and configuration, identify the failed stage, and confirm whether the publisher recommends reinstalling.
Who should I contact?
Contact the specific app publisher for app issues and Safaricom for merchant, menu, line, or provider-controlled problems.
BingwaOne
Turn the guide into a simpler daily workflow.
Use agent posters, a mobile storefront, WhatsApp automation, SMS, and business records from one workspace.
Create a free agent account