Testing is essential to ensure that your Payments API integration is completed successfully and user experience meets mobile operator standards and customer expectations.
While testing the user experience and charging, it's important to validate the following aspects: - user experience, service terms and pricing is clearly presented to the customer (see also Best practices on displaying carrier billing on checkout) - successful purchase flow is straightforward and smoothly triggers service delivery - negative scenarios (like not supported operator or not enough funds) are also supported, e.g. by displaying relevant error messages based on charging error codes - your backend is capable of quickly processing the callback load which corresponds with expected usage (expect 3-6 callback request in total for each auth and purchase attempt) - integration is capable of handling callback retry attempts in case initial attempt fails
For integration testing purposes we have created a dummy carrier for every country. That will allow you test different payment flow scenarios without making any real payments and without needing to have access to any real SIM cards. Sandbox carrier codes always follow a pattern sandbox-xy, xy representing the country code. To test payments in Estonia you could use channel sandbox-ee, for Malaysian payments you could use sandbox-my etc.
|PIN Send||Failure with Fortumo error code XXX on PIN send||***777XXX||N/A|
|PIN Verification||Failure with Fortumo error code XXX on PIN verification||any||8XXX|
|Charge||Failure with Fortumo error code XXX on charge||any||0XXX|
For example, if you would like to test charging error 701 then you would need to enter 0701 as the PIN code and Fortumo will respond with ERR_701.
For doing live tests with different carriers there is a site called simtest.it which you can use to book different sim cards online.