Test your 3DS integration on the Try environment using the magic values provided below. Send requests and see simulated responses.
If you're creating tokens containing the test card numbers you must delete the token before creating another with the same PAN. You are prevented from creating another token using the same PAN. As an alternative, you can also change the namespace used as part of the token creation.
When initializing the Google Pay SDK and setting the gateway to worldpay, and the env to TEST, your wallet will be replaced with a number of test card wallet items. The main schemes and scenarios below are mapped to items in this test wallet.
Liability shift is confirmed on payment authorization. The test card number tables show the different scenarios and the likely liability shift based on the authentication details provided (e.g. authenticationValue, eci, transactionId).
Use different card numbers to alter the 3DS authentication outcome.
Please read if receiving error responses:
You must use a test card number from the table below. Using a number not listed here will result in the challenge failing to load.
Do not mix the old test cardHolderName values used for API v1/v2 with this or you will get unexpected scenario outcomes. Set the
cardHolderNameto any other value e.g.Bob Smith
| Test Scenario | Description | Test Values (2.2.0) | Outcome | Action |
|---|---|---|---|---|
| 3DS - Successful Authentication (Frictionless) | Issuer assessment resulted in a frictionless 3DS authentication. |
| 3dsAuthenticated
| Apply the authentication object in the payment request and proceed with authorization. |
| 3DS - Successful Authentication (Challenged) | The issuer prompts a challenge and the customer responds successfully. |
| 3dsAuthenticated
| Apply the authentication object in the payment request and proceed with authorization. |
| 3DS - Attempts Stand-In Authentication | The cardholder is enrolled in 3DS, but the issuer does not support it; the scheme provides a stand-in authentication. |
| 3dsAttempted
| Apply the authentication object in the payment request and proceed with authorization. |
| 3DS - Authentication Rejected | Authentication is rejected by the issuer and no challenge is offered. |
| 3dsRejected
| Do not proceed with payment authorization. Retry 3DS or use another payment method. |
| 3DS - Not Authenticated | Issuer failed the authentication without offering a challenge. |
| 3dsNotAuthenticated
| Do not proceed with payment authorization. Retry 3DS or use another payment method. |
| 3DS - Authentication Unavailable | The cardholder is enrolled, but authentication is unavailable. |
| 3dsUnavailable
| Proceed as a non-authenticated transaction or retry authentication. |
| 3DS - Authentication Error | An error occurs while attempting authentication. |
| 3dsUnavailable
| Proceed as a non-authenticated transaction or retry authentication. |
| 3DS - Authentication Timeout | Timeout during the authentication request. Note: if authenticationOutage is enabled, the same values may return the outage scenario. |
| 3dsUnavailable
| Proceed as a non-authenticated transaction or retry authentication. |
| 3DS - Failed Challenged Authentication | The issuer prompts a challenge and the customer responds with incorrect details, such as an OTP or fingerprint. |
| 3dsChallengeFailed
| Do not proceed with payment authorization. Retry 3DS or use another payment method. |
| 3DS - Authentication Outage | Recognized downstream issue or timeout, such as a Visa, Mastercard, or ACS provider outage. Additional setup is required. Speak to your Worldpay Implementation Manager for more information. |
| 3dsOutage
| Proceed as a non-authenticated transaction and apply the authenticationOutage exemption or retry authentication. |
| 3DS - Bypass | Bypass the consumer authentication flow via the Cardinal Rules Engine configuration. Returned when 3DS premium is enabled or when there is a timeout connecting to the 3DS directory server. |
| 3dsBypassed
| Proceed as a non-authenticated transaction. |
| 3DS - Exempted | An authentication based exemption is used and is successful. This is only applicable if you are using SCA exemptions. |
| 3dsExempted
| Apply the authentication object and the exemption in the payment request and proceed with authorization. |
| 3DS - Already Authenticated | A Google Pay encrypted payload that is already authenticated | There is no specific test card value for this. The encrypted Google Pay payload must be 3DS_CRYPTOGRAM. | 3dsAlreadyAuthenticated | Proceed to payment using the encrypted payload. |