CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Finance & Banking

🏦 Finance & Banking · C4 Architecture · Pro

Core Banking System Architecture

The main building blocks of a bank's core platform: accounts, deposits, loans, payments and the general ledger, used by branches, internet banking and mobile.

More Finance & Banking templates

C4 Architecture diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.

Drawing diagram…

What this diagram shows

  • All channels go through one API layer
  • Every money movement posts to the general ledger
  • Payment rails (UPI, NEFT, RTGS) connect through a payments hub

Prompt used

Core banking architecture: customers use mobile and internet banking, staff use a branch system; all call an API layer. Core services: customer (CIF), accounts and deposits, loans, payments hub (UPI, NEFT, RTGS, IMPS), and the general ledger that receives every posting. Data in Oracle. External: NPCI and RBI payment systems, credit bureau and the regulatory reporting system.

Mermaid code
C4Container
title Core Banking System
Person(customer, "Customer", "Mobile and internet banking")
Person(teller, "Branch Staff", "Counter operations")
System_Boundary(cbs, "Core Banking") {
  Container(channels, "Digital Channels", "Mobile / Web", "Accounts, transfers")
  Container(branch, "Branch System", "Web", "Teller and back office")
  Container(api, "API Layer", "Java", "Auth and routing")
  Container(cif, "Customer (CIF)", "Java", "Customer master, KYC")
  Container(acct, "Accounts and Deposits", "Java", "Savings, current, FD")
  Container(loans, "Loans", "Java", "Disbursal and EMIs")
  Container(payhub, "Payments Hub", "Java", "UPI, NEFT, RTGS, IMPS")
  Container(gl, "General Ledger", "Java", "Double-entry postings")
  ContainerDb(db, "Core DB", "Oracle", "Accounts and transactions")
}
System_Ext(npci, "NPCI / RBI Systems", "Payment rails")
Rel(customer, channels, "Uses")
Rel(teller, branch, "Uses")
Rel(channels, api, "Calls")
Rel(branch, api, "Calls")
Rel(api, acct, "Routes")
Rel(api, loans, "Routes")
Rel(api, payhub, "Routes")
Rel(acct, gl, "Posts")
Rel(loans, gl, "Posts")
Rel(payhub, npci, "Settles")
Rel(acct, db, "Stores")

How a core banking system is put together

The core banking system (CBS) is the bank's system of record: customers, accounts, balances, loans and every posting to the general ledger. Branch, internet and mobile banking do not keep balances of their own; they call the core through an API layer, so every channel sees the same numbers.

The main building blocks

  • Customer information file (CIF): one record per customer with identity and KYC details, linked to all of that customer's accounts and loans.
  • Accounts and deposits: savings, current, fixed and recurring deposits, with interest accrual, charges and statements.
  • Loans: disbursement, repayment schedules (EMIs), interest calculation and tracking of overdue amounts.
  • Payments hub: sends each transfer over the right payment rail. In India that means UPI and IMPS for instant payments, NEFT for transfers settled in batches and RTGS for high-value payments, through NPCI and RBI systems.
  • General ledger: every transaction ends as balanced debit and credit postings. The ledger is what finance, auditors and regulators rely on.

Design choices that matter

  • Keep the channels thin: business rules (limits, interest, charges) live in the core, not in each app, or the channels drift apart.
  • Plan the end-of-day work: interest, charges and statements are often run as batch jobs, while payments now run around the clock, so the core has to keep posting during batch processing.
  • Integrate through one API or integration layer instead of point-to-point links, so a new channel or partner does not need changes in the core.
  • Treat regulatory reporting and the credit bureau as first-class outputs: they need clean, reconciled data from the ledger.

Using this template

  • Open it and describe your own bank or NBFC: add your channels, products and payment rails, and switch to the Managers view to explain the same system to non-technical stakeholders.

Inside this diagram

A C4 architecture diagram of Core Banking System with 2 people, 9 building blocks, 1 outside system and 11 relationships.

People

  • Customer: Mobile and internet banking
  • Branch Staff: Counter operations

Inside the system

  • Digital Channels (Mobile / Web): Accounts, transfers
  • Branch System (Web): Teller and back office
  • API Layer (Java): Auth and routing
  • Customer (CIF) (Java): Customer master, KYC
  • Accounts and Deposits (Java): Savings, current, FD
  • Loans (Java): Disbursal and EMIs
  • Payments Hub (Java): UPI, NEFT, RTGS, IMPS
  • General Ledger (Java): Double-entry postings

Databases and queues

  • Core DB (Oracle): Accounts and transactions

Outside systems

  • NPCI / RBI Systems: Payment rails

Boundaries

  • Core Banking

How they connect

  • Customer β†’ Digital Channels: Uses
  • Branch Staff β†’ Branch System: Uses
  • Digital Channels β†’ API Layer: Calls
  • Branch System β†’ API Layer: Calls
  • API Layer β†’ Accounts and Deposits: Routes
  • API Layer β†’ Loans: Routes
  • API Layer β†’ Payments Hub: Routes
  • Accounts and Deposits β†’ General Ledger: Posts
  • Loans β†’ General Ledger: Posts
  • Payments Hub β†’ NPCI / RBI Systems: Settles
  • Accounts and Deposits β†’ Core DB: Stores

Make your own diagram like this

Describe your own system in plain English and the AI C4 diagram generator draws it in seconds, in the same style as this template.

Related templates

SequenceFinance & Banking

UPI Payment Flow

The steps behind a UPI payment: the payer's app, the payer's bank, NPCI's UPI switch and the payee's bank, from entering a UPI ID to the money arriving.

C4 ArchitectureProFinance & Banking

Payment Gateway Architecture

A payment gateway that lets online merchants accept cards and UPI: the checkout, the payment core with fraud checks, and the card networks and banks it connects to.

FlowchartFinance & Banking

Loan Origination Workflow

A personal loan from application to disbursal: KYC, credit bureau check, underwriting rules, manual review for borderline cases, and the final agreement.

SequenceFinance & Banking

Card Payment Authorisation

What happens in the second after a card is tapped or entered online: the acquirer, card network and issuing bank authorise the payment, with 3-D Secure for online payments.

Data FlowFinance & Banking

Real-Time Fraud Detection Data Flow

How a bank scores every transaction for fraud in milliseconds: features from history, an ML model, rules, and a case queue for analysts.

FlowchartFinance & Banking

Digital KYC Onboarding

How a bank or fintech opens an account fully online: Aadhaar/PAN verification, video KYC, risk checks and account creation.