# SWIFT GPI UETR Tracking & pacs.002 Status Codes Guide

> Track cross-border wire settlement using UUIDv4 UETR identifiers, ISO 20022 pacs.002 status reason codes (ACSP, ACCC, RJCT), and SWIFT GPI Tracker APIs.

Canonical: https://payclearledger.com/rails/swift-gpi-uetr-tracking-pacs002-status-telemetry-sla
Last updated: 2026-11-14T19:56:06.641Z

**Publication:** PayClear Ledger
**Category:** Iso20022 Pacs008 Cbpr Plus Clearing
**Published:** 2026-11-14T16:15:25.915Z
**Author:** Claire Beaumont, CAMS, CTP (Certified Anti-Money Laundering Specialist (CAMS), Certified Treasury Professional (CTP))
**Reviewer:** Not recorded

## Answer-first summary

Every cross-border SWIFT payment carries an immutable 36-character UUIDv4 UETR linking pacs.008 clearing hops with real-time pacs.002 status telemetry and fee deductions.

## Key takeaways

- Every CBPR+ pacs.008 wire embeds an immutable 36-character RFC 4122 UUIDv4 UETR that persists across intermediary hops and domestic RTGS clearings.
- Universal Confirmations require every FINplus recipient bank to post a final pacs.002 status (ACCC or RJCT) to TRCKCHZZ within two business days.
- Granular pacs.002 proprietary codes distinguish normal forwarding (G000) from Nostro funding delays (G002), regulatory document holds (G003), and missing pacs.009 COV cover legs (G004).
- Consuming GPI v5 REST APIs lets corporate and MSB treasuries calculate exact basis-point fee deductions and trigger automated escalations on stalled G002/G004 wires.

## Related financial entities

- **Committee on Payments and Market Infrastructures (CPMI)** (CPMI) — company: Global standard-setter for payment, clearing, and securities settlement systems operating under the Bank for International Settlements.
- **G20 Cross-Border Payments Roadmap Benchmark** (G20-PAY) — product: International initiative coordinated by the Financial Stability Board to enhance speed, reduce cost, and increase transparency in cross-border payment corridors.
- **ISO 20022 pacs.008 Customer Credit Transfer Standard** (PACS-008) — product: Universal financial industry message scheme defining XML data structures for executing customer credit transfers across commercial banks, RTGS networks, and payment systems.

## Analysis

Real-time visibility across multi-hop correspondent wire chains relies on a deterministic 36-character Universally Unique Identifier (UUIDv4) stored inside `<PmtId><UETR>` on every [ISO 20022 pacs.008 instruction](/corridors/iso-20022-pacs008-standard). Unlike mutable point-to-point transaction references (`InstrId`) that each intermediary bank overwrites at Nostro handoff, the UETR persists unchanged from debtor initiation through final beneficiary credit. Under the SWIFT Universal Confirmations Rulebook, every participating financial institution must update the central GPI Tracker via ISO 20022 `pacs.002.001.10` (`FIToFIPaymentStatusReport`) or API call whenever a wire settles, stalls in compliance review, or incurs lifting-fee deductions.

## UUIDv4 UETR Generation and Immutable Lineage Across pacs and camt Flows

Compliant UETR strings follow strict IETF RFC 4122 Version 4 syntax (`xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx`, lowercase hexadecimal, where `y` is restricted to `8`, `9`, `a`, or `b`). Originating payment engines generate this cryptographic token once at payment capture and embed it alongside `InstrId` (point-to-point agent reference) and `EndToEndId` (corporate invoice reference). As detailed in our [SWIFT CBPR+ ISO 20022 clearing guide](/rails/swift-cbpr-plus-iso-20022-pacs008-pacs009-clearing-guide), preserving all three identifiers prevents reconciliation breaks when wires traverse domestic RTGS bridges.

When an intermediary bank converts a serial cross-border instruction into a domestic clearing leg on Fedwire, CHAPS, or Eurosystem T2, the UETR rides inside the harmonized RTGS header so downstream beneficiary banks can still post final `ACCC` confirmations back to the SWIFT GPI cloud.

## Decoding pacs.002 Transaction Statuses: ACSP, ACCC, RJCT, and Extended G00x Codes

Within `pacs.002` status reports targeting the GPI Tracker BIC (`TRCKCHZZ`), `<TxSts>` combines standard ISO 20022 four-letter status codes with proprietary 4-character status reason codes (`<StsRsnInf><Rsn><Prtry>`) that reveal exact operational states. An `ACSP` (`AcceptedSettlementInProcess`) status paired with `G000` confirms the payment has been forwarded to the next GPI agent on same-day value, whereas `ACSP/G001` flags forwarding to a non-GPI respondent bank where downstream visibility terminates until final confirmation.

Crucially for treasury operations desks, `ACSP/G002` signals credit delayed past same-day cutoff due to insufficient Nostro funds or missing cover (`pacs.009 COV`), `ACSP/G003` indicates the payment awaits beneficiary documentation or regulatory FX clearance in restricted corridors, and `ACSP/G004` confirms funds are parked waiting for an incoming cover settlement leg—a scenario analyzed in [serial pacs.008 vs cover pacs.009 COV routing](/rails/pacs008-pacs009-cov-cover-payment-serial-routing-mechanics).

![SWIFT GPI UETR status telemetry chain from pacs.008 dispatch through pacs.002 ACCC confirmation](/api/figure?type=flow&title=UETR%20Telemetry%20%26%20pacs.002%20Tracker%20Lifecycle&subtitle=Hop-by-hop%20status%20reason%20updates%20reported%20to%20TRCKCHZZ%20across%20correspondent%20banks&steps=1.%20Debtor%20Bank%20Dispatch%3A%3AAssign%20UUIDv4%20UETR%20in%20pacs.008%3B%20log%20initial%20ACSP%2FG000%7C2.%20Intermediary%20Hop%3A%3ADeduct%20lifting%20fee%20%28ChrgsInf%29%3B%20emit%20ACSP%2FG000%20or%20G004%7C3.%20Destination%20RTGS%3A%3APreserve%20UETR%20across%20Fedwire%2C%20T2%2C%20CHAPS%2C%20or%20CHIPS%20leg%7C4.%20Creditor%20Bank%20ACCC%3A%3ACredit%20beneficiary%20IBAN%20and%20post%20final%20pacs.002%20ACCC&metrics=UETR%20Format%3A%3A36-char%20UUIDv4%3A%3ARFC%204122%20immutable%20key%7CUnder%2030-Min%20Share%3A%3A52.0%25%3A%3AGlobal%20GPI%20credit%20benchmark%7C24-Hour%20SLA%20Share%3A%3A91.4%25%3A%3AEnd-to-end%20settled%20wires%7CConfirmation%20Rule%3A%3A100%25%20Mandatory%3A%3AACCC%20or%20RJCT%20within%20T%2B2)

## Universal Confirmations Mandate and Fee/FX Deduction Transparency

Aligned with the [G20 Cross-Border Payments Roadmap](/corridors/g20-crossborder-payments-roadmap) targets, SWIFT enforces mandatory final confirmation reporting on all FINplus `pacs.008` recipients within two business days of value date. Whether the beneficiary bank credits the customer account (`ACCC`), rejects the instruction prior to credit (`RJCT`), or transfers funds outside the SWIFT network (`ACSP/G001`), omitting the final `pacs.002` confirmation degrades the institution’s published GPI Observer compliance score.

Each `pacs.002` hop also records exact timestamped arrival/departure logs, intermediary `<ChrgsInf>` lifting fees deducted from principal, and any in-flight currency conversion exchange rate (`<XchgRateData>`). Corporate treasurers and MSBs reconciling corridor slippage compare these GPI-reported wholesale spreads against theoretical forward benchmarks using our [corridor FX forward points calculator](/calculators/corridor-fx-forward-points-calculator).

| pacs.002 TxSts + Reason | Operational Meaning on GPI Tracker | Typical Root Cause | Automated Treasury Action | Escalation SLA |
| :--- | :--- | :--- | :--- | :--- |
| `ACSP` / `G000` | Forwarded to next GPI participant | Normal serial correspondent transit | Stream timestamp to client portal | Monitor > 2 hrs |
| `ACSP` / `G001` | Forwarded to non-GPI agent / domestic rail | Final mile via local ACH or non-GPI bank | Await beneficiary T+1 confirmation | Monitor > 24 hrs |
| `ACSP` / `G002` | Credit delayed past same-day value cutoff | Insufficient Nostro balance or missed cutoff | Trigger liquidity top-up or cutoff alert | Immediate (< 30m) |
| `ACSP` / `G003` | Pending beneficiary regulatory documents | EM FX control invoice check (INR, PHP, NGN) | Notify beneficiary to upload trade docs | Within 4 hours |
| `ACSP` / `G004` | Waiting for incoming cover (`pacs.009 COV`) | Cover leg stalled in sanctions/liquidity queue | Trace linked UETR on cover correspondent | Immediate (< 15m) |
| `ACCC` / `RJCT` | Final beneficiary credit OR rejected wire | Settled to account OR ISO error (AC04/AM04) | Reconcile ERP or route via [pacs.004](/rails/pacs004-payment-return-reason-codes-cross-border-repair-costs) | Closed / Auto-Reroute |

## Webhook API Integration and Proactive Exception Escalation

Modern payment orchestration hubs at [Deutsche Bank AG](/remitters/deutsche-bank-ag) and global fintech remitters bypass batch polling by consuming SWIFT GPI v5 REST/JSON APIs (`GET /payments/{uetr}/transactions`), streaming status transitions directly into client dashboards. When an outbound wire stays stuck in `ACSP/G002` or `ACSP/G003` beyond corridor-specific P90 latency thresholds, automated workflow engines trigger proactive inquiries or initiate [camt.056 payment cancellation recalls](/rails/camt056-payment-cancellation-camt029-recall-resolution-workflows) before beneficiary credit.

Review the broader [CBPR+ ISO 20022 clearing topic hub](/topics/iso20022-pacs008-cbpr-plus-clearing) to connect GPI status reason telemetry with automated Nostro liquidity sweeps.

![Cross-border SWIFT GPI end-to-end settlement latency percentiles across G10 and emerging corridors](/api/figure?type=bars&title=GPI%20End-to-End%20Settlement%20Speed%20by%20Corridor%20Type&subtitle=Percentage%20of%20UETR-tracked%20pacs.008%20wires%20reaching%20final%20ACCC%20within%2060%20minutes&steps=EUR-GBP%20%28T2%20to%20CHAPS%29%3A%3A78%25%20settled%20%3C%2060m%20%E2%80%94%20direct%20bilateral%20correspondent%20hubs%7CUSD-EUR%20%28Fedwire%2FT2%29%3A%3A69%25%20settled%20%3C%2060m%20%E2%80%94%20overlapping%20afternoon%20NY%2FCET%20hours%7CUSD-PHP%20%28BDO%20%2F%20Citi%20PH%29%3A%3A44%25%20settled%20%3C%2060m%20%E2%80%94%20timezone%20%26%20beneficiary%20bank%20checks%7CUSD-NGN%20%2F%20KES%20Exotics%3A%3A23%25%20settled%20%3C%2060m%20%E2%80%94%20G003%20FX%20regulatory%20documentation&metrics=Tracker%20Endpoint%3A%3ATRCKCHZZ%3A%3ASWIFT%20GPI%20status%20hub%20BIC%7CAPI%20Protocol%3A%3AREST%20JSON%20v5%3A%3AOAuth2%20%2B%20PKI%20signed%20calls%7CG20%20Speed%20Target%3A%3A75%25%20%3C%3D%201%20hr%3A%3A2027%20wholesale%2Fretail%20goal%7CCover%20Wait%20Code%3A%3AACSP%2FG004%3A%3AFlags%20split%20pacs.009%20lag)

## Corridor Transit Latency and Fee Slippage Attribution Formula

By extracting hop-by-hop timestamps (`t_i`) and sequential settled amounts (`Amt_i`) from the GPI Tracker JSON array for a given UETR, payment analytics teams decompose end-to-end remittance friction into compliance/cutoff dwell time and cumulative intermediary fee erosion.

The attribution model below calculates total all-in corridor cost basis points (`TC_bps`) and intermediary dwell share across a multi-hop UETR trace.

```formula
TC_bps = [ (Amt_init - (Amt_cred / FX_mid)) / Amt_init ] * 10,000
Dwell_Ratio_Compliance = Sum(t_dep_k - t_arr_k for G003/Hold) / (t_ACCC - t_dispatch)

Where:
 Amt_init = Instructed USD amount in pacs.008 IntrBkSttlmAmt ($50,000.00)
 Amt_cred = Final credited EUR amount reported in ACCC pacs.002 (EUR 45,890.00)
 FX_mid = Wholesale interbank EUR/USD mid-rate at dispatch (1.0850 -> EUR 46,082.95 par)

Worked UETR Trace Audit:
 Equivalent USD Credited = 45,890.00 * 1.0850 = $49,790.65 (after $25 + $20 lifting + FX spread)
 Total Friction Loss = $50,000.00 - $49,790.65 = $209.35
 TC_bps = ($209.35 / $50,000.00) * 10,000 = 41.87 bps all-in corridor cost
```

## Frequently asked questions

### What is the difference between InstrId, EndToEndId, and UETR in ISO 20022 pacs.008?

InstrId is a point-to-point reference reset by each instructing agent along the chain; EndToEndId is the debtor’s original invoice/customer reference passed unaltered to the beneficiary; UETR is the 36-character UUIDv4 tracking key used by SWIFT GPI across all pacs and camt messages.

### Why does a SWIFT GPI trace pause at status ACSP with reason code G004?

ACSP/G004 means the beneficiary bank received the announcement pacs.008 directly from the debtor bank, but has not yet received settled funds via the separate pacs.009 COV cover payment routed through reimbursement correspondents.

### Are non-GPI banks required to send pacs.002 Universal Confirmations?

Yes. Under SWIFT’s Universal Confirmations mandate, all financial institutions receiving pacs.008 customer credit transfers on FINplus must confirm final credit (ACCC) or rejection (RJCT) within two business days, even if they are not full GPI service subscribers.

### Can corporate ERP systems query UETR tracking statuses directly?

Corporate treasuries access UETR telemetry either through SWIFT GPI for Corporates (pain.002 / camt multi-bank feeds) or via their cash-management bank’s embedded GPI Tracker REST APIs.


## Source URLs

- https://www.swift.com/standards/iso-20022/iso-20022-programme
- https://www.bis.org/cpmi/publ/d223.htm
- https://www.fsb.org/work-of-the-fsb/financial-innovation-and-structural-change/cross-border-payments/

## Citation

- APA: Claire Beaumont, CAMS, CTP. (2026). SWIFT GPI UETR End-to-End Payment Tracking and pacs.002 Status Reason Codes Across Clearing Corridors. PayClear Ledger. https://payclearledger.com/rails/swift-gpi-uetr-tracking-pacs002-status-telemetry-sla
- Canonical article: [SWIFT GPI UETR End-to-End Payment Tracking and pacs.002 Status Reason Codes Across Clearing Corridors](https://payclearledger.com/rails/swift-gpi-uetr-tracking-pacs002-status-telemetry-sla)
- Site research index: [PayClear Ledger](https://payclearledger.com/llms-full.txt)
