Choose payment XML
Open a UTF-8 pain.001.001.03 file up to 2 MB.
Inspect credit transfer instructions safely.
PAIN.001 to JSON
Download normalized JSON from a supported PAIN.001 XML file with group metadata, payment batches, exact amounts, currencies and remittance text.
The JSON model preserves the parsed fields without CSV escaping; no schema or payment settlement certification is implied.
PAIN.001 ViewerYOUR WORKSPACE
Your task
Download JSON
Choose a file, then use Download JSON to save the result.
Also with this file: View payments · Download CSV · Download Excel
Processed privately in your browserNo uploadNo signup
A simple workflow
Three steps. One less thing to do.
Review batches and payments
Inspect debtor and creditor details, exact amounts, execution dates and source control totals.
Export for your review
Download payment CSV, a two-sheet Excel workbook or structured JSON.
Made for the everyday
A useful part of your workflow.
Pre-submission inspection
Read payment batch contents before sending them to a bank.
Operational review
Compare declared counts and sums with visible payments during manual checks.
Structured handoff
Export the payment rows for an internal spreadsheet or data workflow.
Good to know
A few useful answers.
The details that matter before you use PAIN.001 Viewer.
Which PAIN.001 version works?
This release supports the tested pain.001.001.03 CustomerCreditTransferInitiation namespace only. Other ISO 20022 payment versions fail closed.
Does this validate a bank's payment rules?
No. The viewer checks supported structure and required fields, but does not perform XSD, scheme, bank profile, account or settlement validation.
Are control sums recalculated?
No. Declared counts and control sums are displayed as supplied; the number of parsed payments is shown separately.
How are amounts exported?
Decimal strings remain exact. XLSX cells are text, CSV protects formula-like values and JSON preserves semantic values.
What are the XML safety limits?
Files are limited to 2 MB, 50 batches, 5,000 payments, 30,000 XML elements and 64 nesting levels. DTD, entities and XInclude are rejected.
Do payment details leave the browser?
No. XML parsing and all exports run locally. Accounts, names, remittance, filenames and file content are excluded from analytics.