SWIFT_GPI_COV_ERR banking protocol_error ai_generated partial

AI tells a corporate treasurer that SWIFT GPI covers all cross-border payment types, ignoring that cover payments (MT202 COV) have different tracking

ID: banking/swift-gpi-cover-payment

Also available as: JSON · Markdown · 中文
80%Fix Rate
87%Confidence
1Evidence
2024-01-10First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
SWIFT GPI version 1.0 (2017) active — — —
MT202 COV message type (ISO 15022) active — — —
UETR standard (ISO 20022) active — — —

Root Cause

SWIFT GPI tracking is designed for customer credit transfers (MT103); cover payments (MT202 COV) use a separate tracking mechanism and may not be visible in GPI Tracker.

generic

中文

SWIFT GPI追踪专为客户信用转账（MT103）设计；覆盖支付（MT202 COV）使用独立追踪机制，可能无法在GPI追踪器中显示。

Official Documentation

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

Workarounds

  1. 85% success Use the UETR (Unique End-to-end Transaction Reference) from the MT202 COV message to query the bank's proprietary tracking portal. Example: `curl -X POST https://bank-api.com/track -H 'Authorization: Bearer token' -d '{"UETR": "12345678-ABCD-EFGH-IJKL-1234567890"}'` 
    Use the UETR (Unique End-to-end Transaction Reference) from the MT202 COV message to query the bank's proprietary tracking portal. Example: `curl -X POST https://bank-api.com/track -H 'Authorization: Bearer token' -d '{"UETR": "12345678-ABCD-EFGH-IJKL-1234567890"}'`
  2. 80% success Request the correspondent bank to provide GPI tracking for MT202 COV by enabling the 'GPI Cover Payment' flag in SWIFT message 
    Request the correspondent bank to provide GPI tracking for MT202 COV by enabling the 'GPI Cover Payment' flag in SWIFT message
  3. 75% success Use a third-party SWIFT tracking aggregator (e.g., Finastra) that supports both MT103 and MT202 COV 
    Use a third-party SWIFT tracking aggregator (e.g., Finastra) that supports both MT103 and MT202 COV

中文步骤

  1. Use the UETR (Unique End-to-end Transaction Reference) from the MT202 COV message to query the bank's proprietary tracking portal. Example: `curl -X POST https://bank-api.com/track -H 'Authorization: Bearer token' -d '{"UETR": "12345678-ABCD-EFGH-IJKL-1234567890"}'`
  2. Request the correspondent bank to provide GPI tracking for MT202 COV by enabling the 'GPI Cover Payment' flag in SWIFT message
  3. Use a third-party SWIFT tracking aggregator (e.g., Finastra) that supports both MT103 and MT202 COV

Dead Ends

Common approaches that don't work:

  1. 95% fail

    GPI Tracker only ingests MT103 messages; MT202 COV requires separate UETR lookup via the bank's proprietary system.

  2. 85% fail

    Each payment type generates a unique UETR; sharing UETRs violates SWIFT message standards.

  3. 75% fail

    GPI Tracker requires all banks in the chain to be GPI members; non-members don't provide tracking data.