04 · Core banking
CWC Banking
Compliance is the architecture.
Core banking redesigned as configuration-as-code: products, postings, fees, rates and rules are versioned, effective-dated data over a small generic engine.
- 01Configuration-as-code — posting templates, product versions, fees, rates, limits and tax rules are versioned data; past rules are a point-in-time query.
- 02One ledger writer — every subledger hands a PostingRequest to one PostingService: request → template → journal.
- 03Transactional outbox — journals publish to Kafka from the same transaction that writes them.
- 04A full suite — deposits, loans, treasury, teller, fund management and trade finance across 57 modules and a 228-page operations portal.
- 05Internet banking — a customer portal for retail and corporate users: accounts, transfers, payments, mobile money, cards, term deposits and loans, with 11 modules each bank switches on or off.
- 06Observability and analytics — Micrometer metrics with OpenTelemetry tracing; an opt-in Cube.js and Evidence reporting layer.
Powered byCweCi
- 57 Gradle modules
- 228 portal pages
- 1 ledger writer
SurfacesWebInternet bankingOn-premAPI
- Spring Boot
- Java 21
- Kafka
- Oracle · PostgreSQL
- React