After November 2025, the MT message format used by SWIFT will no longer be supported on the SWIFT network. This transition requires all network participants to adopt the ISO 20022 standard payment messages discussed in earlier chapters.
To facilitate this migration, SWIFT has introduced two dedicated programs:
- CBPR+ (Cross-Border Payment Reporting Plus)
- HVPS+ (High-Value Payment Systems Plus)
CBPR + and HVPS + programs assist participants in transitioning from SWIFT MT messages to the ISO 20022 messages, referred to as MX messages. IN CBPR+ and HVPS +, SWIFT has provided guidelines for translating MT messages into their MX equivalents. Rather than directly adopting the vanilla ISO 20022 messages, SWIFT implemented modifications to ISO Xsd’s to align the messages with the legacy MT format.
For example, The Street Name field in the standard ISO 20022 message allows a length of 140 characters but the CBPR+ and HVPS+ messages restrict it to 70 characters to make it consistent with MT messages.
Participants can access the detailed CBPR+ and HVPS+ guidelines via the following links:
- https://www2.swift.com/mystandards/#/c/cbpr/landing
- https://www2.swift.com/mystandards/#/group/HVPSPlus
Converting MT messages to MX messages can be a complex process. Organizations like Prowide, Payments Components, and Volante, offer specialized solutions to support banks in migrating from MT to MX hassle-free.
Below is a list mapping MT messages to their ISO 20022 counterparts:
| Category | MT Message | ISO 20022 (MX) Equivalent |
| Category 1 | MT 101 | pain.001.001.09 |
| MT 102 | pacs.008.001.08 | |
| MT 103 | pacs.008.001.08 | |
| MT 103 REMIT | pacs.008.001.08 | |
| MT 103 STP | pacs.008.001.08 | |
| MT 103 /RETN/ | pacs.004.001.09 | |
| MT 104 / MT 107 | pain.008.001.08 / pacs.003.001.08 | |
| MT 110 | camt.107.001.01 | |
| MT 111 | camt.108.001.01 | |
| MT 112 | camt.109.001.01 | |
| MT 190 | camt.105.001.02 (Single Transaction) | |
| MT 191 | camt.106.001.02 (Single Transaction) | |
| MT 192 | camt.056.001.08 | |
| MT 196 | camt.029.001.09 / camt.111.001.01 | |
| MT 195 (Query) | camt.110.001.01 | |
| MT 199 (Investigation Request / Response) | camt.110.001.01 / camt.111.001.01 / admi.024.001.01 | |
| Category 2 | MT 200 | pacs.009.001.08 |
| MT 201 | pacs.009.001.08 | |
| MT 202 | pacs.009.001.08 | |
| MT 202 (ADV) | pacs.009.001.08 ADV | |
| MT 202 COV | pacs.009.001.08 COV | |
| MT 202 /RETN/ | pacs.004.001.09 | |
| MT 203 | pacs.009.001.08 | |
| MT 204 | pacs.010.001.03 | |
| MT 205 | pacs.009.001.08 | |
| MT 205 COV | pacs.009.001.08 COV | |
| MT 205 /RETN/ | pacs.004.001.09 | |
| MT 210 | camt.057.001.06 | |
| MT 290 | camt.105.001.02 (Single Transaction) | |
| MT 291 | camt.106.001.02 (Single Transaction) | |
| MT 292 | camt.056.001.08 | |
| MT 295(Query) | camt.110.001.01 | |
| MT 296 (Response) | camt.029.001.09 / camt.111.001.01 | |
| MT 299(Request / Response) | camt.110.001.01 / camt.111.001.01 / admi.024.001.01 | |
| Category 9 | MT 900 | camt.054.001.08 |
| MT 910 | camt.054.001.08 | |
| MT 920 | camt.060.001.05 | |
| MT 935 | camt.053.001.08 | |
| MT 940 | camt.053.001.08 | |
| MT 941/942 | camt.052.001.08 | |
| MT 950 | camt.053.001.08 |
Example of a MT 202 Sample with its converted Pacs.009 Message
