Detect "silent data loss" in MX payment payloads before they hit legacy systems. Paste any pacs.008 or ISO 20022 MX message to identify XML fields exceeding MT character limits and audit postal addresses against the mandatory November 2026 SWIFT/EPC structured address standard. All parsing runs in your browser.
Zero PII · Client-Side Only⚠ Nov 2026 MandateTruncation CheckAddress Audit
⚠️ SWIFT CBPR+ Deadline: 15 November 2026 — Unstructured postal addresses will be rejected by SWIFT CBPR+ and the EPC. Hybrid (TwnNm + Ctry present) is the minimum. Fully structured is preferred. Source: swift.com
Supports any MX message type. The tool will scan all recognised element names and every PstlAdr block.
Truncation Risk Findings
Compares every matched element's text length against legacy MT field limits (35 chars for names/IDs, 140 chars for remittance). Fields that overflow will be silently truncated during MX→MT translation — potentially causing compliance screening failures, STP breaks, or sanctions screening mismatches.
📋
Paste an MX XML message above and click Run Both Checks (or Run Both Checks) to see truncation findings here.
Export
Address Compliance — Nov 2026 Mandate
Checks every <PstlAdr> element in the message against the SWIFT CBPR+ / EPC November 2026 structured address requirement. TwnNm and Ctry are mandatory. StrtNm, BldgNb, and PstCd are strongly recommended. Addresses still using only AdrLine without TwnNm/Ctry will be rejected after the deadline.
CBUAE note: CBUAE compliance depends on issuer bank-ownership status. Results shown for conservative (non-bank) interpretation where 100% cash escrow is required.
🏛️
Paste an MX XML message above and click Run Both Checks to see address audit results here.