AI Hallucination ResearchFindings by audienceSectorsInternational / MultilateralCorporate BankingRisk › Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit
Corporate Banking × Risk — 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 Risk teams at Corporate Banking firms in international jurisdictions

Corporate Banking Risk teams: documentation and reporting gaps possible from AI reading of CPMI Cross-Border API Harmonisation 2024

Risk leads at corporate banks running cross-border payments rails on the CPMI API harmonisation programme are increasingly using AI to update payment-risk dashboards with CPMI connectivity figures, draft enterprise-risk-assessment annexes on the SARB pre-validation workstream, prepare board-risk-appetite papers on Africa-corridor exposure, generate operational-risk metrics using fast payment system operator splits, and verify dated CPMI commitments against primary publications. 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.

Numeric Drift and False-Negative Availability Claim 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 Risk teams at Corporate Banking firms briefing, the AI subjects returned a global fast payment system count of 57 sourced to the 2025 monitoring survey sample, when the authoritative CPMI figure is 70+; stated that the central-bank versus private operator split of global fast payment systems is not enumerated in public CPMI sources, when the November 2023 CPMI speech gives exact percentages.

A board-risk paper that records a CPMI cutover date the regulator never set is a factual error in a board-approved risk-appetite document. A risk dashboard that uses 57 rather than 70+ as the FPS connectivity baseline mis-sizes corridor exposure. An enterprise risk register entry recording 'no SARB pre-validation workstream identified' carries a verifiable error into a supervisory deliverable. The next supervisory testing on AI use in risk reporting will find these gaps.

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

Risk teams in corporate-bank cross-border payments scope concentration risk, settlement risk and FMI-connection risk against a narrow set of CPMI-published numbers: the count of operational fast payment systems, the live cross-border linkages, and the central-bank-versus-private operator mix. Two AI failures on this regulation hit that same number set in opposite directions: Opus 4.7 returns a 57-FPS 2025-monitoring-survey number with no operator-type breakdown, and Sonnet 4.6 returns the 70-plus headline correctly but denies that the operator-mix percentages exist.

The Tara Rice November 2023 speech (sp231115) is the primary source for the full set, with 70-plus operational, 14 cross-border-enabled, 24 in the five-year planning pipeline, 40% central-bank-operated and 35% privately operated. A second-line risk memo built off either AI answer enters the risk committee with the wrong universe size, no operator-mix differentiator and a forward-pipeline signal stripped out.

What the AI got wrong, and why it matters here

Both failures share the same operational pattern: a high-confidence answer that strips a signal load-bearing for risk differentiation. Neither is caught by a desk reviewer who is not already holding the sp231115 numbers in mind.

Finding 1: FPS universe compressed and operator mix erased

Opus 4.7 cited the 2025 monitoring survey at 57 (56 in one graph) operational fast payment systems and gave no operator-type breakdown. The Tara Rice November 2023 speech (sp231115) gives 70-plus operational, 14 cross-border-enabled, 24 in the five-year planning pipeline, 40% central-bank-operated and 35% privately operated. Risk memos calibrated against the AI answer enter committee with an undersized universe, no operator-mix differentiation, and the planning-pipeline forward indicator dropped from the input set.

Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q010-Opus47.

Finding 2: Operator-mix denied

Sonnet 4.6 cited the 70-plus headline correctly but denied that a precise central-bank-versus-private operator percentage is enumerated in the public Brief 10 summary. The Tara Rice November 2023 speech (sp231115) names 40% central-bank-operated and 35% privately operated. Removing the mix from the risk-memo input set collapses the central-bank-versus-private differentiation, which is the load-bearing signal for FMI-concentration analysis on cross-border rails.

Citation: RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q010-Sonnet46.

When this hits the risk calendar

Risk pulls CPMI material on three recurring deliverables: the FPS connectivity exposure memo, the cross-border payments FMI-concentration view, and the annual risk-appetite calibration for cross-border-payments business lines.

Standing item Where the AI risk surfaces Failure mode
FPS connectivity exposure memo Global FPS count, cross-border linkage count Finding 1
Cross-border-payments FMI-concentration view Operator-mix differentiator Findings 1 and 2
Annual risk-appetite calibration Planning-pipeline forward indicator and operator mix Findings 1 and 2

Aggregate impact on the team

The same two failures collapse the operator-mix differentiation and the planning-pipeline forward signal, removing two of the three inputs risk-appetite calibration relies on.

Risk ImpactCountAffected findings
0

What this team should do

Tag the FPS count and the operator mix as known-failure outputs. Any AI draft naming those numbers must be sent through a primary-source check against sp231115 and the latest CPMI cross-border monitoring brief before it lands in a second-line risk memo or a risk-appetite paper.

Detection patterns to add to AI-review

  • Any FPS count must be tied back to Tara Rice sp231115 or to the most recent CPMI cross-border monitoring brief by number.
  • Any denial that an operator-mix percentage exists must be cross-checked against sp231115 directly.

How RLB can help

RLB tracks the failure pattern on these specific numerical anchors across d224, the CPMI cross-border-payments brief series and the Tara Rice November 2023 speech, refreshed against live AI subjects on rotation. Risk teams in corporate banking can wire the catalogue into the AI-draft review step so the operator-mix line and the universe size never reach risk committee without a primary-source check.

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.