--- type: "AILabsWhitepaper" title: "Hallucination findings: Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit" slug: "CPMI-API-HARMONISATION-CROSS-BORDER-2024-general-v1" audience: "general" regulation_slug: "CPMI-API-HARMONISATION-CROSS-BORDER-2024" regulation_id: "320322" body_id: "BIS-CPMI-INT-001" jurisdiction_code: "INT" j_level: "J1" regulator_short_code: "BIS-CPMI" methodology_version: "2.0" substrate_version: 1 generated_at: "2026-06-07T07:58:31.691947+00:00" published_at: "2026-06-07T07:58:31.691947+00:00" license: "CC-BY-4.0" resource: "https://reglegbrief.com/regulators/j1/int/bis-cpmi/CPMI-API-HARMONISATION-CROSS-BORDER-2024/ai-labs/" timestamp: "2026-06-16T00:00:00+00:00" --- # Hallucination findings: Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit - **Regulation.** [`CPMI-API-HARMONISATION-CROSS-BORDER-2024`](/okf/regulations/CPMI-API-HARMONISATION-CROSS-BORDER-2024.md) — Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit - **Regulator.** [`BIS-CPMI-INT-001`](/okf/bodies/BIS-CPMI-INT-001.md) - **Audience.** general - **Methodology.** 2.0 - **Generated.** 2026-06-07T07:58:31.691947+00:00 ## Full whitepaper # Hallucination findings, Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit _Jurisdiction: INT ; Body: BIS-CPMI-INT-001 ; Regulation: CPMI-API-HARMONISATION-CROSS-BORDER-2024_ This page lists each instance in which a tested AI assistant produced an answer that the regulator's own published text contradicts. Each row links the assistant's claim, the contradicting regulator text, and the status of any source the assistant cited. **Citation status legend**: - _Fabricated_, the URL the assistant cited does not exist as a public document. - _Inaccessible_, the URL exists but its content is not available for public verification. - _Accessible-but-contradicts-claim_, the URL is reachable and its content does not support the assistant's claim. **Question text below is paraphrased to protect IP** in the underlying question bank. --- | # | Subject | Question (paraphrased) | Assistant claim | Regulator says | Cited source(s) | |---|---|---|---|---|---| | 1 | opus-47-websearch | A payments operations manager asks what the CPMI October 2024 API harmonisation report's self-assessment toolkit contains, what areas it covers, how it is structured, what assessment dimensions or criteria it uses, and how a bank team should use it to evaluate API harmonisation readiness. | the toolkit is organised as a self-assessment workbook keyed recommendation-by-recommendation, intended for use both by operators of payment systems and by participants/users (banks). I am NOT in a position to verify from memory the exact number of assessment questions | Landing page d224: 'accompanied by a toolkit for stakeholder self-assessment' and 'practical implementation actions for each recommendation.' PDF not extractable. No third-party source describes toolkit contents. | Contradictory; Contradictory; Contradictory | | 2 | opus-47-websearch | A compliance analyst asks which of the 10 CPMI API harmonisation recommendations specifically target commercial banks or correspondent banking institutions, which target payment system operators, which target central banks or regulators, and which target standards bodies, seeking a recommendation-by-recommendation stakeholder breakdown. | (i) FACILITATIVE / GLOBAL HARMONISATION PROCESSES, primarily targeted at API standards-setting bodies (ISO, BIAN, Swift, regional/sectoral bodies), CPMI itself, and public authorities coordinating global governance; secondarily at payment-system operators that adopt those standards. Not specificall | Official text: '10 recommendations directed at a broad array of stakeholders.' Individual stakeholder targeting per recommendation is in the inaccessible PDF. | Contradictory; Contradictory; Contradictory | | 3 | opus-47-websearch | What specific changes did the February 2026 update to the CPMI harmonised ISO 20022 data requirements make relative to the original October 2023 version, and how does the separate technical annex relate to the main document? | (1) to incorporate standardisation and regulatory developments since 2023 (2) to provide clarifications in areas where market participants had sought further guidance on how to apply the d218 requirements (3) to set out the updated and expanded data model in a separate technical annex | The updated version of the report takes into account standardisation and regulatory developments since 2023, provides clarification where market participants had sought further guidance, and sets out the updated and expanded data model in a separate technical annex | Contradictory; Contradictory; Contradictory; Contradictory; Contradictory; Fabricated | | 4 | sonnet-46-websearch | A payments counsel prepared a client memo on the CPMI's October 2024 API harmonisation report (d224). The memo correctly identified the four recommendation categories but fabricated specific sub-requirements for each category, presented as approximate guidance for what each individual recommendation requires, when that content is inaccessible in any public source. | Category 1 recommendations (approximately 2–3 recommendations) broadly require: (i) establishing or designating a governance body to maintain harmonised API standards on an ongoing basis; (ii) creating a process to evaluate and endorse industry API proposals | Individual recommendation text not accessible in any public source fetched. | Contradictory; Contradictory; Contradictory; Contradictory | | 5 | sonnet-46-websearch | A payments operations manager asked what the CPMI d224 self-assessment toolkit contains, its areas, structure, and assessment criteria. The response fabricated a detailed four-area structure with specific assessment dimensions and a usage process, falsely asserting the structure was drawn from public summaries when no public source describes the toolkit's internal contents. | Area 1, Harmonisation Governance and Processes... Area 2, API Design Principles and Data Standards... Area 3, Developer Experience... Area 4, Pre-Validation APIs... The description above reflects what is confirmed from public summaries of d224's structure. | Landing page d224: 'accompanied by a toolkit for stakeholder self-assessment' and 'practical implementation actions for each recommendation.' PDF not extractable. No third-party source describes toolkit contents. | Contradictory; Contradictory; Contradictory | | 6 | sonnet-46-websearch | Which central bank is explicitly named as a collaborating partner with CPMI on the payment pre-validation API recommendation from the October 2024 API harmonisation report, and what does that collaboration involve? | available sources do not identify SARB as a named pilot partner for any specific d224 recommendation, including the pre-validation API recommendation | CPMI Brief No. 9 (Nov 2025): 'The CPMI, in collaboration with the South African Reserve Bank (SARB), has been advancing the API recommendation on payment pre-validation by conducting interviews with m | Contradictory; Inaccessible; Contradictory; Contradictory | | 7 | sonnet-46-websearch | A compliance analyst was asked for a recommendation-by-recommendation stakeholder breakdown of the CPMI d224 API harmonisation report. The response fabricated per-category stakeholder assignments, naming specific institution types (e.g., 'ISO, SWIFT, regional open banking standards bodies' for Category 1) by inferring from APEX composition and category names, when the actual per-recommendation stakeholder designations are only in the inaccessible PDF. | CATEGORY 1, Primary stakeholders: Standards bodies (ISO, SWIFT, regional open banking standards bodies); industry associations; regulators and central banks... CATEGORY 4, Primary stakeholders: Commercial banks and PSPs (who must implement or consume pre-validation APIs); payment system operators. | Official text: '10 recommendations directed at a broad array of stakeholders.' Individual stakeholder targeting per recommendation is in the inaccessible PDF. | Contradictory; Contradictory; Contradictory | | 8 | sonnet-46-websearch | What specific changes did the February 2026 updated CPMI harmonised ISO 20022 data requirements make compared to the October 2023 original, including regulatory developments incorporated, clarifications provided, and how the separate technical annex relates to the main document? | From November 2026 onwards, only structured and hybrid addresses will be permitted in ISO 20022 cross-border payment messages, the fully unstructured address format is being phased out. This is being driven by the SWIFT/CBPR+ community and is reflected in d230's updated requirements. | The updated version of the report takes into account standardisation and regulatory developments since 2023, provides clarification where market participants had sought further guidance, and sets out the updated and expanded data model in a separate technical annex. | Contradictory; Contradictory; Contradictory; Contradictory; Fabricated; Contradictory | --- _Published: 2026-06-07T07:58:31.558479+00:00_ ## Related concepts - Regulation: [CPMI-API-HARMONISATION-CROSS-BORDER-2024](/okf/regulations/CPMI-API-HARMONISATION-CROSS-BORDER-2024.md) - Regulator: [BIS-CPMI-INT-001](/okf/bodies/BIS-CPMI-INT-001.md) - Methodology: [v2.3](/okf/methodology.md)