-
Notifications
You must be signed in to change notification settings - Fork 3
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
Wallee Fingerprint Script in Magento 2.4.7 Checkout #38
Comments
Hello, Thank you for your message. I have involved our experts and we are working on a solution. I will get back to you with an update as soon as possible. Thank you for your patience and understanding for the longer processing time. Sincerely, |
Hello, In order to analyse your request we would need more informations. Could you please expand on what settings you are using in our plugin and provide us with a detailed instruction on how to reproduce the error? Could you also please provide us with the URL/which script is blocking? Thank you in advance for your response. Sincerely, |
Hello @Dominik-Niziol To repeat the problem: Magento needs to be updated to the latest version: 2.4.7-p1 The update introduced new CSP security features. CSP must be enabled on the site. Blocked script: Best regards |
Dear @mischi99 We have added a new option in the configuration to disable the fingerprint setting. If you are still having issues you can disable it with the following steps in Magento Stores -> Sales -> wallee Payment -> Checkout Best regards |
We have updated the Wallee payment to the latest version,
2.1.14
.On the website, there is only one block left that does not load an additional script correctly. Therefore, Magento complains about:
As a result, Magento blocks the "fingerprint" script.
https://fingerprint.com/
They add this script aggressively, almost like a hacker would. We can't fix it because the process is embedded in a script downloaded from the Wallee server.
The payment works, but the "fingerprint" script doesn't collect information about the current customer.
The text was updated successfully, but these errors were encountered: