# ISO 20022 pacs.002 Payment Status Parser & Schema Validator
> Parse payment status reports and rejection reason codes from pacs.002 SWIFT MX messages into JSON.

- **Canonical URL:** https://stanzaapi.com/tools/iso20022-parser/messages/pacs-002-payment-status
- **Governing Standard:** ISO 20022 XML Financial Schemas (ISO 20022 Universal Financial Industry Message Scheme)
- **Latency:** <2ms Edge
- **Privacy:** In-memory execution only (zero data stored or logged)

## Technical Overview & Governing Rules
The pacs.002 message is used by financial institutions and clearing systems to communicate the status of a payment instruction.

Extracts TxSts (Transaction Status): ACTC (Accepted Technical Validation), ACCP (Accepted Customer Profile), RJCT (Rejected), PDNG (Pending).

Extracts StsrRsnInf (Status Reason Information) with standard ISO external status reason codes (e.g. AC01 Incorrect Account, AM04 Insufficient Funds).

## Specification Matrix
| XML Path | Description | Extracted JSON Field | Standard |
| --- | --- | --- | --- |
| TxInfAndSts/TxSts | Transaction Status | status | ACTC / ACCP / RJCT / PDNG |
| TxInfAndSts/StsRsnInf/Rsn/Cd | Status Reason Code | reasonCode | ISO 20022 External Code |
| TxInfAndSts/OrgnlUETR | Original UETR | originalUetr | UUID v4 |

## Standard JSON Response Model
```json
{
  "messageType": "pacs.002.001.10",
  "originalUetr": "eb9b1248-8422-441a-8c85-80252f9b8830",
  "status": "RJCT",
  "reasonCode": "AM04 (Insufficient Funds)",
  "statusDate": "2026-08-30T12:05:00Z"
}
```

## Frequently Asked Questions & Edge Cases
### Q: Does this handle clearing system settlement confirmations?
**A:** Yes, settlement timestamps and clearing references from FedNow, SEPA, and TARGET2 are extracted.