Eleven days remain for companies to make sure their web-facing applications and websites are PCI Compliant according to section 6.6. Authoring the PCI Compliance blog series I often look up interesting websites for insights and quotes, although for this part in the series I can pretty much look inward at our own solutions.

The general thought is that by June 30, most of the companies who need it will fail to comply with section 6.6. The sad reality is the quick fix mentality will lead to many of the compliance issues, as application firewalls only place a Band-Aid on the gaping wound that is poor code development. So will your website be compliant? [The Tech Herald]

E-xact recently launched Web Secure Pay, which is a fully compliant way of having your website visitors complete transactions without ever leaving card data behind. Customers and clients stay within the confines of your website then when it comes time for transaction is processing they are passed through our secure systems and brought back to your online environment seamlessly.

We’ve also produced step-by-step screencasts featuring everything from implementation to the code that drives our intuitive transaction processing manager.

Section 6.6 is about looking at the code AND the application itself. It’s no secret that our application runs smoothly with Ruby on Rails, which allows for a slick interface while remaining secure with its tight and compliant code. You can view more detailed screencasts involving implementation and processes on our Viddler profile and click here to find out more about WSP.

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.