MESSAGING — 9 MIN READ
pacs.002 Payment Status Report Handling
Use pacs.002 payment status reports to drive exception queues, customer updates, and Protocol 201.3 state machines without mistaking status for settled cash.
|
Status is a control signal, not cash
pacs.002 payment status reports tell counterparts whether an instruction was accepted, rejected, pending, or otherwise progressed under ISO 20022 semantics. They are essential for exception queues—yet they are not nostro evidence and not payment finality.
Map pacs.002 reason codes into Protocol 201.3 states carefully so customer channels do not announce settled funds on a mere ACCP. globalserverbank is not a licensed bank and is not affiliated with Visa.
Keep status field dictionaries aligned with Global Server Protocol and ISO 20022 readiness. See pacs.002, UETR, and end-to-end ID.
Ingest, correlate, and act
Correlate on UETR and end-to-end ID first, then instruction IDs. Duplicate status messages must be idempotent. Late RJCT after a provisional post must open a break—see Protocol 201.3 reconciliation.
Route codes to queues: repairable data errors, compliance holds, liquidity rejects, beneficiary unknown. Preserve original codes in the audit trail.
Throughput and hosting
Status floods follow outages and cut-offs. Parse and enqueue on cloud banking servers isolated from live credit acceptance so status storms do not block new instructions.
Related: partial settlement mechanics.
Evaluation CTAs
Architecture reviews: S2S transfer frameworks, node access, specs at Global Server Protocol.
FURTHER CLARITY
Frequently asked questions
Does ACCP mean funds are available to the beneficiary?
Not necessarily. ACCP often means the agent accepted the instruction for processing; availability depends on posting and scheme rules.
How do pacs.002 relate to MT199 investigations?
They can cover similar operational needs in ISO 20022 rails; map carefully during coexistence rather than assuming one-for-one field equality.
Does globalserverbank send pacs.002 on behalf of banks?
No. It documents handling patterns only.
PRIMARY SOURCES & STANDARDS
References and citations
AN INFORMED NEXT STEP
Bring architectural discipline to your payment and ledger systems.
Start with your architecture, integration boundaries and operational requirements.