The product line is consolidated to three. BX Core Banking Platform is the on-premise core for institutions that need control over the deployment environment — typical implementation runs twelve to eighteen months and the customer or its system integrator manages day-to-day operations. BADA is the cloud-native SaaS core for institutions that want to focus on business configuration and channel integration rather than infrastructure operations — typical go-live is five to six months and Bankware operates the platform. BX Payment Suite is the e-wallet and payment platform — two to three months go-live, ISO 20022 compliant, with deep regional payment-standard integration including PromptPay, DuitNow, InstaPay, and Myanmar FAST.
THREE PRODUCTS, FOUR PATHS
Three core products, four implementation paths — chosen by the institution you are today.
Bankware delivers three product lines — BX CBP on-premise, BADA SaaS, BX Payment Suite — across four implementation paths chosen to match the institution's existing footprint, regulatory posture, and time-to-market constraint.
The product line
The implementation paths
Four implementation paths organize the engagement model. Core modernization is the path for established institutions replacing aging legacy cores — OK Savings Bank completed a full core replacement in thirteen months under this path. Greenfield internet bank is the path for new digital-banking license applicants — K-Bank built Korea's first internet bank in eleven months under this path, on CBP. Greenfield SaaS is the path for digital-banking license applicants and digital sub-brands that want the SaaS operating model — typical timeline five to six months on BADA. Card system replacement is the path for institutions modernizing card and capital systems — Hyundai Card and GMO Payment Gateway are reference cases under this path on H-ALIS and the card variant.
Methodology
Implementation methodology is hybrid — Waterfall stability for requirements and design, Agile sprints for development. Six phases run from Initiation through Analysis and Design, Development, Testing, Go-Live, and Stabilization, with five milestone reports (M1 to M5) at the phase transitions. A Migration Track runs in parallel for data migration. Component reuse drives the effort estimate: sixty percent of typical requirements are met by existing components, twenty percent through assembly, and ten percent require custom development. Hypercare runs three to six months post go-live. Implementation deliverables, fit-and-gap analysis, configuration design, and the test strategy are made available to system integrator partners under the certification programme.
Continue the conversation