> ## Documentation Index
> Fetch the complete documentation index at: https://developers.ligdicash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 3D Secure

> 3D Secure is mandatory for every Visa card payment via LigdiCash — what it is, how it works, and what to do if it fails.

3D Secure (3DS) is a strong authentication protocol enforced by card networks for online payments. LigdiCash applies it **mandatorily** on all Visa card payments.

## Why 3DS is mandatory

3D Secure protects both the cardholder and the merchant against fraud. LigdiCash cannot accept a card payment without this authentication layer. If the customer's card does not have 3DS enabled, **the transaction will be declined** — regardless of the validity of the card number, expiration date, or CVV.

<Warning>
  The card must have **3D Secure enabled with the issuing bank** before it can be used. If a customer encounters a failure, the first cause to check is whether 3DS is enabled on their card.
</Warning>

## How to enable 3DS on a card

Enabling 3D Secure is the cardholder's responsibility, not the merchant's. The customer must contact their bank to:

1. Check that their card supports 3D Secure.
2. Enable the option if it is not already active (sometimes via the banking app, sometimes by request at the branch).
3. Make sure their phone number registered with the bank is up to date (to receive SMS validation codes).

## What the customer experiences during the 3DS flow

After entering their card details on the LigdiCash page:

<Steps>
  <Step title="3DS triggered">
    LigdiCash submits the transaction to the Visa network, which triggers the 3DS process with the card's issuing bank.
  </Step>

  <Step title="Bank authentication">
    The customer is redirected to their bank's authentication page. Depending on the bank, this authentication can take several forms:

    * SMS code
    * Mobile banking app validation
    * Email code
    * Pre-registered security question
  </Step>

  <Step title="Return to LigdiCash">
    After successful validation, the customer automatically returns to the LigdiCash page, which finalizes the transaction.
  </Step>

  <Step title="Return to your site">
    The customer is redirected to your `return_url` or `cancel_url` based on the outcome.
  </Step>
</Steps>

## What to do if 3DS fails

If a customer reports a card payment failure, here are the most common causes and the actions to recommend:

| Likely cause                    | Recommended action for the customer                               |
| ------------------------------- | ----------------------------------------------------------------- |
| 3DS not enabled on the card     | Contact their bank to enable 3DS                                  |
| SMS code not received           | Check the number registered with the bank, request the code again |
| Authentication timeout exceeded | Restart the payment from the beginning                            |
| Card not supported by LigdiCash | Try with another Visa card with 3DS enabled                       |
| Online payment limit reached    | Contact their bank to raise the limit                             |

<Note>
  As a merchant, you do not have direct visibility into the reason for a 3DS failure. The customer must resolve the issue with their bank. Your role is to offer them the option to retry or switch to another payment method (mobile money, for example).
</Note>

## Merchant side — no action required

Triggering and handling 3DS is fully managed by LigdiCash. You do not have to integrate a 3DS SDK, handle bank redirects, or modify your existing code. A Visa payment declined due to 3DS reaches you with a `status` of `notcompleted` in the `confirm` response and in the callback.

## Related pages

* [Visa payment flow](/en/payment-api/visa-cards/payment-flow) — the full flow walkthrough
* [Activate Visa on your project](/en/payment-api/visa-cards/activation) — contractual activation conditions
* [Verify the status](/en/payment-api/hosted-payin/verify-status) — reading `status` after a payment