3D Secure 2.0 explained
What customers experience, why liability shift matters, and how version 2 differs from the one you remember.
Where the plugin records decline reasons, and what information the bank needs from you to trace a failure.
Failed transactions, in test or live mode, are unsettling. The plugin gives you the information you need to work out what went wrong rather than leaving you guessing.
The customer gets a deliberately generic message: their order cannot be processed because the originating bank or merchant declined the transaction, and they should try again. This is intentional. Detailed decline reasons are never shown to cardholders, because they can be used to probe stolen card details.
On the back end, the order is marked Failed. The plugin writes the reason for the failure into the order notes, so open the order and scroll to the notes panel on the right.
The note contains the full error response from the gateway, including:
Most failures fall into a small number of causes: a currency mismatch, an expired or insufficient card, a failed 3D Secure challenge, or credentials that have not been fully activated by the bank.
If the note does not make the cause obvious, send the error code, error message and last four digits to your Scotiabank representative. Those three pieces of information are what the bank needs to trace the transaction on their side. Do not send the full card number, and never ask the customer for it.
Still stuck? Professional and Premium licence holders get priority support, answered from Trinidad and Tobago.
Contact support