Case Study
How Vivasoft Helped City Bank Eliminate Third-Party Licensing Costs Through a Unified Banking Platform

Overview
City Bank PLC was founded in 1983 as Bangladesh's first private commercial bank. Over the past four decades, it has grown into one of the country's most prominent financial institutions, serving millions of individuals and businesses across a wide range of banking products.
As the bank expanded, its operations became increasingly dependent on two third-party platforms - Finacle and Ababil. These platforms handle everything from treasury bonds and loan approvals to account management and card processing. The problem was the pricing model. Both platforms charged per user, so every time City Bank added staff or expanded access, the licensing cost went up with it.
To solve this, City Bank started building a unified banking platform that would bring all these operations under one system. The platform had a wide scope, covering over 30 modules, and the internal team needed more engineers to keep up with the timeline. That's when they approached Vivasoft for staff augmentation support.
Vivasoft joined the project in January 2025, embedding six engineers directly into City Bank's development team. The engineers worked alongside City Bank's team to build and improve the platform, following the bank's technical direction while actively contributing to development. The project is still ongoing, with two Vivasoft engineers continuing to work on the platform today.
Technologies Used
Java
Spring Boot
Python
Next Js
Oracle
Oracle
Elasticsearch
Redis
kafka
Cashin
Challenges faced by the Client
When City Bank started building the unified banking platform, they were dealing with a set of interconnected problems that had built up over years of relying on third-party systems
1.A licensing model that kept getting more expensive
Since both Finacle and Ababil charged per user, the cost of running these platforms grew every time the bank expanded its team or increased access. City Bank had over 30 modules tied to these platforms covering treasury bonds, loans, account management, cards, cheques, and more which meant the licensing exposure was significant and growing.
2. No single place to see the full picture
3. Customers with multiple accounts were hard to manage
4. The platform scope was too large for the existing team alone
The platform was not a small build. It needed to cover account lifecycle management, treasury operations, loan workflows, card and cheque processing, and a full 360-degree customer view, among other things. The internal team had the direction, but they needed more engineers to match the pace the project required.
5. Requirements kept shifting during development
As development progressed, stakeholder discussions led to changing priorities and evolving requirements. The team working on the platform needed to stay flexible while still keeping the project on track.
How Vivasoft Solved It
1. Adding engineering capacity quickly
2. Building the API layer that reduced licensing costs
One of the core architectural decisions in the platform was to route all banking requests through it first, before anything reaches Finacle or Ababil. The platform logs the request internally, then sends only what is necessary to the third-party platform. Because of this, Finacle and Ababil only ever see a single user making requests on their end, regardless of how many people are actually using it. This approach significantly reduces per-user licensing costs.
3. Building the 360 module for unified customer identity
4. Taking ownership of key modules
Vivasoft’s engineers built and improved several core areas of the platform, including account opening, account maintenance, account closing, and treasury bond management. These now run through it rather than being handled separately through legacy platforms.
5. Staying adaptable as requirements changed
Core Features of The Unified Banking Platform
Unified multi-account management
360-degree customer identity
Treasury bond management
The full process of handling treasury bond requests, from submission through approval, runs within the platform.
Account lifecycle management
Loan workflow management
Loan requests go through a structured process within the unified banking platform, including submission, processing, and multi-level approval routing.
Card and cheque handling
API gateway to legacy systems
The platforma sits between City Bank’s operations and Finacle or Ababil, acting as the single point of contact with those systems. This reduces dependency on them while keeping existing infrastructure in place.
Performance infrastructure
Dedicated Experts
| Resources | Count |
|---|---|
| Backend Developers | 5 |
| Full-stack Developers | 1 |
Project Duration
Project Start Time
Jan 2025
Project Status
Continuing
What's Next
The unified banking platform is still in active development, and the scope continues to grow. City Bank plans to bring all remaining operational modules into this over time, which would significantly reduce and eventually eliminate their reliance on Finacle and Ababil for per-user licensing.
On the partnership side, City Bank has indicated interest in working with Vivasoft on additional projects once the current phase progresses. The work on this platform has built a level of familiarity and trust that makes expanding the engagement a natural next step for both sides.
As more modules move into the platform and the 360 customer identity tools mature, the platform is also expected to improve the overall experience for City Bank’s customers. It will make service faster and more consistent across the board.










Thinking About Consolidating Your Banking Systems?




