pain.001 Generator and Validator
Generate an ISO 20022 pain.001 XML for a SEPA batch credit transfer, or structurally validate a pain.001 file you already have (required fields, IBAN MOD-97, amount/count consistency).
Updated:
Privacy: The calculation runs in your browser; the full IBAN, account number, amount and reference you enter are not sent to a server, logged or passed to analytics. Some tools may pass only a non-sensitive term (e.g. bank code, BIC, currency) to a lookup service for search/matching. Per-tool detail: Privacy.
Sender (debtor)
Recipients (transactions)
How does this tool calculate?
High — matches current official data- Method/formula used
- Generating a pain.001.001.03 (SEPA payment initiation) XML from your inputs; validation checks required fields, IBAN MOD-97, amount format and NbOfTxs/CtrlSum consistency.
- Data used
- ISO 20022 pain.001 + EPC Implementation Guidelines structure
- Unsupported cases
- Does not guarantee bank acceptance (version/required-field differences)
- Not a full XSD schema validation, only a structural check
What is pain.001?
pain.001 (CustomerCreditTransferInitiation) is the SEPA payment initiation message sent from a customer to a bank under the ISO 20022 standard. It is the XML format organisations use to send single/batch credit transfer instructions to their banks. The bank-to-bank transfer itself runs through a separate message (pacs.008) — see what is SEPA.
How do I use the generator?
- Sender details: Enter your name, your IBAN and (if any) BIC, and the execution date.
- Add recipients: For each recipient enter name, IBAN, amount and description. Use "+ Add recipient" to add multiple rows (batch transfer).
- Generate XML: The tool produces the pain.001.001.03 XML; save it as
.xmlwith "Download XML" and upload it to your bank's channel.
How do I use the validator?
- Switch to the Validate tab and paste the pain.001 XML you have.
- The tool checks the required fields (MsgId, date, number of transactions), the sender/recipient IBANs with MOD-97, the amount format and the NbOfTxs/CtrlSum consistency.
This tool produces/checks a structural XML; it does not guarantee your bank will accept it. Banks may differ in version (…03 / …09) and in required fields — rely on your bank's technical documentation. Everything runs in your browser; your data does not go to a server.
Sources
ISO 20022 message standards (pain / camt)
ISO 20022 Registration Authority
- Document date:
- 2025
- Last checked:
- 2026-07-16
SEPA scheme rulebooks & geographical scope
European Payments Council (EPC)
- Document date:
- 2025
- Last checked:
- 2026-07-16