Page MenuHomePhabricator

Solution for 3DS2.0 name field issue which caused Wikimedia to shut off 3Ds on payment page
Closed, ResolvedPublic

Description

We had an issue on September 12 where Ingenico deployed some updated 3DS capabilities, which introduced a second name field on their payments page in addition to our own. This caused Wikimedia to disable 3DS on all sites. We have been working to figure out what we do from here as Ingenico is adamant that they must collect the name as part of PSD2 and 3DS2.0 requirements. See thread entitled:
Re: Name field appearing in hosted checkout, API calls timing out sporadically [ ref:_00D57ri6p._5001iF2T8h:ref

Ingenico has discussed with me the following solution that will allow us to have 3ds enabled on merchant (authenticationindicator=1) while Ingenico not show the cardholdername on the payment page. There will be a way to suppress the field via API, which Wikimedia will control. The sprint to release this functionality is set to go for the end of October 2019 and targeted to be available to Wikimedia by mid November. When the time draws closer for release I would like to organize a call with FRTech and Ingenico to discuss the suppression process and scope the work involved.

Event Timeline

11.14 . A further update on this task is the following:

a) Ingenico will NOT require Wikimedia to do any coding. The work to suppress the second name field is on their side. They intend to deploy this fix on their end during November (date not determined as yet).
b) Unless we reenable 3DS we will not be impacted by the deployment of the change they are making.
c) Before we reenable 3DS in Q3, we will want to test that the name field suppression works as designed. I am therefore leaving this task open.

From Ingenico: "You should test when you enable 3DS again, but until then you won’t be impacted."

Ingenico advises that this change will be deployed mid January 2020 now.

EMartin claimed this task.