Skip to main content

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 (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.
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.

​
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:
1

3DS triggered

LigdiCash submits the transaction to the Visa network, which triggers the 3DS process with the card’s issuing bank.
2

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
3

Return to LigdiCash

After successful validation, the customer automatically returns to the LigdiCash page, which finalizes the transaction.
4

Return to your site

The customer is redirected to your return_url or cancel_url based on the outcome.

​
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 causeRecommended action for the customer
3DS not enabled on the cardContact their bank to enable 3DS
SMS code not receivedCheck the number registered with the bank, request the code again
Authentication timeout exceededRestart the payment from the beginning
Card not supported by LigdiCashTry with another Visa card with 3DS enabled
Online payment limit reachedContact their bank to raise the limit
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).

​
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.