Financial Services
Banking & Financial Services
Comprehensive guide to core banking systems, digital banking, payments, lending, and treasury management — the backbone of modern financial infrastructure.
$190T+
Global Assets
3.6B
Digital Users
$13B
API Economy
12B+
India UPI
Understanding Banking & Financial Services— A Developer's Domain Guide
Banking involves accepting deposits, lending money, processing payments, and providing various financial services to individuals and businesses. Modern banking has evolved from traditional brick-and-mortar operations to digital-first platforms, with core banking systems (CBS) at the heart of all operations. This domain covers retail banking, corporate banking, treasury operations, and the emerging fintech ecosystem.
Why Banking & Financial Services Domain Knowledge Matters for Engineers
- 1Banking is a $25+ trillion global industry with constant technology modernization
- 2High demand for developers who understand both banking domain and technology
- 3Complex transaction processing, regulatory compliance, and security requirements
- 4Core banking modernization projects are high-value, long-term engagements
- 5Fintech disruption creates opportunities for innovation in payments and lending
- 6Understanding banking APIs is essential for Open Banking/PSD2 compliance
How Banking & Financial Services Organisations Actually Operate
Systems & Architecture — An Overview
Enterprise Banking & Financial Services platforms are composed of a set of core systems, data platforms, and external integrations. For a detailed, interactive breakdown of the core systems and the step-by-step business flows, see the Core Systems and Business Flows sections below.
The remainder of this section presents a high-level architecture diagram to visualise how channels, API gateway, backend services, data layers and external partners fit together. Use the detailed sections below for concrete system names, API examples, and the full end-to-end walkthroughs.
Technology Architecture — How Banking & Financial Services Platforms Are Built
Modern Banking & Financial Servicesplatforms follow a layered microservices architecture. The diagram below shows how a typical enterprise system in this domain is structured — from the client layer through the API gateway, backend services, data stores, and external integrations. This is the kind of architecture you'll encounter on real projects, whether you're building greenfield systems or modernising legacy platforms.
End-to-End Workflows
Detailed, step-by-step business flow walkthroughs are available in the Business Flows section below. Use those interactive flow breakouts for exact API calls, system responsibilities, and failure handling patterns.
Industry Players & Real Applications
🇮🇳 Indian Companies
HDFC Bank
Private Sector Leader
Finacle CBS, Oracle
India's largest private bank by market cap
ICICI Bank
Universal Bank
Finacle, iMobile
Pioneer in digital banking innovations
State Bank of India
Public Sector Giant
TCS BaNCS, YONO
Largest bank in India by assets
Axis Bank
Private Bank
Finacle, Open APIs
Strong focus on digital transformation
Kotak Mahindra
Private Bank
Oracle FLEXCUBE
Known for innovative digital products
Yes Bank
Private Bank
Finacle CBS
API Banking pioneer
Paytm Payments Bank
Payments Bank
Custom Platform
Digital-first banking model
RazorpayX
Neobank
Custom, APIs
Business banking platform
🌍 Global Companies
JPMorgan Chase
USAUniversal Bank
Custom, Athena
Largest US bank by assets
Bank of America
USARetail Giant
Custom CBS
Erica AI virtual assistant
HSBC
UKGlobal Bank
TCS BaNCS
Present in 64 countries
DBS Bank
SingaporeDigital Leader
Custom Platform
World's best digital bank
Revolut
UKNeobank
Custom, Microservices
35M+ customers globally
Nubank
BrazilDigital Bank
Custom, Clojure
World's largest digital bank
N26
GermanyMobile Bank
AWS, Kotlin
European mobile banking leader
Chime
USANeobank
Custom Platform
14M+ US customers
🛠️ Enterprise Platform Vendors
Infosys Finacle
Core Banking, Digital Banking, Payments Hub
1B+ accounts managed globally
TCS BaNCS
Core Banking, Payments, Wealth Management
Used by 450+ financial institutions
Oracle FLEXCUBE
Universal Banking, Core Banking, Payments
140+ countries deployment
Temenos
T24 Core Banking, Transact, Infinity
3000+ banks use Temenos globally
FIS
Modern Banking Platform, HORIZON
Processing 75B+ transactions annually
Fiserv
DNA, Signature, Premier
Serves 1 in 3 US financial institutions
Mambu
Cloud Banking Platform, SaaS CBS
Cloud-native banking engine
Thought Machine
Vault Core Banking
Used by JPMorgan, Lloyds, Standard Chartered
Real World Use Cases
Core Banking Systems
Customer accounts, deposits, transactions, and ledger management
Explore →Digital & Mobile Banking
Internet banking, mobile apps, and omnichannel experiences
Explore →Payments & Transfers
RTGS, NEFT, UPI, SWIFT, card payments, and real-time payments
Explore →Lending & Credit
Loan origination, underwriting, disbursement, and collections
Explore →Core Systems
These are the foundational systems that power Banking & Financial Services operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.
Business Flows
Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.
The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.
Technology Stack
Real Industry Technology Stack — What Banking & Financial Services Teams Actually Use. Every technology choice in Banking & Financial Servicesis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.
The pattern across Banking & Financial Services is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern Banking & Financial Servicesplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.
⚙️ backend
Java/Spring Boot
Core banking services, transaction processing
COBOL/Mainframe
Legacy CBS systems, batch processing
Golang
High-performance payment processing, APIs
Python
ML models for fraud, credit scoring
Node.js
API gateway, BFF services
🖥️ frontend
React/Angular
Internet banking, admin portals
React Native/Flutter
Mobile banking apps
Swift/Kotlin
Native mobile banking apps
🗄️ database
Oracle DB
Core banking, transaction data
PostgreSQL
Digital banking, modern systems
MongoDB
Customer profiles, documents
Redis
Session management, caching
Apache Kafka
Event streaming, real-time processing
🔗 integration
ISO 20022
New payment messaging standard
ISO 8583
Card transaction messaging
SFMS
RBI payment system integration
REST/gRPC
Internal service communication
MQ/Kafka
Async messaging between systems
☁️ cloud
AWS/Azure
Cloud infrastructure for digital banking
Kubernetes
Container orchestration
HashiCorp Vault
Secrets management
Elasticsearch
Log aggregation, search
📋 compliance
HSM
Hardware Security Module for keys, PINs
PCI-DSS
Card data security compliance
AML/CFT Systems
Anti-money laundering, sanctions screening
Interview Questions
Q1.Explain the difference between NEFT, RTGS, IMPS, and UPI.
NEFT is batch-based (half-hourly), no minimum, used for non-urgent transfers. RTGS is real-time gross settlement for high-value (min ₹2 lakh) urgent transfers. IMPS is 24x7 real-time up to ₹5 lakh, works on MMID/mobile. UPI is mobile-first real-time using VPA (virtual payment address), supports QR, collect requests, and has ₹1 lakh limit. UPI is the most popular with 12B+ monthly transactions.
Q2.What is a Core Banking System (CBS) and what are its key modules?
CBS is the central IT system that manages all banking operations across all branches in real-time. Key modules include: Customer Information File (CIF), Account Management (savings, current, FD, RD), Transaction Processing, General Ledger, Interest Calculation, Product Definition, and Regulatory Reporting. Popular products: Finacle (Infosys), TCS BaNCS, Oracle FLEXCUBE.
Q3.How does UPI settlement work?
UPI follows deferred net settlement. Real-time: When you pay, your bank debits you immediately, beneficiary bank credits instantly. Settlement: Actual money movement between banks happens in cycles (hourly during day, specific windows at night). NPCI calculates net position of each bank and settles via RBI. Banks maintain prefunded settlement accounts to honor obligations.
Q4.Explain NPA classification in Indian banking.
NPA (Non-Performing Asset) classification per RBI: Standard - performing loan, SMA-0 - 1-30 days overdue, SMA-1 - 31-60 days, SMA-2 - 61-90 days. After 90 days overdue, loan becomes NPA. Sub-standard - NPA up to 12 months, Doubtful - NPA 12-36 months, Loss - NPA > 36 months or unrecoverable. Banks must make provisions: 15% (substandard), 25-100% (doubtful), 100% (loss).
Q5.What is Basel III and its key requirements?
Basel III is global regulatory framework for banks. Key requirements: Capital - Minimum 8% CAR with Tier 1 >= 6% (CET1 >= 4.5%). Liquidity - LCR (Liquidity Coverage Ratio) >= 100%, NSFR (Net Stable Funding Ratio) >= 100%. Leverage - Maximum 3% leverage ratio. India follows Basel III with RBI setting stricter norms like 11.5% CAR for scheduled commercial banks.
Q6.How do you handle idempotency in payment APIs?
Idempotency ensures duplicate requests don't cause duplicate transactions. Implementation: Client sends unique idempotency key (UUID) in header. Server stores key with response in Redis/DB with TTL. On duplicate request, return cached response instead of processing again. Critical for payments to prevent double-debit scenarios during network retries. Also use database constraints on reference numbers.
Glossary & Key Terms
CIF
Customer Information File - master record containing customer's KYC and relationship data
CBS
Core Banking System - centralized banking software managing all operations across branches
CASA
Current Account Savings Account - low-cost deposits, key profitability metric for banks
NPA
Non-Performing Asset - loan where interest/principal overdue for 90+ days
CAR
Capital Adequacy Ratio - capital to risk-weighted assets ratio (min 11.5% in India)
ALM
Asset Liability Management - managing interest rate and liquidity risk
VPA
Virtual Payment Address - UPI identifier like name@bank
IFSC
Indian Financial System Code - 11-character code identifying bank branch
UTR
Unique Transaction Reference - tracking number for interbank transfers
PSP
Payment Service Provider - intermediary like PhonePe, GPay providing UPI access
SFMS
Structured Financial Messaging System - RBI's payment messaging infrastructure
KYC
Know Your Customer - identity verification process mandated by RBI