Check a pain.001.001.09 file before it goes to your bank: the ISO 20022 schema, the EPC SEPA Credit Transfer rules, control totals, IBANs including national account check digits, and reference formats. Each finding names the element and line.
Use the Payment Preflight API to check pain.001 files and generate negative test files in your pipeline. Tell us what your ERP or treasury system sends and to which bank.
pain.001.001.09 against the ISO 20022 schema and the EPC SEPA Credit Transfer customer-to-PSP implementation guidelines (2025 version), plus control totals, IBAN and reference checks.
No. It means no errors were found for the rules listed. Banks can apply their own conditions, and some rules depend on facts that are not in the file.
Yes. The API generates synthetic pain.001 files for typical failures: IBAN checksum, currency, identifier format, missing town and wrong control sum.
No. It is checked in a temporary sandbox and not stored. Use synthetic data where you can.
IBANgen provides synthetic QA data. Simulated files and responses do not reflect how any real bank or operator processes payments.