Technology & Data teams at Payment Institutions building cross-border payment infrastructure under the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to design address parsers, build message-schema components for Fedwire-connected rails, and generate API documentation for connected clients. The same tools draft technical specifications for white-label cross-border payment products.
Two frontier AI models tested by the RLB Specialist Panel on the workflows payment-institution technology and data teams use to support advice on the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) produced one discrete hallucination bound to regulator-issued source text. The Panel records a single recurring failure class: Schema Over-Specification across the set. Questions were prepared by the Specialist Panel based on real practical AI usage in the workflows payment-institution technology and data teams use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.
For Technology & Data teams at Payment Institutions, each hallucination has a direct operational consequence in the address parser, message-schema component, or API specification. The Panel's testing surfaces Fedwire hybrid postal address schema over-specification. Where these errors flow into a deliverable, the exposure is non-compliant Fedwire messages flowing through sponsor-bank governance, multi-team remediation across release cycles, and a contractual breach finding with the sponsor bank.
The pattern is uniform across the set: the AI returns a confident, sourced-looking answer that conflicts in a load-bearing specific with the regulator's verbatim text, and the error survives a first-pass review precisely because the surface form is plausible. The Panel records each hallucination with the regulator's primary substrate held as the anchor, so the corrective text is available alongside the failure.
The Specialist Panel records the citation IDs as follows: RLB-H-INT-BIS-CPMI-ISO-20022-HARMONISATION-UPDATED-2026-Q010-Opus47 (Claude Opus 4.7 (web search on), Schema Over-Specification). Each citation links to the verbatim regulator-issued source text, the tested AI question, and the recorded AI response, so the Panel's assessment is traceable end to end. For technology & data teams at payment institutions, the citation IDs operate as a reference index: when an AI answer in the working draft matches a known Panel finding, the cited regulator text is already available as the corrective anchor.
The full per-finding analysis cards, including the audience-specific impact statement, sit on the cell's detail surface for sign-off use.
This is the consolidated view of findings. Click the Citation IDs or 'see details →' on any item for the full details for each finding.
A Technology & Data team that builds its ISO 20022 address parser from this AI response will configure optional structured fields (Street Name, Building Number, Post Code) where the FRB Services FAQ specifies optional free-format lines of 70 characters, an inversion that produces non-compliant Fedwire messages. The error propagates through message schema design into counterparty onboarding templates, API documentation for connected clients, and any white-label product built on top of the firm's cross-border rails, requiring multi-team remediation across release cycles once discovered at clearing.
For a Payment Institution accessing Fedwire through a sponsor bank, the non-compliance is a contractual breach finding as well as a technical defect, with remediation timelines controlled by the sponsor's governance rather than the firm's own sprint cadence.
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.