#Hakan de Chargemap-3DS

1 messages ยท Page 1 of 1 (latest)

azure geyserBOT
hushed scaffold
#

Hakan de Chargemap-3DS

#

Hi ๐Ÿ‘‹ 3DS issues can be tricky to track down because we provide the frame/popup for those flows, but the issuing bank provides the content that gets displayed in those. Do you have more details on when the error that your customers are seeing is encountered?

lone yoke
#

Yeah sure, I asked my colleague and he sent me the error displayed to the user. It's in french so I might have to translate it ๐Ÿ˜„

#

Btw, event id : evt_3LutgxFigtNEoosZ0P9UdKVE

#

The user has the following message: "Nous n'arrivons pas ร  authentifier votre moyen de paiement", that means "We cannot authenticate your payment mean" or something like that

#

Sorry if that doesn't help much

#

it's all I got

hushed scaffold
#

Hm, the event you shared is showing that the authentication failed, rather than the authentication flow not being able to be completed, which seems to align with the error message.

#

Has the customer tried contacting their bank to see why the authentication failed?

lone yoke
#

Nope, will ask him to do so and get back at you.

#

For me there's clearly something fishy with his bank, because I just tried and with my credit card 3DS works like a charm.

#

So no need to upgrade our libraries I guess ? At least, it seems that it won't help in this case.

hushed scaffold
#

Yeah, as far as I know there isn't a need to upgrade. The frontend code that handles that comes from stripe.js, so you would always get the newest version of those flows when our scripts get imported to your site.

lone yoke
#

yup, that's what I thought. We contacted the user so he can ask his bank why they deny this authentication. Thanks toby, as always Stripe customer support is killing it.