Home
About us
Solutions
Case studies
News
Case study · Banking
Corporate Remote Banking: a multi-bank platform on microservices.
A multinational group providing infrastructure and technology services to financial institutions asked us to rebuild its Corporate Remote Banking platform.
outages during the rebuild
bank and multi-company, on one platform
components: front end, back office and monitoring, payment routing
The challenge
A platform ready for
new requirements and
banking standards.
The platform had to evolve to meet payment compliance and security requirements, align with interbank standards, and support the service expanding into new markets.
Regulation and security
Payment regulation and security requirements change over time. The platform had to absorb those changes through an architecture built to evolve.
Interbank standards
Aligning with the Corporate Banking interbank standards was what made the service compatible with a wider market.
How it feels to use
The interface had to simplify the daily work of the companies using it and fit into how they already manage accounts and payments.
The solution
Three components
running the service.
We built a multi-bank, multi-company Corporate Remote Banking platform on a modern interface and a microservices back end. It is organised in three components: the front-end application, the back office with monitoring, and the payment routing system.
Component 01
Front-end application
The interface through which companies reach their banking services and handle accounts and payments. Designed for daily use and to fit into their own processes.
Component 02
Back office and monitoring
The component that runs the platform day to day: configuration, control and monitoring while the service is live.
Component 03
Payment routing
The component that routes payment instructions to their destination circuits, in line with the interbank standards.
What it does well
An architecture built
to keep changing.
A microservices architecture lets each component be updated and sized on its own, which makes the platform easier to evolve and the load easier to handle.
An interface built for daily work
An interface built around what the companies actually do, simplifying the recurring operations and making Corporate Banking services quicker to use.
Microservices back-end architecture
Each component can be updated and sized independently, so features can change and load can vary without touching the whole platform.
Technologies and areas
Keep reading
Other stories
Banking · Data
Data migration machine
Automates diagnostics, normalisation and transfer of the data needed to migrate NPL portfolios and support later acquisitions.
~350 transformations · 10 verticals
The full caseBanking · Software
NPL field agents app
The Android app and the web portal, whose features partly overlapped, were brought together into one Angular Progressive Web App for the field agents and the recovery firms.
from 2 applications to 1
The full caseInsurance · Software
Regression testing
An automated testing service running since 2019, first with UFT and then with Playwright, to check that new features do not break the existing ones.
+3,700 automated tests
The full caseBanking · Software
Exchange Digital Corporate
The Corporate Banking flow backbone was rebuilt and run in parallel with the old system, handling around 1.5 million flows a day.
from 10 minutes to under 1
The full caseInsurance · Software
API Management middleware
A custom .NET API Manager with a two-way orchestrator and ELK monitoring, for near real-time policy issuing, 24/7.
+20% performance
The full caseInsurance · Software
Life AM
Running and maintaining the life insurance software: corrective and evolutionary work, plus the one-off requests.
97% SLAs met
The full caseIndustrial · Data
From on-premise to ROSA
The OpenShift environment migrated to Red Hat OpenShift Service on AWS, with automated pipelines, Infrastructure as Code and health checks on the critical components.
migrated in about 3 months
The full case