Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3D secure challenge handling #2

Open
alexr8 opened this issue Apr 12, 2024 · 2 comments
Open

3D secure challenge handling #2

alexr8 opened this issue Apr 12, 2024 · 2 comments

Comments

@alexr8
Copy link

alexr8 commented Apr 12, 2024

Hi guys, first just want to say this plugin has been a lifesaver with the recent switching off of sagepay urls. One issue i seem to be running into, is sporadically customers getting a 'request timeout' issue.

The checkout page is loaded, with the opayo gateway set on the cart, and the form is output. When the customer inputs their card info and hits submit, sometimes it will output 'Request Timeout' error. Other times transactions will process just fine.

image

I've been chatting to support at Opayo and they had the following information to share:

As discussed on the phone call, the transactions are submitted correctly, but whenever a challenge (i.e. request for additional verification) is issued during the 3D-Secure authentication process, your shopper is not redirected to complete that step, until the payment session eventually times out and the transaction is cancelled.

Our escalations team advised that "we can see in the logs that we're sending the instruction to the vendor to redirect the customer to the ACSURL and the onus is on you to then do this, following our protocol guide." 

So far, we've successfully experienced the 3D-Secure behaviour from the Opayo plugin with American Express (my client says he has but i've not seen it first hand), but it doesnt seem to be triggered for Mastercard (and maybe visa but unsure).

Sometimes Mastercard transactions go through fine - and my guess is these are instances where the banks do not request any 3D-Secure info, but will occasionally fail with the above error - and my hunch is that its whenever a 3D secure event is trying to be triggered from either specific card providers, or specific banks (unsure which at this point).

Wondered if you might have experienced similar or have any ideas where in the chain its failing?

Thanks

Alex

@alexr8
Copy link
Author

alexr8 commented Apr 29, 2024

Hi, I wondered if you might be able to shed any light on the above and if there's anyway I can explore/debug from my side?

@samuelbirch
Copy link
Member

Hi @alexr8, sorry for the delay, we'll be getting someone looking at it fairly soon.

If you have any replication steps in testmode using the example creditcard numbers, that would be very helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants