CBPR+ Structured Address Lint

Lint ISO 20022 pacs.008, pacs.009 and pain.001 XML for postal addresses CBPR+ will not accept: unstructured blocks, missing Ctry or TwnNm, and values duplicated between a structured field and AdrLine. Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

Get the complete version $29

This page is the working piece. The full pack has everything below.

Find the ISO 20022 postal addresses your correspondent bank will repair by hand, before you send the message

A correspondent bank charges $15 to $40 to repair one cross-border payment by hand; the average fee for a rejected or repaired payment is reported at about $12.

Buy the full version — $29

Questions people ask

What does CBPR+ Structured Address Lint actually do?

It reads the PstlAdr blocks in your ISO 20022 XML - pacs.008, pacs.009, pain.001 - and flags each one that breaks a CBPR+ postal-address rule, on the line where it breaks, with the rule behind it. 9 rules, 6 of them errors. It runs on the file in your editor and, with a key, across the whole workspace into a dated audit file.

Who is this for?

Payments-integration developers and ISO 20022 migration engineers at banks, PSPs and treasury software vendors - the people who write the mapping code or review what a code assistant generated. If you own a pacs.008 template, an ERP payment export, or the address mapping from a customer master file, this is your file.

Why doesn't schema validation catch this?

Because a malformed hybrid address is schema-valid. XSD checks types and lengths, so a block that repeats Milano in both TwnNm and an AdrLine passes. The CBPR+ usage guidelines sit above the schema: hybrid rules live since 2025-11-22, and the unstructured cutover deferred 2026-08-27. A general chatbot gets those two dates wrong in both directions.

What is free and what needs a licence key?

Free, with no key: lint the file open in your editor against all 9 rules and see every failing address block with its line number. That finishes the job for one file. The paid layer is ownership - a dated CSV and Markdown audit of every message in the workspace, written to disk as evidence you can hand over. $29 once, 7-day full refund.

What would this cost without the tool?

A correspondent bank charges $15 to $40 to repair one cross-border payment by hand, and the average fee for a rejected or repaired payment is reported at about $12. Those are per payment, and a bad address template repeats on every payment it generates. The extension is $29 once, and the file check is free.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Want the full version?
Enter your email and we send the download link.
ENDEJAESPT

Find a tool