Testing Steps
Careful testing is the cornerstone of software development, making your integration safe and free of errors. You cannot move on to a live environment and handle real payments until you have confirmed that your integration works as desired in all scenarios.
Prerequisites
Before you start testing your mobile integration, you must complete:
- Basic integration.
- Any customizations related to the payment methods that you want to support.
- All security-related functionality that you need.
Testing your integration
Cover at least the following steps in your testing:
- For the payment methods you support in your mobile app, test the payment process for each until the point where the session has been updated with the payment details.
- Test the 3D Secure (3DS) authentication process if you use it.
- Confirm that your app reacts appropriately and overcomes all common error scenarios related to invalid requests and connection problems. Determine the transaction responses that require further actions from you, and test that your integration is taking expected actions.
- To test the final payment transaction and any subsequent transactions that are handled from your server and not in the app, follow the instructions for Hosted Session Testing Steps.
Testing tools
To test your integration, the ANZ eGate payment gateway provides some helpful tools:
- Test cards
If you support card payments as payment methods, the gateway provides test cards to enable you to test various scenarios, including 3D Secure authentication. For details, see Test Cards and Testing your 3DS Integration. - Test wallet tokens
If you support Apple Pay or Google Pay as payment methods, you can use provided test card details to test the wallet functionality. For details, see Apple Pay and Google Pay.