You receive the "Protected Browser could not be started" message or you are unable to enter your banking website username and password without the keystrokes being "scrambled".
Solution: Disable keystroke encryption in software that uses this technology, for example, IBM Trusteer Rapport, Hitman Pro Alert, Web Companion, SpyShelter, KeyScrambler or Zemana AntiLogger. If keystroke encryption cannot be disabled, you may need to uninstall the software to resolve this issue.
Banking & Payment protection will not start after upgrading from Firefox 47 to Firefox 48.
Solution: Follow our Online Help instructions to resolve browser issues including clearing your cache.
Banking & Payment redirector shows connection as insecure.
Solution: Your browser’s address bar may display “Not Secure” immediately after opening ESET Banking and Payment protection. This is normal and does not constitute a security risk.
The landing page is strictly informational and you cannot upload or download content on this page. It uses the http protocol, which causes your browser to display “Not Secure.” After navigating to your banking or payment site, the browser should display "Secure", which indicates that the secure https protocol is being used. This lets you know that your login information is being encrypted by both the website and ESET Banking and Payment Protection. For more information about "Not Secure" messages in the Google Chrome Browser, visit the following We Live Security article.
If you are experiencing this issue (error 0x847695d7), we recommend that you restart your computer.
If restarting your computer does not fix this issue, we recommend that you try each solution in the order below: