Multichannel Payment Integration Testing
Budget: $30 – $250 USD
I need end-to-end testing for several payment rails that I am about to launch. The scope covers:
• E-wallet flows – I’m enabling wallet payments and want each major provider exercised, from tokenisation through to refund.
• QR-based check-out – scan, pay, and instant status updates must be verified across devices.
• Bank transfers – ACH Transfer and Wire Transfer need to move through their full life-cycle, including failed, pending, and successful scenarios.
What I expect from you
1. A concise test plan that lists every scenario, the data you will use, and the APIs or SDK calls each step touches.
2. Automated or repeatable scripts (Postman collections, Cypress/Selenium suites, or similar) so my team can rerun the checks in CI later.
3. A final report that highlights defects, edge-cases you uncovered, and confirmation that all critical paths now pass.
Feel free to suggest the exact combination of tools; I am comfortable with anything widely adopted in QA (e.g. JMeter for load, Charles/Fiddler for traffic capture). Timeline and milestone breakdown are appreciated so I can slot your work into our release calendar.
• E-wallet flows – I’m enabling wallet payments and want each major provider exercised, from tokenisation through to refund.
• QR-based check-out – scan, pay, and instant status updates must be verified across devices.
• Bank transfers – ACH Transfer and Wire Transfer need to move through their full life-cycle, including failed, pending, and successful scenarios.
What I expect from you
1. A concise test plan that lists every scenario, the data you will use, and the APIs or SDK calls each step touches.
2. Automated or repeatable scripts (Postman collections, Cypress/Selenium suites, or similar) so my team can rerun the checks in CI later.
3. A final report that highlights defects, edge-cases you uncovered, and confirmation that all critical paths now pass.
Feel free to suggest the exact combination of tools; I am comfortable with anything widely adopted in QA (e.g. JMeter for load, Charles/Fiddler for traffic capture). Timeline and milestone breakdown are appreciated so I can slot your work into our release calendar.