Your Guide to eCommerce PCI Compliance

With sites like Shopify and other tools that make it easier for anyone to set up their own online shop, new eCommerce sites are popping up every day as large-scale businesses and as side gigs for people who want to make a little extra cash. Whether your business is a budding side hustle or a thriving company, PCI compliance must be a top priority.

What is PCI compliance and what do you need to know about it as an eCommerce business? This guide digs into the key details you need to know to get started with your compliance process.

What is PCI compliance?

The term “PCI compliance” is actually referring to compliance to the PCI DSS - the Payment Card Industry Data Security Standard. This is a set of standards and requirements established by the PCI Security Standards Council to make sure that when customers use their credit cards (including online), businesses are taking steps to protect customers’ payment data.

Do eCommerce businesses need to comply with PCI standards?

Does your business need to be PCI compliant? For eCommerce, the answer is yes. Every business that collects, processes, stores, or transmits payment data is responsible for complying with PCI standards.

Within PCI compliance, there are two types of businesses that need to adhere to the standards: merchants and service providers. For purposes of eCommerce compliance, eCommerce businesses are merchants. Service providers include any other businesses that come into contact with your customers’ data, like your cloud provider.

Why is PCI compliance for eCommerce sites so important?

Unlike some privacy requirements like GDPR, PCI compliance is not a legal or regulatory requirement. It’s an industry-wide requirement that is enforced by major banks and credit card companies like Visa and MasterCard. These companies can leverage serious fines against your business if you don’t comply.

On top of avoiding those fines, you can expect that if you’re doing business with new vendors, partners, or other key stakeholders, they may ask if you’re PCI compliant. They want to know that they’re doing business with someone that does their due diligence, and lack of compliance can be a deal breaker for customers.

Finally, remember that PCI compliance isn’t just about marking off a checklist. The standards exist for a reason: to protect customer payment data. If you’re abiding by the PCI DSS, you’ll have a lower risk for data breaches (and the PR nightmares, loss of trust, and potential legal liabilities that come with them).

What standards do I need to meet to be PCI compliant as an eCommerce business?

To be broad, there are 12 requirements listed in the PCI DSS. These include:

  1. Maintain a firewall that protects customer data.
  2. Use secure passwords instead of vendor-supplied default passwords.
  3. Protect any stored cardholder data.
  4. Encrypt any customer data that you transmit over open, public networks.
  5. Maintain up-to-date antivirus software.
  6. Maintain secure systems and applications.
  7. Only allow access to cardholder data for those who truly need access.
  8. Assign a personal ID to each internal employee or contractor with computer access.
  9. Restrict the ability to physically access customer data.
  10. Track and monitor any access to cardholder data and network resources.
  11. Regularly test your security systems and processes to ensure that they’re working properly.
  12. Establish a company policy that addresses information security practices for employees and contractors.

Each of these 12 requirements has sub-requirements that are more specific about how you can meet the goals of the requirement. To be PCI compliant, you must adhere to all of these requirements and sub-requirements.

How do I document that I’m PCI compliant?

To officially document your PCI compliance, there are documents and reports you need to complete annually. Which documents need to be completed vary based on the size of your business and how you interact with cardholder data.

The PCI DSS defines four different levels of merchants. Level 1 merchants are those that process at least six million transactions per year. Level 2 merchants process between one million and six million transactions annually, level 3 merchants process 20,000 - one million transactions per year, and level 4 merchants process less than 20,000 transactions annually.

If you qualify as a level 2, 3, or 4 merchant, you’ll need to complete an annual self-assessment questionnaire that assesses your PCI compliance. You’ll submit this along with supporting documentation like third-party vulnerability scans and an Attestation of Compliance (AOC). A level 1 merchant, on the other hand, needs to have an annual assessment called a Report on Compliance (ROC) and AOC completed by a third-party Qualified Security Assessor (QSA) or Internal Security Assessor (ISA).

How Can I Make My PCI eCommerce Compliance Process Easier?

PCI compliance for your eCommerce business doesn’t need to be as cumbersome of a process as you might expect. You can make it far easier with PCI compliance software like Vanta. This type of tool continuously monitors your PCI environment and helps you gather evidence required  to meet applicable PCI DSS controls. It provides you with a straightforward report of the requirements you already meet and the ones that require attention so you can cut to the chase and only focus on the necessary steps for PCI compliance.

This automated software can also continue to regularly monitor your system so that if you make changes that impact your compliance, you are alerted quickly and can solve the problem before it becomes a security or compliance issue. When you’ve reached compliance, the software’s reports can also streamline the external QSA assessment process, making Level 1 compliance far smoother and more efficient.

Begin your PCI compliance

Automate your PCI DSS compliance

How to Get PCI Compliant

PCI compliance in 3 steps

Interested in more?

Share your email so Vanta can send you new guides and helpful steps to improve security at your company.


PCI Compliance Selection Guide

Determine Your PCI Compliance Level

If your organization processes, stores, or transmits cardholder data, you must comply with the Payment Card Industry Data Security Standard (PCI DSS), a global mandate created by major credit card companies. Compliance is mandatory for any business that accepts credit card payments.

When establishing strategies for implementing and maintaining PCI compliance, your organization needs to understand what constitutes a Merchant or Service Provider, and whether a Self Assessment Questionnaire (SAQ) or Report on Compliance (ROC) is most applicable to your business.

Answer a few short questions and we’ll help identify your compliance level.


Does your business offer services to customers who are interested in your level of PCI compliance?


Identify your PCI SAQ or ROC level

The PCI Security Standards Council has established the below criteria for Merchant and Service Provider validation. Use these descriptions to help determine the SAQ or ROC that best applies to your organization.

Good news! Vanta supports all of the following compliance levels:


A SAQ A is required for Merchants that do not require the physical presence of a credit card (like an eCommerce, mail, or telephone purchase). This means that the Merchant’s business has fully outsourced all cardholder data processing to PCI DSS compliant third party Service Providers, with no electronic storage, processing, or transmission of any cardholder data on the Merchant’s system or premises.

Get PCI DSS certified


A SAQ A-EP is similar to a SAQ A, but is a requirement for Merchants that don't receive cardholder data, but control how cardholder data is redirected to a PCI DSS validated third-party payment processor.

Learn more about eCommerce PCI

for service providers

A SAQ D includes over 200 requirements and covers the entirety of PCI DSS compliance. If you are a Service Provider, a SAQ D is the only SAQ you’re eligible to complete.

Use our PCI checklist

Level 1 for service providers

A Report on Compliance (ROC) is an annual assessment that determines your organization’s ability to protect cardholder data. If you’re a Merchant that processes over six million transactions annually or a Service Provider that processes more than 300,000 transactions annually, your organization is responsible for both a ROC and an Attestation of Compliance (AOC).

Automate your ROC and AOC

Download this checklist for easy reference


Learn more about how Vanta can help. You can also find information on PCI compliance levels at the PCI Security Standards Council website or by contacting your payment processing partner.

The SOC 2 Compliance Checklist

Most businesses look at security compliance as a mountain that is impossible to conquer without an equally mountainous budget and ample time with endless frustrations. The truth is that every organization’s experience will vary, but in most cases, you can achieve compliance and certification easier than you think if you only prepare properly.

That begins with educating yourself about the road ahead and having the right tools in your toolbox, like automated compliance software. If you’re preparing to guide your organization through SOC 2 compliance, our SOC 2 compliance checklist will break down the process and give you a digestible view of the road ahead.


Pre-Work for Your SOC 2 Compliance

Choose the right type of SOC 2 report:

A SOC 2 Type 1 report assesses how your organization aligns with the security controls and policies outlined in SOC 2
A SOC 2 Type 2 report has all the components of a Type 1 report with the addition of testing your controls over a period of time
The correct report will depend on the requirements or requests of the client or partner that is requested a SOC 2 report from you

Determine the framework for your SOC 2 report. Of the five Trust Service Criteria in SOC 2, every organization needs to comply with the first criteria (security), but you only need to assess and document the other criteria that apply. Determining your framework involves deciding which Trust Service Criteria and controls are applicable to your business using our Trust Service Criteria Guide.

Estimate the resources you expect to need. This will vary depending on how closely you already align with SOC 2 security controls but it can include several costs such as:

Compliance software
Engineers and potentially consultants
Security tools such as access control systems
Administrative resources to draft security policies
Auditing for your compliance certification

Obtain buy-in from your organization leadership to provide the resources your SOC 2 compliance will need.


Work Toward SOC 2 Compliance

Begin with an initial assessment of your system using automated compliance software to determine which necessary controls and practices you have already implemented and which you still need to put in place.

Review your Vanta report to determine any controls and protocols within the “Security” Trust Service Criteria that you do not yet meet and implement these one by one. These are multi-tiered controls across several categories of security, including:

CC1: Control Environment
CC2: Communication and Information
CC3: Risk Assessment
CC4: Monitoring Activities
CC5: Control Activities
CC6: Logical and Physical Access Controls
CC7: System Operations
CC8: Change Management
CC9: Risk Mitigation

Using Vanta’s initial assessment report as a to-do list, address each of the applicable controls in the other Trust Services Criteria that you identified in your initial framework but that you have not yet implemented.

Using Vanta’s initial assessment report, draft security policies and protocols that adhere to the standards outlined in SOC 2. Vanta’s tool includes thorough and user-friendly templates to make this simpler and save time for your team.

Run Vanta’s automated compliance software again to determine if you have met all the necessary criteria and controls for your SOC 2 report and to document your compliance with these controls.


Complete a SOC 2 Report Audit

Select and hire an auditor affiliated with the American Institute of Certified Public Accountants (AICPA), the organization that developed and supports SOC 2.

Complete a readiness assessment with this auditor to determine if you have met the minimum standards to undergo a full audit.

If your readiness assessment indicates that there are SOC 2 controls you need to address before your audit, complete these requirements. However, if you have use automated compliance software to guide your preparations and your SOC 2 compliance, this is unlikely.

Undergo a full audit with your SOC 2 report auditor. This may involve weeks or longer of working with your auditor to provide the documentation they need. Vanta simplifies your audit, however, by compiling your compliance evidence and documentation into one platform your auditor can access directly.

When you pass your audit, the auditor will present you with your SOC 2 report to document and verify your compliance.


Maintain Your SOC 2 Compliance Annually

Establish a system or protocol to regularly monitor your SOC 2 compliance and identify any breaches of your compliance, as this can happen with system updates and changes.

Promptly address any gaps in your compliance that arise, rather than waiting until your next audit.

Undergo a SOC 2 re-certification audit each year with your chosen SOC 2 auditor to renew your certification.

Prioritizing Your Security and Opening Doors with SOC 2 Compliance

Information security is a vital priority for any business today from an ethical standpoint and from a business standpoint. Not only could a data breach jeopardize your revenue but many of your future clients and partners may require a SOC 2 report before they consider your organization. Achieving and maintaining your SOC 2 compliance can open countless doors, and you can simplify the process with the help of the checklist above and Vanta’s compliance automation software. Request a demo today to learn more about how we can help you protect and grow your organization.

Download this checklist for easy reference


“Getting our SOC 2 and HIPAA was an absolute game-changer for the way that Nayya is able to sell into larger companies.”

Akash Magoon
Co-Founder + Chief Technology Officer  |  Nayya

Related guides


Vanta's PCI Selection Guide

Which PCI compliance level is right for you? Answer a few short questions and we'll help identify your compliance level.

Your CCPA guide to data privacy compliance

What is CCPA compliance and how will it affect your business? Learn about California’s new regulations in this essential CCPA guide.
Security monitoring

2022 State of Startup Security

Vanta asked startups to honestly and anonymously answer questions about their security posture, their security roadmap, and how satisfied they are with their security in general.
Vanta automates security compliance.
Please enter your first name
Please enter your last name
Please enter a valid email address
Please enter a job title
Please enter your company name
Please enter your company website
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.