EMV 3DS is enabled on Payment Pages for all merchants by default and your account can be configured to manage the entire process for you. You will first need to contact our Support Team and ensure your account has been configured to automatically retry payments with 3DS authentication when a soft decline response is returned. Following this, there should be no further steps needed in order to support EMV 3DS on your Payment Pages solution.
-
If you are using version 3 of our JavaScript Library, your solution already supports EMV 3DS. You will need to contact our Support Team to enable EMV 3DS and ensure that the “THREEDQUERY” request is submitted in the JWT payload.
-
If you are using version 2 of our JavaScript Library, your solution already supports EMV 3DS. You will need to contact our Support Team to enable EMV 3DS, 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 was sunset and is no longer 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 3DS, and then migrate to JavaScript Library version 3.
As of 1st December 2021, the Trust Payments JavaScript Library (st.js) for version 1 was sunset and is no longer officially supported.
Click here to open our migration document in a new tab.
If you are processing payments using our Webservices API, EMV 3DS can be implemented using one of the following methods:
-
Recommended: You can continue to use the Webservices API to process the payment authorisation, while using our JavaScript Library to process the EMV 3DS authentication.
Click here to get started. -
Use Trust Payments 3DS API
You can utilise our 3DS API to process the EMV 3DS authentication independently of the subsequent transaction (additional fees apply - please contact your account manager before deploying this solution). Click here to learn more. -
Use a third party MPI for EMV 3DS authentication
Alternatively, you can use an external MPI to process the EMV 3DS authentication and include the authentication data in authorisation requests to our Webservices API. Click here to learn more. -
Migrate to JavaScript Library completely: Instead of using our Webservices API, you can embed our JavaScript Library within your checkout page and we will automatically perform the EMV 3DS authentication and process the payment.
Click here to get started. -
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.
- If you are using one of our Mobile SDKs, your solution already supports EMV 3DS. You will need to contact our Support Team to enable EMV 3DS and ensure that the “THREEDQUERY” request is submitted in the JWT payload.
