FINANCIAL INFRASTRUCTURE CONCEPT

pacs.002

pacs.002 is the ISO 20022 Payment Status Report message used by agents to communicate acceptance, rejection, or other processing statuses for a payment instruction.

Architectural context & analysis

Status reports drive exception queues and customer updates but are not themselves cash settlement evidence.

Reason codes should be preserved verbatim in audit logs and mapped carefully into internal Protocol 201.3 states.

Worked operational scenario

A pacs.002 with RJCT and an invalid beneficiary account code parks the case in a repair queue without marking funds settled.

Implementation considerations & controls

Treat duplicate pacs.002 deliveries as idempotent updates correlated by UETR and instruction IDs.

CONCEPTUAL RELATIONSHIPS

Related concepts

RELATED CONCEPT

ISO 20022

ISO 20022 is an international, open financial messaging standard based on an extensible XML and JSON data dictionary, unifying cross-border, securities, and high-value payments globally.

RELATED CONCEPT

UETR

UETR (Unique End-to-end Transaction Reference) is a UUID-based tracking reference that identifies a payment instruction across agents for investigation and status correlation.

RELATED CONCEPT

End-to-End ID

An end-to-end identification is a business reference assigned to identify a payment end-to-end across parties, distinct from clearing system references generated per hop.

RELATED CONCEPT

Payment Finality

Payment finality is the legally defined, irrevocable point in time at which a funds transfer is completed and cannot be rescinded, reversed, or clawed back under statutory law.

AN INFORMED NEXT STEP

Establish clear operational parameters for pacs.002.

Start with your architecture, integration boundaries and operational requirements.

Discuss your requirements