Executive brief

Pain001 Executive Brief

One page. Five facts. One ask. Also available in French, German, and Spanish, and print-ready from your browser.

To print or save as PDF: use your browser's print function (⌘P / Ctrl+P). This page carries a print stylesheet that produces a clean single page, with no navigation, no footer, and links written out in full.

Read in: Français · Deutsch · Español

The problem#

Banks reject malformed payment files. Every rejection costs a repair cycle; a repair that misses the day's cut-off costs a settlement day. The rejection reasons are knowable in advance, and therefore preventable.

The deadline#

Deferred, not dropped. In August 2026 Swift postponed the rule that rejects cross-border payments (CBPR+) with fully unstructured addresses, and the move from interbank MT101 to ISO 20022 pain.001 version 9. The new timing comes by December 2026. The exposure still sits in customer master data, and dates already set remain: June 2027 (investigations), November 2027 (CHAPS purpose codes), November 2028 (MT statements). Sources: Swift and central banks, cited in full at pain001.com/2026-iso20022-migration-trends.

What Pain001 does#

An open-source suite that converts existing data (spreadsheets, ERP exports, legacy SWIFT files) into bank-ready ISO 20022 payment files, and proves each file against the bank's official rulebook (ISO 20022 XSD) before submission. It runs entirely on your own infrastructure: no upload, no vendor cloud, no telemetry.

What it costs#

Nothing, at any scale, under open licences (Apache-2.0 / MIT). Commercial reference point: SWIFT's translation SDK is publicly listed at €10,000–30,000 per year.

Support, an LTS line and private profile work for your bank's guideline are offered separately, without changing the licences: enterprise page.

The evidence#

Published dependency inventory (SBOM) · 100% branch-covered code as a CI gate · independently scored supply chain (OpenSSF Scorecard) · WCAG 2.2 AAA accessible documentation · security policy with private disclosure. All verifiable at pain001.com.

The ask#

Have your payments engineering team run the 60-second demo at pain001.com/try. It validates a sample batch and proves it against the official ISO 20022 schema, in the browser, with nothing uploaded. If it holds up, the installation guide takes minutes.