{"title":"Redirect 3DS API-only integration","category":"default","creationDate":1567783140,"content":"
\n

\"\"  Postman collection<\/a><\/p>

Implementation examples<\/strong>
\"\"  Node.js<\/a><\/p>\n  \n  \n\n <\/div><\/div>\n\n

Use our APIs to accept cards with 3D Secure authentication through a redirect page. When adding card payments with redirect 3D Secure authentication to your integration, you additionally need to:<\/p>\n

    \n
  1. Collect the additional parameters in your payment form<\/a>.<\/li>\n
  2. Provide the required 3D Secure parameters<\/a> when making a payment request.<\/li>\n
  3. Handle the redirect<\/a>.<\/li>\n<\/ol>\n

    Requirements<\/h2>\n

    Before starting your integration:<\/p>\n

      \n
    1. If building a mobile integration, contact our Support Team<\/a> to make sure that 3D Secure is triggered in your app.<\/li>\n
    2. Make sure that you have integrated our Card Component for Web<\/a>, iOS<\/a>, or Android<\/a> or built your own UI<\/a> for collecting shopper's card details.<\/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 card holder name, the shopper 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

      Collect card holder name in your payment form<\/h3>\n

      You can use our Card Component<\/a> to build your payment form for 3D Secure 2 authentication. Select the channel that you are using below:<\/p>\n\n

      \n
      \n \n <\/tabs>\n <\/div>\n<\/div>\n\n

      Make a payment<\/h2>\n

      Select the channel that you are using below:<\/p>\n\n

      \n
      \n \n <\/tabs>\n <\/div>\n<\/div>\n\n<\/li>\n<\/ol>\n

      Present the payment result<\/h2>\n

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

      <\/p>\n

      For card payments, you can receive the following resultCode<\/code> values:<\/p>\n\n\n\n\n\n\n\n\n
      resultCode<\/th>\nDescription<\/th>\nAction to take<\/th>\n<\/tr>\n<\/thead>\n
      Authorised<\/strong><\/td>\nThe payment was successful.<\/td>\nInform the shopper that the payment has been successful.
      If you are using manual capture<\/a>, you also need to capture<\/a> the payment.<\/td>\n<\/tr>\n
      Cancelled<\/strong><\/td>\nThe shopper cancelled the payment.<\/td>\nAsk the shopper if they want to continue with the order, or ask them to select a different payment method.<\/td>\n<\/tr>\n
      Error<\/strong><\/td>\nThere was an error when the payment was being processed. For more information, check the \n refusalReason<\/code>\n<\/a> field.<\/td>\nInform the shopper that there was an error processing their payment.<\/td>\n<\/tr>\n
      Refused<\/strong><\/td>\nThe payment was refused. For more information, check the \n refusalReason<\/code>\n<\/a> field.<\/td>\nAsk the shopper to try the payment again using a different payment method.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Test and go live<\/h2>\n

      Use our test card numbers to test how your integration handles different 3D Secure authentication scenarios<\/a>.<\/p>\n

      When you are ready to go live<\/a>, follow our go-live checklist<\/a>.<\/p>\n

      When using our live endpoints<\/a>, make sure that all API requests you make for the same payment session use the same live endpoint region. Using different regions for \/payments<\/a> and \/payments\/details<\/a> requests may result in errors when authenticating with 3D Secure.<\/p>\n

      See also<\/h2>\n