Explain SWIFT GPI tracking status codes and provide stuck-payment investigation guidance.

USE THIS TOOL FIRST whenever the user reports a payment that is stuck, delayed, not arriving, held, pending, rejected, or otherwise not behaving as expected. It is the primary diagnostic entrypoint for payment investigation — calling with a specific code returns a full investigation playbook (common delay causes, recommended actions, GPI SLA timeframes, escalation steps).

Recommended calls by scenario:

• Payment "stuck" / "in progress" / "pending" / "not arrived": gpi_status_codes("ACSP") → playbook for in-progress payments

• Payment explicitly "on hold" / compliance review: gpi_status_codes("PDNG") → playbook for held payments

• Payment "blocked" / sanctions flag: gpi_status_codes("BLCK") → playbook for blocked payments

• Payment rejected by a bank in the chain (never credited): gpi_status_codes("RJCT") → rejection investigation playbook

• Payment returned to sender (accepted then sent back): gpi_status_codes("RTRN") → return investigation playbook

• Reference for ISO 20022 codes: gpi_status_codes() → list all codes

Each code call returns:

• Code description and meaning

• For ACSP/PDNG/BLCK/RJCT/RTRN: investigation playbook with common causes, recommended actions (request gCCT tracker, request pacs.002/pacs.004 reason code, verify beneficiary details, escalate via MT199, etc.), and common ISO 20022 reason codes (AC01, AC04, AG01, RR01-RR04, etc.) when applicable

• Child reason codes (e.g., G001-G004 for ACSP) that narrow the cause further

Common codes: ACCC (success), ACSP (in progress), RJCT (rejected), PDNG (on hold), BLCK (blocked). GPI reason codes (G000-G004) qualify ACSP with more detail (e.g. G001 = passed on to a bank that is not a gpi member, G002 = credit pending, may not be same day).

Examples: gpi_status_codes("ACSP") # stuck-payment diagnostic playbook gpi_status_codes("G001") # detail on a specific reason code gpi_status_codes() # full reference list