Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I have received email from Global Payments (Realex) saying that:
Here's what you need to know:
From September 2019, most ecommerce payments will have to undergo Strong Customer Authentication (SCA).
A new authentication protocol is being introduced by the Card Schemes (Mastercard, Visa, etc.) called 3D Secure 2 (3DS v2).
Global Payments will be supporting the 3DS v2 protocol by introducing options that will make it easy for you to comply with the SCA requirement.
What Do I Need to Do?
As you're integrated with our Hosted Payment Page (HPP), there are additional fields that need to be sent in the HPP POST, which will ensure you're compliant with the regulation. When you update your integration to support these additional required fields, we'll seamlessly transition you to 3DS v2, once it's supported, without any further changes being needed.
Please click on the link below to obtain the details of the changes.
What you'll need to do?
We'd recommend that you forward this communication to your web developer and/or shopping cart provider to ensure that they're aware of these required changes.
We've set a deadline of May 2019 for you to make the HPP changes. This supports our recommendation to complete any changes that are required well in advance of the SCA being introduced. Failure to make the changes may affect your ability to process successful transactions.
Integration type Communication of Changes Target Date for changes to be made
Hosted Payment Page On this email May - 2019
Shoping Carts and Platforms Mar - 2019 Jun - 2019
API; Apr - 2019 Jun - 2019
MOTO No action needed No action needed
I have open the same issue on commerce realex today:
https://www.drupal.org/project/commerce_realex/issues/3034651
Comments
Comment #2
brightstorm CreditAttribution: brightstorm as a volunteer commented@adpo I am currently looking into implementing this work as paid consultancy for a client of ours. If you are still looking to do this on your site, let me know.
Comment #3
frost CreditAttribution: frost as a volunteer commentedI'm happy to bounce ideas back and forth with someone on this but can't do the actual coding/debugging since my php is very rusty.
Realex docs recommend a list of additional fields in the XML request (I'm looking at the list of mandatory and recommended fields). Looks like the ones in that list that aren't already being sent are things like customer email, billing and shipping addresses and a few other fields that are readily available from existing data.
In module uc_realex_remote.module, the function uc_realex_remote_charge() builds the XML request. I would guess/hope that the $order object that's being used already has some or all of this additional data already in it.
So I'd say a quick way to try this out (for someone who can do a quick debug and examine the $order object), would be to see what's in the $order object and then update uc_realex_remote_charge() to include the additional fields.
As I said, happy to work with someone if they take the coding lead on this :-)
Comment #5
stella CreditAttribution: stella at Annertech commentedA new alpha2 release was made this morning to add 3DS2 support for Hosted Payment Pages.