Payment Hub Architecture Simulator

Representative reference architecture for teaching. Real banks implement these functions differently; component boundaries, names and order vary by bank, vendor and rail. There is no single canonical 18-component hub: functions may be combined in one platform, split across vendors, or provided by a scheme or utility. This is a catalogue in rough flow order, not a strict sequence: the orchestrator is present throughout, liquidity is checked before a payment is released to clearing or settlement, and screening points vary by bank. Functions not listed here include FX pricing and execution, reference-data management, KYC/CDD and customer profile, charge and fee calculation, customer notification, and scheme connectivity testing and certification.

Eighteen components. Click a component to see what comes in, what it does, what goes out, which systems it calls, what data it uses, what happens if it fails, and how the payment recovers. Or pick a flow to see which components that flow touches and which it skips.

Flow order (rough, not strict): channels and gateway feed ingestion, validation, enrichment, screening, and fraud checks. The orchestrator coordinates throughout, including routing, processing, liquidity, and clearing. Settlement, core banking, ledger, reconciliation, exceptions, and audit close the loop. An on-us payment needs no clearing or interbank settlement leg at all; an instant payment cannot wait for a batch clearing cycle; a high-value payment settles individually and gross in central-bank money; a cross-border payment needs correspondent funding and the cover or serial method.