# AI tells a corporate treasurer that SWIFT GPI tracking works for all cross-border payments, ignoring correspondent bank limitations

- **ID:** `banking/swift-gpi-tracking-fail`
- **Domain:** banking
- **Category:** network_error
- **Error Code:** `SWIFT_GPI_TRACK_TIMEOUT`
- **Verification:** ai_generated
- **Fix Rate:** 78%

## Root Cause

SWIFT GPI (Global Payments Innovation) tracking requires both sender and receiver banks to be GPI members; many smaller correspondent banks in emerging markets are not GPI-enabled, causing tracking failures and delayed confirmations.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT GPI v1.4 | active | — | — |
| SWIFT MT103 standard 2024 | active | — | — |

## Workarounds

1. **Pre-validate GPI capability using SWIFT GPI directory API: curl -X GET https://api.swift.com/gpi/directory?bic=BANKUS33 -H 'Authorization: Bearer token' - check 'gpiMember' field before initiating payment** (78% success)
   ```
   Pre-validate GPI capability using SWIFT GPI directory API: curl -X GET https://api.swift.com/gpi/directory?bic=BANKUS33 -H 'Authorization: Bearer token' - check 'gpiMember' field before initiating payment
   ```
2. **Use alternative tracking via correspondent bank's proprietary platform (e.g., J.P. Morgan Access) for non-GPI corridors** (75% success)
   ```
   Use alternative tracking via correspondent bank's proprietary platform (e.g., J.P. Morgan Access) for non-GPI corridors
   ```
3. **Implement manual reconciliation using SWIFT FIN Copy service for non-GPI payments, requesting status via MT199 query** (70% success)
   ```
   Implement manual reconciliation using SWIFT FIN Copy service for non-GPI payments, requesting status via MT199 query
   ```

## Dead Ends

- **Assuming all banks in SWIFT network support GPI by default** — GPI is an opt-in service; only ~4,000 of 11,000 SWIFT members are GPI-enabled as of 2024 (90% fail)
- **Relying on MT103 status codes without checking GPI UETR** — Non-GPI banks use legacy MT103 without UETR (Unique End-to-End Transaction Reference), so tracking is impossible (85% fail)
- **Using SWIFT GPI API without fallback for non-GPI corridors** — API returns 'GPI_NOT_AVAILABLE' error; payment still processes but without tracking data (80% fail)