You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Did you search for similar issues before submitting this one? Yes
Describe the issue you encountered: I attempted to purchase an item from www.currys.co.uk today as was continually receiving an error (a generic technical error from the bank site) during the 3D secure part of the payment process (when the site redirect to the bank website to ask for further details, such as a password). Even after disabling global shield options for ad blocking, 3rd party cookie blocking and HTTPS Everywhere, the problem persisted.
I was able to put through the payment in Google Chrome immediately afterwards without any issue.
Expected behavior: I should be able to proceed with payment without any errors at the 3D secure stage.
Platform (Win7, 8, 10? macOS? Linux distro?): Tested on Linux (Ubuntu 16.04)
I'm going to close this in favor of #1268 and #4594.
I personally think that some indicator that the 3rd party cookie is blocked and suggests enabling it (which is not always bad in terms of privacy) might fix the issue should be implemented 🤔
Did you search for similar issues before submitting this one? Yes
Describe the issue you encountered: I attempted to purchase an item from www.currys.co.uk today as was continually receiving an error (a generic technical error from the bank site) during the 3D secure part of the payment process (when the site redirect to the bank website to ask for further details, such as a password). Even after disabling global shield options for ad blocking, 3rd party cookie blocking and HTTPS Everywhere, the problem persisted.
I was able to put through the payment in Google Chrome immediately afterwards without any issue.
Expected behavior: I should be able to proceed with payment without any errors at the 3D secure stage.
The text was updated successfully, but these errors were encountered: