PCI DSS compliance is now a legal requirement for anyone with merchant services, having just had to go through this myself and knowing that our clients are also going to have to do the same, I started searching for a simple guide that I could pass on to clients and came across this book.
Complying with the PCI Data Security Standard may seem like a daunting task for merchants. This book is a quick guide to understanding how to protect cardholder data and comply with the requirements of PCI - from surveying the standard's requirements to detailing steps for verifying compliance.
PCI Compliance for Dummies arms you with the facts, in plain English, and shows you how to achieve PCI Compliance.
And yes my company BlueThunder Internet is fully PCI DSS compliant before you ask :-)
Jan 29, 2010 at 3:04 PM Might be good to also mention that if you use a Third Party (PSP - Payment Service Provider) like RBS worldpay, you as a company don't need to be PCI complient on your website. Unless for some strange reason you capture card info.
Jan 29, 2010 at 9:46 PM Correct, but that should be made clear by your merchant provider as it should be the first question they ask you. But then saying that,we technically do not have to be as we technically don't own the server the card details are stored on, but I still have to complete the SAQ.
Aug 18, 2012 at 8:21 AM tom,That's the core CFC for CFGroovy that is missing, not a Java class file. More sacpifieclly, it's a bug in the demo application it can't correctly resolve the path to cfgroovy.cfc correctly, so it can't instantiate it. If you create a "/groovyEngine" mapping in the CF Administrator that points to the "groovyEngine" within the demo app, that should get you going.I'm not sure why this would be the case, though. I built the demo app with relative paths everywhere so there wouldn't be a constraint. Or at least that was my intent. Can you tell me more about how you've got everything set up, and I'll take a look a it and see if I can replicate (and then fix) the issue.