
Frequently asked questions
Everything you need to know about validating and generating SEPA XML with PainXML.
Do my payment files ever leave my browser?
No. Validation (via WebAssembly) and generation run 100% client-side. PainXML makes no network calls for your payment data, nothing is uploaded, logged, or stored.
What formats do you support?
We validate pain.001 and pain.008 XML against ISO 20022 XSD schemas, and generate pain.001 / pain.008 from CSV or Excel (.xlsx) files.
Do I need an account to use PainXML?
No, you can try the Studio with 5 free conversions (up to 5 transactions per batch) without an account. Sign in free to unlock up to 50 transactions per batch and to save column-mapping presets.
What's the difference between SEPA and CBPR+?
SEPA covers euro payments within the Single Euro Payments Area (pain.001.001.03/.09). CBPR+ is Swift's cross-border scheme (pain.001.001.09) and adds UETR and structured-address requirements.
Which pain.001 editions are supported?
pain.001.001.03 and pain.001.001.09 for credit-transfer files, plus pain.008.001.02 for direct-debit files.
Is there a free tier?
Yes. Without an account you get 5 free conversions (up to 5 transactions per batch). Sign in free for up to 50 transactions per batch, forever. Pro and Team remove the limit.
Where do the XSD schemas come from?
We ship the official ISO 20022 XSD schemas (licensed from SWIFT/ISO) for pain.001.001.03 and pain.001.001.09. Validation runs entirely in your browser, the schemas are fetched and applied locally.
Can I use generated files in production?
PainXML is a tool, not a bank. Always review generated files before submitting them to your bank or payment provider.