Payments Clearing & Settlement
FIToFIPaymentStatusRequestV04
Payments Clearing & Settlement
Asking the other side what happened, when no pacs.002 arrived. The polite version of a payment investigation.
Start with the payment story
Then the technical flows
Schema versions
SWIFT and ISO publish successive XSD revisions of the same business message (e.g. pacs.008.001.08 → .10 → .13; same pattern for camt and pain). Markets pin one via a usage guideline (EPC SEPA, CBPR+, Swiss SPS…) and may add a country suffix (pacs.008.001.08.ch.02) — the Document xmlns must match that XSD.
ISO catalogue (XSD) ↗SWIFT / CBPR+ ↗SWIFT & versioning glossary →
Catalogue entry pacs.028.001.04 (variant 001, version 04).
Facts
- Root element
FIToFIPmtStsReq- Direction
- Bank → bank
- Namespace
urn:iso:std:iso:20022:tech:xsd:pacs.028.001.04- Variant (flavour)
001- Version
04
Elements a validator will insist on
Not the full XSD — the paths whose absence causes the rejections you actually see in production.
- FIToFIPmtStsReq/GrpHdr/MsgId
- FIToFIPmtStsReq/TxInf/OrgnlEndToEndId
Usage in flows
ISO 20022 payload· XML
pacs.028 SCT Inst status request
Investigation after missing pacs.002 inside the instant window. Switch XML | JSON in the inspector without leaving this sample.
Edit in the XML / JSON tab, then run the check.