Test Data for Sandbox
To execute a test transaction you only need to make sure that you are using the public commerce key for the Sandbox environment. Remember that it has the pub_test_ prefix.
In what follows you will see the required test data for each payment method:
Cards
For a test transaction with a card number, you could use the following card numbers when you use the tokenization endpoint (if you use an integration with API) or when you fill the card data in our Widget, so you could obtain different responses:
1. Frictionless Authentication - (BROWSER_INFO)
It is an approach that uses data analysis and advanced technologies to transparently verify the cardholder's identity without interruptions for the user. Behavioral data is collected and analyzed to assess the legitimacy of the transaction. If the analysis indicates a low probability of fraud, the transaction is authorized without requiring additional authentication steps. This provides a smooth and secure user experience by minimizing the cardholder's intervention:
4917 4800 0000 0057for an approved transaction (APPROVED).4917 4800 0000 0008for a declined transaction (DECLINED).
2. Direct Authentication - (CHALLENGE)
It is an additional security process in online transactions. When a risk is detected or certain criteria are met, the cardholder is requested to complete an authentication challenge, such as entering an additional password or validating information through a code sent to their mobile device. This additional step helps ensure that the transaction is legitimate and protects against potential fraud:
4970 1100 0000 1029for an approved transaction (APPROVED).4970 1100 0000 0062for a declined transaction (DECLINED).
3. Full Authentication - (BROWSER_INFO - CHALLENGE)
In certain scenarios, some transactions may initially trigger frictionless authentication, which is a smooth and seamless process. However, in situations where an additional level of security is deemed necessary, direct authentication is also triggered. This means that the cardholder is required to complete an additional authentication challenge to more effectively ensure the legitimacy of the transaction:
4666 5330 0000 0031for an approved transaction (APPROVED).4666 5330 0000 0015for a declined transaction (DECLINED).
4. No Authentication
No Authentication is used:
4242 4242 4242 4242for an approved transaction (APPROVED).4111 1111 1111 1111for a declined transaction (DECLINED).
It is essential to use any of the above cards with a valid expiration date in the future and a 3-digit CVC to complete the online transaction correctly. If a card that does not meet these requirements is used, the transaction will end in an ERROR status and the payment process will not be completed.