{"title":"Redirect 3DS Drop-in integration","category":"default","creationDate":1776961627,"content":"

Our Android Drop-in<\/a> 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 redirects the shopper to perform 3D Secure 2 authentication.<\/p>\n

When adding card payments with redirect 3D Secure authentication to your integration, you additionally need to:<\/p>\n

    \n
  1. Configure Drop-in<\/a> to collect the card holder name.<\/li>\n
  2. Provide the required 3D Secure parameters<\/a> when making a payment request.<\/li>\n
  3. Handle the redirect<\/a> after the shopper returns to your website.<\/li>\n<\/ol>\n
    \n

    This page describes the integration steps for Android Drop-in v4.0.0 or later<\/a>.<\/p>\n<\/div>\n

    Requirements<\/h2>\n

    This page explains how to add cards with redirect 3D Secure 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<\/a>.<\/p>\n

    Before you begin your integration:<\/p>\n

      \n
    1. Make sure that you have set up your back end implementation<\/a>, and added Drop-in to your payment form<\/a>.<\/li>\n
    2. Add the cards that you want to accept in your test Customer Area<\/a>.<\/li>\n
    3. If you are using 3D Secure for PSD2 compliance, read our comprehensive PSD2 SCA guide<\/a>.<\/li>\n<\/ol>\n

      Collect additional parameters in your payment form<\/h2>\n

      For higher authentication rates, we strongly recommend that you collect the shopper's billing address and email address in advance in your payment form. Deliver these parameters to your backend when making a payment<\/a> as they are required by the card schemes.<\/p>\n

      Show the available cards in your payment form<\/h2>\n
      \n

      For information about the supported countries\/regions and currencies for each card, refer to Payment methods<\/a>.<\/p><\/div><\/div>\n\n

      To show cards in your payment form:<\/p>\n

        \n
      1. \n

        Specify in your \/paymentMethods<\/a> request a combination of countryCode<\/a> and amount.currency<\/a>. Drop-in uses this information to show the available cards to your shopper.<\/p>\n<\/li>\n

      2. \n

        <\/a>When creating an instance of Drop-in<\/a>, create a configuration object, and pass your client key<\/a>. To make sure you collect the cardholder name, set holderNameRequired<\/code> to true<\/strong>.<\/p>\n<\/li>\n<\/ol>\n

        val cardConfiguration = CardConfiguration.Builder(context, \"YOUR_CLIENT_KEY\")\n  \/\/ Makes the cardholder name required\n  .setHolderNameRequired(true)\n  \/\/ When you are ready to accept live payments, change the value to one of our live environments.\n  .setEnvironment(Environment.TEST)\n  .build()\n\nval dropInConfiguration = DropInConfiguration.Builder(context, YourDropInService::class.java, \"YOUR_CLIENT_KEY\")\n   \/\/ When you are ready to accept live payments, change the value to one of our live environments.\n   .setEnvironment(Environment.TEST)\n   .addCardConfiguration(cardConfiguration)\n   .build()<\/code><\/pre>\n
        Make a payment<\/h2>\n
        When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod<\/code>.<\/p>\n
          \n
        1. Pass the paymentComponentData.paymentMethod<\/code> object to your server.<\/li>\n
        2. \n
          When you make a payment request<\/a>, include the following additional 3D Secure 2 parameters.<\/p>\n
          \n
          See additional 3D Secure 2 parameters that we recommend to include in your request to increase authentication performance in our API reference<\/a>.<\/p>\n<\/div>\n<\/li>\n<\/ol>\n\n\n\n\n\n\n\n\n\n\n\n\n
          Parameter name<\/th>\nRequired<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
           paymentMethod<\/a><\/td>\n\"Required\"<\/span><\/td>\nThe type and required details for a card payment method. The paymentComponentData.paymentMethod<\/code> object from your client app.<\/td>\n<\/tr>\n
           paymentMethod.holderName<\/a><\/td>\n\"Conditionally<\/span><\/td>\nUse case<\/strong>: required for Visa and JCB transactions. 
           The cardholder's name.<\/td>\n<\/tr>\n
           channel<\/a><\/td>\n\"Required\"<\/span><\/td>\nThe platform where the transaction takes place. Set to Android<\/strong>.<\/td>\n<\/tr>\n
           returnUrl<\/a><\/td>\n\"Required\"<\/span><\/td>\nThe URL where the shopper will be redirected back to after completing 3D Secure authentication. Get this URL from Drop-in in the RedirectComponent.getReturnUrl(context)<\/code>. 
           Format<\/strong>: 
          • Maximum characters: 1024.<\/li>
          • Must not include \/\/<\/code> (double slash) after the top-level domain.<\/li><\/ul><\/td>\n<\/tr>\n
           browserInfo<\/a><\/td>\n\"Required\"<\/span><\/td>\nThe shopper's browser information. The following sub-fields are required: 
           shopperIP<\/a><\/td>\n\"Conditionally<\/span><\/td>\nUse case<\/strong>: required for Visa and JCB transactions. 
           The shopper's IP address.<\/td>\n<\/tr>\n
           shopperEmail<\/a><\/td>\n\"Conditionally<\/span><\/td>\nUse case<\/strong>: required for Visa and JCB transactions. 
           The cardholder's email address. If you do not include the shopper email, you must include the shopper's phone number in your request.<\/td>\n<\/tr>\n
           telephoneNumber<\/a><\/td>\n\"Conditionally<\/span><\/td>\nUse case<\/strong>: required for Visa and JCB transactions if you did not include the shopperEmail<\/code> field. 
          The shopper's phone number. To be more specific, you can use the mobilePhone<\/code>, homePhone<\/code>, and workPhone<\/code> fields in the threeDS2RequestData<\/code> object.  
           Format<\/strong>: The phone number must include a plus sign (+) and a country code (1-3 digits), followed by the number (4-15 digits). 
            Example<\/strong>: +4912345678901<\/strong> 
           If the value you provide does not follow the guidelines, we drop the value and do not submit it for authentication. <\/div><\/div><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
          \"This Required for all transactions. 
          \"This Required for particular setups, or issuers and card schemes. 
          \"This Recommended for all transactions, but not required.<\/p>\n
          \n    <\/code-sample>\n<\/div>\n
            \n
          1. \n
            In the response, check if there is an action<\/code> object.<\/p>\n\n
            \n    
            \n        \n        <\/tabs>\n    <\/div>\n<\/div>\n\n<\/li>\n<\/ol>\n
            Handle the redirect<\/h2>\n
            Drop-in redirects the shopper to perform the 3D Secure authentication. When the shopper returns back to your app, Drop-in provides the actionComponentData<\/code> object.<\/p>\n
              \n
            1. Pass the actionComponentData.details<\/code> to your server.<\/li>\n
            2. \n
              From your server, make a POST  \/payments\/details<\/a> request specifying:<\/p>\n