The G20 cross-border payments programme has been running since 2020, when leaders committed to a roadmap for making international payments faster, cheaper, more transparent and more inclusive. For most of that period, the targets felt distant and the timeline felt flexible. That is changing.

The 2030 deadline for the quantitative targets is close enough now that regulators in key jurisdictions are translating the high-level commitments into specific requirements. Compliance teams that haven't started preparing are already behind.

What the G20 targets actually say

The key quantitative targets set by the Financial Stability Board are:

These are ambitious targets. They imply significant infrastructure change in most markets — and significant compliance implications for institutions that serve international payment corridors.

Where the compliance gaps are appearing

The shift to faster payments creates friction with existing AML and sanctions screening processes. Manual intervention points that were acceptable in a T+2 or T+3 environment are not compatible with a one-hour SLA. Compliance teams are being asked to achieve the same or higher levels of assurance in a fraction of the time.

The practical implications include:

The ISO 20022 transition

ISO 20022 is the new global standard for financial messaging, and its adoption is accelerating. SWIFT's cross-border payments have been migrating to ISO 20022 since 2022, and the transition deadline for the legacy MT message formats is November 2025. For compliance teams, this means a richer data set — more information accompanying each payment — which both enables better screening and requires updated systems to process it.

Institutions that haven't migrated their systems to handle ISO 20022 data will face increasing friction in processing international payments as the new standard becomes the norm.

What compliance teams should be doing now

The institutions best positioned for the regulatory environment ahead are those treating these changes as infrastructure decisions, not compliance ones. The technology needs to support real-time screening, ISO 20022 data handling, and end-to-end payment tracking before the regulatory requirement arrives — not after.

For teams evaluating their infrastructure, the questions to ask are: Can your current platform screen in real time? Does it support ISO 20022? Can it provide the transaction-level transparency that regulators and customers will increasingly expect?

If the honest answer to any of those questions is no, the window for addressing it is narrowing.

Sources: G20 cross-border payments targets and FSB quantitative goals: Financial Stability Board — Cross-border Payments. ISO 20022 migration timeline: SWIFT ISO 20022 programme.
Note: This article is intended as a general overview. Specific regulatory requirements vary by jurisdiction. Cymonz's compliance infrastructure is configurable to meet local requirements — speak to our team for a conversation about your specific environment.