# AI tells a corporate treasurer that SWIFT GPI tracking works instantly for all cross-border payments to small banks in emerging markets

- **ID:** `banking/swift-gpi-tracking-delay-for-small-corridors`
- **Domain:** banking
- **Category:** runtime_error
- **Error Code:** `GPI_TRACKING_TIMEOUT`
- **Verification:** ai_generated
- **Fix Rate:** 70%

## Root Cause

SWIFT GPI tracking relies on end-to-end gpi capabilities at both sending and receiving banks; many small or regional banks in emerging markets (e.g., in Bangladesh, Kenya) have not fully adopted gpi, so tracking updates are delayed by 1-3 days or unavailable.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT GPI v2.0 (2023) | active | — | — |
| SWIFT GPI Observer API v1.0 | active | — | — |
| gpi Tracker v3.2 | active | — | — |

## Workarounds

1. **Use SWIFT GPI's 'gpi Observer' tool to manually check the status via the receiving bank's BIC, if available.** (80% success)
   ```
   Use SWIFT GPI's 'gpi Observer' tool to manually check the status via the receiving bank's BIC, if available.
   ```
2. **Pre-fund the payment via a correspondent bank that supports gpi, such as JP Morgan or Citi, for the final leg to the small bank.** (85% success)
   ```
   Pre-fund the payment via a correspondent bank that supports gpi, such as JP Morgan or Citi, for the final leg to the small bank.
   ```
3. **Example script to poll for gpi status using SWIFT's API (pseudo-code):
curl -X GET 'https://api.swift.com/gpi/v1/payments/{uetr}/status' \
-H 'Authorization: Bearer {token}' \
-H 'Accept: application/json'
# Parse 'confirmationTimestamp' field; if null after 24 hours, initiate manual check.** (75% success)
   ```
   Example script to poll for gpi status using SWIFT's API (pseudo-code):
curl -X GET 'https://api.swift.com/gpi/v1/payments/{uetr}/status' \
-H 'Authorization: Bearer {token}' \
-H 'Accept: application/json'
# Parse 'confirmationTimestamp' field; if null after 24 hours, initiate manual check.
   ```

## Dead Ends

- **** — The issue is the receiving bank's lack of gpi support, not the message format; resending does not change the bank's infrastructure. (90% fail)
- **** — Sending bank can only provide gpi data up to the correspondent bank; if the receiving bank doesn't send gpi confirmation, tracking stops. (75% fail)
- **** — The payment may have been credited, but tracking is delayed; a premature recall can cause double payments or fees. (60% fail)