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.
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:
Important
Keep in mind that, due to our risk policies, the available payment methods and the integration type may vary once you complete the affiliation. We will tell you how to proceed in case this process applies to your merchant.
This is what a payment with 3DS authentication will look like:
100% API integration
If you are a PCI-certified merchant or PSP, you will be able to authenticate your one-time card payments with 3DS by consuming our API.
Integration via Kushki.js
Use this option if you have implemented or plan to implement kushki.js in your front-end and want to authenticate your transactions with 3DS.
