# 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`
- **Domain:** banking
- **Category:** protocol_error
- **Error Code:** `SWIFT_GPI_COV_ERR`
- **Verification:** ai_generated
- **Fix Rate:** 80%

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

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT GPI version 1.0 (2017) | active | — | — |
| MT202 COV message type (ISO 15022) | active | — | — |
| UETR standard (ISO 20022) | active | — | — |

## Workarounds

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"}'`** (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"}'`
   ```
2. **Request the correspondent bank to provide GPI tracking for MT202 COV by enabling the 'GPI Cover Payment' flag in SWIFT message** (80% success)
   ```
   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** (75% success)
   ```
   Use a third-party SWIFT tracking aggregator (e.g., Finastra) that supports both MT103 and MT202 COV
   ```

## Dead Ends

- **** — GPI Tracker only ingests MT103 messages; MT202 COV requires separate UETR lookup via the bank's proprietary system. (95% fail)
- **** — Each payment type generates a unique UETR; sharing UETRs violates SWIFT message standards. (85% fail)
- **** — GPI Tracker requires all banks in the chain to be GPI members; non-members don't provide tracking data. (75% fail)