Channel side (MCA)
Mobile, internet, teller, ATM and call-centre channels connect to the core through one adapter layer.
Technology Platforms
Integration Platform · BX-I
Connect your banking ecosystem.
BX-I connects channels, applications and external institutions through configurable data exchange. It is optional in BX-CBP-based offerings, where an agreed integration product may be retained, and can also be evaluated independently.
02 / Role and where it applies
Where BX-I sits
Inside the bank (EAI)
Core, product factory, general ledger, card and data systems exchange messages through registered routes.
Outside the bank
Payment networks, card schemes, credit bureaus and regulators connect through external interfaces.
Optional in offerings
Included when Bankware supplies the interface layer, and replaced when the bank keeps its own product.
03 / Key functions
What BX-I does and how it works
Tiered routing
External channel, flow processing and internal channel tiers, each handling its own protocol.
Registration first
Registered interface parameters drive execution; custom flows only for bank-specific patterns.
Web administration
Routing rules, interface definitions and flow status managed from a web console.
Monitoring and re-processing
Volumes and errors in one place; failed messages re-processed without touching the base flow.
Protocols and formats
Built on Apache Camel, Netty, Spring and Apache Kafka, with asynchronous transformation.
Test before production
Changes validated in a test simulator and an integrated test environment first.
How BX-I sits between systems
Three tiers, three flows, one registration for every interface. External channel, flow processing and internal channel tiers receive, transform and deliver a request to the core. Error flow is its own layer; asynchronous handling separates message processing from counterparty response, within the configured flow.
Why BX-I
Why do banks put channel, internal and external interfaces on one configurable layer?
01Multi-protocol routing through a tiered structure
Each tier handles its own protocol, so a new channel or counterparty is added at the edge, not in the core. Base, message and error flows are separate layers.
02Manage routing rules from the browser
Routing rules, interface definitions and flow status are managed from a web console. Registering interface information sets up standard patterns, so operations changes a route without a development release.
03Integration with minimal programming
Registered parameters drive execution; custom Camel flows are written only for bank-specific patterns. Changes are validated in the test simulator and integrated test environment before production.
04One management plane across internal, external and channel systems
Internal, external and multi-channel integration are controlled and monitored centrally. Operations sees every interface, volume and error flow in one place, with capacity confirmed for the target environment.
What BX-I does
Six capabilities, covering every direction data leaves or enters the core.
01Multi-channel integration (MCA)
One adapter layer connects mobile, internet, teller, ATM and call-centre channels to the core, transforming each format.
02Enterprise application integration (EAI)
Core, product factory, general ledger, card and data systems exchange messages through registered routes, not point-to-point links.
03External financial interfaces
External interfaces cover payment networks, card schemes, credit bureaus and regulators; local rails such as Philippine InstaPay and PESONet are connected in delivery work.
04Monitoring and operations
A web console shows definitions, routes, volumes and errors; failed messages are re-processed without touching the base flow. Re-processing is an integration operation. Retry controls and responsibility for financial transaction state, duplicate handling, reversal, settlement and reconciliation are agreed separately for each interface.
05Protocol and format support
Built on Apache Camel, Netty, Spring and Apache Kafka, transforming between protocols and message types asynchronously.
06Optional, and replaceable by a third-party product
Included when Bankware supplies the interface layer, replaced by the bank’s existing product, or proposed alone beside another core.
04 / Relation to other offerings
How BX-I relates to other products
BX-CBP
BX-I is the optional integration product of BX-CBP-based suites and solutions.
Third-party products
A bank’s existing interface product can take its place in an offering.
Other cores
BX-I can be proposed on its own beside another core.
Local rails
Connections such as Philippine InstaPay and PESONet are set up in delivery work.
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
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
05 / Conditions and dependencies
What applies when you adopt BX-I
Availability
Sold separately in Korea, Japan and Southeast Asia.
Interface list
The interfaces to connect are agreed per bank at scoping.
Message standards
ISO 8583 card authorization messages are supported, and ISO 20022 message brokers connect on the same layer.
Deployment environment
Confirmed per engagement.
Re-processing is an integration operation. Retry controls and responsibility for financial transaction state, duplicate handling, reversal, settlement and reconciliation are agreed separately for each interface.
06 / Evidence
Card authorization interfaces on BX-I
BC Card
Card authorization interfaces on BX-I
BX-I CARD AUTHORIZATION INTERFACES
BC Card rebuilt external, internal and channel interfaces for card authorization on BX-I, replacing its Stratus-based external system with x86 Linux.
BX-I also delivered to: Hyundai Card · OK Savings Bank · LINE Bank Taiwan
07 / Contact
Tell us about your interface list, and we will show it on BX-I.
Describe your channels, internal systems and external counterparties, and the interface product you use today.