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

- **ID:** `banking/swift-gpi-cover-payment-mt202`
- **Domain:** banking
- **Category:** protocol_error
- **Error Code:** `GPI_COVER_EXCLUSION_ERR`
- **Verification:** ai_generated
- **Fix Rate:** 83%

## Root Cause

SWIFT GPI (Global Payments Innovation) tracking applies only to customer credit transfers (MT103) and not to cover payments (MT202 COV) used in correspondent banking, where the ordering bank sends funds via a separate cover message to the intermediary, and AI fails to distinguish between these message types, a common protocol error in treasury advice.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT GPI v2.0 (2023) | active | — | — |
| SWIFT Message Types Standards (MT103 vs MT202 COV) | active | — | — |
| ISO 20022 migration (2025) | active | — | — |

## Workarounds

1. **Advise the treasurer to use serial payments (MT103) instead of cover payments (MT202 COV) for cross-border transfers where GPI tracking is needed. Example: 'Configure your payment system to send MT103 with field 56A (intermediary) instead of MT202 COV.'** (88% success)
   ```
   Advise the treasurer to use serial payments (MT103) instead of cover payments (MT202 COV) for cross-border transfers where GPI tracking is needed. Example: 'Configure your payment system to send MT103 with field 56A (intermediary) instead of MT202 COV.'
   ```
2. **Use a payment hub that supports ISO 20022 (e.g., Finastra, SAP) to convert MT202 COV to MT103 serial payments, leveraging the 'Payment Initiation' API. Example command: 'Set payment type to 'C2C' (customer-to-customer) instead of 'C2B' (customer-to-bank).'** (82% success)
   ```
   Use a payment hub that supports ISO 20022 (e.g., Finastra, SAP) to convert MT202 COV to MT103 serial payments, leveraging the 'Payment Initiation' API. Example command: 'Set payment type to 'C2C' (customer-to-customer) instead of 'C2B' (customer-to-bank).'
   ```
3. **For urgent payments, use a GPI-compliant corridor like SWIFT gpi for MT103 and a separate non-GPI channel for cover payments, then manually track via the bank's portal. Advise: 'Ask your relationship manager for the bank's GPI tracker URL for MT103 payments only.'** (75% success)
   ```
   For urgent payments, use a GPI-compliant corridor like SWIFT gpi for MT103 and a separate non-GPI channel for cover payments, then manually track via the bank's portal. Advise: 'Ask your relationship manager for the bank's GPI tracker URL for MT103 payments only.'
   ```

## Dead Ends

- **** — GPI tracking is only enabled for MT103 messages; MT202 COV messages are not tracked because they are internal to correspondent banks and not visible to the end customer. The tracking ID (UETR) is present but not propagated for cover payments. (70% fail)
- **** — SWIFT rules require unique UETRs per message; reusing a UETR causes message rejection by the SWIFT network (error code 'UETR_DUPLICATE'). Additionally, cover payments are not routed through GPI trackers. (85% fail)
- **** — SWIFT GPI is a standard that explicitly excludes cover payments; no bank can enable it because the SWIFT network does not support tracking for MT202 COV. The only solution is to change the payment method to serial (MT103) or use a different network like TARGET2. (90% fail)