Track a SWIFT gpi payment end-to-end using the UETR and gpi Tracker API

Steps

1. Generate a UUID v4 as the UETR (Unique End-to-end Transaction Reference) at payment initiation and include it in the gpi service level field of the pacs.008 message; this UETR is the immutable tracking key through the entire payment chain
2. After submission, query the SWIFT gpi Tracker via your bank's gpi API or the SWIFT API platform using the UETR to retrieve the transaction status; the tracker returns a gpi status object with the current processing bank, timestamp, and status code
3. Interpret the g4C status codes: ACCC (AcceptedCreditSettlementCompleted) means funds have been credited to the beneficiary; ACSP (AcceptedSettlementInProcess) means the payment is in the correspondent chain; RJCT means rejected
4. For ACSP statuses, the tracker shows each intermediary bank's confirmation timestamp; use this to identify which hop in the chain is causing delays if SLA is breached
5. Implement an escalation workflow: if the payment does not reach ACCC within your SLA threshold, use the gpi stop-and-recall mechanism (camt.056) to initiate a recall before funds are applied