3D Secure
Testing
The Braintree sandbox allows end-to-end testing for each of the card brands supported in our 3DS integration. If you want to test in the production environment, see our guidelines on Testing in Production.
Below is a list of card numbers that can be used for testing 3DS in Sandbox:
noteIt is recommended to disable ad blockers when using the test cards below. Some ad blockers have been found to prevent device data collection, resulting in an inadequate 3DS response.
importantFor expiration year values for all test cards in the table below, use the current year + 3 years. The expiration month should always be 01.
noteIf you call
Transaction.sale()without performing a 3D Secure authentication, the issuing bank may return a soft decline indicating that the issuing bank will not proceed with the transaction without requiring the cardholder to authenticate. In this case, 2099 - Cardholder Authentication Required, or another soft decline code, will be returned. You can simulate this scenario by creating a test transaction in Sandbox with an amount of2099.
| Scenario | Card brand specific test values |
|---|---|
| Successful No-Challenge Authentication Cardholder enrolled, authentication successful, and signature verification successful. status: authenticate_successful | Visa
|
| Failed No-Challenge Authentication Cardholder enrolled, authentication unsuccessful. Merchants should prompt customers for another form of payment. status: authenticate_frictionless_failed | Visa
|
| Attempt No-Challenge Authentication The provided card brand authenticated this 3D Secure transaction without password confirmation from the customer. status: authenticate_attempt_successful | Visa
|
| Unavailable No-Challenge Authentication from the Issuer Authentication unavailable for this transaction. status: authenticate_unable_to_authenticate | Visa
|
| Rejected No-Challenge Authentication by the Issuer Authentication unsuccessful. Merchants should prompt customers for another form of payment. status: authenticate_rejected | Visa
|
| Authentication Not Available on Lookup Authentication unavailable for this transaction. status: authentication_unavailable | Visa
|
| Error on Lookup An error occurred while attempting to lookup enrollment. status: lookup_error | Visa
|
| Timeout on Lookup Attempting to lookup enrollment resulted in a timeout. status: lookup_failed_acs_error | Visa
|
| Bypassed Authentication Bypass used to simulate a scenario where merchant has elected to bypass the consumer authentication flow via CardinalCommerce Rules Engine configuration. status: lookup_bypassed | Visa
|
| Successful Challenge Authentication Cardholder enrolled, authentication successful, and signature verification successful. status: authenticate_successful | Visa
|
| Failed Challenge Authentication Cardholder enrolled, authentication unsuccessful. Merchants should prompt customers for another form of payment. status: challenge_required | Visa
|
| Challenge Authentication is Unavailable Authentication unavailable for this transaction. status: challenge_required | Visa
|
| Error on Authentication An error occurred while attempting to authenticate. Alternatively, merchants can ask customers for an alternative form of payment. status: authenticate_error | Visa
|
| Data Only Successful The data-only 3D Secure call was successfully created. The dataOnlyRequested flag must be sent to receive a successful response. status: data_only_successful | MasterCard
|
| Authentication Unsuccessful Authentication unsuccessful. Merchants should prompt customers for another form of payment. status: authenticate_rejected | Visa
|
For more details on the test card numbers above, see the guide from CardinalCommerce, our 3DS authentication provider.