Skip to main contentTesting Environment
This guide provides instructions for testing your Tumipay integration in the Sandbox environment before moving to production.
Environment for Certification
Before going live with your integration, all implementations must be certified in the Sandbox environment. This ensures that your system properly handles all transaction flows, including approvals, rejections, and webhook notifications.
Transaction Approval
To approve a transaction during testing, follow these steps:
-
Use the PSE button:
Navigate to the list of banks and select any option from the list.
-
Complete the form:
Fill out the form with the required user information to proceed.
-
Final transaction status:
At this point, a webhook notification will be triggered based on the transaction’s status.
Sandbox Testing Parameters
PayIn Testing
To control transaction outcomes in the sandbox environment:
-
For approved transactions:
Use the email
[email protected] in the customer_data.email field.
-
For rejected transactions:
Use any other email domain not ending in “topup.com.co”.
PayOut Testing
For PayOut transaction testing:
- First create a successful PayIn transaction to fund your wallet
- Then initiate a PayOut with the following test parameters
- For testing transaction outcomes using description field:
- For approved transactions: Send “APPROVED” in the description field
- For rejected transactions: Send “REJECT” or any other value in the description field
Webhook Testing
When testing webhook integrations:
- Make sure your webhook endpoint is publicly accessible
- Your endpoint should return a 200 OK response
- Verify that you’re correctly handling the signature validation
Moving to Production
Once you’ve thoroughly tested your integration in the Sandbox environment:
- Submit your integration results to [email protected]
- Our team will review your implementation
- Upon approval, you’ll receive production credentials
Note: Production credentials are distinct from Sandbox credentials and should be securely stored.