Exception handling
Swiss Payment Standards / SICSIC IP timeout and enquiry
No pacs.002 inside the SIC IP window. Hold the reservation and investigate with pacs.028 — never re-initiate blindly.
Why read this
Same class of bug as SCT Inst timeouts, on the Swiss instant rail.
Try editor — open message samples →
Samples in this flow
Try in live showcase
Technical view of Swiss Credit Transfer (SIC / SIC IP)
Messages · pacs.008 → pacs.028 → pacs.002
Transaction flow
pacs.008 submitted, timer starts
Clearing layerReservation placed. Clock is the SIC IP SLA, not next SIC batch.
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…).
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
- euroSIC EUR clearing leg
- A2A overlay payment (Wero sample)
- Instant Payment (IP) flow via Payment Hub & ILM
- Non-Instant Payment (Standard Batch) flow via Payment Hub & ILM
aspsprail
ISO 20022 payload· XML
pacs.008 SIC Instant Payment
CHF instant credit on SIC IP. Same message family as SCT Inst, Swiss instant ClrSys.