Skip to main content
The Sandbox environment uses the same operations as Live, with a Sandbox key and Ipay-Target-Environment: sandbox; no real transaction is triggered. The requests themselves are not repeated here: use the Create a transaction and Retrieve a transaction pages, and only replace the values with the ones below.

​
Mobile test numbers

For Ipay-Payment-Type: mobile in Sandbox, with country: NE (the documentation example), only the ten numbers below are accepted, and each one simulates a fixed result. Any other msisdn for this type returns 400 Bad Request: Incorrect MSISDN, even if it is well formed: this is not a generic simulator that accepts any number. “Error”, “Insufficient funds” and “Declined” share the same final status failed: the API does not expose any additional sub-category in the status field to tell these three cases apart. The two pending numbers do not stay pending forever: they automatically move to succeeded after a delayed resolution of about 90 seconds — this is neither a stuck state to fix manually nor a random result.

​
Minimum amount in Sandbox

For mobile, the minimum accepted in Sandbox is 50 XOF, whereas the Live minimum for the same type is 25 XOF. An amount between 25 and 49 XOF is therefore refused in Sandbox even though it would be accepted in Live: do not infer production behavior from it, and test your error handling with an amount clearly below both thresholds.

​
Cases to cover before going live

Treat the validation error as a customer input error, not as an incident to retry automatically. The full list of codes and messages is in Errors.