SWIFT_GPI_TRACK_TIMEOUT banking network_error ai_generated partial

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

Also available as: JSON · Markdown · 中文
78%Fix Rate
83%Confidence
1Evidence
2024-04-05First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
SWIFT GPI v1.4 active — — —
SWIFT MT103 standard 2024 active — — —

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.

generic

中文

SWIFT GPI（全球支付创新）追踪要求发送方和接收方银行均为GPI成员；许多新兴市场的小型代理行未启用GPI，导致追踪失败和确认延迟。

Official Documentation

https://www.swift.com/our-solutions/payments/gpi

Workarounds

  1. 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 
    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. 75% success Use alternative tracking via correspondent bank's proprietary platform (e.g., J.P. Morgan Access) for non-GPI corridors 
    Use alternative tracking via correspondent bank's proprietary platform (e.g., J.P. Morgan Access) for non-GPI corridors
  3. 70% success Implement manual reconciliation using SWIFT FIN Copy service for non-GPI payments, requesting status via MT199 query 
    Implement manual reconciliation using SWIFT FIN Copy service for non-GPI payments, requesting status via MT199 query

中文步骤

  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
  2. 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

Dead Ends

Common approaches that don't work:

  1. Assuming all banks in SWIFT network support GPI by default 90% fail

    GPI is an opt-in service; only ~4,000 of 11,000 SWIFT members are GPI-enabled as of 2024

  2. Relying on MT103 status codes without checking GPI UETR 85% fail

    Non-GPI banks use legacy MT103 without UETR (Unique End-to-End Transaction Reference), so tracking is impossible

  3. Using SWIFT GPI API without fallback for non-GPI corridors 80% fail

    API returns 'GPI_NOT_AVAILABLE' error; payment still processes but without tracking data