Reference stack
Modernise core banking and ledger infrastructure
A transformation stack for replacing or surrounding a legacy core with a modern ledger, payment hub, API layer, data migration and compliance integrations.
Intended audience and markets
Audience
Markets
Infrastructure layers
Core and ledger
RequiredProvide the system of record for accounts, balances and products.
Selection criteria
- Ledger integrity
- Product configuration
- Deployment and resilience
Payment hub and scheme connectivity
RequiredConnect the core to payment schemes and processors.
Selection criteria
- Required rails
- ISO 20022 support
- Exception and liquidity controls
Card processing
OptionalIntegrate issuing and card-account events where required.
Selection criteria
- Processor scope
- Authorisation and clearing integration
- Migration and token continuity
API and integration layer
RequiredExpose controlled services to channels and partners.
Selection criteria
- API governance
- Event streaming
- Backward compatibility
Data migration and reconciliation
RequiredMove account history and prove ledger continuity.
Selection criteria
- Data quality
- Parallel run
- Financial reconciliation and rollback
Compliance integration
RequiredConnect onboarding, screening and monitoring to the new core.
Selection criteria
- Customer and transaction identifiers
- Real-time event delivery
- Audit evidence
Implementation sequence
- Core and ledger
- Payment hub and scheme connectivity
- Card processing
- API and integration layer
- Data migration and reconciliation
- Compliance integration
Regulatory considerations
- A core replacement changes regulated books and records, outsourcing risk and operational-resilience controls.
Technical considerations
- Use phased migration, parallel ledgers and independently reconciled checkpoints.
- Define canonical product, customer and transaction models before selecting migration tools.
Questions to ask providers
- Which legal entity contracts for each service and in which jurisdictions?
- Which responsibilities remain with the product operator rather than the provider?
- What are the implementation, approval, testing and migration timelines?
- How are incidents, exits, data portability and business continuity handled?
- What is the rollback and customer-remediation plan if migrated balances differ?
What this stack does not cover
- Systems integration, programme governance and data-cleaning effort are not represented by provider names alone.
Related stacks
Reviewed on 2026-07-07.
Provider options are examples of infrastructure roles, not endorsements or a guarantee of suitability, availability or regulatory compliance. Confirm requirements for your product with each provider and qualified advisers.