Open Bitdefender Safepay in its own screen or window.

@phnelth It's how is implemented. Without getting in too much gory details, Safepay is a self-shielded environment from the outside world. This is why it opens in a separate desktop, for example - if some s.c.r.i.p.t. or print screen or keylogger attempts to hook a window from the default desktop, it cannot do it in another desktop. Also the print screen is intercepted and disabled in safepay as well, virtual keyboard renders a keylogger unusable etc.

So from the security standpoint it was created as an isolated environment. I understand that there are scenarios where another webpage or document can be opened in the default desktop, and thus making the payment a back-and-forth desktop switch, which is, indeed, not very straightforward.

Now to make Safepay open in the same desktop will strip out a number of security advantages. If such an implementation (i.e. some option saying "Open Safepay in a separate desktop", default ON as is now, but with the possibility to let the user to switch it to OFF and thus opening Safepay in the same desktop) will be done, I won't hide this will be quite an implementation, and will require basically to (re)work and retest everything. Most likely it won't be very high on the list of emergencies to do, although it is an important idea. If something like this would be done, it would need to run similarily with a virtual machine (like VirtualBox, VMware, Hyper-V etc.) which will need to still deter print screens, disable mouse and keys to/from other programs etc. This will not be an easy implementation, trust me.

A few words about the comparison with SafeMoney. While such a comparison is normal, it is not comparing the same set of features. What SafeMoney does it to protect the network data exchange by verifying the website certificates, analyzing the website addresses if they are malware or not - something both the product (via the https scan) and Safepay (using its own analyzing of the navigated address and certificates) already does. But this comparison it does not take into account multiple other features, like, for example, Safepay is basically always in incognito mode, its storage is deleted at start (and end) of a session; its storage is protected being directly inside the product; is not using another browser, which in turn have extensions, plugins etc. which might intervene in the traffic, while Safepay actively disables any extension (not counting its own Password Manager, which is also loaded from a controlled location directly and not loaded from some other expose location).

But points taken. I will think on this and try to produce a proof of concept, and if that works, I will demonstrate it to the team and perhaps it will make it into such a feature update. I cannot guarantee now a timeline - or even a succes on releasing such a thing - but at least I can promise I will try to make it work. That is, among the (hundreds of) other things on my to do list.