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. Sandbox channels also support
hours as subscription unit for faster testing. Please note, when using
hours you will also need to define
|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|
|Charge||First renewal failure with error code XXX on charge||any||2XXX|
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.
If you want to test failed subscription renewals which happens after the first cycle of the subscription then you should insert PIN starting with 2 and specific error code XXX. As a result you will get a failed renewal after the first cycle of subscription. It is better to test with hourly configured subscriptions in sandbox.
Please note that sandbox subscriptions will be automatically suspended after 60 days of creation unless "cycles" parameter is defined in the JWT payload.
Make thorough tests before considering the integration live ready. Check out testing best practises here.
We have to make thorough UAT tests on our end to ensure the quality of the integration and present it to operators. Please make sure that you set up a staging environment/app or provide us accounts with special permissions in production environment so we can test your integration in easy manner.
For doing live tests with different carriers there is a site called simtest.it which you can use to book different sim cards online.