CBPR+ SR2026 Structured Address Pre-Flight

Classify each party and agent postal address in a CBPR+ payment message as structured, hybrid, or unstructured, and see exactly which ones Swift will reject at network level once the structured-address requirement takes effect. Swift applied a controlled extension of Standards Release 2026 on 27 August 2026, deferring that requirement from its former 14 November 2026 date, and has published no replacement date; SR2025 rules apply meanwhile. Enter fields directly or paste a synthetic <PstlAdr> fragment.

⚠ This tool encodes publicly stated Swift CBPR+ SR2026 guidance (message-type exemption list, hybrid definition, rejection mechanics) as of 2026-08-20, per the pinned clause snapshot referenced below. It is not the formal Standards Release Usage Guidelines and does not replace your own validation against the Swift MyStandards / Usage Guidelines portal.

CBPR+ SR2026 Zero PII Client-Side

Scope & reliance: 🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Message-type scope, exemption list, hybrid definition, and rejection mechanics are cited from the Swift CBPR+ SR2026 public guidance pages pinned in research/clause-snapshots/Swift-CBPR-SR2026-unstructured-address-removal-2026-08-20.excerpt.md (paragraphs P1–P6). No hybrid-format sunset date is claimed; none has been announced. Deterministic logic · no inference · zero PII · runs offline · CC BY 4.0.

Message Type

ISO 20022 message identifier

Parties & Agents (synthetic data only)