-
Notifications
You must be signed in to change notification settings - Fork 78
SagePay Strong Customer Authentication and 3D Secure v2 #136
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
Comments
Did you mean to post this to the Sage Pay driver? |
If you think thats more suitable please send me the link. I do apologise if I post this in the wrong project. |
No problem, I'll transfer this issue. |
Thank you. |
Please close this issue if you think this previous issue covers the changes: #135 |
It is. Many thanks. |
Ta. We are at the stage of going through the docs to see what needs to be done. So eyes are on it, but no progress with implementation so far as I am aware. |
Sage pay now has a requirement to do all ecommerce transactions to be processed via secured industry protocol such as 3D Secure. They will not allow transactions which does not have Strong Customer Authentication. More details.
Is this issues being addressed already? or will there be any updated regarding this?
The text was updated successfully, but these errors were encountered: