Introduction to 3DS

October 11, 2024

Introduction

For the security of your merchant, the Kushki fraud prevention team will request you to activate the 3DS authentication when receiving card payments.

By having the 3DS authentication service active, your customers will be requested to complete an extra verification step (from now on, challenge) with the card issuer to complete certain transactions. This challenge usually consists of an OTP sent by the bank to your customer’s e-mail address or telephone number.

3DS Validation Availability

Check below for the availability of 3DS validation with the affiliation and integration models available in Kushki.

By affiliation models

3DS validation is available when processing transactions with the following card brands:

Aggregation

Credit and debit cards

Acquiring

Credit and debit cards

Availability by integration method

3DS validation is available in the following integration methods:

• Integration with Magento
• Prestashop integration
• WooCommerce integration
• Integration with VTEX
• Shopify integration
• Adobe Commerce Integration
• Smartlink Integration
• Kajita Integration
• Android Integration (SDK)
• iOS Integration (SDK)
• Payment button integration
• Kushki.js integration
• Kushki.js Hosted Fields integration
• API Integration

How does the 3DS authentication work?

Once the user fills out the form and clicks on the Pay button, Kushki will validate if 3DS authentication is required for the transaction. If this validation is required, your customer will be displayed a challenge whose experience may vary depending on the brand and the issuing bank. When your customer completes the challenge, they will be able to finalize the transaction.

The 3DS authentication flow with Kushki is shown below:

This is what a payment with 3DS authentication will look like: