Case study · Banking and payments
Wibmo payments app framework
An engine that auto generates mobile wallets for banks.
- Client
- Wibmo, a PayU company
- Service
- Framework development
- Sector
- Banking and payments
- In production with
- HDFC, Bank of Baroda, IDBI
Impact
What the engine changed
A bank wallet went from a bespoke build to a configuration exercise.
Delivery time for a new branded wallet fell from twelve weeks to under two.
Team size per wallet halved, because most of the work stopped being code.
Shipped with HDFC Bank's PayZapp, Bank of Baroda's MClip and IDBI Bank.
The brief
Every bank wants the same wallet, in its own colours
Wibmo builds payment infrastructure for banks. Every bank client wanted a mobile wallet, and every one of those wallets was substantially the same product wearing different branding, with different back-end endpoints behind it.
Built the obvious way, that means a new project per bank: twelve weeks, two developers, and a codebase that diverges from its siblings the moment it ships. The maintenance cost of that arrangement grows with every client won, which makes commercial success into an engineering problem.
The same product ten times is not ten projects. It is one product and ten configurations.
The build
Turning a build into a configuration
The framework's whole claim is that a new wallet stops being a software project. Branding, screens, endpoints and authentication all become configuration the engine reads, which is why the number moved as far as it did: 85% less development time, twelve weeks down to under two, and the team per project halving from two developers to one.
The knock-on effects matter as much as the headline. Faster go-to-market for each bank, lower maintenance because there is one codebase instead of a family of drifting forks, and customisation that no longer requires touching code.
It is in production with banks including HDFC Bank (PayZapp), Bank of Baroda (MClip) and IDBI Bank.
How it works
Four pieces of the engine
Config-driven UI customisation
Branding is defined in a plist configuration file rather than in code, so a bank's identity is data the app reads, not a fork of the app.
Automated UI component builder
Screens are generated dynamically from configuration, which is what removes the per-bank build rather than merely shortening it.
Generic API handler
One standardised layer for API requests and authentication, including two-factor, so each bank's back end plugs in instead of being integrated against.
Object handler
A unified data processing layer, so the parts of a wallet that are genuinely identical across banks are written once.
Stack
What it was built with
Questions
The framework, answered
What does the Wibmo framework do?
It automatically generates branded iOS mobile wallets for banks, turning what had been a bespoke build per bank into a configuration exercise.
How much faster is it?
85% less development time. A new branded wallet went from twelve weeks to under two, and the team needed per project fell from two developers to one.
Which banks use it?
It is in production with banks including HDFC Bank (PayZapp), Bank of Baroda (MClip) and IDBI Bank.
How does the customisation work without code changes?
Branding and configuration live in a plist file the engine reads, screens are generated dynamically by an automated UI component builder, and a generic API handler standardises requests and authentication so each bank's back end plugs in rather than being integrated against.
Let's talk
Got a developer product nobody finishes integrating?
Tell us what you are building. We will tell you how we would ship it.
