---
type: "AIHallucinationFinding"
title: "A compliance analyst asks which of the 10 CPMI API harmonisation recommendations specifically…"
citation_id: "RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47"
finding_uid: "INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-008--opus-47-websearch"
question_uid: "INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-008"
regulation_id: "INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024"
regulation_slug: "CPMI-API-HARMONISATION-CROSS-BORDER-2024"
regulation_title: "Promoting the Harmonisation of Application Programming Interfaces to Enhance Cross-Border Payments: Recommendations and Toolkit"
regulator_short_code: "BIS-CPMI"
regulatory_body_id: "BIS-CPMI-INT-001"
jurisdiction_code: "INT"
j_level: "J1"
ai_subject: "claude-opus-4-7"
ai_subject_display: "Claude Opus 4.7 (web search on)"
ai_subject_version: "opus-47-websearch"
response_failure_mode: "inference_drift"
substrate_document_name: "cpmi-d224-api-harmonisation-2024.pdf"
substrate_document_path: "https://reglegbrief.com/substrate/INT/BIS-CPMI/CPMI-API-HARMONISATION-CROSS-BORDER-2024/_raw_manual_substrate/cpmi-d224-api-harmonisation-2024.pdf"
substrate_section_anchor: "Section 2.2.1 Recommendation 1 (p.15) and Section 2.2.2 Recommendation 2 (p.16)"
citation_issue_types: ["Contradictory"]
audiences: ["ai_labs"]
published_at: "2026-06-04T03:07:05.744638+00:00"
substrate_version: 1
methodology_version: "2.3"
license: "CC-BY-4.0"
resource: "https://reglegbrief.com/regulators/j1/int/bis-cpmi/CPMI-API-HARMONISATION-CROSS-BORDER-2024/ai-labs/finding/INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-008--opus-47-websearch/"
tags: ["ai-hallucination", "inference_drift", "bis-cpmi", "cpmi-api-harmonisation-cross-border-2024", "int"]
timestamp: "2026-06-16T00:00:00+00:00"
---

# AI Hallucination Finding: A compliance analyst asks which of the 10 CPMI API harmonisation recommendations specifically…

- **Citation ID.** `RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47`
- **Finding UID.** `INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-008--opus-47-websearch`
- **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) — Bank for International Settlements — Committee on Payments and Market Infrastructures (CPMI)
- **AI subject.** Claude Opus 4.7 (web search on)
- **Failure mode.** [`inference_drift`](/okf/taxonomy/failure-modes.md)
- **Published.** 2026-06-04T03:07:05.744638+00:00

## Question put to the AI subject

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.

## AI subject's verbatim answer

(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 specifically at correspondent banks.

## Verbatim regulator text contradicting the answer

> Recommendation 1: Open API standards. All stakeholders in API standardisation, but especially jurisdictional authorities and standards organisations, should actively support the development of cross-border payment API standards that are voluntary, open and consensus-based. [...] Recommendation 2: Existing harmonisation initiatives. Jurisdictional authorities (eg central banks, relevant government agencies, and regulatory bodies) and standards organisations should leverage the experience of existing API harmonisation initiatives [...]

_Source:_ [cpmi-d224-api-harmonisation-2024.pdf](https://reglegbrief.com/substrate/INT/BIS-CPMI/CPMI-API-HARMONISATION-CROSS-BORDER-2024/_raw_manual_substrate/cpmi-d224-api-harmonisation-2024.pdf)
_Section anchor:_ Section 2.2.1 Recommendation 1 (p.15) and Section 2.2.2 Recommendation 2 (p.16)

## Failure mode

**`inference_drift`** — Inference drift — the AI inferred a conclusion the regulator's text does not warrant, often by combining unrelated provisions.

## Citation-issue types

- **Contradictory** — <https://www.bis.org/cpmi/publ/d224.htm>
- **Contradictory** — <https://www.bis.org/cpmi/publ/d224.pdf>
- **Contradictory** — <https://www.bis.org/press/p241015.htm>

## 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)
- Failure-mode taxonomy: [inference_drift](/okf/taxonomy/failure-modes.md)
- Methodology: [v2.3](/okf/methodology.md)
- Editorial standards: [right of reply](/okf/editorial-standards.md)

## Reproduction

Citation ID: `RLB-H-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q008-Opus47`

Resource URL (HTML view of this finding):

<https://reglegbrief.com/regulators/j1/int/bis-cpmi/CPMI-API-HARMONISATION-CROSS-BORDER-2024/ai-labs/finding/INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-008--opus-47-websearch/>

This finding is reproducible against the substrate document linked above, using the same AI subject, the same methodology version, and the verbatim question text.