Bite Apps › SafeCAMT › Postal address checker
ISO 20022 postal address checker — structured, hybrid or unstructured?
Open a payment file and see, for every debtor, creditor and agent, whether its postal address is fully structured, hybrid or unstructured — and what to change before unstructured addresses are removed from cross-border payments.
Checking the whole payment file? SafeCAMT validates pain.001 and pain.008 files — counts, control sums, IBANs, BICs and SEPA rules — locally, nothing is uploaded.
Open SafeCAMT — free, in your browserEnglish · Deutsch · Nederlands
The file is read by this page only — nothing is uploaded or stored.
Structured, hybrid and unstructured addresses
| Format | What it contains | Status |
|---|---|---|
| Fully structured | Only structured elements (StrtNm, BldgNb, PstCd, TwnNm, Ctry, …) and at least town and country; no AdrLine. | recommended |
| Hybrid | TwnNm and Ctry (mandatory) plus at most 2 AdrLine of up to 70 characters, which must not repeat the structured data; other structured elements optional. | accepted |
| Fully unstructured | Only AdrLine (in CBPR+ at most 3 lines × 35 characters; pain.001 allows up to 7). | being removed |
The rules come from the CBPR+ usage guidelines and the Payments Market Practice Group (PMPG). For a bank (agent), a BIC alone remains enough — no postal address is needed.
When unstructured addresses stop working
Swift originally planned to reject fully unstructured postal addresses in CBPR+ payment messages from 14 November 2026. In 2026 it deferred all payment changes of Standards Release 2026: the partial “SR 2026 deferred release” goes live on 12 June 2027, and the removal of unstructured addresses has no new date yet. Many banks and market infrastructures still plan for the change, and hybrid and structured addresses are already accepted today — so cleaning address data now carries no risk. Sources: Swift — removal of unstructured address, Swift — structured address deadline extended.
The rule covers payment messages (pacs.008, pacs.009 and the pain.001 your bank converts into them). Statements and notifications — camt.052, camt.053 and camt.054 — are out of scope.
How to fix the addresses this tool flags
- Unstructured: at minimum move the town into
TwnNmand the country code intoCtry, and keep the street in one or twoAdrLine— that is a valid hybrid address. Better: split street, building number and post code into their own elements. - Hybrid with 3 or more lines: hybrid allows two lines of up to 70 characters. Join the lines, or move the post code and building into their structured fields.
- Data repeated in AdrLine: remove the town, post code or country from the address lines once they are in their own elements.
- Placeholders such as
NOTPROVIDEDinTwnNmare not accepted — use the real town.
Use the SEPA character converter to clean names and address lines, and SafeCAMT to check the rest of a pain.001 file — counts, sums, IBANs, BICs and SEPA rules.
FAQ
What is a hybrid postal address in ISO 20022?
An address with the town name (TwnNm) and country (Ctry) as structured elements plus at most two free-text address lines (AdrLine) of up to 70 characters that do not repeat the structured data.
Is the November 2026 structured address deadline still valid?
No. Swift deferred the payment changes of Standards Release 2026; the removal of unstructured addresses has no new date yet. Hybrid and structured addresses are already accepted, so you can switch at any time.
Do agents (banks) need a postal address?
No. For agents a BIC alone remains a valid option instead of a name and address.
Does the rule apply to camt.053 statements?
No. Statements and notifications (camt.052, camt.053, camt.054) are excluded from the CBPR+ address rule.
Is my payment file uploaded?
No. The page reads the file in your browser and has no network access.
Last updated 2026-11-14. Something wrong or missing? Email support@biteapps.cc.