# AI tells a corporate treasurer that SWIFT GPI covers all cross-border payment types, ignoring that cover payments (MT202 COV) are rejected by many correspondent banks

- **ID:** `banking/swift-gpi-cover-payment-rejection`
- **Domain:** banking
- **Category:** protocol_error
- **Error Code:** `MT202 COV rejected: correspondent not GPI-enabled`
- **Verification:** ai_generated
- **Fix Rate:** 82%

## Root Cause

SWIFT GPI (Global Payments Innovation) primarily tracks serial payments (MT103); cover payments (MT202 COV) are not supported by all GPI members, leading to tracking failures and rejections.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT GPI 2024 | active | — | — |
| ISO 20022 2023 | active | — | — |
| SWIFT MT message standards 2024 | active | — | — |

## Workarounds

1. **Check the GPI directory (https://www.swift.com/gpi) to verify if all correspondent banks in the chain are GPI-enabled; if not, use serial payment (MT103) for the customer transfer.** (90% success)
   ```
   Check the GPI directory (https://www.swift.com/gpi) to verify if all correspondent banks in the chain are GPI-enabled; if not, use serial payment (MT103) for the customer transfer.
   ```
2. **If cover payment is required by local regulation, send MT202 COV but request the beneficiary bank to confirm receipt via a GPI tracker (UETR).** (75% success)
   ```
   If cover payment is required by local regulation, send MT202 COV but request the beneficiary bank to confirm receipt via a GPI tracker (UETR).
   ```
3. **Use SWIFT's Transaction Manager (if available) to route the payment through GPI-enabled correspondents only.** (80% success)
   ```
   Use SWIFT's Transaction Manager (if available) to route the payment through GPI-enabled correspondents only.
   ```

## Dead Ends

- **** — Only ~70% of correspondent banks are GPI-enabled; the rest reject MT202 COV or process it without tracking, causing loss of visibility. (85% fail)
- **** — MT103 is for customer transfers; using it for interbank cover violates SWIFT rules and may cause compliance flags. (90% fail)
- **** — This defeats the purpose of cover payments (separating customer funds from bank funds) and may breach local regulations. (80% fail)