Steps of this lesson, in order.
Payment Hub Architecture Inside a Bank
What you will learn
Your objective. By the end of this lesson, you will be able to explain payment hub architecture inside a bank. A payment hub is the central processing engine that receives payment instructions from every channel in a bank and routes each one to the correct destination.
Why it matters. This matters because the architecture decides what the bank can build, how fast it can change, and where a payment can fail. Most payment requirements live in the architecture.
Chapter objective: Learner applies system design to payments, covering throughput, latency, idempotency, exactly-once processing, and failure recovery, and designs a system for a stated load. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.
Key learning points
- Payment hub
- Journey of a payment
- Payment engine
- Hub decides which engine
- Worked example
- Supplier bank
Key terms
Payment hub: A central system in a bank that receives payment instructions from all channels, validates them, applies screening and routing rules, and sends them to the correct clearing system or correspondent.
Value date: The date on which funds become available to the beneficiary and on which interest starts to accrue. It is the date used for settlement and for nostro posting.
Clearing: The process of exchanging payment instructions between banks and calculating what each bank owes the others.
Banking architecture diagram showing Payment Hub Architecture Inside a Bank.
Practise this lesson
Exercise
Read ch48s1 Hub components: what a hub is and what it contains. Then list the five hub layers and name one component in each.
ch48s1 covers channels, gateway, hub core, rails and settlement. This lesson is a pointer only.
- What to do. Write the five layers in order, with one component and its job in each layer.
Correct result. Channels: online banking captures the instruction. Gateway: validation and enrichment convert the instruction to the hub canonical model. Hub core: routing, screening, limits and value dating. Rails: T2, SEPA, Faster Payments, CHAPS, SWIFT. Settlement: central bank accounts move the funds.
Why. A hub is a layered platform, not a single box. Each layer has one job, and a payment that breaks is found by asking which layer it stopped in.
Check your understanding
Practice question
A bank routing table says that all euro payments above EUR 100,000 to Germany go through T2, while euro payments below that amount go through a different rail. What does this show about hub routing?
Takeaway and next step
What to remember
Read ch48s1 for the full treatment.
Send a payment through the hub and watch it pass each component named in this lesson.
Open the Payment Hub Architecture Simulator →
Builds on "Your Learning Path Forward".
Transcript and full text
Show transcript
This topic now lives in ch48s1 Hub components: what a hub is and what it contains, which is the master lesson for the payment hub. A payment hub is the central processing engine that receives instructions from every channel, runs them through intake, validation, screening, enrichment, routing and settlement, and instructs core banking to debit and credit the right accounts. The component catalogue is taught in ch48s2, ch48s3 and ch48s4, and the day to day running of the hub is taught in ch48s9 Hub operations. Read ch48s1 for the full treatment.
This topic now lives in ch48s1 Hub components: what a hub is and what it contains, which is the master lesson for the payment hub. A payment hub is the central processing engine that receives instructions from every channel, runs them through intake, validation, screening, enrichment, routing and settlement, and instructs core banking to debit and credit the right accounts. The component catalogue is taught in ch48s2, ch48s3 and ch48s4, and the day to day running of the hub is taught in ch48s9 Hub operations. Read ch48s1 for the full treatment.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.