Payment Flow Simulator
pain.001 → bank → pain.002 — the complete lifecycleWalk through a real ISO 20022 payment flow step by step. Fill in payment details, see the generated pain.001 XML, choose a bank outcome, and get the parsed pain.002 response — all in one place. Useful for understanding the SEPA payment lifecycle before integrating with a real bank API.
This simulates what happens when you submit a payment batch to your bank and receive the status report back. All data is synthetic — for testing and development only.
All processing happens in your browser. No payment data is sent to any server.
Who this is for
This simulator is designed for developers building SEPA payment integrations. It lets you understand the full request-response cycle before connecting to a real bank API — including what a pain.001 file looks like on the wire, what different bank outcomes (accepted, rejected, pending) look like in a pain.002, and how rejection codes map to actionable errors.
- Explore the pain.001 XML structure without a bank connection
- See how RJCT, ACSC, PDNG outcomes appear in pain.002
- Understand reason codes (AC01, AM04, DUPL, etc.) in context
- Test your parsing logic against realistic response data