Banking IT Systems & Payment Rails

Real-world analogy

What is it?

Banking IT domain literacy covers CBS, channels, switches, payment rails, SWIFT, reconciliation, cut-offs, and ICT-risk expectations. You don’t have to be a specialist to sound credible; you have to show you understand how the pieces connect.

Real-world relevance

An ATM network throws ‘switch unavailable’ at 8 PM. Junior checks the switch host, confirms a failed VPN tunnel to the acquirer, raises an incident with timeline and evidence, keeps comms to the branch manager calm and factual. Senior restores the tunnel; junior documents the full RCA entry for tomorrow’s operations review.

Key points

• Core banking system (CBS) — CBS holds customer accounts, balances, transactions, GL, interest, and product configurations. Names you will hear: Finacle, FLEXCUBE, Temenos T24, bankUltimus, Ababil NG. A junior doesn’t configure CBS — they support the environment around it.
• Channels — where customers touch the bank — Branch counters, internet banking, mobile banking, ATMs/CDMs, chatbots, call centers, agent banking. Each channel has its own dependencies on CBS + identity + network + switches.
• Switches and card systems — A card switch (e.g., ATM/POS switch) routes authorization requests between cards, acquirers, issuers, and networks (local NPS and international schemes like Visa/Mastercard). Downtime here = cards declined.
• Payment rails at a glance — Different rails serve different money movements: RTGS for large-value, net systems for retail batch settlement, interbank fund transfer systems, and instant payment rails. Naming differs by country; recognize the structure.
• SWIFT — cross-border messaging — SWIFT isn’t a payment network; it’s a secure financial messaging standard banks use to instruct and confirm cross-border payments. Operators care about message integrity, reconciliation, and strict auditability.
• Reconciliation and cut-offs — End-of-day, end-of-month reconciliation ensures internal records match external clearing. Cut-off times for SWIFT, RTGS, and retail systems are non-negotiable. Missing them is a real financial/regulatory event.
• ICT risk and central-bank expectations — Banks operate under ICT risk frameworks issued by regulators that expect patching, MFA, segregation of duties, logging, incident reporting, DR drills, vendor management, and critical-incident timelines. You don’t write the policy — you live it daily.
• The junior’s contribution — You won’t run the CBS, but you will: support branch devices, patch channel gateways, watch switch alarms, help reconcile evidence, support SWIFT workstation environments, assist audit teams, and follow documented procedures exactly.

Code example

// Banking IT landscape (simplified mental map)

Customer channels
  Branch counter  <--->  Channel gateway
  Internet/mobile <--->  Channel gateway
  ATM/CDM         <--->  ATM switch
  Call center     <--->  IVR + agent desktops
                      |
                      v
           Core banking system (CBS)
                      |
                      v
  Payment rails / clearing
    - Large value (RTGS-like)
    - Retail net settlement
    - Interbank fund transfer
    - Instant payment rail
    - Cross-border via SWIFT messaging
                      |
                      v
   Counterparty banks, schemes, regulator

Line-by-line walkthrough

1. 1. Banking IT mental map
2. 2. Channels header
3. 3. Branch to gateway
4. 4. Internet/mobile to gateway
5. 5. ATM to switch
6. 6. Call center to IVR
7. 7. Flow down to CBS
8. 8. Flow down to rails
9. 9. Rail types
10. 10. SWIFT messaging
11. 11. Flow to counterparties/regulators

Spot the bug

During a month-end incident, junior tweets: 'Our ATM network is down, working on it, many cards declined — stay tuned!'

Explain like I'm 5

Fun fact

Hands-on challenge

More resources

• Temenos core banking overview (Temenos)
• FIS/Finastra core banking (Finastra)
• SWIFT Customer Security Programme (CSP) (SWIFT)