Search

Are you looking for test card numbers?

Would you like to contact support?

Online-payment icon

Native 3DS2 Drop-in integration

Add native 3D Secure 2 authentication to your existing Drop-in integration.

Our Android Drop-in renders the available cards in your payment form, and securely collects any sensitive card information, so it doesn't touch your server. Drop-in also handles the 3D Secure 2 device fingerprinting and challenge flows, including the data exchange between your front end and the issuer's Access Control Server (ACS).

When adding 3D Secure 2 authentication to your integration, you also need to:

  1. Configure Drop-in to collect the card holder name.
  2. Provide additional parameters when making a payment request.
  3. Submit authentication results if you receive an action object in response to your /payments or /payments/details request. In case of a 3D Secure 1 fallback, you also need to check the payment result.

This page describes the integration steps for v3.0.0 or later of Android Drop-in. If you are using an earlier version, refer to an earlier version of this integration guide.

Before you begin

This page explains how to add cards with native 3D Secure 2 authentication to your existing Android Drop-in integration. The Android Drop-in integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Drop-in integration guide.

Before you begin your integration:

  1. Make sure that you have set up your back end implementation, and added Drop-in to your payment form.
  2. Add the cards that you want to accept in your test Customer Area.

Show the available cards in your payment form

For information about the supported countries and currencies for each card, refer to Payment methods.

To show cards in your payment form:

  1. Specify in your /paymentMethods request a combination of countryCode and amount.currency. Drop-in uses this information to show the available cards to your shopper.

  2. When creating an instance of Drop-in, create a configuration object:

    a. Set holderNameRequire to true. This will show the input field for the card holder name.

    For higher authentication rates, we strongly recommend that you collect the card holder name for payments with 3D Secure authentication.

    b. Pass your Client Encryption Public Key.

    To get your Client Encryption Public Key:

    1. Sign in to your Customer Area using your company-level account.
    2. Navigate to Account > Users.
    3. Click on your web service user (ws@Company.[YourCompanyAccount]) in the users list.
      This opens the Edit Web Service User page.
    4. In the Client-Side Encryption panel, copy the Client Encryption Public Key.
    val cardConfiguration = CardConfiguration.Builder(context, "<publicKey>")
         .setHolderNameRequire (true)
            .build()
    
    val dropInConfiguration = DropInConfiguration.Builder(this@MainActivity, YourDropInService::class.java)
           .setEnvironment(Environment.TEST)
           // When you're ready to accept live payments, change the value to one of our live environments.
           .addCardConfiguration(cardConfiguration)
           .build()

Make a payment

When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod.

  1. Pass the paymentComponentData to your server.
  2. From your server, make a /payments request, specifying:
    • paymentMethod: The paymentComponentData.paymentMethod from your client app.
    • additionalData.allow3DS2true.
    • channel: Android
    • shopperIP: The shopper's IP address.
    • returnURL: In case of a 3D Secure 1 fallback, this is the URL where the shopper will be redirected back to after completing 3D Secure 1 authentication. Get this URL from Drop-in in the RedirectComponent.getReturnUrl(context).

To increase the likelihood of achieving a frictionless flow and higher authorisation rates, we also recommend that you send additional parameters in this list.

   curl https://checkout-test.adyen.com/v51/payments \
   -H "X-API-key: [Your API Key here]" \
   -H "Content-Type: application/json" \
   -d '{
      "amount":{
         "currency":"EUR",
         "value":1000
      },
      "reference":"YOUR_ORDER_NUMBER",
      "shopperReference":"YOUR_UNIQUE_SHOPPER_ID",
      "{hint:paymentComponentData.paymentMethod from app}paymentMethod{/hint}":{
         "type":"scheme",
         "encryptedCardNumber":"adyenjs_0_1_18$k7s65M5V0KdPxTErhBIPoMPI8HlC..",
         "encryptedExpiryMonth":"adyenjs_0_1_18$p2OZxW2XmwAA8C1Avxm3G9UB6e4..",
         "encryptedExpiryYear":"adyenjs_0_1_18$CkCOLYZsdqpxGjrALWHj3QoGHqe+..",
         "encryptedSecurityCode":"adyenjs_0_1_24$XUyMJyHebrra/TpSda9fha978+..",
         "holderName":"S. Hopper"
      },
      "additionalData":{
         "allow3DS2":true
      },
      "storePaymentMethod":true,
      "shopperIP":"192.0.2.1",
      "channel":"Android",
      "returnUrl":"adyencheckout://your.package.name",
      "merchantAccount":"YOUR_MERCHANT_ACCOUNT"
   }'

Your next steps depend on whether the /payments response contains an action object, and on the action.type:

If you receive an action object, store the action.paymentData on your server - you'll need this when making a /payments/details request later.

action.type Description Next steps
No action object The transaction was either exempted or out-of-scope for 3D Secure 2 authentication. 1. Return CallResult with ResultType FINISHED, and the resultCode from the /payments response.
2. Use the resultCode to present the payment result to your shopper.
threeDS2Fingerprint The payment qualifies for 3D Secure 2, and will go through either the frictionless or the challenge flow. 1. Return CallResult with ResultType ACTION and the action object.
2. Proceed to the next section to Submit authentication results.
redirect We will initiate a 3D Secure 1 fallback, because the issuer does not support 3D Secure 2.
1. Return CallResult with ResultType ACTION and the action object.
2. Check the payment result.

The following example shows a /payments response with action.type: threeDS2Fingerprint

{
  "resultCode":"IdentifyShopper",
  "action":{
    "{hint: Store this on your server.}paymentData{/hint}":"Ab02b4c0!BQABAgCuZFJrQOjSsl\/zt+...",
    "paymentMethodType":"scheme",
    "token":"eyJ0aHJlZURTTWV0aG9kTm90aWZpY...",
    "type":"threeDS2Fingerprint"
  },
  "authentication":{
    "threeds2.fingerprintToken":"eyJ0aHJlZURTTWV0aG9kTm90aWZpY..."
  },
  ...
}

Submit authentication results

If the CallResult.ResultType is ACTION, Drop-in performs the makeDetailsCall method, and then provides the actionComponentData.

  1. Pass the actionComponentData.details to your server.
  2. From your server, make a /payments/details request, specifying:
    • paymentData: The paymentData from the response to your last API request (either to the /payments, or the /payments/details endpoint.)
    • details: The actionComponentData.details from Drop-in.
{
        "{hint:value that you stored on your server}paymentData{/hint}":"Ab02b4c0!BQABAgCuZFJrQOjSsl\/zt+...",
        "{hint:actionComponentData.details from app}details{/hint}":{
           "threeds2.fingerprint": "eyJ0aHJlZURTQ29tcEluZCI6ICJZIn0="
        }
}

Your next steps depend on whether the /payments response contains an action object:

If you receive an action object, store the action.paymentData on your server - you'll need this when making a /payments/details request later.

action.type Description Next steps
No action object The 3D Secure 2 authentication process has been completed. 1. Return CallResult with ResultType FINISHED and the resultCode from the /payments/details response.
2. Use the resultCode to present the payment result to your shopper.
threeDS2Challenge The payment needs to go through a 3D Secure challenge flow. 1. Return CallResult with ResultType ACTION and the action object.
2. Perform the step of submitting authentication results again.

Present 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 notification webhook.

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

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful.
If you are using manual capture, you also need to capture the payment.
Cancelled The shopper cancelled the payment. Ask the shopper whether they want to continue with the order, or request that they select a different payment method.
Error There was an error when the payment was being processed. For more information, check the refusalReason field. Inform the shopper that there was an error processing their payment.
Refused The payment was refused. For more information, check the refusalReason field. Ask the shopper to try the payment again using a different payment method.

Test and go live

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

See also