UltraCart’s integration with https://www.paay.co/ allows merchants to support 3DS 2.0 / PSD2 requirements.
Apart from meeting the Strong Customer Authentication (SCA) compliance under PSD2, there are numerous benefits to the new 3DS 2.0 protocol, especially from a mobile payments standpoint. The improved design dramatically increases the user experience on mobile devices by being fully compatible with mobile wallet applications and in-app transactions. 3DS 2.0 is user friendly where 3DS 1.0 was not.
Benefits of implementing 3DS 2.0:
With the addition of an SDK component, comprehensive integration with mobile apps is
now possible, allowing merchants to natively integrate 3D Secure into their mobile apps.
Merchants can ensure that the authentication process looks
and feels consistent with the rest of the app
Dramatically increases the user experience on mobile devices, including
non-browser based platforms and mobile integration
Biometric authentication whilst still in the merchant’s app it will
likely just feel like a valid security measure
The merchant’s platform will only require additional authentication if the risk is high –
that will happen in only a small percentage of the transactions
Authentication activity will be invisible to the cardholder
3DS 2.0 brings the promise of machine learning algorithms to better risk assessment. The new algorithms allow for a seamless data exchange across the three domains (merchant/acquirer, issuer, and interoperability). Furthermore, 3DS 2.0 utilizes machine learning and has 10 times more assessment data points than its predecessor, allowing for a more robust risk-based authentication. This means that with 3DS 2.0, repeated purchases online would be marked as low-risk by the merchant and issuing bank, which translates to a faster, easier, and more secure payment.
To learn more, please visit: https://3dsecure2.com/
Your payment gateway must be:
Network Merchants (NMI)
PayPal Payflow Pro
World Pay Corporate (World Pay Business is not allowed to use an external MPI)
Braintree (*Does not support rotating gateways configuration)
You must utilize the StoreFront checkout on a visual builder based theme (Elements, Hero, Lifty, etc.)
Navigate to:
Configuration → Checkout → Payments |
Click on the Settings associated with credit cards as shown below:
Scroll to the bottom of the modal and configure the API Key and Secret Key associated with your Paay.co account:
Close the modal dialog and save.
Open the visual builder for your checkout and edit the settings on the “checkout form” element as shown below:
You can configure:
whether or not to perform 3DS on the transaction
whether to challenge the customer or not
the other elements involved in challenging the customer (modal and panel)
the maximum amount of upsell revenue (UltraCart will calculate the theoretical max amount if the customer accepts all the upsells associated with the items in the cart, but this field gives you the ability to cap that number so it doesn’t get out of control high)
whether to pull a second authorization that is used to protect the first rebill
Since the integration with Paay.co is new, theme releases have not occurred with the modal baked into them. The following CJSON file will provide the necessary modal. Once you add this modal underneath your checkout form element, make sure to pick the proper modal and panel elements.
If you are choosing to never challenge the customer (challenge indicator = No challenge requested) then these elements are not necessary.
You can adjust the columns that are displayed and the order to include a new column named “3DS Status”. Please see View Orders → Row & Column Orders for more information on how to adjust the columns.
When you view an individual order, all of the 3DS fields will be displayed below the order if the order transacted with 3DS. Below is a sample screenshot of the display:
If you view the transaction history associated with an order, the transaction response will contain all of the 3DS fields.
If you run the Rotating Transaction Gateway History report, you can select 3DS = Yes to filter to only 3DS transactions.
In the Excel spreadsheet there will be a column labeled 3DS Status which will contain the overall 3DS status value as well as additional columns for the other 3DS related values.
A) The expiration date on the 3DS information retrieved during the original checkout expires after 45 days.
A) UltraCart has to add support for individual gateways one by one. If your gateway is capable of supporting an external MPI, we can consider adding support for it.
Q) Do you have a point of contact for Paay.co? Yes, for more information about Paay.co, please contact Josh Cohen at josh@paay.co