A mobile wallet that moved cash into the app.
This mobile banking app development case study covers a commercial bank in Africa, where most transactions were still done in cash. We built a customer wallet app, an admin panel and a payment gateway on .NET microservices and Azure. The project is live in production, with change requests still coming in. Bank administrators approve providers, set roles and tiers, and see full audit logs.
| Before | With the new platform | |
|---|---|---|
| Everyday payments | Most transactions were done in cash | Send, request, pay bills and pay merchants from the app |
| Reach | Limited financial access in remote regions | A mobile banking experience for customers in remote regions |
| Admin work | Manual, time-consuming administrative operations | Users, providers, tiers and notifications run from one admin panel |
| Notifications | No real-time notification system | Email, SMS and push, sent instantly, scheduled or in bulk |
| Partner checks | No secure real-time way to verify partners | Partners verified with API keys on every call |
| Fraud | Repeated cases of fraudulent wallet deductions | Balance checks, dual-side validation and device-history monitoring |
The customer app, the admin panel and the gateway work as one platform. The bank stays in control of who gets in and what gets approved.
The wallet app has passed 100K+ downloads, and it's still live and taking change requests.
Real-time reporting in the admin panel cut manual errors significantly.
Thousands of bulk notifications went out with zero downtime, and the platform scaled through traffic spikes without slowing down.
Bank administrators approve providers, set roles and tiers, and can see full audit logs.
Transactions and failures are logged, and security logs automatically mask passwords and account numbers.
Partner verification, balance checks before payment and device-history monitoring sit in the flow itself.
A customer wallet app, an admin panel and a wallet payment gateway. The app covers P2P transfers, bill payments, merchant QR payments, remittance, savings goals and card management.
Yes. It's in production and the team still ships change requests.
The platform is built as .NET microservices on Azure, using Azure Service Bus, Azure AD B2C and Azure Key Vault, with RabbitMQ, an Ocelot API gateway and SQL databases. The admin panel adds Dapr, Redis, Consul, Angular and Power BI reports.
Bank administrators. They approve bill providers, set roles and tiers, run notifications and review audit logs from the admin panel.
Tell us what your customers and your admin team still do by hand. We'll walk you through how a build like this would work.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.