- Get Started
- Guides
- Integrations
- References
- API Reference
- Basic Payment
- Forex
- Authentication
- Card Account
- Apple Pay
- Virtual Account
- Bank Account
- Token Account
- Customer
- Billing Address
- Merchant Billing Address
- Shipping Address
- Merchant Shipping Address
- Merchant
- Corporate
- Recipient
- Marketplace & Cart
- Airline
- Lodging
- Passenger
- Tokenization
- Recurring Migration
- 3D Secure
- Custom Parameters
- Async Payments
- Webhook notifications
- Job
- Risk
- Point of Sale
- Response Parameters
- Card On File
- Chargeback
- Result Codes
- Payment Methods
- Transaction Flows
- Regression Testing
- Data Retention Policy
- API Reference
- Support
Regression Testing
We are committed to delivering resilient, high-performing payment solutions. Our Open Payment Platform is being enhanced daily with new features, functionality, and security. Before issuing each new release, we run thousands of regression tests to assess and confirm backward compatibility with each code deployment. While our testing is rigorous, we still recommend you take action to validate your integration. By completing your own set of regression tests, you can further ensure your integration will continue to work following any new releases.
Our UAT environment is continuously available to customers, 24 hours a day, 7 days a week, ensuring a fully functional end-to-end consumer workflow
We encourage you to implement automated regression tests.
Building automated regression tests in the UAT environment will help you to identify potential issues before those changes move to the Production environment. If you encounter any issues in UAT during testing, please reach out to us immediately and include the phrase “UAT Integration Problem” in the subject, so we can assign the appropriate priority to the ticket and work to prevent any potential Production incidents before they occur.
Don't use production MIDs or production configuration data in UAT. Check the integration sheet for each connector you use to get the corresponding test data.
Never use real cards for testing. Use the test cards listed here.
Server-to-Server Integration
This integration doesn’t involve a web browser. They can be tested by sending requests to our API and verifying the response.
The API documentation can be found here.
Check the interactive tutorials here.
For back-office transactions (Captures, Reversals, Refunds), check this documentation.
COPYandPAY Integration
This integration needs a browser to be tested and we recommend that you check your integration using a payment page exactly as your production payment page. This will ensure that any change in the payment widget will be checked using your current production integration.
We recommend running the tests using different browsers, as there could be differences in the execution of JavaScript on each browser. Look for a Cross-Browser Testing Tool that fits your need. If you just want to test with Chrome, you can use the headless version of Chrome with different test frameworks.
Check the interactive tutorials here.
Webhooks
You can always configure a Webhook in our UAT environment to receive the notifications about transactions, like you would do in production. This is strongly recommended.
For more information on how to use the Webhooks, please visit this page.
What if we find a problem?
If you have a test starting to fail after it was successful for some time, we should be informed immediately.
Please inform in the subject that this is a UAT Integration Problem. We check for all tickets referring to UAT, especially before each release, and give them high priority to avoid releasing changes that might break customer integrations.