Redirect 3D Secure Component integration

The Card Component handles 3D Secure redirect flow to complete the required 3D Secure authentication.

To handle card payments with redirect 3D Secure authentication:

1. Get additional shopper details in your payment form.
2. Make a payment request with additional 3D Secure parameters.
3. Redirect the shopper to perform 3D Secure authentication.
4. Handle the redirect result when the shopper returns to your page.
5. Show the payment result.

Before you begin

This page assumes you have already built a Card Component integration.

If you are using 3D Secure for PSD2 compliance, read our comprehensive PSD2 SCA guide.

Step 1: Get additional shopper details in your payment form

For higher authentication rates, we strongly recommend that you collect the shopper's email address, cardholder name, billing address, and IP address for payments with 3D Secure authentication.

To get the cardholder name and billing address in your payment form, include the following when creating an instance of the Card Component:

• hasHolderName: true. This shows the input field for the cardholder name.
• holderNameRequired: true. This makes the cardholder name a required field.
• billingAddressRequired: true. This shows the billing address input fields.

     const card = checkout.create("card", {
         hasHolderName: true,
         holderNameRequired: true,
         billingAddressRequired: true
     }).mount("#card-container");

Step 2: Make a payment

From your server, make a /payments request, specifying:

Parameter name	Required	Description
paymentMethod		The state.data.paymentMethod object from the onChange event. For higher authentication rates, we strongly recommend including paymentMethod.holderName.
browserInfo		The state.data.browserInfo object from the onChange event.
channel		Set to Web.
origin		The origin URL of the page where you are rendering the Component. This can be a maximum of 80 characters and should not include subdirectories and a trailing slash. For example, if you are rendering the Component on https://your-company.com/checkout/payment, specify: https://your-company.com. To get the origin: Open the browser console and call window.location.origin.
returnUrl		In case of a 3D Secure redirect flow, this is the URL where the shopper will be redirected back to after completing 3D Secure 2 authentication. The URL should include the protocol: http:// or https://. For example, https://your-company.com/checkout/. You can also include your own additional query parameters, for example, shopper ID or order reference number.
billingAddress		The state.data.billingAddress object from the onSubmit event.
shopperEmail		The cardholder's email address.
shopperIP		The shopper's IP address.

Your next steps depend on whether the /payments response contains an action object. Choose your API version:

Step 3: Redirect the shopper

If you receive action.type: redirect, Card Component handles the redirect:

1. Call handleAction, passing the action object from the /payments response.
2. The Component redirects the shopper to the issuer page (the action.url) to perform 3D Secure authentication.
3. When the shopper completes authentication, the payment is authorized. The shopper is redirected back to the returnUrl from your /payments request.

Test environment

In our test environment, you can perform the authentication with test credentials.The action.url for testing is https://test.adyen.com/hpp/3d/validate.shtml.
Perform the authentication using the 3D Secure test credentials:

• Username: user
• Password: password

Step 4: Handle the redirect result

The issuer (or our back end, if you're using the test environment) redirects the shopper back to the returnUrl from your payment request.

GET /?shopperOrder=12xy...&&redirectResult=X6XtfGC3%21Y.... HTTP/1.1
Host: www.your-company.com/checkout

POST / HTTP/1.1
Host: www.your-company.com/checkout?shopperOrder=12xy..
Content-Type: application/x-www-form-urlencoded
MD=Ab02b4c0%21BQABAgCW5sxB4e%2F%3D%3D..&PaRes=eNrNV0mTo7gS..

Step 5: Show the payment result

Use the  resultCode from the /payments or /payments/details response to present the payment result to your shopper. You will also receive the outcome of the payment asynchronously in a webhook.

For card payments, you can receive the following resultCode values:

Test and go live

Use our test card numbers to test how your integration handles different 3D Secure authentication scenarios.

See also