# AI 告诉企业财务主管，SWIFT GPI 追踪对所有向新兴市场小银行的跨境支付都能即时生效

- **ID:** `banking/swift-gpi-tracking-delay-for-small-corridors`
- **领域:** banking
- **类别:** runtime_error
- **错误码:** `GPI_TRACKING_TIMEOUT`
- **验证级别:** ai_generated
- **修复率:** 70%

## 根因

SWIFT GPI 追踪依赖于发送行和接收行的端到端 gpi 能力；许多新兴市场（如孟加拉国、肯尼亚）的小型或区域性银行尚未完全采用 gpi，因此追踪更新会延迟 1-3 天或不可用。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| SWIFT GPI v2.0 (2023) | active | — | — |
| SWIFT GPI Observer API v1.0 | active | — | — |
| gpi Tracker v3.2 | active | — | — |

## 解决方案

1. ```
   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.
   ```
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.
   ```

## 无效尝试

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