Credit-card issuer processing for financial institutions running a card business.
Built on BX-CBP, member servicing, billing and payment-related processing share configurable product rules. Issuers can reflect changes in card products and policies, with external system connections defined for the delivery.
Billing and paymentsMerchant and brand settlementRisk and receivablesProduct rules and controls
02 / Situations
Are these obstacles affecting your card business?
01
Card product and policy changes affect multiple operating functions.
Products, services and conditions may be managed separately, making it difficult to identify which business rules are affected when a product or policy changes.
02
Member servicing lacks continuity.
Customer details, transaction history and notes may be difficult to review together. Staff need sufficient operational context when returning to a member-service task.
03
Billing and settlement are difficult to organise.
Member payments, merchant information and settlement by card brand require distinct responsibilities, records and processing arrangements.
04
Operational changes require clear controls.
Teams need to review the impact of rule changes, determine who can perform specific actions, control the display of sensitive information and trace what has changed.
03 / Value
Support more structured and controlled card operations.
01
Manage product and policy changes
Organise products, services and applicable conditions into maintainable rules that support new products and policy changes.
How it works
Offer definition: Product · Services · Conditions
Standard templates, condition groups and graphical rule-maintenance tools provide a shared environment for supported business-rule changes. New conditions can be simulated before application to help assess their potential impact.
Requirements beyond the supported configuration capabilities are evaluated separately.
02
Maintain continuity in member servicing
Bring customer information, transaction history and related notes into the operational context for ongoing member servicing.
How it works
Member context: Customer record · Transactions · Notes and work history
Centrally maintained customer and member records work alongside tabbed screens, work history and screen reactivation to help staff resume tasks.
Support staff operations, with cardholder mobile applications and self-service portals scoped separately.
03
Organise billing and settlement operations
Support the management of member billing and payments, merchant-related settlement and card-brand settlement responsibilities.
How it works
Distinct responsibilities: Member billing · Merchant settlement · Brand settlement
Maintain related business records and configure payment-allocation categories and priorities.
Detailed merchant and card-brand settlement rules and external connections are determined for each project. These issuer-side functions do not include acquiring or card switching.
04
Review and trace operational changes
Use change simulation, permissions and audit records to support control over business-rule changes.
How it works
Change governance: Permissions · Impact simulation · Change history
Review potential impacts before applying conditions, allocate menu and button permissions, configure how sensitive information appears and retain rule-change history.
Apply these controls alongside the institution's compliance policies and responsibilities.
04 / Scope and functions
Core capabilities organised around issuer operations.
Explore five capability areas for credit-card issuer operations.
Explore detailed functions
Customers, members and issuanceCustomer and member information, acquisition, examination, issuance, history and notes6 functions
Customers, Members and Issuance
Acquisition management:Manage the recruitment of new card members.
Examination and issuance:Process credit-card application examinations and card issuance.
Member management:Maintain card-member information.
Customer information:Maintain customer records centrally and organise customer information in a database.
Credit information:Manage coded credit information relating to members and cards.
History and notes:Store transaction history and related notes for display in the operational interface.
Transaction records, billing and paymentsCard-usage records, member billing, incoming payments and allocation rules5 functions
Transaction Records, Billing and Payments
Sales reception:Receive and process card-usage records.
Member billing and payments:Manage member billing and incoming payments.
Payment allocation:Configure the priority in which incoming payments are applied.
Allocation categories:Adjust allocation rules for late-payment damages, usage fees and principal.
Segment-based allocation:Adjust allocation priorities by customer segment.
Merchant information and settlementMerchant information and merchant- and brand-related settlement3 functions
Merchant Information and Settlement
Merchant information:Maintain information relating to merchants.
Merchant settlement:Process settlement relating to merchant transactions.
Brand settlement:Manage settlement by card brand.
Risk, receivables and servicesRisk-related operations, card receivables, member services and common operations4 functions
Risk, Receivables and Services
Risk management:Manage risk-related work associated with card issuance and use.
Debt management:Manage receivables associated with issued cards.
Service management:Manage services provided to members.
Common operations:Support common operational tasks required for the card business.
Product management and operational controlsProduct conditions, business rules, simulation, permissions, masking and audit records12 functions
Product Management and Operational Controls
Products and conditions:Define and combine products, services and their applicable conditions.
Business rules:Manage rules and applicable conditions separately from application programs.
Condition groups:Combine business-processing conditions using condition groups.
Rule data:Maintain business rules in a database.
Rule-maintenance interface:Adjust supported business rules using graphical tools.
Product templates:Use standard templates to support new product and campaign definitions.
Change simulation:Simulate new conditions before applying them to review potential impacts.
Multiple screens:Work with multiple operational screens through a tabbed interface.
Work continuity:View work history and reactivate previous screens.
Menu and button permissions:Control menu access and button operations according to user permissions.
Data masking:Configure masking rules, fields and visible digit positions for the card institution.
Audit records:Retain rule-change history and audit trails.
05 / Foundation and delivery
Products, connections and delivery
Products behind the solution
BX-CBP Main product
Core banking software foundation for issuer operations
Agree interfaces, processing responsibilities and applicable network requirements. Authorisation and connectivity are scoped separately.
External services & channels
Define protocols, data mappings and external adaptations during design.
Retained systems
Agree which card-business activities the solution handles and which systems remain in place.
Step 1
Define & configure
Agree issuer scope and supported product rules. Identify extension points and additional development.
Step 2
Connect & validate
Implement agreed interfaces and data mappings. Validate processing responsibilities and test the solution.
Step 3
Rehearse & launch
Plan migration data, rehearsals and checks. Agree cutover, monitoring and operational handover.
Explore architecture and delivery topics
Application and platform layers
Keep card applications, product definitions and application-framework responsibilities distinct in the solution design.
Integration mechanisms
Use API connections, normalised data structures and channel connection management, with protocols, data mappings and external adaptations defined during design.
Integration products
Select BX-I or an agreed third-party integration product and define the required interfaces.
Product and rule configuration
Use supported templates, conditions and rules; additional products or workflows may require development.
Architecture choices
Evaluate BX-CoCore as an alternative Main Product where microservices or containers are required, subject to technical assessment.
Migration and operation
Plan migration objects, data-quality responsibilities, rehearsals, checks, cutover windows, monitoring and maintenance responsibilities. Select tools and automation for the project.
06 / Customer experience
Card-system technology and partnerships
GMO Payment Gateway
Technology partnership for card-processing services
GMO Payment Gateway adopted BX-M and BX-PF and works with Bankware as a technology partner for card-processing ASP services for small and mid-sized card issuers in Japan.
Product and integration technology for a card system
Bankware supplied BX-M as the card system’s development and operations framework, BX-PF to manage card products and benefits, and BX-I for system interfaces.
Tell us which issuer operations you want to change and which systems you plan to retain. Together, we can define the product, interface and delivery scope to evaluate.
