F A Q

1. How do I test the API endpoints in the WapiPay sandbox environment?

• Answer: To test the WapiPay API endpoints, you need to use the sandbox environment. You can generate sandbox API keys, configure your API client with those keys, and then make API requests to the sandbox URLs. Always ensure that you are using the correct endpoint (e.g., sandbox-test) and that your test data is valid to simulate real-world transactions.

2. What should I do if I receive a 400 Bad Request error during testing?

• Answer: A 400 Bad Request error typically occurs when the request is malformed or missing required parameters. Check the request payload, ensure that all required fields are included, and that the data types and formats are correct. Also, ensure your API keys and endpoint URLs are correctly configured.

3. Can I use real phone numbers and bank account details in the sandbox environment?

• Answer: No, in the sandbox environment, you should use test data. WapiPay provides dummy phone numbers and account details that you can use for testing purposes. This ensures that no real transactions are processed while you are verifying the integration.

4. What is the process for handling callbacks in WapiPay integration testing?

• Answer: During integration testing, you need to set up a callback URL to receive transaction status updates from WapiPay. Once the transaction is processed, WapiPay will send a POST request with the result to your callback URL. Ensure that your server is ready to handle these POST requests and parse the response data (e.g., status, error codes).

5. How do I verify that a payment has been successfully processed in the sandbox environment?

• Answer: After making a payment request in the sandbox environment, check the response to confirm that the transaction was successful (e.g., resultCode 0 and success message). You can also use WapiPay’s API to query the transaction status or check the callback responses to confirm whether the payment has been processed successfully.