Clearing & settlement
NextGenPSD2 XS2A FrameworkNon-Instant Payment (Standard Batch) flow via Payment Hub & ILM
End-to-end non-instant (standard batch / credit transfer) payment flow through internal architecture: External Network > AGI > Payment Hub > ILM > Core Banking (T24) / Settlement Engine.
Why read this
Standard payment processing detailing mandatory routing legs and optional Sub Participant clearing vs direct clearing.
Try in live showcase
Messages · pacs.008 → pacs.002
Transaction flow
Direct clearing member: ILM liquidity checks stay on the path before settlement.
Inbound pacs.008 standard credit transfer
Clearing layerThe external network (STEP2 / SWIFT / CSM) delivers a batch or standard credit transfer pacs.008 to the Access Gateway Interface (AGI).
Messagepacs.008Full detail →
The interbank credit transfer. Everything a PISP initiates eventually becomes one of these. SWIFT and ISO publish successive schema versions (…001.08, …001.10, …001.13); each market picks one via its usage guideline (EPC SEPA, CBPR+, SIC…).
This flow
Also used in
- SEPA credit transfer with decoupled SCA
- Clearing leg: initiation to settlement
- Rejection: reading a pacs.002 RJCT
- SCT Inst happy path (≤10s)
- SCT Inst reject inside the window
- SCT Inst with Verification of Payee
- SCT Inst timeout & investigation
- SIC CHF customer credit (Regular Payment)
- SIC Instant Payment (SIC IP)
- TARGET2 / T2 regular credit transfer
- SIC IP timeout and enquiry
- euroSIC EUR clearing leg
- A2A overlay payment (Wero sample)
- Instant Payment (IP) flow via Payment Hub & ILM
external-networkagi
ISO 20022 payload· XML
pacs.008 interbank credit transfer
The same payment on the interbank leg. InstdAmt became IntrBkSttlmAmt, an IntrBkSttlmDt appeared, and TxId is now the identifier the CSM quotes in every response.