Spreedly is a PCI Level 1 Service Provider, the highest level of PCI DSS certification. You can access our current compliance documents here:
We are also a registered service provider with both Visa and MasterCard:
Who must be PCI compliant?
If you accept credit cards from your customers, then you must be PCI compliant.
Many payment gateways and online payment processing solutions may claim that their “drop-in” credit card widget excludes you from worrying about PCI compliance. This is not true. Even if you are using a third party to handle the collection, processing and storage of protected cardholder data, you must still follow the necessary certification process.
Third party solutions allow you to be PCI compliant with much less effort and expense than if you were processing and storing the card data yourself, but you still have to certify each year. Companies like Spreedly can help reduce your PCI compliance burden, but no one can eliminate it entirely.
Proof of PCI Compliance
What is required to prove your PCI compliance is ultimately up to your merchant/acquiring bank, and it depends on several factors, including the number of transactions you process annually. Generally, however, if you are using Spreedly you will rely on our PCI Level 1 status and complete the relevant SAQ. Depending on which category you fall under, you may be required to have an Approved Scanning Vendor provide an up-to-date scan of your systems, performed quarterly.
How Do I Self-Assess?
Performing a PCI compliance self-assessment requires you to complete a questionnaire and, depending on what self-assessment category you fall under, having an outside provider perform a quarterly security scan of your systems.
There are currently eight categories of self-assessment, but not all of these are applicable to online merchants. Your level of PCI scope will ultimately depend on how you capture and work with credit card data. If you are using a third party service like Spreedly it is likely that you will be required to fill out either a SAQ A, SAQ A-EP or SAQ D. View the table to the right for more information:
|IF YOUR SYSTEMS
|Do not touch, process or store cardholder data, and do not serve any card collection forms (e.g. you use Spreedly’s iFrame)
|Do not touch, process or store cardholder data, but do serve card collection forms (e.g. you use Spreedly’s transparent redirect)
|Do touch, process or store cardholder data
Where Can I Find More Information?
The PCI compliance guidelines and their interpretations are constantly evolving. We regularly blog about PCI developments so check back regularly, but we have included some relevant posts below:
For additional information, including copies of the PCI compliance guidelines, explanatory background materials,
downloadable SAQ forms and general instructions and guidelines, please visit the PCI Security Standards Council’s Documents Library.