Meercat RiskView and HTTPS
Our Risk Product now imposes better security within the application.
For the time being, you have the option to use your Site in HTTP or HTTPS mode.
HTTP is not encrypted and is vulnerable to man-in-the-middle and eavesdropping attacks, which can let attackers gain access to website accounts and sensitive information, and modify webpages to inject malware or advertisements. HTTPS is designed to withstand such attacks and is considered secure against them.
Once implemented, all the communications between you and Meercat RiskView will be performed according to TLS 1.2.
If you wish to enforce HTTPS on your Site (i.e. it will always direct you to the HTTPS URL), please let us know and we will apply that for you.
Early in 2016, we will be imposing HTTPS for all clients.