AI Hallucination ResearchFindings by audienceSectorsInternational / MultilateralStatutory Boards & AgenciesCompliance › Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit
Statutory Boards & Agencies × Compliance — International / Multilateral · Last updated 11 Jun 2026 · methodology v2.3 · Hallucination Register
Share / Print X LinkedIn Email

AI Hallucination on Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit for Compliance teams at Statutory Boards & Agencies firms in international jurisdictions

Compliance teams at statutory boards and public agencies engaging with the CPMI API harmonisation programme for cross-border payments oversight are increasingly using AI to draft inter-agency briefing notes, prepare board-paper annexes on the SARB pre-validation workstream, generate regulatory horizon-scan summaries on the 10 CPMI recommendations for senior officials, update programme-level CPMI mapping documents, and verify ISO 20022 commitments against regulator-issued source text. The RLB Specialist Panel tested how that AI usage performs against the regulator's own primary text on CPMI's October 2024 d224 report and the related CPMI Brief and speech series.

The audit surfaced four substantive failure modes that the AI subjects delivered with regulator-fluent confidence.

Confident Denial and Stakeholder Taxonomy Fabrication on CPMI API Harmonisation for Cross-Border Payments. Two frontier AI models tested by the RLB Specialist Panel returned confident, citable answers across the panel's CPMI substrate-bound question set on the October 2024 d224 report and the related CPMI Brief and speech series. The panel binds each AI finding to verbatim regulator-issued source text held as primary substrate.

Across the 2 findings in this Compliance teams at Statutory Boards & Agencies briefing, the AI subjects denied that any pilot partner has been named for the CPMI pre-validation API recommendation; built a recommendation-by-recommendation stakeholder breakdown from category names rather than the regulator's actual recommendation text.

An inter-agency briefing note that records 'no jurisdictional partner identified' on the CPMI pre-validation workstream embeds a verifiable factual error into official correspondence. A senior-official horizon scan that quotes a fabricated November 2026 structured-ISO-20022 cutover commits the agency's position to a regulator commitment the regulator never made.

The findings are published with immutable RLB Citation IDs: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q007-Sonnet46, RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47. The full audit is published at the CPMI API Harmonisation for Cross-Border Payments hub on RegLegBrief.com.

This is the consolidated view of findings. Click the Citation IDs or 'see details →' on any item for the full details for each finding.

  1. SARB pre-validation partnership denied
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q007

    Compliance teams inside statutory boards and agencies (a national payments council, a designated FMI oversight unit, a financial-services authority's payments-policy desk) read CPMI material to track which jurisdictions are moving on regulator-led pre-validation rails. Sonnet 4.6 denies any CPMI statement names SARB. CPMI Brief No. 9 (Nov 2025) names SARB outright. A compliance officer at a statutory body who lifts the AI denial into the peer-jurisdiction tracker, the inter-agency policy briefing or the parliamentary question response is denying a documented regulator workstream that the body's own counterpart in SA can confirm in print.

    see details →
  2. Invented per-recommendation stakeholder taxonomy
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008

    Statutory body compliance teams scope which of d224's 10 recommendations affect the body's own jurisdiction (licensing regime, oversight perimeter, payments-act amendment scope) before writing a policy memo or a minister's brief. Opus 4.7 returns a clean stakeholder taxonomy reconstructed from category labels rather than the recommendation text. A scoping memo written off that taxonomy mis-scopes which CPMI recommendations require domestic action and which fall to standards bodies or payment-system operators.

    see details →

Every finding on this page compares an AI subject's account of the rule against the regulator's verbatim text from the regulator's own portal. Both are linked. Each delta, its root causes, and impact analysis are documented and published with immutable Citation IDs.