When practitioners discuss "ISO 20022", they often mean different things. ISO 20022 is a meta-standard — a methodology for defining payment messages — and within it sit several incompatible regional dialects. Getting them confused causes integration headaches.
MX is the umbrella term for ISO 20022 XML messages on SWIFT, in contrast to MT (the legacy FIN format). All pacs / pain / camt messages on SWIFT are MX.
CBPR+ (Cross-Border Payments and Reporting Plus) is the SWIFT usage guideline for cross-border payments. It defines which fields are mandatory, optional or forbidden in pacs.008 / pacs.009 / camt.054 etc. when sent over the SWIFT network. CBPR+ is what most banks mean when they say "ISO 20022 cross-border".
HVPS+ (High-Value Payments Systems Plus) is the parallel usage guideline for domestic RTGS systems — TARGET2, Fedwire, CHAPS, SIC, MEPS+ etc. all converge on HVPS+. Field requirements differ from CBPR+ in subtle but important ways.
The practical issue: a pacs.008 valid for CBPR+ may need adjustment to be valid for TARGET2's HVPS+ profile. Banks handle this translation at the network boundary.
EBA Clearing's EURO1 / STEP1 use their own usage guideline, as does Fedwire (slightly different from CHIPS, both within HVPS+). For multi-currency payment platforms, supporting CBPR+ alone is not enough.
For senders this is invisible. For payment-platform developers it is critical — testing against CBPR+ only and assuming TARGET2 will accept the same XML is a common cause of integration failures.
Annual updates are issued by the Payments Market Practice Group (PMPG). The 2025 update introduced stricter address structuring rules — fully structured addresses become mandatory in 2026.
Yes — Federal Reserve adopted HVPS+ for the Fedwire ISO 20022 cutover in 2025. The Bank of England uses it for the new CHAPS RTGS. HVPS+ is global.
Each RTGS has slightly different legal and operational requirements — for example, TARGET2 mandates the BIC of every intermediate bank, while CHIPS does not. The dialects formalize these regional needs.
No. GPI tracking operates on the UETR, which is identical across all dialects. The XML payload variations do not affect tracking.