pacs.002 Status Codes Explained

In pacs.002 (and related status messages), common status codes include: ACSP (accepted for settlement/processing) — the payment has been accepted but may not yet be settled; ACSC (accepted and settled) — the payment has been settled; RJCT (rejected) — the payment was rejected; PDNG (pending) — the payment is in a pending state. ACSP does not mean final settlement; it indicates acceptance into the process. Settlement confirmation is typically ACSC or equivalent. Operational meaning and exact code sets can vary by scheme and implementation.

Status updates are sent as the payment moves through the pipeline. Order of events is typically: acceptance (e.g. ACSP), then settlement (e.g. ACSC) or rejection (RJCT). Pending (PDNG) can appear when waiting for a condition or next step. Timing depends on the scheme, the institution, and cutoffs. For monitoring and SLA, distinguish between “accepted” and “settled” so that SLAs are measured against the right event.

• Confirm the exact status code and transaction identification to match the right payment.
• If status is RJCT, use the reason code or narrative to determine cause and next steps.
• If stuck in PDNG or ACSP beyond expected window, trigger stuck-payment or SLA logic.

• Ingest pacs.002 (or equivalent) into a single view so acceptance, settlement, and rejection are tracked consistently.
• Define SLA and “stuck” thresholds based on settlement (ACSC) or final status, not acceptance only.
• Use status flows to drive investigation and case creation when RJCT or timeout occurs.