OpenChainGraph Suite · RCA-03 · ISO 20022 Address Verifier
v1.0.0

ISO 20022 Structured-Address Migration Verifier

Validate pacs.008 structured postal address fields against the SWIFT CBPR+ November 2026 structured-address mandate. Enter records manually or paste CSV. Checks country code (ISO 3166-1), mandatory fields, character limits, MT103 legacy truncation risk (addresses ≥50 chars at risk in legacy interop), and country-specific postal-code formats. Returns a November 2026 readiness score per batch with per-record PASS / WARN / FAIL and field-level error enumeration. GPU-accelerated in browsers that support OffscreenCanvas — graceful CPU fallback.

AP2 Export Chains: ART-11 · PTG-01 Deadline: Nov 2026 SWIFT CBPR+ Mandate GPU Accelerated Zero PII
🔒 All validation runs locally in your browser. No data is transmitted. Use synthetic or anonymised address records only — do not enter real customer or counterparty data.
⏰ November 2026 — SWIFT CBPR+ structured-address mandate takes effect. All pacs.008 cross-border credit transfers must carry structured postal address data (StrtNm/BldgNb/PstCd/TwnNm/Ctry) rather than unstructured AddressLine free text. Financial institutions that have not migrated risk message rejection by correspondent banks.
⚠ Educational tool. Validation rules implement widely-published CBPR+ guidance and ISO 20022 pacs.008 schema constraints as of 2026. Postal code format rules are indicative — full national postal authority specs vary. MT103 truncation risk is flagged when combined address length ≥50 characters (indicative threshold for MT103 field 50a/59 interop). Verify final implementation against SWIFT's published 2026 CBPR+ migration guide and your correspondent bank's specific requirements.
Input method
Name / Nm
Street / StrtNm
Bldg / BldgNb
Postcode / PstCd
City / TwnNm
Country / Ctry
Validation settings
GPU · WebGPU/OffscreenCanvas
Detecting GPU support…
November 2026 readiness score
Per-record validation results
#StatusNameStreetBldg PostcodeCityCtry MT103 riskCombined lenErrors / Warnings
Related tools: ISO 20022 Builder + Pilot Brief Generator | AINumbers.co · Tool 57: ISO 20022 ↔ DLT Flow Mapper · Tool 81: ISO 20022 Migration Navigator · Tool 98: ISO 20022 Message Validator + Field Explorer · ISO 20022 Migration Readiness Scorer · ISO 20022 Remittance Data Enrichment Validator · T178 · ISO 20022 Quick Validator · T254 · ISO 20022 Status & Rejection Decoder · EU IPR ISO 20022 Structured Address Field Validator · ISO 20022 Schema-Subset Tables & Validators · ISO 20022 ↔ On-Chain Correspondence Receipt
Related on the graph: SWIFT / ISO 20022 PQC Readiness Checker · ISO 20022-to-EVM Calldata Mapper · Using OpenChainGraph with ISO 20022 | Integration Guide

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `verify_address_migration_batch`. Task: Validate ISO 20022 pacs.008 structured postal address fields against SWIFT CBPR+ November 2026 mandate.
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: this node computes in your browser, so the MCP endpoint returns no execution_hash. Run the tool in the page, export the Policy Mandate artifact it produces, and call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with that artifact.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/rca-03-iso20022-address-migration-verifier.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA