Skip to main content

​
Testing 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:
  1. Use the PSE button: Navigate to the list of banks and select Banka.
  2. Complete the form: Fill out the form with the required user information to proceed.
  3. 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 approved@tumipay.co in the customer_data.email field.
  • For rejected transactions: Use any other email domain not ending in “uat.topup.com.co”.
For methods that stay pending (BREB, EFECTY, SPEI, QR, and others), use the Sandbox Confirm endpoints to approve, reject, or expire the transaction without waiting for an external webhook. CARD, PSE, and NEQUI_PUSH are exceptions: they are not confirmed through sandbox confirm. For CARD, the result is fixed by the test card number. For PSE, create the PayIn with bank Banka and complete the normal flow using the email rules above. For NEQUI_PUSH, sandbox automatically simulates the push after create — see Colombia PayIn.

​
Card Payment SDK

Use the Cards SDK Demo to test initialize(), validateCard(), getBinInfo(), and authenticateCard() in UAT with your merchant credentials before integrating tumipay-cards-js. See the SDK reference for method details and error codes.

​
PayOut Testing

For PayOut transaction testing:
  1. First create a successful PayIn transaction to fund your wallet
  2. 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
When the PayOut is already waiting for the bank, use Sandbox Confirm to force APPROVED, REJECTED, or EXPIRED and receive the merchant webhook.

​
Webhook Testing

When testing webhook integrations:
  1. Make sure your webhook endpoint is publicly accessible
  2. Your endpoint should return a 200 OK response
  3. Verify that you’re correctly handling the signature validation

​
Moving to Production

Once you’ve thoroughly tested your integration in the Sandbox environment:
  1. Submit your integration results to tecnologia@tumipay.co
  2. Our team will review your implementation
  3. Upon approval, you’ll receive production credentials
Note: Production credentials are distinct from Sandbox credentials and should be securely stored.