AI Hallucination ResearchAudiencesSectorsInternational / MultilateralPayment InstitutionsLegal › Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit
Payment Institutions × Legal — International / Multilateral · updated 2026-06-04 · methodology v2.3
Share / Print Twitter LinkedIn Email

AI on CPMI API Harmonisation for Cross-Border Payments for Legal teams at Payment Institutions firms 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. SARB pre-validation partnership misidentified with fabricated citation
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q007

    When Legal teams at Payment Institutions firms ask AI tools which central bank is actively partnering with CPMI on the payment pre-validation API recommendation, AI assistants tested produced a confident but wrong answer — identifying no named partner and proposing the Bank of England as the closest analogue, while a fabricated Bank of England source was offered as corroboration. CPMI Brief No. 9 (November 2025) explicitly names the South African Reserve Bank as the collaboration partner.

    Any Legal horizon-scanning note or jurisdictional intelligence memo built on this AI output will mischaracterise the active implementation geography for pre-validation, causing Legal to mis-scope which cross-border corridors face near-term compliance obligations and which counterparty arrangements require accelerated legal review.

    see details →
  2. Per-recommendation stakeholder breakdown invented without textual support
    RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008

    When asked to map CPMI's ten API harmonisation recommendations to specific actor classes — standards bodies, payment system operators, central banks, commercial banks — AI tools produced a detailed, category-level breakdown that goes beyond what any accessible public CPMI document supports. The AI committed to specific actor assignments per recommendation cluster, then retreated when challenged, acknowledging the breakdown was not derivable from available sources.

    Legal teams that use this output to draft API integration agreements, structure correspondent banking representations, or advise on product scope will embed unsupported obligation-assignment assumptions into transaction documents and internal compliance matrices — creating documentation risk that persists in deal files and is difficult to remediate after execution.

    see details →