@passmarked/ssl/docs/fields.creditcard.md

Rules that relate to checking the SSL configuration of each individual resolved server from the domain to ensure locked down config with the broadest compatibility

Starting from Chrome 56, credit cards fields not hosted over HTTPS will show a "insecure" warning. 

This will be less noticeable for 56 at first, but will be a large red error in later versions which will chase users away.

Any pages with credit card information must be secured to avoid any warnings being shown on the url bar.

# How do I fix this ?

Enable HTTPS for the entire website or just for the specific pages that require the user to enter their payment information.

This will avoid the error on Chrome and show a **SECURE** status on the url bar again.

# Resources

* [Moving towards a more secure web](https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html)
* [Google Search Console warns of nonsecure collection of passwords with upcoming Chrome browser release](http://searchengineland.com/google-search-console-warns-nonsecure-collection-passwords-upcoming-chrome-browser-release-266486)
* [Chrome 56 to Show Warnings on HTTP Pages with Payment and Password Forms](https://www.bleepingcomputer.com/news/software/chrome-56-to-show-warnings-on-http-pages-with-payment-and-password-forms/)