X-Payments:3D-Secure settings - Revision history

Dohtur at 22:18, 31 January 2022

2022-01-31T22:18:14Z

Dohtur at 22:13, 31 January 2022

2022-01-31T22:13:52Z

Dohtur at 22:02, 31 January 2022

2022-01-31T22:02:47Z

Dohtur at 19:39, 15 December 2019

2019-12-15T19:39:21Z

Dohtur at 10:09, 30 March 2017

2017-03-30T10:09:07Z

Dohtur at 10:04, 30 March 2017

2017-03-30T10:04:18Z

Dohtur at 09:54, 30 March 2017

2017-03-30T09:54:43Z

Dohtur at 09:51, 30 March 2017

2017-03-30T09:51:22Z

Dohtur at 09:50, 30 March 2017

2017-03-30T09:50:30Z

Dohtur at 10:35, 10 August 2016

2016-08-10T10:35:13Z

@@ Line 12: / Line 12: @@
 * Global Payments (formerly Realex);
 * Opayo Direct (formerly Sage Pay Go - Direct Interface);
 * Worldpay Corporate Gateway - Direct Model. <br />
 For many other payment solutions it is possible to use the 3-D Secure authentication solution by CardinalCommerce (X-Payments provides an integrated module for this purpose). Solutions that can be used with 3-D Secure authentication by CardinalCommerce include:

@@ Line 5: / Line 5: @@
 Some payment solutions supported by X-Payments provide their own built-in integrated 3-D Secure authentication systems that can be used with X-Payments. Such solutions include:
 * PayPal's Payflow Pro;
 * Cardinal Commerce Centinel;
 * Elavon (Realex API);

@@ Line 10: / Line 10: @@
 * Global Iris/HSBC - RealAuth Remote;
 * Global Payments (formerly Realex);
-* Sage Pay Go - Direct Interface;
+* Opayo Direct (formerly Sage Pay Go - Direct Interface);
 * Worldpay Corporate Gateway - Direct Model. <br />
 For many other payment solutions it is possible to use the 3-D Secure authentication solution by CardinalCommerce (X-Payments provides an integrated module for this purpose). Solutions that can be used with 3-D Secure authentication by CardinalCommerce include:

@@ Line 6: / Line 6: @@
 * PayPal's Payflow Pro;
 * Cardinal Commerce Centinel;
-* Elavon Payment Gateway;
+* Elavon (Realex API);
 * Global Iris/HSBC - RealAuth Remote;
-* Realex;
+* Global Payments (formerly Realex);
 * Sage Pay Go - Direct Interface;
 * Worldpay Corporate Gateway - Direct Model. <br />
 For many other payment solutions it is possible to use the 3-D Secure authentication solution by CardinalCommerce (X-Payments provides an integrated module for this purpose). Solutions that can be used with 3-D Secure authentication by CardinalCommerce include:
-* PayPal Payments Pro;
+* PayPal Payments Pro,
-* Authorize.Net AIM, AIM XML and CIM;
+* Authorize.Net,
-* Bean Stream, a Digital River Company/FirstData Canada;
+* Bambora (Beanstream),
-* Caledon;
+* Beanstream (legacy API),
-* CyberSource - SOAP toolkit API;
+* Blue Pay Canada (formerly Caledon),
-* DIBS;
+* Chase Paymentech Orbital,
-* Digital River World Payments / Beanstream;
+* CyberSource - SOAP toolkit API,
-* ECHO NVP;
+* DIBS,
-* eSELECTplus;
+* ECHO NVP,
-* HeidelPay;
+* eSELECTplus,
-* Netbilling - Direct Mode 3.1;
+* HeidelPay,
 * PSiGate XML API;
 * USA ePay - Transaction Gateway API;
 * WebXpress.
-(More up-to-date information on the type of 3-D Secure system supported by specific payment gateways integrated with X-Payments can be found in the [[X-Payments:Supported_payment_gateways|X-Payments:Supported payment gateways]] table.)
+(Since the list of payment gateway integrations supported by X-Payments tends to change with time, we recommend to check with the document [[X-Payments:Supported_payment_gateways|X-Payments:Supported payment gateways]] for information on the type of 3-D Secure system supported by specific payment integrations as it may be more up-to-date than the list above.)
 When a customer pays using a payment method with 3-D Secure enabled, in addition to providing their card details they also have to go through an additional authentication step validating that they are actually the cardholder. Depending on the bank and the payment method used, the process will have slight variations. For example, here's what we get in a demo X-Cart 5 store using X-Payments 3.0.x when attempting to pay using a 3-D Secure enabled payment method:

@@ Line 33: / Line 33: @@
 :[[File:xp3_3dsecure_form.png|border]]
 On this page, we have to submit a password to continue with our payment.
-<br />
+<br /><br />
-Please note that using 3-D Secure requires cardholder data to be stored temporarily by X-Payments. No worries about that - cardholder data is only needed while the transaction is in progress. X-Payments will not store CHD longer than is necessary and will remove the stored CHD for the transactions that have been finalized as often as every few minutes.
+'''Important''': Please be aware that using 3-D Secure requires cardholder data to be stored temporarily by X-Payments. No worries about that - cardholder data is only needed while the transaction is in progress. X-Payments will not store CHD longer than is necessary and will remove the stored CHD for the transactions that have been finalized as often as every few minutes.
 So, before you start using 3-D Secure payer authentication with X-Payments, make sure that storage of cardholder data has been enabled in the [[X-Payments:General_settings|General_settings]] section (Settings -> General settings). Also ensure that [[X-Payments:Encryption_keys|cardholder data encryption keys]] have been properly generated.

@@ Line 28: / Line 28: @@
 (More up-to-date information on the type of 3-D Secure system supported by specific payment gateways integrated with X-Payments can be found in the [[X-Payments:Supported_payment_gateways|X-Payments:Supported payment gateways]] table.)
-When a customer pays using a payment method with 3-D Secure enabled, in addition to providing their card details they also have to go through an additional authentication step validating that they are actually the cardholder. Depending on the bank and the payment method used, the process will have slight variations. For example, in a demo X-Cart 5 store using X-Payments 3.0.x, while paying with a VISA card via Authorize.Net with 3-D Secure enabled, we get redirected to the bank page for 3-D Secure payer authentication:
+When a customer pays using a payment method with 3-D Secure enabled, in addition to providing their card details they also have to go through an additional authentication step validating that they are actually the cardholder. Depending on the bank and the payment method used, the process will have slight variations. For example, here's what we get in a demo X-Cart 5 store using X-Payments 3.0.x when attempting to pay using a 3-D Secure enabled payment method:
 :[[File:xp3_3dsecure_redirect2bank.png|border]]
-where we see the following form:
+Once we are redirected, we get a page for user authentication like the following:
 :[[File:xp3_3dsecure_form.png|border]]
 <br />
 Please note that using 3-D Secure requires cardholder data to be stored temporarily by X-Payments. No worries about that - cardholder data is only needed while the transaction is in progress. X-Payments will not store CHD longer than is necessary and will remove the stored CHD for the transactions that have been finalized as often as every few minutes.

@@ Line 32: / Line 32: @@
 For payment gateways providing native (built-in) 3-D Secure, no further steps to configure 3-D Secure in X-Payments need to be taken: everything should work automatically as soon as you have properly configured the settings required for 3-D Secure in your account with the respective payment processing provider. To use 3-D Secure payer authentication solution by CardinalCommerce you will, however,  need to sign up for the respective service with CardinalCommerce (CardinalCommerce can be contacted at xpayments@cardinalcommerce.com) and implement some further 3-D Secure related configuration in X-Payments. For instructions, see the appropriate section below:
-:* [[#Managing your 3-D Secure system configuration in X-Payments 2.1|Managing your 3-D Secure system configuration in X-Payments 2.1 or later]]
+:* [[#Managing your 3-D Secure system configuration in X-Payments 2.1 or later|Managing your 3-D Secure system configuration in X-Payments 2.1 or later]]
 :* [[#Managing your 3-D Secure system configuration in X-Payments 1.0 or 2.0|Managing your 3-D Secure system configuration in X-Payments 1.0 or X-Payments 2.0]]
 Once you have everything configured to start using 3-D Secure, it is a good idea to run a couple of test transactions to make sure it works as expected. To run transactions through 3-D Secure in test mode, some preparation will be needed: