Skip to main content

Test Data for Sandbox

To execute a test transaction you only need to make sure that you are using the public account key for the Sandbox environment. Remember that it has the pub_test_ prefix.

Below you will see the required test data for each payment method:

Cards

For a transaction with a test card number you should use the following numbers to obtain different responses:

  • 4242 4242 4242 4242 for an approved transaction (APPROVED). Any future expiry date and 3 digit CVC is valid.
  • 4111 1111 1111 1111 for a declined transaction (DECLINED). Any future expiry date and 3 digit CVC is valid.

If you use any other card that is not one of the aforementioned ones, the final state of you transaction will be ERROR.

Nequi

To create an approved or declined transaction in Sandbox mode you only need use the following numbers:

  • 3991111111 for an approved transaction (APPROVED)
  • 3992222222 for a declined transaction (DECLINED)

Take into account that any other number which you use will result in a transaction with a final state of ERROR.

If you're using an API integration, you'll do the following:

{
// Other transaction data...
"payment_method": {
"type": "NEQUI",
"phone_number": "3991111111" // This will result in an APPROVED transaction
}
}

PSE

For PSE payments, in the case of API integrations, you must send a specific financial_institution_code within payment_method, when creating a transaction (using POST /transactions endpoint). For example:

{
// Other transaction data...
"payment_method": {
"type": "PSE",
"user_type": 0, // User type, person (0) or company (1)
"user_legal_id_type": "CC", // Document type, CC or NIT
"user_legal_id": "1999888777", // Document number
"financial_institution_code": "1", // "1" for APPROVED transactions, "2" for DECLINED transactions
"payment_description": "Payment to John Store" // Max. 30 characters
}
}

In the Widget, only two banks will be available, which will return specific transaction results:

  • Banco que aprueba: This will return an approved PSE transaction.
  • Banco que rechaza: This will return a rejected PSE transaction.

Botón Bancolombia

For Botón Bancolombia payments, in the case of API integrations, you must send a sandbox_status within payment_method, when creating a transaction (using POST /transactions endpoint). For example:

{
// Other transaction data...
"payment_method": {
"type": "BANCOLOMBIA_TRANSFER",
"user_type": "PERSON",
"payment_description": "Payment to John Store", // Max. 64 characters
"sandbox_status": "APPROVED" // Desired final status of the transaction. Can be one of the following: APPROVED, DECLINED or ERROR
}
}

In the Widget, the following options will be available:

  • Transacción APROBADA: For approved transactions.
  • Transacción DECLINADA: For declined transactions.
  • Transacción con ERROR: For transactions with an error.

Bancolombia QR

For Botón Bancolombia payments, in the case of API integrations, you must send a sandbox_status within payment_method, when creating a transaction (using POST /transactions endpoint). For example:

{
// Other transaction data...
"payment_method": {
"type": "BANCOLOMBIA_QR",
"payment_description": "Pago a Tienda Wompi", // Max. 64 characters
"sandbox_status": "APPROVED" // Desired final status of the transaction. Can be one of the following: APPROVED, DECLINED or ERROR
}
}

In the Widget, the following options will be available:

  • Transacción APROBADA: For approved transactions.
  • Transacción DECLINADA: For declined transactions.
  • Transacción con ERROR: For transactions with an error.

Puntos Colombia

For PCOL payments, in the case of API integrations, you must send a sandbox_status within payment_method, when creating a transaction (using POST /transactions endpoint). For example:

{
// Other transaction data...
"payment_method": {
"type": "PCOL",
"sandbox_status": "APPROVED_ONLY_POINTS" // Desired final status of the transaction.
}
}

For PCOL sandbox_status the possible options are:

  • APPROVED_ONLY_POINTS: Total Payment with Points
  • APPROVED_HALF_POINTS: Half Payment make with Points
  • DECLINED: Points redemption Declined
  • ERROR: Points redemption with Error

BNPL Bancolombia - Daviplata

For the BNPL sandbox environment, the only difference you will encounter is that the URL leading you to the BNPL experience will direct you to a page where you can define the final state in which the transaction will conclude. The website will appear as follows:

sandbox bnpl

DAVIPLATA

When you initiate a transaction with the payment method Daviplata and use the interface provided by Wompi, you will have the option to choose the final status of the transaction, as shown in the following image:

sandbox daviplata

To carry out transactions through the API, you just need to consider the following OTP codes:

  • 574829 for an approved transaction (APPROVED)
  • 932015 for a declined transaction (DECLINED)
  • 186743 for a declined without sufficient balance transaction (DECLINED)
  • 999999 for an error transaction (ERROR)