Mula - mobile payments across 40+ banks and service providers
Users needed to pay bills, buy airtime and send money across many separate banks and providers, each with its own interface and failure behaviour.
What we changed
- 1
Built the backend and the APIs that put every provider behind one consistent interface.
- 2
Moved payment confirmations, transaction processing and verification into background workers so the app stays responsive while they run.
- 3
Took on continuous production support, so failures are found and resolved by us rather than reported by users.
Qualitative evidence
What changed operationally
- One app covers providers that would otherwise each be a separate errand.
- Slow provider calls no longer block the person using the app.
- Production issues have an owner outside the client’s own team.
Evidence standard: These are delivered workflow and operating-state changes supported by the project record. They are qualitative results, not estimated percentages or modelled savings.
What Devntech continued to own
- Production support
- Provider integrations
- Background job infrastructure
- Issue resolution
This is what we mean by
Operate & protectMore like this
Internal software · Integration
e-Locker
Smart locker systems for asset management
Internal software · Integration
CTO Connection
Community for engineering leadership
Got a workflow like Mula’s?
Describe the process. We come back with what it costs today, what could be automated and what we would build first.
- For established businesses from $5M in revenue, and products that are live, business-critical or already depended on
- No long-term commitment
- Start with one workflow or one system
- Keep ownership of everything we build