Regression testing
Peach Payments commits to delivering resilient, high-performing payment solutions. The Open Payments Platform is continuously enhanced with new features, functionality, and security. Before releasing any updates, Peach Payments runs thousands of regression tests to ensure backward compatibility. Despite this rigorous testing, Peach Payments recommends that you validate your integration.
UAT
The Peach Payments User Acceptance Testing environment is available every day and ensures a fully functional end-to-end consumer workflow.
By running your own set of regression tests, you can ensure your integration remains functional following any new releases:
- Identify potential issues before changes occur in production.
- Ensure seamless integration with the updated platform.
If you have issues in UAT, contact support to prevent potential production incidents.
Testing guidelines
- Do not use production MIDs or configuration data in the UAT environment.
- Never use real cards for testing. Use these test cards.
Server-to-Server integration testing
- This method bypasses a web browser.
- Test by sending requests to the API and verifying the responses.
Use the following resources to test:
- API documentation
- Tutorials
- Backoffice transactions documentation for captures, reversals, and refunds.
COPYandPAY integration testing
- Requires a browser for testing.
- Ensure your integration uses a payment page that is the same as your production payment page.
Follow these testing recommendations:
- Test using multiple browsers to account for differences in JavaScript execution.
- Consider using a cross-browser testing tool.
- For Chrome-specific testing, use its headless version with different test frameworks.
View the COPYandPAY integration documentation for more information.
Webhooks
Configure webhooks in the UAT environment to receive transaction notifications. View the webhook documentation for more information.
Troubleshooting
If a test that used to pass starts failing, contact support. Use the subject line "UAT Integration Problem" when reporting issues.
Updated about 7 hours ago