Skip to main content
Bankware Global
PRODUCTS OFFERING

Core Banking Suites

A core that fits how your bank operates today and how it plans to grow.

Start with how customers will reach the bank. A retail bank can renew its core while keeping its existing channels. A digital bank can launch with mobile and internet banking included. For a rural bank evaluating BADA, the decision also turns on how the institution and the SaaS operator will share operating responsibilities.

Compare suitesContact Sales
Your institution

Find the right starting point

  • Your core needs to serve a different mix of corporate, retail or digital banking business.
  • Product, customer and accounting information is spread across systems that need to work together.
  • Your institution needs to choose between an institution-specific core implementation and a SaaS service.
Your decisions

Compare the decisions that matter

01

Match the institution

Compare suites by the customers, banking domains and service channels you need to support.

02

Understand the operating model

Distinguish BX-CBP-based implementations from BADA’s SaaS service, including the different product composition and operating responsibilities.

03

Define a practical scope

Identify the banking domains to introduce or modernise and the systems to retain before planning interfaces and migration.

Compare suites

Four suites for different banking models

BX-CBP

Commercial Bank Suite

Who it’s for
Commercial banks serving corporate and retail customers.
What you can do
Connect deposits, lending, trade finance, foreign exchange, payments, treasury and accounting.
Why choose it
You need corporate and retail banking domains to work together on one core.
Explore Commercial Bank Suite
BX-CBP

Retail Bank Suite

Who it’s for
Retail and savings banks.
What you can do
Connect retail products, customer relationships and everyday banking services, including agency banking.
Why choose it
You need a retail core and want to choose whether to keep or add customer channels.
Explore Retail Bank Suite
BX-CBP

Digital Bank Suite

Who it’s for
Digital banks and institutions building a digital-bank operating model.
What you can do
Connect digital customer journeys with core banking services.
Why choose it
You want the core and digital customer channels delivered together.
Explore Digital Bank Suite
BADA

SaaS Core Banking Suite

Who it’s for
Rural banks and microfinance institutions.
What you can do
Customer, deposit, loan, collateral, teller and accounting services.
Why choose it
You want a SaaS core for rural banking or microfinance operations.
Explore BADA

Scroll horizontally to compare all four suites. Row labels stay in view.

Banking capabilities and applications across Commercial, Retail, Digital and BADA. Each cell states Included, Optional, Not included or To confirm.

Core Banking Suites at a glance

Capability or application		CommercialBX-CBP-basedRetailBX-CBP-basedDigitalBX-CBP-basedBADASaaS
Banking capabilities
Customer management / CIFIncludedIncludedIncludedIncluded
Deposits / CASAIncludedIncludedIncludedIncluded
LendingIncludedIncludedIncludedIncluded
  • Included
  • Optional
  • Not included
  • To confirm
Two delivery routes

Understand the foundation and delivery model

Commercial · Retail · Digital

BX-CBP-based implementations

Product foundation
BX-CBP provides the core foundation and reusable banking business services for Commercial, Retail and Digital Bank Suites.
Product composition
BX-PF for financial product definitions and an applicable BX-M or BX-CM Java development platform are required for the BX-CBP-based composition. BX-I is optional; an agreed third-party integration product may connect retained systems instead.
Deployment environment
On-premises or dedicated cloud environments are planned for the institution.
Operations and support
Hosting, platform operation and support responsibilities are agreed for the implementation.
Implementation scope
Confirm supported technology combinations, interfaces, migration and additional development during design.
Availability and scope
Supported versions, product composition and implementation scope are confirmed for each engagement.
Rural banks · Microfinance institutions

BADA SaaS service

Product foundation
BADA is separately composed for SaaS delivery and microfinance operations.
Product composition
Banking modules, institution configuration and service operations form the BADA SaaS composition.
Deployment environment
Hosting and data residency are defined in the service arrangement.
Operations and support
Platform maintenance, service-operator support and the institution’s banking responsibilities are defined in the service arrangement.
Implementation scope
Agree activated modules, institution configuration, interfaces, onboarding and migration requirements.
Availability and scope
Choose the modules and service arrangement for your institution.
Delivery models

Choose a model, then follow four phases

On-Premises
Institution-controlled infrastructure
  • Deploy on infrastructure controlled by the institution.
  • Agree platform operations and support responsibilities.
  • Confirm supported technology combinations during design.
Best for
Institutions retaining their own infrastructure.
Dedicated Cloud
A dedicated cloud environment
  • Plan a dedicated cloud environment for the institution.
  • Agree hosting, platform operations and support responsibilities.
  • Scope interfaces, migration and additional development.
Best for
Institutions evaluating dedicated cloud deployment.
Cloud Banking Service (BADA SaaS)
Separately composed SaaS service
  • Agree banking modules and institution configuration.
  • Define hosting and data residency in the service arrangement.
  • Confirm service-operator support and the institution’s banking responsibilities.
Best for
Rural banks and microfinance institutions evaluating BADA.
Adoption phases
  1. Phase 1

    Insight & Blueprint

    Banking scope, retained systems and deployment requirements.

  2. Phase 2

    Agile Build & Validation

    Product configuration, agreed extensions, interfaces and validation.

  3. Phase 3

    Migration & Go-live

    Data mapping, migration rehearsals, reconciliation and cutover.

  4. Phase 4

    Empowerment & Evolution

    Knowledge transfer and operational handover.

TECHNOLOGY STACK

Technology choices for your implementation

Supported technology combinations and versions are confirmed for each engagement. BADA’s SaaS composition is defined separately.

Bankware Platform

For BX-CBP-based Commercial, Retail and Digital Bank Suites. Product composition is confirmed for each engagement.

  • BX-CBPMain Product
  • BX-PFRequired
  • BX-M or BX-CMRequired
  • BX-IOptional

BX-I may be replaced by an agreed integration product. BX-CoCore requires separate technical assessment; BADA has its own SaaS composition.

  • BX-CoCoreAlternative Main Product
  • BADASeparate SaaS composition

Technology Foundation

Language
  • Java 21 (OpenJDK / Oracle JDK)
Frameworks
  • Spring (MVC / Security / JPA / Hibernate)
  • Spring Batch
  • Apache Camel
  • Netty4
  • MicroProfile LRA
Application servers
  • WebSphere
  • WebLogic
  • JBoss
  • Resin
  • Springboot 3 (internal WAS)
Messaging
  • Apache Kafka
  • ActiveMQ
Databases
  • Oracle 12c / 19c
  • MySQL Enterprise 8.x
  • RDS for MySQL
  • DB2
  • Oracle RAC
  • Data Guard
  • CDC
Cloud and DevOps
  • Kubernetes
  • Docker
  • VM
  • Amazon EKS
  • Jenkins
  • Terraform
  • ELK
Registry
  • GitLab
  • Nexus
  • Amazon ECR
Historical delivery references

Explore relevant delivery experience

OK Savings Bank

A next-generation core for savings banking

Retail and savings banking

OK Savings Bank’s next-generation core was delivered under the former BX-RBS name using BX-CBP and related platforms.

Explore OK Savings Bank’s core system

K-Bank

Core banking for a digital-bank launch

Digital banking

K-Bank’s core banking delivery used BX-CBP and BX-PF for its launch.

Explore K-Bank’s launch
Contact Sales

Discuss your core banking priorities

Tell us about your institution, target customers, banking domains, current systems and preferred operating model. We can help identify the suite and implementation questions to evaluate.

Contact Sales