Most probably this error happened because either the customer's card issuing bank does NOT support 3DSecure authentication mode at all, or the customer's card does NOT (have active/enrolled in) 3DSecure authentication mode.
In this article you will be going to know about:
- How to investigate the reason that caused this error?
- Reason #1: Customer's card issuing bank does NOT support 3DSecure authentication mode
- Reason #3: Acquirer bank doesn’t allow recurring payment for 3DS cards (Recurring Mode)
How to investigate the reason that caused this error?
You can check the "Response Code" in the transaction screen from the Transactions button in your profile. Also, you can check the 'Response Status' under the "AUTHENTICATION" tab.
Usually, the ECI value for this kind of error will be either 07 or 00
Reason #1: Customer's card issuing bank does NOT support 3DSecure authentication mode
This means that the card issuer (customer bank) does not support 3DS at all, which in this case, you will need to guide your customer to use another card related to another issuing bank.
Reason #2: Customer's Card not enrolled in 3DSecure authentication mode
This means that the card issuer (customer bank) does support the 3DS authentication mode but the customer card is not enrolled yet in this mode. In other words, the feature is deactivated for this card, which in this case, you will need to guide your customer to check with his bank to activate/enroll the 3DSecure authentication mode for his card.
Reason #3: Acquirer bank doesn’t allow recurring payment for 3DS cards (Recurring Mode)
In some rare cases, the customer card is already enrolled in the 3DSecure authentication and already has an authorized transaction with 3DS as well. And you are sure that the customer card has 3DSecure authentication activated (since it has authorized transaction)
Yet the transaction is related to a recurring payment being declined regarding this issue.
In this case, in the first transaction customer already fulfilled the 3DS, but with any next recurring transactions to it (which should be deducted with no need for 3DS) It fails because "3DSecure authentication not available".
Only in this case, you will need to contact us at (customercare@paytabs.com), with the first Auth transaction and the recurring ones transaction references, along with the country your business operates in.