
🏦 Finance & Banking · Database ERD
A relational schema for retail banking: customers, accounts, transactions, cards, loans and beneficiaries.
Drawing diagram…
ERD for retail banking: Customer holds Accounts through AccountHolder (supporting joint accounts), each Account belongs to a Branch and has Transactions and Cards; Customer has Beneficiaries for transfers; Loan belongs to a Customer and has EmiSchedule rows.
erDiagram
CUSTOMER ||--o{ ACCOUNT_HOLDER : holds
ACCOUNT ||--|{ ACCOUNT_HOLDER : "held by"
BRANCH ||--o{ ACCOUNT : manages
ACCOUNT ||--o{ TRANSACTION : records
ACCOUNT ||--o{ CARD : issues
CUSTOMER ||--o{ BENEFICIARY : adds
CUSTOMER ||--o{ LOAN : takes
LOAN ||--|{ EMI_SCHEDULE : "repaid by"
CUSTOMER {
int id PK
string cif_no
string name
string pan
}
ACCOUNT {
int id PK
string account_no
string type
decimal balance
int branch_id FK
}
TRANSACTION {
int id PK
int account_id FK
string type
decimal amount
datetime posted_at
}
LOAN {
int id PK
int customer_id FK
decimal principal
decimal rate
}
EMI_SCHEDULE {
int id PK
int loan_id FK
date due_date
decimal amount
}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.
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.
A personal loan from application to disbursal: KYC, credit bureau check, underwriting rules, manual review for borderline cases, and the final agreement.
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.
How a bank scores every transaction for fraud in milliseconds: features from history, an ML model, rules, and a case queue for analysts.
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.