Iso20022 Pacs008 Cbpr Plus Clearing
SWIFT GPI UETR End-to-End Payment Tracking and pacs.002 Status Reason Codes Across Clearing Corridors
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.

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. 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, 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.
Universal Confirmations Mandate and Fee/FX Deduction Transparency#
Aligned with the G20 Cross-Border 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.
| 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 | Closed / Auto-Reroute |
Webhook API Integration and Proactive Exception Escalation#
Modern payment orchestration hubs at 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 before beneficiary credit.
Review the broader CBPR+ ISO 20022 clearing topic hub to connect GPI status reason telemetry with automated Nostro liquidity sweeps.
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.
- DwellRatioCompliance = Sum(tdepk - tarrk for G003/Hold) / (tACCC - tdispatch)
- 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.
Publication record
- Published
- November 14, 2026
- Updated
- November 14, 2026
- Author
- Claire Beaumont, CAMS, CTP
- Review
- Review not recorded
- Automated fact check
- Passed in the stored pipeline record
- Source URLs
- 3 recorded
AI assistance recorded: anthropic/claude-opus-4.6. This field does not establish human review or source verification.
Academic & Institutional Attribution
Cite This Research & Embed Live Data Card
Standard academic & institutional research paper citation format.
Claire Beaumont, CAMS, CTP. (2026, November 14). 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-slaRelated Iso20022 Pacs008 Cbpr Plus Clearing & Institutional Briefings
Explore Iso20022 Pacs008 Cbpr Plus Clearing Hub (20) →Iso20022 Pacs008 Cbpr Plus Clearing
SWIFT CBPR+ ISO 20022 pacs.008 & pacs.009 Clearing Architecture: 2026 Institutional GuideIso20022 Pacs008 Cbpr Plus Clearing
ISO 20022 camt.056 Payment Cancellation and camt.029 Recall Resolution Workflows in Cross-Border ClearingIso20022 Pacs008 Cbpr Plus Clearing
Fedwire Funds Service ISO 20022 Schema: IMAD/OMAD Mapping and High-Value Wire Transfer SettlementIso20022 Pacs008 Cbpr Plus Clearing
Bank of England CHAPS ISO 20022 Enhanced Data: Purpose Codes and LEI Mandates in Sterling ClearingIso20022 Pacs008 Cbpr Plus Clearing
Eurosystem T2 RTGS ISO 20022 Clearing: Central Liquidity Management and pacs.009 Wholesale SettlementIso20022 Pacs008 Cbpr Plus Clearing
CHIPS ISO 20022 High-Value Clearinghouse Mechanics: Multilateral Netting Algorithms and Intraday FinalityIso20022 Pacs008 Cbpr Plus Clearing
Serial pacs.008 vs Cover Method pacs.009 COV Routing: Transparency and Settlement Latency on SWIFT RailsIso20022 Pacs008 Cbpr Plus Clearing
Preventing ISO 20022 Field Truncation: UTF-8 MX Character Sets and Legacy Payment Gateway RepairEmi Safeguarding Psd2 Psr Accounts
Safeguarding Electronic Money via Secure Liquid Low-Risk Assets: Sovereign Debt Haircuts and Custody RulesEmi Safeguarding Psd2 Psr Accounts
D+1 Internal and External Safeguarding Reconciliations: Resolving Relevant Funds Shortfalls for EMIsEmi Safeguarding Psd2 Psr Accounts
Annual Independent Safeguarding Audits for UK EMIs and PIs: Material Breach Reporting and RemediationEmi Safeguarding Psd2 Psr Accounts
Direct Non-Bank PSP Access to Bank of England CHAPS and Eurosystem TARGET Settlement Accounts
PayClear Ledger Data, Benchmarks & Contributor Records
CC BY 4.0 Open Data
Open Institutional Datasets (CSV / JSON) →
Download desk-compiled quantitative series & schemas.
2026 Reference Matrix
2026 Institutional Benchmarks & Thresholds →
Statutory capital, clearing, margin & rate conventions.
Editorial Records
Authors & Review Records →
View named contributors where those records are available.
Complete Index
Master Research & Dossier Archive →
Browse all published briefings by topic pillar & date.
