MT202 COV vs pacs.009 COV
The two cover messages that fund a customer payment travelling by the cover method: the legacy SWIFT MT202 COV and its ISO 20022 successor, the pacs.009 COV. Both carry the money bank to bank while repeating the underlying customer details so intermediaries can screen the real parties.
| DIMENSION | MT202 COV | pacs.009 COV |
|---|---|---|
| Message standardBoth are financial-institution transfers used specifically to cover an underlying customer credit transfer. | A legacy SWIFT MT (message type) in the FIN format: fixed field tags, a 4-character message type, and character-set limits inherited from the network. | An ISO 20022 (MX) message in structured XML: named elements, richer data types, and a Business Application Header carrying routing and identity metadata. |
| Underlying customer details | Sequence B of the MT202 COV repeats the ordering and beneficiary customers from the underlying MT103, so the cover leg is not anonymous. | A dedicated underlying-transaction block repeats the debtor and creditor from the pacs.008, in the same structured fields the original used. |
| Data structure and richness | Party names and addresses sit in free-text lines with tight length limits, so long or structured addresses are often truncated. | Names, structured postal addresses, and identifiers such as the LEI (Legal Entity Identifier) have dedicated elements, so more survives intact for screening and reconciliation. |
| End-to-end tracking | Under SWIFT gpi (global payments innovation) the UETR (unique end-to-end transaction reference) rides in a header block, letting a tracker join the legs. | The UETR is a native, mandatory field, so end-to-end tracking is built into the message rather than added alongside it. |
| Standing and timelineDuring the coexistence period a bank may have had to translate between the two, with the truncation risks that implies. | Being retired for in-scope cross-border payments: SWIFT ended MT-to-ISO 20022 coexistence for cross-border instructions in November 2025. | The successor format for cross-border cover payments under CBPR+ (Cross-Border Payments and Reporting Plus) usage guidelines. |
Sources for this comparison3
- Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · MT202 COV usage rules
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login; content here relies on public summaries. Swift ended MT-to-ISO 20022 coexistence for in-scope cross-border payment instructions (for example MT103 and MT202) in November 2025; MT statement messages are being phased out on a separate timeline.
- Market practice
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · pacs.009 COV cover payment usage guidelines
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Both messages have many optional fields and usage rules this comparison omits; the migration timeline is summarised and varies by corridor and message subtype.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.