Skip to main content

Overview

3D Secure (3DS) is an authentication protocol designed to provide an additional layer of security for online credit and debit card transactions. It helps prevent unauthorized card usage by requiring cardholders to authenticate themselves with their card issuer before completing a transaction. When 3DS is enabled, the cardholder is redirected to their card issuer’s authentication page where they must provide additional verification, typically through OTP (One-Time Password) or biometric authentication.

Integration Steps

Step 1: Enable 3DS in Payment Request

To enable 3DS authentication, include the following parameters in your Payment Intent creation or confirmation request:

Step 2: Handle 3DS Authentication

After creating or confirming the Payment Intent with 3DS enabled:
  1. Check the Payment Intent status in the response
  2. If the status is REQUIRES_CUSTOMER_ACTION, examine the next_action field
  3. If next_action.redirect_iframe.iframe is present, embed the provided iframe URL in your payment page
  4. The iframe will automatically display the 3DS authentication interface for the customer to complete OTP input or other verification methods

Step 3: Handle Post-Authentication

After the payment process is completed (whether successful or failed), the customer is redirected to the return_url specified in the initial request. The redirect URL includes the merchant_order_id and other parameters, as shown in the example below:
Use the merchant_order_id to query the payment status and display the corresponding result to the customer.

API Example

Sample Request

Sample Response (REQUIRES_CUSTOMER_ACTION)

Note: All examples in this guide are for demonstration purposes only and should not be used in production.