Technology Platforms

Banking Product Factory · BX-PF

Define financial products, conditions and calculation rules across banking systems.

BX-PF is required in BX-CBP-based offerings and can also be evaluated separately alongside another vendor’s core.

BX-PF product master — Four product-team roles maintain one product definition for selected core, channel and partner systems. Interfaces are agreed per engagement.

02 / Role and where it applies

Where BX-PF sits

Product master

Define product attributes, fee schedules and interest rules in BX-PF, and reuse them across connected core, channel and partner systems.

Inside BX-CBP-based offerings

BX-PF is a required product in every BX-CBP-based suite and solution.

Beside another core

BX-PF can be licensed on its own and connected to a core from another vendor.

For product teams

Planning, design, configuration and distribution are separate roles, each with its own permissions.

03 / Key functions

What BX-PF does and how it works

Product definition and lifecycle

Plan, design, configure, distribute and retire a product in one system.

Condition templates

A product is a set of condition values in templates, so a new product type within supported templates can be configured without a model change.

Configuration and simulation

Rates, fees and conditions set within template ranges and simulated before launch.

Multi-channel distribution

Distributor sends a product to selected systems with validation and change tracking.

Classification and search

Risk, compliance, seller, buyer and finance views; search by keyword or customer attributes.

Unified fee management

One fee model shared with the core, with what-if simulation.

How the product factory works

From idea to a sellable product, in four steps and one master record. A product is a set of conditions: Planner records the project, Designer builds the templates, Configurator sets the values and Distributor sends the definition to core, channel and partner systems.

Plan

Spec, roadmap and product taxonomy

Design

Parameter modeling and template binding

Develop

Configurator-driven rule assembly

Deploy

Multi-channel rollout pipeline

Product API

Canonical record distribution

Why BX-PF

Why do banks put product definition in a factory instead of in core code?

01Define once, use everywhere

Define product attributes, fee schedules and interest rules in BX-PF, and reuse them through standardised APIs across connected core, channel and partner systems. These systems read one product master to reduce differences between separate product tables.

02One operating model from planning to distribution

Planner holds the project, Designer the templates and rules, Configurator the sellable products, Distributor the checked push to target systems. Per-role permissions let partners define products within bank-set limits.

03Fee and interest simulation before launch, within supported configuration scope

Fee and interest calculation lives in BX-PF, not core code; the core calls it. Product teams simulate pricing, eligibility and accrual before launch and change rules by configuration.

04Condition templates carried over from earlier sites

Condition templates built across deposits, loans, cards and payments at earlier bank sites ship with the product. A new site starts from them; validation and cloning reduce manual errors.

What BX-PF does

Six capabilities, each one a task a product team performs.

01Product definition and lifecycle management

One system plans, designs, configures, distributes and retires a product, and tracks packages, relationships and classification with it.

02Condition templates and calculation units

Products are condition values inside Designer’s templates, so a new product type within supported templates can be configured without a model or program change.

03Rate, fee and condition configuration with pre-launch simulation

Configurator sets rates, fees and conditions within template ranges, clones products and simulates fees and interest pre-launch.

04Multi-channel deployment with change tracking

Distributor pushes a product to selected targets with validation and change tracking, so connected channels read one master.

05Multi-view classification and search

Products carry risk, compliance, seller, buyer and finance classifications and are found by keyword, natural language or customer attributes. Availability and supported scope of natural-language search are confirmed for the proposed version.

06Unified fee management and AI-assisted entry

One fee model, shared with the core, with what-if simulation; AI-assisted entry captures product terms from source documents. Availability and supported scope of natural-language search and AI-assisted entry are confirmed for the proposed version.

04 / Relation to other offerings

How BX-PF relates to other products

BX-CBP

BX-CBP-based suites and solutions read product definitions, conditions and interest and fee formulas from BX-PF.

BX-CBB and BX-RDF

Together with BX-PF they form the reusable banking engine underneath BX-CBP.

BX-M / BX-CM

A separate product; BX-CBP-based offerings require BX-PF and one Java development platform.

BX-Payment and Bankware SCF

Solutions on their own Main Products do not require BX-PF.

BX-CBP-based suite or solution

BX-CBP · Main Product
BX-CBB technical foundation, 11 components; Business Service Library, 11 domainsBX-PF · Required
Product definitionBX-M or BX-CM · Required
One Java development and runtime platform matched to the environmentBX-I · Optional
Interfaces to channels and partners; replaceable by a third-party product

Bankware Mobile is not part of this composition. These requirements apply to BX-CBP-based offerings.

05 / Conditions and dependencies

What applies when you adopt BX-PF

Availability

Sold separately in Korea, Japan and Southeast Asia.

With BX-CBP

Included as a required product of the suite or solution.

Beside another core

The core calls BX-PF for product conditions and fee and interest calculation; the interfaces are agreed per engagement.

Deployment environment

Confirmed per engagement.

A new product type can be configured within supported templates. Calculation integration, and availability and supported scope of AI-assisted entry and natural-language search, are confirmed for the proposed version.

06 / Evidence