# AI tells a corporate treasurer that they can still use MT103 for cross-border payments after November 2025, ignoring the ISO 20022 migration deadline

- **ID:** `banking/mt103-unavailable-after-iso20022-migration`
- **Domain:** banking
- **Category:** protocol_error
- **Error Code:** `SWIFT-ISO20022-MT103-DEPRECATED`
- **Verification:** ai_generated
- **Fix Rate:** 75%

## Root Cause

SWIFT mandated a global migration from MT to ISO 20022 (MX) message formats for cross-border payments and cash reporting by November 2025, after which MT103 messages are no longer accepted on the SWIFT FIN network for new payments.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| SWIFT FIN MT103 (pre-2025) | active | — | — |
| ISO 20022 pacs.008.001.08 (post-2025) | active | — | — |
| SWIFT GPI v2.0 | active | — | — |

## Workarounds

1. **Migrate to ISO 20022 MX pacs.008.001.08: modify payment initiation system to generate MX XML and use SWIFT GPI v2.0. Example: in a Java application using SWIFT Alliance Gateway, replace outgoing MT103 mapping with MX pacs.008 generation via JAXB: 'JAXBContext.newInstance(Pacs008.class).createMarshaller().marshal(pacs008, outputStream)'** (85% success)
   ```
   Migrate to ISO 20022 MX pacs.008.001.08: modify payment initiation system to generate MX XML and use SWIFT GPI v2.0. Example: in a Java application using SWIFT Alliance Gateway, replace outgoing MT103 mapping with MX pacs.008 generation via JAXB: 'JAXBContext.newInstance(Pacs008.class).createMarshaller().marshal(pacs008, outputStream)'
   ```
2. **Use a SWIFT-certified translation service like SWIFT Translator or a fintech middleware (e.g., Finastra) that automatically converts MT103 to MX on the fly, but ensure testing covers all field mappings.** (70% success)
   ```
   Use a SWIFT-certified translation service like SWIFT Translator or a fintech middleware (e.g., Finastra) that automatically converts MT103 to MX on the fly, but ensure testing covers all field mappings.
   ```

## Dead Ends

- **Converting MT103 to MX format using a simple field mapping tool without updating the underlying payment workflow** — The MX message requires additional structured data (like structured remittance information and purpose codes) that MT103 doesn't carry; simple mapping often leads to rejected messages due to missing mandatory fields. (65% fail)
- **Continuing to send MT103 via SWIFT FileAct as a fallback** — SWIFT will block all MT103 messages on the FIN network after November 2025, and FileAct also requires ISO 20022 compliance for cross-border payments; there is no grandfather clause for legacy formats. (80% fail)