Safaricom’s annual engineering summit (Decode 4.0), held in Nairobi in early April 2026, served as the stage for the official unveiling of My OneApp, a platform designed to collapse the M-PESA app and the MySafaricom app into a single experience.
The pitch was straightforward: instead of switching between two apps to pay bills, buy bundles, check balances, and manage financial services, users would do all of it in one place.
The app had been in early access on Android for several months before the Decode 4.0 announcement. Migration started pushing to M-PESA app users from April 3rd.
By April 7th, Safaricom was publicly acknowledging on X that My OneApp had login issues and that most of the financial mini-app services were not working.
My OneApp is built on cloud-native infrastructure rated at 6,000 transactions per second and hosts more than 80 third-party services.
What went wrong at launch
The complaints that surfaced in the days following the rollout fell into four clear categories: login failures, Wi-Fi access restrictions, device compatibility gaps, and missing user data.
On login, Safaricom’s own support account on X confirmed the problem on April 4th, stating the app had login issues and that most financial mini-app services were not working.
I independently tested and confirmed the reports. I had been testing the app since March, and to my shock, I had been logged out and my transaction data, including saved favorite paybills, had not fully migrated from the M-PESA app.
A businessman in Nyanza said he had downloaded the app after an update arrived on his device but had not been able to log in at all.
My OneApp now requires Safaricom mobile data during setup and, for some users, during regular use. The SIM-binding authentication logic behind this is likely a security decision, but it creates a hard wall for Kenyan diaspora users who rely on Wi-Fi or foreign data plans.
Google Play reviews from users outside Kenya describe the experience as requiring expensive roaming just to log in. One reviewer called it a total mess, adding that it made no sense to force SIM data on users who are abroad and cannot use the app to buy roaming data in the first place, since the app itself is the tool they would normally use to do that.
Device compatibility is another friction point. My OneApp now requires at least Android 7.0 or iOS 13. The old M-PESA app ran on Android 6.0 and above. That gap may seem small in percentage terms, but at Safaricom’s user base size, it translates to a non-trivial number of people who cannot run the new app at all.
Some older Android devices are also failing to complete setup even when they meet the minimum OS requirement.
Then there is the data migration problem. Multiple users, myself included, have reported that saved paybill numbers, favorite contacts, and transaction categories did not carry over from the old app.
For a financial app where users invest in real time, losing that data without warning is a significant inconvenience. One Apple App Store reviewer noted that the app frequently drops entire transaction histories, with sometimes only a single transaction visible from the current year.
However, one of the loudest specific complaints, particularly from power users, has been about communication. Safaricom did not send email alerts, SMS notifications, or push messages in the days before the migration began.
Users who had built years of saved contacts and payment shortcuts inside the old M-PESA app woke up to a fundamentally different interface without any prior notice.
How to roll back to the old M-PESA app on Android
If you are on Android and My OneApp is not working for you, rolling back to M-PESA version 3.5.9 is currently possible. This is the last stable build before the full My OneApp migration, and it runs on Android 6.0 and above. The process requires a few steps because modern Android app packaging is not as simple as it used to be.
Step 1: Download the old M-PESA APK. Get M-PESA version 3.5.9 from APKMirror. If you run into download friction on mobile, transfer the file from a PC instead. The file is a standard APK.

Step 2: Install APKMirror Installer from the Play Store. You need this because Android’s current packaging system does not always handle manual sideloads cleanly. APKMirror Installer supports .apkm, .xapk, .apks, and regular APK files, and it explains clearly when and why an install fails.

Step 3: Uninstall My OneApp first. Android will not let you install an older package version over a newer one. Remove My OneApp completely before attempting the sideload.
Step 4: Use APKMirror Installer to install M-PESA 3.5.9. Open the installer, grant the necessary permissions, browse to the downloaded file, and follow the prompts. Once done, sign back in and resume normal use.
Step 5: Disable automatic updates for the app on the Play Store. This is the step most people miss. If you leave auto-updates enabled, Google Play will push My OneApp back to your device the next time it gets a chance. Open the M-PESA listing on the Play Store, tap the three-dot menu in the top right, and uncheck the auto-update option. Doing this per-app, rather than globally, means the rest of your apps continue updating normally.

What about iPhone?
Android users have a rollback path because the platform allows sideloading. iPhone does not work that way.
Once an iOS app has been updated, there is no practical way for an ordinary user to reinstall an older version. If you are still on the old M-PESA app on iPhone and you want to stay there as long as possible, turn off automatic updates now.
Go to Settings, scroll to the App Store section, and disable App Updates under Automatic Downloads. That buys time but it does not guarantee anything permanent.
For iPhone users who have already updated to My OneApp and are experiencing problems, the only current path is to wait for Safaricom to fix the issues or to adapt to the new interface.
Safaricom’s official position
Safaricom has acknowledged the issues without providing specific fix timelines. In an April 4th response on X, the company said it was aware of the login problems and that resolution was underway.
In a separate statement, Safaricom told TechCabal that it intends to decommission both the M-PESA app and the MySafaricom app six months after the My OneApp launch, and that it would ensure a smooth transition through support channels, rapid iteration on problems, and continuous improvement.
Safaricom is also soliciting user feedback directly within the app and through external channels. Whether that feedback loop produces visible improvements quickly enough to recover user confidence before the six-month decommission deadline is the critical question hanging over the product right now.





Leave a Reply