Enabling 3-D Secure version 2

TRU Connect - Payment Pages

Contact our Support Team to discuss configuring your site reference(s) to support EMV 3-D Secure version 2.

TRU Connect - JavaScript Library
  • If you are using version 3 of our JavaScript Library, your solution already supports EMV 3-D Secure version 2. You will need to contact our Support Team to enable EMV 3-D Secure version 2 and ensure that the “THREEDQUERY” request is submitted in the JWT payload, in order for EMV 3-D Secure version 2 to be performed on a given transaction.


  • If you are using version 2 of our JavaScript Library, your solution already supports EMV 3-D Secure version 2. You will need to contact our Support Team to enable EMV 3-D Secure version 2, which will then be attempted for every transaction providing your acquiring bank supports this (no additional steps are needed).

      As of 1st December 2021, the Trust Payments JavaScript Library (st.js) for version 2 will be sunset and will no longer be officially supported.
    Click here to open our migration document in a new tab.


  • If you are using version 1 of our JavaScript Library, you will need to contact our Support Team to enable EMV 3-D Secure version 2, and then migrate to JavaScript Library version 3.

      As of 1st December 2021, the Trust Payments JavaScript Library (st.js) for version 1 will be sunset and will no longer be officially supported.
    Click here to open our migration document in a new tab.

TRU Connect - Webservices API

If you are processing payments using our Webservices API, the following migration routes are available to you:

  • Recommended: You can continue to use the Webservices API to process the payment authorisation, while using our JavaScript Library to process the EMV 3-D Secure version 2 authentication.
    Click here to get started.
  • Migrate to JavaScript Library: You can embed our JavaScript Library within your checkout page and we will automatically perform the EMV 3-D Secure version 2 authentication and process the payment.
    Click here to get started.
  • Using your own MPI: If you are already using your own MPI to process 3-D Secure v1.x transactions, you would need to ensure your own MPI provider provides EMV 3-D Secure v2.x support. Please refer to our latest documentation to ensure your system is submitting the required fields for EMV 3-D Secure v2.x.
  • Migrate to hosted Payment Pages: Alternatively, you may prefer to migrate to our hosted Payment Pages solution. The customer is redirected to our hosted checkout, and we will handle the entire payment session, including prompting the customer for their billing and delivery details, their card details and then processing a EMV 3-D Secure-authenticated payment, before redirecting the customer's browser back to your website. Because no sensitive payment credentials are entered on your servers, this can streamline the PCI accreditation process.
    Click here to learn more.
TRU Mobile
  • If you are using our Mobile SDK, your solution already supports EMV 3-D Secure version 2. You will need to contact our Support Team to enable EMV 3-D Secure version 2 and ensure that the “THREEDQUERY” request is submitted in the JWT payload, in order for EMV 3-D Secure version 2 to be performed on a given transaction.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request