To help you integrate and test your project, use the sandbox and live environments before release.
The sandbox environment is best used to test all possible scenarios, as well as all possible results including error handling, additional security features, etc. Make sure that you are not jumping into the live environment before you are comfortable that everything is working as expected in the sandbox.
A “by appointment” test service is available which allows the validation of the myPOS Mobile Checkout iOS SDK calls. Testers should negotiate exclusive access to the testing service and ensure monitoring by a myPOS engineer.
Depending on your business requirements, we encourage you to test your project in all the possible scenarios and using all the supported card networks. This means:
Generate successful payments:
This test scenario is for generating a successful payment status and applies to perform a payment and to perform a refund.
A successful test is passed when the value for the ‘result’ is ‘successful’ and the user is returned to your app’s flow according to your design.
Generating declined payments:
This test scenario is for generating a successful payment status and applies to perform a payment and to perform a refund.
When testing for a ‘Payment declined’ result, you should process transactions with the following variables.
- Incorrect CVC2 (card security code) values
- Incorrect/Invalid dates
- Invalid card numbers
Testing 3D security features:
The final results of testing 3D Secure can only be binary (success or failure), but there are diverse scenarios during the 3D Secure check that can conduct one end or the other.
