Test Scenarios in 3DS Authorization

To successfully simulate the complete flow in a production scenario:

1. Use a valid 3DS Setup card/token.
2. Then, successfully simulate 3DS Enrollment.
3. Save the generated chargeId.
4. To display the 3DS challenge, follow the steps described on the Transparent Checkout via API page.
5. With this chargeId, call the 3DS authorization endpoint and use the values above to test different responses.

Important!

In sandbox: it is not possible to render the Enrollment link with Challenge, therefore skip step 4 above and go directly to step 5

Test Cards

Card Number	Test Scenario	Result Description
4716100289307782 5597773670668839	3DS Setup	These cards simulate a scenario where 3D configuration is allowed.
5466245842998772	3DS Enrollment - Rejected	This card simulates a scenario where a 3DS enrollment is rejected. Use it to test how your application handles rejected 3DS enrollment transactions.
5245581323894413	3DS Enrollment - with Challenge	This card simulates a scenario where 3DS enrollment generates a challenge. Use it to test how your application handles 3DS enrollment transactions that generate a challenge.

Temporary Test Tokens

Temporary Token	Test Scenario	Result Description
card_ZVHmBRSw3EjkJ7s93Vm4S5FiZwuQjgTi card_RtyG5hOw3EiJ8EJbwFHGQJJNDB0pqBXJ	3Ds Setup	These cards simulate a scenario where 3D configuration is allowed.
card_icZKwUvB3EgIJiPqTLXwQZBdcls8Hx5t	3DS Enrollment - Rejected	This card simulates a scenario where a 3DS enrollment is rejected. Use it to test how your application handles rejected 3DS enrollment transactions.
card_7HdM7UvB3EgC0FQQ1/LSS5gF8OU5Ie6r	3DS Enrollment - with Challenge	This card simulates a scenario where 3DS enrollment generates a challenge. Use it to test how your application handles 3DS enrollment transactions that generate a challenge.

3DS Authorization Endpoint

This endpoint simulates the final moment of 3DS authentication, where the transaction is approved or rejected after the previous setup and enrollment steps.

Important!

To successfully test this endpoint in the sandbox, you must first go through the 3DS Setup and Enrollment endpoints following the steps described above.

This will generate a chargeId that will be accepted at this endpoint. If you try to use a chargeId that has not gone through the previous steps, you will receive the following error:

{
  "message": "3D Secure Authentication not found with chargeId: ff46de80-f29b-4ed5-8d24-bdad5f49a8d7",
  "success": false
}

Scenarios for simulation

By default, all valid requests to this endpoint are approved. To simulate failures, use the following CVV values:

Scenario	Description	Field	Value
Error 500	Returns a standard error 500	CVV	500
Error 400	Returns a standard error 400 (Bad Request) response for this endpoint	CVV	400