FSB Cross-Border Payments Progress Report 2026: KPIs and 2027 Dates
On 16 November 2026 the Financial Stability Board (FSB) published G20 Roadmap for Enhancing Cross-border Payments: Consolidated progress report for 2026. The FSB cross-border payments progress report says the FSB, the Committee on Payments and Market Infrastructures (CPMI) and partner organisations have largely completed the policy work envisaged in the 2020 Roadmap and its 2023 update, while progress in the end-user experience, as measured by the key performance indicators (KPIs) for cost, speed, access and transparency, “remains gradual and uneven across payment segments and jurisdictions”. Most of the G20 targets carry an end-2027 date. The global average cost of retail cross-border payments has not moved since monitoring began in 2023.
FSB publications state that its activities “shall not be binding or give rise to any legal rights or obligations”, and the report adds no template, threshold or filing deadline for firms. Its relevance for payment service providers (PSPs) and the teams that own payment data sits in the 2027 calendar it sets out and in the measurements it publishes. Several KPIs are computed from payment messages and published price information that PSPs themselves generate, and the open policy items (the FATF guidance on Recommendation 16, ISO 20022 harmonisation, legal entity identifier (LEI) adoption and cross-border data sharing) all land on message fields, customer disclosures and data flows.
Annex 3 carries the KPI tables, and Annex 2 summarises the 2026 FSB-CPMI monitoring survey on legal, regulatory and supervisory (LRS) matters.
Related reading: G20 Cross-Border Payments Targets: The 2027 Reporting Countdown
Dates the 2026 report puts on the calendar
The 2026 report, the 2021 targets report, the Bank of England’s CHAPS policy statement and Sveriges Riksbank’s action plan fix the following dates. The UK and Swedish dates are jurisdiction-specific and are labelled as such.
- 30 October 2026: the date by which the FSB Chair asked jurisdictions to develop a cross-border payments action plan, as quoted in Sveriges Riksbank’s published response.
- Early 2027: the FSB will publish a summary report highlighting key observations from the jurisdictional action plans.
- 2027: the FATF aims to adopt its Guidance on Recommendation 16, following a public consultation that ran from June to August 2026.
- 2027: the FSB’s Standing Committee on Standards Implementation will conduct a thematic peer review of FSB members’ implementation of the two December 2024 sets of FSB recommendations on cross-border payments.
- March 2027 (Sweden): RIX INST begins supporting the Nordic Payments Council’s One-Leg-Out Instant Credit Transfer scheme (NOLO Inst).
- November 2027 (UK): the Bank of England will extend mandatory purpose codes to all CHAPS payments initiated through channels within direct CHAPS participants’ control. It will also mandate LEIs for pacs.004 return payments and pacs.009 COV payments between financial institutions, within those controlled channels.
- End-2027: common target date for the G20 targets, with the exception of the remittance cost target.
- End-2028: a further 28% of RTGS systems and 2% of fast payment systems (FPS) are expected to have migrated to ISO 20022.
- 2030: target date for the remittance cost target, and the end-2030 date by which the revised FATF Recommendation 16 is expected to come into effect.
One date is absent. The report says the phase-out of fully unstructured postal addresses in ISO 20022 cross-border payment messages on the Swift network was postponed, and it gives no replacement date.
A report to the G20, measured at global level
The consolidated progress report is the FSB’s annual delivery under priority action 13 of the Roadmap, “Monitoring and progress reporting”, which Annex 1 lists as ongoing and annual. Since 2025 the FSB has folded the separate KPI monitoring report into this single consolidated document. The report is organised around the three priority themes from 2023: payment system interoperability and extension; legal, regulatory and supervisory frameworks; and cross-border data exchange and message standards.
The 2021 targets report states that the targets “are set at a global level”. A PSP that reads Annex 3 as a scorecard for its own service is reading it beyond its design: the G20 retail cost target is a global average of no more than 1%, with no corridors above 3%, and no single provider is measured against it in the report. The Swedish action plan discussed below shows one authority applying the targets to national bank price data.
The survey in Annex 2 is a survey of jurisdictions, distributed in April 2026 with responses gathered until August 2026. The respondent list changed between years: the 2026 list in Table A adds, among others, Switzerland and the Netherlands, while Norway and New Zealand appear only in the 2025 column. Headline percentages therefore compare different populations, which is why the report adds common-sample comparisons for several questions, and the two can diverge by several points.
FSB cross-border payments progress report: the KPI table
The table below reproduces the global KPIs most relevant to PSPs from Annex 3, against the G20 targets set in October 2021. Wholesale figures come from Swift data for Q1 of each year, retail figures from FXC Intelligence as of March, and remittance figures from the World Bank’s Remittance Prices Worldwide database for Q1.
| Segment and measure | 2023 | 2026 | G20 target |
|---|---|---|---|
| Wholesale: payments (other than forward-dated) credited within one hour of initiation | 53.8% | 57% | 75% within one hour of initiation (forward-dated: of the agreed settlement time), the rest within one business day, by end-2027 |
| Wholesale: payments (other than forward-dated) credited within one business day | 92.7% | 93.9% | Covered by the same speed target |
| Retail: services (by PSP) crediting recipients within one hour | 34.2% | 32.9% | 75% within one hour, the rest within one business day, by end-2027 |
| Retail: services (by PSP) crediting within one business day | 74% | 59.8% | Covered by the same speed target |
| Retail: average cost by use case (B2B for MSMEs / B2P / P2B / P2P excluding remittances) | 1.5% / 1.7% / 2% / 2.5% | 1.5% / 1.8% / 1.9% / 2.7% | Global average no more than 1%, no corridor above 3%, by end-2027 |
| Retail: corridors with costs above 3% | 23.7% | 15.1% | No corridors above 3% |
| Remittances: global average cost of sending USD 200 | 6.3% | 5.7% (6.2% without adjustment) | No more than 3% by 2030, no corridor above 5% |
| Remittances: services making funds available within one hour | 52.6% | 60% | 75% within one hour in every corridor, the rest within one business day, by end-2027 |
| Retail: payment services providing cost and speed information | 54.5% | 67.5% | All PSPs disclose total cost, expected time, payment status and terms of service to payers and payees, by end-2027 |
Wholesale speed and remittance speed improved, the share of very expensive retail corridors fell by 8.6 percentage points (pp) since 2023, and the share of retail payment services providing speed information, among services already transparent about costs, rose by 13 percentage points over the same period. Retail speed fell on both measures. Retail average costs were flat, with B2B at 1.5% and B2P at 1.8% sitting closest to the 1% target. The report also introduces a wholesale payment-status metric based on Swift confirmation data: 85.9% of wholesale payments had been credited with the confirmation reported to the Swift Tracker in Q1 2026, with regional values from 67.8% for Africa to 91% for Europe outside the euro zone.
Three readings of Annex 3 that the footnotes rule out
The footnotes to Section 3 and Annex 3 carry qualifications that change what a number can support in an internal report or a board paper.
The remittance cost decline is mostly a rebasing effect
The global average cost of sending USD 200 fell from 6.3% in 2023 to 5.7% in 2026, and USD 500 from 4.3% to 3.8%. The report states that this slight decline “was entirely due to adjustments” to local currency equivalents of the USD 200 and USD 500 benchmarks, rebased in 2026 for exchange rate movements in Brazil, South Africa, Rwanda, Japan, Norway, Tanzania and Australia. Without the adjustments, the cost would have remained broadly unchanged at 6.2% and 4%. This is the most important qualification in Annex 3 for anyone quoting a remittance cost trend.
Retail speed is measured from pre-initiation information
The retail speed KPIs count payment services by PSP, and footnote 41 states that they rely on information about execution time available before the payment is initiated. They do not reflect actual execution times. A PSP comparing its own end-to-end crediting data with the 32.9% figure is comparing two different things: realised speed for its flows against the advertised speed of a population of services.
Coverage changes move the averages
The report warns that changes in sample composition, which have tended to expand the sample, make it hard to separate genuine market improvement from coverage effects. For the expensive-corridor KPI, the decline among payment services common to 2025 and 2026 was 1.7 pp, against 3.2 pp for the full sample, which the report reads as newly added services being more often priced below the 3% threshold. Receiver-side costs show the same care: 1.4% of the value for payments below USD 500, plus 0.9% where a currency conversion is needed, and the report states that these cannot simply be added to the sender-side averages, since they may be deducted from the amount received or invoiced between intermediaries.
Where payment-firm data enters the KPIs
Annex 3 and the receiver-side cost analysis in Section 3 draw on commercial datasets, World Bank databases and one voluntary survey of PSPs, and knowing which source applies tells a reporting team where its own data might already be in the numbers. None of the sources is a regulatory return.
| KPI area | Source named in the report | Reference point |
|---|---|---|
| Wholesale speed and payment status | Swift Observer analytics | Q1 of each year |
| Wholesale access | Swift data on institutions active per country | Q1 of each year |
| Retail cost, speed and speed transparency | FXC Intelligence | Data as of March |
| Remittance cost and speed | World Bank Remittance Prices Worldwide | Q1 of each year |
| Receiver-side retail costs | Voluntary, anonymous firm-level survey of PSPs from FSB and Regional Consultative Group members and World Bank members | Third collection; 304 responses from 44 jurisdictions, up from 262 |
| Retail and remittance account access | World Bank Findex, Enterprise Survey and Global Payments Systems Survey | Survey years vary; several 2026 cells are NA |
Two gaps are worth knowing. Annex 3 states that no source is currently available for wholesale KPI 3 (forward-dated payments credited on the agreed date) or KPI 4 (payments reconciled by the end of the crediting day), so the reconciliation element of the wholesale target is unmeasured. Swift also cautions that its statistics on financial flows do not represent complete market or industry statistics, because institutions have other channels to exchange information about their transactions.
Wholesale speed and the ISO 20022 cut-over
The wholesale improvement came from the beneficiary leg, which the methodology defines as the time from receipt of the payment by the beneficiary financial institution to crediting of the end user. According to Swift, contributing factors to this year’s gain may include better data quality from the migration of cross-border payments from MT to ISO 20022 messages in November 2025, continued infrastructure modernisation, and industry work to raise straight-through processing and reduce operational dependencies that delay crediting. The report frames these as possible factors, and no causal split is given.
Regional spreads are wide. North America credited 74.2% of wholesale payments within one hour, Europe’s euro zone rose 4.2 pp to 69.6% (entirely through the beneficiary leg), the Middle East moved from 25.7% to 37%, Asia-Pacific stood at 28.8% and Africa at 26%.
The ISO 20022 numbers come from the 2025 CPMI-FSB monitoring survey: 53% of RTGS systems and 77% of FPS have migrated to ISO 20022, while only 13% of RTGS systems and 19% of FPS have also aligned with the original CPMI harmonised data requirements. Migration and harmonisation are separate milestones. A system or bank that has completed the MT-to-ISO 20022 cut-over may still populate the messages in ways the harmonised requirements discourage. The report adds that 25% of RTGS systems and 12% of FPS have outlined plans to adopt the harmonised requirements.
The CPMI published its updated harmonised requirements on 26 February 2026, with a standalone technical annex of expanded data models. Our article on the CPMI harmonised ISO 20022 data requirements covers the requirements themselves.
The structured address item is where most firm-side data work sits. Unstructured postal addresses will “continue to be technically accepted for longer” on the Swift network, hybrid and fully structured addresses can already be used, and the CPMI requirements encourage structured data. Canada’s Lynx case study in Box 3 shows the gap between format and content: effectively all Lynx payment volume is transmitted in ISO 20022, yet as of early 2026 most Canadian messages still carry unstructured addresses. SEPA schemes run on a separate European Payments Council timeline, covered in our piece on the EPC SEPA structured address migration delay.
The Riksbank’s action plan adds a data-handling point that applies well beyond Sweden. It notes that some PSPs do not process ISO 20022 messages natively and convert them into proprietary formats for internal processing, and that those formats must support the full ISO 20022 data set to avoid data loss or truncation. For a reporting team, that conversion layer is where structured address lines, LEIs and remittance information can disappear before they reach the screening engine or the reporting warehouse.
LEI and purpose codes: what the CHAPS case study shows
Box 5 is the most concrete PSP-facing example in the report. The Bank of England is aligning CHAPS with the CPMI harmonised requirements ahead of the end-2027 timeline, and cross-border CHAPS payments are around half of CHAPS volumes. From May 2025 the Bank mandated purpose codes and LEIs for all CHAPS payments between financial institutions, and purpose codes for all property-related transactions.
The mandate has a scope boundary that is easy to miss. It applies to direct CHAPS participants for payment initiation channels where they can enforce the population of enhanced data, such as online banking or a corporate client request. Footnote 28 states that it excludes most incoming cross-border payments, because those are initiated in channels outside the direct participants’ control, such as Swift CBPR+. Non-compliance does not yet result in rejection, and coverage of purpose codes and LEIs for in-scope payments has exceeded 90%.
From November 2027, the Bank will extend the purpose-code mandate to all CHAPS payments initiated through channels within direct participants’ control. It will not extend the mandatory requirements to initiation channels outside that control at this stage.
The same box shows what the central bank does with the data. The Bank uses LEIs to assess indirect participant flows and tiering risk and to link datasets such as trade repository data using GLEIF APIs and daily downloads, and it uses the BIC and IBAN elements (which carry country codes) to classify cross-border CHAPS payments automatically. That classification model has also been used to identify payment-level costs for CHAPS payments initiated in a non-sterling currency, so that the Bank can assess costs against the G20 targets. In the CHAPS case, message fields populated for settlement now feed the central bank’s own analysis.
At the global level, the survey shows slow movement on identifiers. In 2026, 48% (39) of responding jurisdictions had taken no steps to enhance the use of global standard identifiers such as the LEI, against 59% (44) a year earlier; on the common sample the figure is 48% against 55%. Reasons cited include established national identifiers, data quality concerns and lack of resources. The FSB’s Forum on Cross-border Payments Data runs a workstream on staged LEI adoption under Recommendation 6 of the December 2024 data frameworks recommendations, which asks national authorities to support enhanced use of standardised global identifiers such as the LEI.
Recommendation 16: the guidance moves to 2027, the deadline stays at 2030
The FATF finalised its revision of Recommendation 16 on payment transparency in June 2025. The FSB’s 2025 progress report expected the implementing guidance to be completed in late 2026. The 2026 report moves that: the FATF consulted on draft Guidance from June to August 2026, engaging more than 180 respondents, and “aims to adopt the Guidance in 2027”. The changes to Recommendation 16 are expected to come into effect by the end of 2030, three years after the G20 end-2027 milestone. Our article on the FATF travel rule consultation on Recommendation 16 covers the consultation draft.
Box 2 lists what the Guidance is to address:
- Alignment checks: examples for the three implementation options (pre-validation, holistic ongoing monitoring and post-validation), and the notion and scope of alignment.
- Card transactions and cash withdrawals: the roles of card issuers and acquirers along the payment chain, how card networks can support the obligations, and the information sharing expected in cross-border cash withdrawals.
- Payment market infrastructures: their part in transmitting the required information across the chain.
- Financial inclusion and data protection: alternative identification and verification methods, and the fit between AML/CFT and data protection objectives.
The data content is already set at the standard level. The CPMI’s technical annex summarises it: cross-border payments above the applicable threshold carry the names of originator and beneficiary, account numbers (or a unique transaction reference), the originator’s address and the beneficiary’s country and town, the originator’s date of birth for natural persons, and, for legal persons where it exists, a BIC, an LEI or a unique official identifier. The FSB’s 2025 report puts the applicable threshold at no higher than USD/EUR 1,000. The CPMI describes its harmonised data model for persons and entities as identifier-neutral and as an early-alignment framework for these requirements, to be reviewed once the FATF Guidance is final.
Box 2 places card issuers, acquirers and card networks on the Guidance agenda. Teams reviewing Recommendation 16 should assess relevant card-funded transfers and cross-border cash withdrawals alongside credit transfers. The scope assessment must preserve the exemption for qualifying credit, debit and prepaid card transactions used to purchase goods or services. The FATF Guidance expected in 2027 will clarify implementation issues for the relevant payment types.
Data localisation rose in the 2026 survey
The data-framework results in Annex 2 move in different directions, and two of them affect group-wide payment operations directly.
- Data localisation: 48% (39) of responding jurisdictions had data localisation policies in 2026, against 31% (23) in 2025; on the common sample the share rose from 37% to 47%. Eight of the 39 reported no legal pathway or other arrangement to support cross-border data flows.
- Sharing with foreign authorities: 30% (24) do not allow PSPs to share payments data with foreign authorities, down from 46% (34), a trend the report says holds for common respondents.
- Privacy-protective transfer mechanisms: 31% (25) have no framework or mechanism for cross-border transfer of payment data with privacy protection, against 39% (29) in 2025, and only three jurisdictions plan to establish one by end-2028.
- Impact analysis: 36% (29) do not consider potential impacts or seek input from end users and PSPs when designing data-related policies.
Fraud is where these frictions bite. The report records limitations on sharing targeted information on payment fraud in a timely manner, and the April 2026 IIF-FSB summit on fraud and scams surfaced uncertainty about whether payment transaction details, including personally identifiable information, may be shared. It notes that IBANs, LEIs and mobile numbers are used differently across jurisdictions and sectors, which hinders information sharing, and it mentions clarifying legal “safe harbours” for specific use cases as one option. The CPMI’s PIE task force is working on pre-validation API harmonisation after its February 2026 fraud report. The report also cautions that pre-validation tools proven domestically, such as payee verification, remain hard to scale across borders because of legal and technical interoperability hurdles.
Non-bank PSPs: licensing, expectations and system access
The bank and non-bank strand reads as slow progress from a low base. In 2026, 32% (26) of responding jurisdictions reported that regulatory and supervisory expectations for cross-border payment services had not been issued or updated since 2020, against 43% (32) in 2025. A quarter, 25% (20), have no licensing or registration regime for PSPs, and 23% of those with a regime plan to review or adjust it. On sector risk assessments, 57% (46) responded negatively, against 64% (47) in 2025. Where assessments exist, AML/CFT dominates, with operational resilience a lesser focus.
Annex 1 closes the two international follow-ups. Action 4(a), standard setters adapting their standards to the FSB recommendations on bank and non-bank supervision, is marked completed because CPMI standards and guidance are already well aligned with them, so no additional adjustments or new standards are needed. Action 4(b), possible new recommendations on barriers to non-bank participation in payment systems, is also completed, with the focus shifted to implementing existing frameworks through established groups such as the PIE task force. Action 4(c), national authorities evaluating what changes to make to their frameworks, carries the date “In 2026”, and the FSB has invited jurisdictions to cover it in their action plans. Under this strand, any change to how a PSP is licensed or supervised sits with national authorities.
On access, the 2025 survey found that 45% of surveyed FPS and 39% of RTGS systems offered access to non-bank PSPs. Eleven of the 82 responding RTGS systems operated 24/7 in 2025, up from five in 2024, 13 extended their hours in 2025 and another 23 plan to. The PIE task force has developed a toolkit on expanding access to payment systems for non-bank PSPs, building on its February 2026 report.
What a national action plan contains: Sweden’s response
The FSB will summarise the action plans in early 2027, and Sweden’s is already public. Sveriges Riksbank published its Response to FSB: Action plan for G20 targets in October 2026, prepared with input from the Swedish Financial Supervisory Authority and informed by meetings with the five largest banks offering payment services in Sweden. The Riksbank states that the document complements the EU-level action plan submitted to the FSB.
The plan applies each target to Swedish data and names the frictions:
- Cost: the large banks charge a fixed fee of at least SEK 50 for cross-border credit transfers in the destination currency under shared cost arrangements, with euro payments to SEPA countries the exception, which makes low-value transfers disproportionately expensive.
- Speed: more than 70% of Swift payments to Sweden are credited within one hour, close to the 75% target, with manual controls, Swedish krona liquidity at foreign respondent banks and RIX RTGS operating hours cited as limiting factors.
- Messaging: ISO 20022 went live in RIX RTGS in May 2025, with full alignment to the CPMI harmonised requirements expected after a 2027 update.
- Instant cross-border: RIX INST will support NOLO Inst from March 2027, and the Riksbank encourages use of the TIPS cross-currency service, although no RIX INST participants are yet reachable through it.
The plan also records the banks’ position plainly: they find NOLO Inst and the TIPS cross-currency service of interest but have no concrete implementation plans, and some point to a collective-action problem when reachability is low. The cross-currency service itself is covered in our article on Riksbank cross-currency instant payments over TIPS.
Frequently Asked Questions
Does the 2026 report change any reporting template, threshold or deadline for my firm?
No. The FSB states that its activities do not create legal rights or obligations, and the report sets no firm-level requirement. Obligations that follow from the Roadmap reach firms through national law, supervisors, central-bank system rules or scheme rulebooks, as the Bank of England’s CHAPS purpose code and LEI mandate shows.
Our firm answered the receiver-side cost survey. Will our figures be published?
The survey is described as a voluntary and anonymous firm-level survey of PSPs from FSB and Regional Consultative Group members and World Bank members. The report publishes aggregates only, and it states that, because of the limited number of responses, fees applied by correspondent institutions cannot be represented; the analysis covers fees applied by the beneficiary financial institution.
Will the 2027 FSB peer review assess individual PSPs?
The thematic peer review by the Standing Committee on Standards Implementation covers implementation by FSB member jurisdictions of the December 2024 recommendations on data frameworks and on regulating and supervising bank and non-bank PSPs. Its subjects are national frameworks. The report describes thematic peer reviews as encouraging consistent implementation, evaluating where possible whether standards and policies had their intended results, and identifying gaps for follow-up by FSB members.
Does the postponed Swift address phase-out also mean unstructured addresses are acceptable for Recommendation 16?
The two are separate questions. The Swift postponement concerns what the network will technically accept. Recommendation 16 sets which originator and beneficiary information must accompany a payment, and its implementation in each jurisdiction depends on national law and the FATF Guidance expected in 2027. Technical acceptance of a format says nothing about whether the content meets an AML/CFT requirement.
Is the revised Recommendation 16 already applied anywhere?
FATF standards bind firms only once a jurisdiction implements them. Section 8-6 of Australia’s AML/CTF Rules 2025, which deals with payment transparency during the transition to the revised FATF Recommendations, lets a reporting entity meet its payer-information obligations using the payer’s full name, a unique identifier for a body corporate (if any), date of birth for an individual, and a full business or residential address that is not a post box; an entity using that option must also handle specified payee location and identifier information. In the EU, the information accompanying transfers of funds is set by Regulation (EU) 2023/1113, whose recitals refer to the FATF Recommendations as revised in June 2019; the FSB report does not address EU implementation of the 2025 revision.
If the KPIs miss the end-2027 targets, will the G20 set new ones?
The report is silent on that. It speaks of action “in 2027 and beyond” and commits the FSB to continued work with international organisations and industry, but it neither resets the targets nor proposes new dates. The 2026 survey annex adds that where further jurisdictional work is planned, completion may extend beyond 2028.
Related Articles
- G20 Cross-Border Payments Targets: The 2027 Reporting Countdown: the end-2027 target set and what payment institutions were preparing before the 2026 report.
- Harmonised ISO 20022 Data Requirements: The 2027 Alignment Window: the CPMI’s February 2026 update and its end-2027 alignment window for usage guidelines.
- FATF Travel Rule Consultation: What EU Payment Firms and CASPs Should Consider: the draft Recommendation 16 guidance put out for comment in 2026.
- Riksbank Cross-Currency Instant Payments: What the SEK-EUR Go-Live Means for PSPs: the June 2026 TIPS cross-currency go-live for RIX INST participants.
- OCT Inst Scheme Explained: Sending Instant Euro Beyond SEPA: the EPC rulebook for the euro leg of international instant credit transfers.
- EPC Delays SEPA Structured Address Migration: Revised Timeline: the SEPA scheme timetable for structured addresses, which runs separately from Swift’s.
Key Takeaways
- Before an Annex 3 figure goes into a board or supervisory paper, check its footnote for rebasing, sample change and measurement basis.
- Owners of ISO 20022 conversion layers: test internal formats for truncation of structured address, LEI and remittance fields, since harmonised-requirements alignment depends on data surviving end to end.
- Recommendation 16 programme: establish a field-level baseline and revisit the gap analysis after the FATF adopts its Guidance, currently targeted for 2027. The FATF’s global implementation horizon is end-2030; firm-level obligations and effective dates must be checked against applicable national rules.
- Card issuers and acquirers: assess which card-funded transfers and cross-border cash withdrawals fall within revised Recommendation 16, distinguishing qualifying purchases of goods or services that remain exempt from its full requirements.
- UK CHAPS direct participants: extend purpose-code controls to all CHAPS initiation channels within their control for November 2027, and prepare LEI population for in-scope pacs.004 return and pacs.009 COV payments between financial institutions.
- Non-bank PSPs: track the home authority’s action plan for licensing or supervisory-expectation changes; the international follow-ups under Action 4 are closed.
- Group payment operations: review data-residency and fraud-data-sharing assumptions per jurisdiction against the localisation trend in Annex 2.
Sources and References
- FSB (16 November 2026), G20 Roadmap for Enhancing Cross-border Payments: Consolidated progress report for 2026 (PDF)
- FSB press release (16 November 2026), Further work by jurisdictional authorities and private sector necessary to enhance cross-border payments
- FSB (13 October 2021), Targets for Addressing the Four Challenges of Cross-Border Payments: Final report (PDF)
- FSB (9 October 2025), G20 Roadmap for Cross-border Payments: Consolidated progress report for 2025 (PDF)
- FSB (12 December 2024), Recommendations for Regulating and Supervising Bank and Non-bank Payment Service Providers Offering Cross-border Payment Services: Final report
- FSB (12 December 2024), Recommendations to Promote Alignment and Interoperability Across Data Frameworks Related to Cross-border Payments: Final report
- CPMI (26 February 2026), Harmonised ISO 20022 data requirements for enhancing cross-border payments: updated report, and data models technical annex
- Sveriges Riksbank (October 2026), Response to FSB: Action plan for G20 targets
- Bank of England, Expanding mandatory ISO 20022 enhanced data in CHAPS from 2027 (policy statement, including the 2026 update)
- FATF (June 2025), FATF updates Standards on Recommendation 16 on Payment Transparency
- Australia, Anti-Money Laundering and Counter-Terrorism Financing Rules 2025 (Compilation No. 1, 31 March 2026), section 8-6
- Regulation (EU) 2023/1113 on information accompanying transfers of funds and certain crypto-assets (recast)
Preparing for the 2027 payments data agenda
The 2026 report leaves the end-2027 targets in place and puts the weight of the remaining work on jurisdictions, regions and the private sector. For PSPs, the concrete items are already visible: ISO 20022 content quality and structured data, LEI and purpose code population where a system operator mandates it, payee alignment checks under the revised Recommendation 16, and the cost, timing, status and terms-of-service disclosures that the transparency target defines. The next fixed points are the FSB summary of jurisdictional action plans in early 2027 and the FATF Guidance on Recommendation 16 the same year. The artifact to have ready before either lands is a field-level gap list comparing current outbound and inbound message content with the Recommendation 16 data elements and the CPMI harmonised data model.
Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.
