Lints SEPA Credit Transfer pain.001 XML against the 2019 ISO 20022 message version and EPC scheme rules: retired namespace, IBAN mod-97, CtrlSum/NbOfTxs, SEPA character set. Runs entirely in your browser — nothing is uploaded.
Same engine as the VS Code extension, byte for byte.
Free for the file open in your editor - no key, no limit. The workspace sweep and the report ask for a key.
Open VSX (Cursor, VSCodium)npmDocker Hubnpx @readystack/sepa-pain001-reject-lint <file> docker run --rm -v "$PWD:/w" getreadystack/sepa-pain001-reject-lint /w
Team? One key for every ReadyStack linter, 5 seats, $149 once
This page is the working piece. The full pack has everything below.
Find the lines your bank will refuse before you send the batch
By hand this is 25 rule checks per transaction, read against the EPC rulebook every time the batch changes
Buy the full version — $29It reads a SEPA credit transfer XML file and marks every line a bank gateway will refuse, with the rule and the line number. It covers 25 rules: the pain.001.001.09 message version, IBAN mod-97 check digits, BIC shape, CtrlSum and NbOfTxs arithmetic, ChrgBr, the 140 character remittance limit, duplicate EndToEndId values and the SEPA Latin character set.
Developers and payment operations engineers at EU companies who generate pain.001 files: ERP and accounting integrators, treasury teams building their own payment runs, and fintech engineers shipping a SEPA credit transfer feature. If a returned batch lands on your desk on a Monday morning, this is aimed at you.
An XSD says whether the shape is legal, not whether the batch will clear. A file can validate perfectly against the schema while CtrlSum disagrees with the amounts, an IBAN fails its mod-97 check digits, a supplier name carries an umlaut, or the whole document still declares the retired pain.001.001.03 version. The schema has no opinion about any of those.
Free checks one open file against all 25 rules and shows every finding with its line, in the editor or on the web page, with no key. The paid version adds a different axis: it scans every payment file in the workspace in one pass and exports the findings as JSON, CSV or Markdown that you keep and hand to the bank or the auditor.
Reading a batch against the rulebook is 25 rule checks per transaction, repeated in full every time the file changes, because a single edit can break CtrlSum, NbOfTxs and a check digit at once. A four transaction batch is 100 checks. The licence is 29 dollars once, with a seven day full refund.
One question, answered by the person who built it. Your email only if you want the answer sent.