Test how your ERP, treasury or payment integration handles the bank's answer before you have a bank connection: ISO 20022 status reports and notifications, NACHA returns and notifications of change, payee-name checks and provider webhooks.
Simulate the bank's answer to a pain.001. Paste a SEPA pain.001 and get schema-valid pain.002 status reports (accepted, rejected, partial) and camt.054 notifications.
Use forERP and treasury integration testsVerification of Payee outcome fixtures. Match, close match, no match and not-possible fixtures for Verification of Payee and Confirmation of Payee flows.
Use forPayee name-check (VoP / CoP) flowsACH, FPS, BECS and EFT test data. Fixtures for domestic payment rails outside SEPA.
Use forUK, AU, CA and US rail integrationsPayment provider events for integration QA. Replayable provider payment and webhook fixtures.
Use forWebhook and payment-event handlersOutcome checks for Stripe ACH test numbers. A downloadable pack that checks five Stripe ACH terminal outcomes in your own test runs.
Use forStripe ACH test-mode outcomesPaste your pain.001 into the pain.002 / camt.054 generator, choose accepted, rejected, partial or pending, and download schema-valid responses.
Use the ACH test file generator: it creates the original NACHA file plus a return file (R01, R03…) and a notification of change (C01…) linked by trace number.