Case study · Banking and payments
Jana Finance Bank, JFS banking portal
Netbanking portal and companion wallet apps.
- Client
- Jana Finance Bank
- Service
- Design and development
- Sector
- Banking
- Scope
- Web portal and wallet apps
At a glance
What was delivered
The web portal and the companion wallet apps came from one engagement rather than two vendors.
The complete retail journey rather than a subset with the awkward parts left in a branch.
One coherent experience across the portal and the wallet apps.
Built for retail customers, which sets the usability bar rather than the feature count.
The brief
A bank's portal is the bank, for most customers
For a retail customer, netbanking is not a channel alongside the bank. It is the bank. Almost every interaction that used to require a branch now happens there, which means the portal has to cover the full servicing journey rather than the easy eighty percent.
Delivering that alongside companion wallet apps raises the harder question: the same customer moves between the portal and the wallet and expects one bank, not two products that happen to share a logo.
Full coverage is the requirement. A journey that ends at a branch visit has not been digitised.
The build
Why one delivery matters here
Wow Labz designed and developed the complete netbanking web portal for JFS, along with the companion wallet apps. Holding both in one delivery is the substantive point rather than a scope note.
Banking products split across vendors tend to diverge in the places customers notice most: what a transaction is called, how a payee is added, which limits apply where. Building the portal and the wallets together means those decisions get made once.
The result is one delivery across web and mobile covering the full account servicing journey for retail customers.
Scope
What one delivery covered
The netbanking web portal
The complete web experience for JFS, covering retail account servicing end to end rather than a subset of transactions.
Companion wallet apps
Mobile wallets built alongside the portal, so the mobile experience is part of the same product rather than a later port of it.
One servicing journey
Designed as a single journey across web and mobile, which is what stops a customer meeting two different banks depending on the device.
Stack
What it was built with
- Web portal
- Native mobile
- Netbanking
- Payments
Questions
The JFS portal, answered
What did Wow Labz build for Jana Finance Bank?
The complete netbanking web portal for JFS, designed and developed end to end, along with the companion wallet apps.
Does it cover the whole customer journey?
Yes. The delivery covers the full account servicing journey for retail customers, across the web portal and the wallet apps.
Why build the portal and the wallets together?
Because a customer moves between them and expects one bank. Splitting them across deliveries is how naming, payee management and transaction limits start to diverge in ways customers notice.
Who is it built for?
Retail customers, which sets the usability requirement rather than the feature count.
Keep reading
Related work
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.