AI Hallucination ResearchAudiencesPractitionersInternational / MultilateralLawyers › Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit
Practitioners — Lawyers · updated 2026-06-04 · methodology v2.3
Share / Print Twitter LinkedIn Email

AI on Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit for Lawyers in international jurisdictions

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. Fabricated self-assessment toolkit structure
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q005

    Any lawyer briefing a client on readiness under the CPMI API framework will encounter the self-assessment toolkit as the first practical reference — AI assistants produced a fully invented four-area structure with assessment dimensions and usage methodology that bears no verified relationship to the actual document. An opinion memo or readiness assessment built on this fabricated framework is wrong in every material particular. The client cannot detect the error from the public landing page; verification requires accessing the primary BIS PDF directly, which the AI did not do and did not disclose it could not do.

    see details →
  2. SARB pre-validation partnership misattributed
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q007

    AI tools misidentified the Bank of England — not the South African Reserve Bank — as CPMI's named implementation partner on the payment pre-validation API recommendation, and fabricated a supporting URL. A lawyer advising a South African financial institution on its regulator's CPMI engagement, or advising any client on bilateral implementation coordination, starts from the wrong factual premise. CPMI Brief No. 9 (November 2025) is the authoritative source and explicitly names SARB; the misattribution is not detectable without reviewing that brief directly.

    see details →
  3. Invented stakeholder obligation category map
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008

    AI invented a category-level stakeholder map assigning which of the 10 recommendations target correspondent banks, payment system operators, central banks, and standards bodies — content the official text places in an inaccessible PDF. A compliance opinion structured around this fabricated map misstates the scope of obligations for every client category it addresses. The AI's partial retraction under challenge does not protect against the risk that the initial output was accepted, forwarded, and acted upon before the challenge was made.

    see details →
  4. d230 publication date and annex content fabricated
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q009

    AI reported d230 — the February 2026 updated CPMI ISO 20022 data requirements — as published in April 2026, a two-month error sourced from a third-party aggregator article rather than the primary BIS page. AI simultaneously fabricated specific data entity breakdowns for the technical annex. A lawyer or compliance team relying on AI-sourced publication history for ISO 20022 compliance timelines will have the wrong effective date and wrong annex scope, both of which bear directly on advice about implementation deadlines and data-model conformity obligations.

    see details →
  5. Fast payment system statistics confused
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q010

    AI conflated a 57-system survey sample with the global universe of 70+ domestic fast payment systems, and omitted the 40%/35% central bank/private operator breakdown that is available in primary CPMI speeches. A market briefing or client memo built on these figures — particularly for clients sizing cross-border linkage opportunities or regulatory engagement strategies — delivers materially wrong statistics about the scale and governance structure of the global FPS landscape, with the lawyer's name on a deliverable that will not survive basic fact-checking.

    see details →