Core banking
Connect institution setup, customers, accounts and financial close through one controlled banking day.
Nucleus is the core banking platform. It owns the authoritative records and financial effects for accounts assigned to it. An institution can use the Nucleus web app, its own interfaces or both on the same versioned APIs.
Establish the operating scope
The institution sponsor, Finance, compliance and technology owners select legal institution, country, currencies, hosting and operating responsibility. Configure jurisdiction requirements, business calendar, products, chart of accounts, branches, roles and independent approval rules. A country or entitlement selection alone cannot establish readiness.
Use a named local or sandbox instance with synthetic records to qualify the initial product set. Every command carries the verified institution and actor context. Group, branch, customer and platform authority remain explicit.
Run a complete banking day
| Work | Starting point | Evidence and recovery |
|---|---|---|
| Establish a customer relationship | Customer onboarding | Identity evidence, approved customer record and pending requirements with owners |
| Configure and open accounts | Accounts and identifiers | Product version, terms, account identity and approved currency |
| Originate and service credit | Credit guide | Application version, decision, conditions and separate disbursement evidence |
| Receive and pay physical cash | Teller and cash | Custodian, till, currency, retained movements and independently approved cash proof |
| Move funds | Transfer | Durable instruction, funding, approval, external outcome and reconciliation |
| Reconcile and close | General ledger | Balanced journals, resolved differences, governed jobs and business-date evidence |
Retain operation identity across interruptions. An approval binds the exact proposed version. A changed amount, account, date or material term requires current validation and a new decision where the operation demands it.
Available contracts
The core source reference supplies discovered endpoints and schema annotations. The separately scoped local profile describes selected local Transfer and consented-read evidence. Current generated source also includes governed close, cash correction, credit committee and provisioning routes. Their presence alone establishes no broad runtime or institution acceptance.
Restrictions and recovery
A signed entitlement, software availability, configured product, actor permission and live qualification are separate prerequisites. Rejected commands should identify the required owner or evidence. Unknown external instructions stay with their original funding, route and recovery owner until authoritative status is known. Posted history is corrected by linked events and preserved for audit.