Checklist for PCI DSS v4.requirements for e-commerce businesses
This checklist covers all 12 requirements of PCI DSS v4.0 for e-commerce businesses. Use it to review the necessary security measures, internal rules, and operational procedures to build a secure payment environment.
This document provides an overview of PCI DSS, along with a checklist of the 12 requirements for compliance and essential knowledge.
E-commerce sites that offer credit card payments require a system to handle card information securely. PCI DSS is an international security standard for this purpose. The current version, PCI DSS v4.0, defines 12 requirements, and compliance requires not only technical aspects but also confirmation of internal rules and operational procedures.
This article introduces the basic knowledge and checklists needed to obtain PCI DSS certification as a security measure for e-commerce sites. Please use this as a reference to build a secure payment environment.
What is PCI DSS?
PCI DSS (Payment Card Industry Data Security Standard) is a data security assessment standard that defines the technical and operational requirements for businesses involved in credit card payments to protect customer data.
The PCI SSC (Payment Card Industry Security Standards Council), jointly established by the five major international credit card brands (Visa, Mastercard, American Express, Discover, and JCB), formulates and manages the standards. Currently, version 4.0, released in March 2022 (the latest version is v4.0.1 with minor changes), is in use.
All businesses that store, process, or transmit cardholder data or sensitive authentication data are required to comply with the requirements of credit card companies under their contracts. This includes payment processing companies and e-commerce platform operators, as well as merchants and e-commerce sites that accept credit cards.
Risks of not complying with PCI DSS
PCI DSS is the de facto industry standard for payment security, and merchants who contract with card brands are also required to comply with it. If data breaches or other incidents occur while non-compliant, the following penalties and damages may result.
- Damages and Fines: In addition to compensation for victims, card brands and payment processing companies may also claim investigation costs and damages.
- Stricter contract terms: Transaction fees may be increased, and compliance verification requirements may become stricter.
- Payment suspension, contract termination: The merchant agreement may be terminated, and credit card payments may become unavailable.
PCI DSS v4.0 12 Requirements Checklist
- Implement and maintain network security controls.
- Apply safe settings to all system components.
- Protect your saved account data
- Protecting cardholder data transmitted over open networks
- Protect your system and network from malware.
- Develop and maintain secure systems and software.
- Restrict access to only what is necessary for business operations.
- Identify users and establish an access authentication mechanism.
- Restrict physical access to card information
- Record and monitor access to systems and card information.
- Regularly test the security of the system and network.
- Supporting information security through organizational policies and programs.
1. Implement and maintain network security controls.
Networks that transmit credit card information must have firewalls and other security measures in place to block unauthorized communications and restrict connections to general networks. Furthermore, settings and communication rules must be regularly reviewed to maintain a secure environment.
2. Apply safe settings to all system components.
We will change all system components to secure settings instead of using default passwords and initial settings. We will disable unused accounts and functions, establish system-specific setting standards, and verify that the settings are being followed.
3. Protect your saved account data.
We will review whether it is necessary to store card information, and if so, limit storage to only the minimum necessary data. We will define the types of information to be stored, the retention period, and the deletion method, and manage it securely by implementing access restrictions and encryption. Confidential authentication data such as card security codes must not be stored after payment authorization and must be properly deleted. We will also consider enforcing operational rules, such as not receiving card information via email or chat.
4. Protect cardholder data transmitted over open networks.
When transmitting customer-entered card information over the internet, it is protected by strong encryption technology. We also verify that the certificates and encryption settings used for communication are effective and that the system remains secure.
5. Protect your system and network from malware.
We implement malware protection (malicious software that damages terminals and systems, such as viruses and ransomware) in all systems and networks that handle credit card information, and keep our protection software and detection functions up to date. We also establish mechanisms to notify responsible personnel when malware is detected, and define procedures for investigation and response in case of suspected infection.
6. Develop and maintain secure systems and software.
We check for vulnerabilities in the systems and software we use and always apply the latest security updates. When developing and using custom or bespoke software, we establish secure development and verification procedures. For example, if we use scripts on a payment page, we record the scripts used and their purpose, and verify that they are authorized and have not been tampered with.
7. Restrict access to only what is necessary for business operations.
Access to card information and related systems will be limited to only those personnel who require it for their work. Each person will be granted only the necessary permissions, and any unnecessary permissions will be removed if their responsibilities change or they leave the company.
8. Identify users and establish an access authentication mechanism.
Individuals accessing the system will be assigned unique IDs to track who performed the operations. Multi-factor authentication will be implemented for access to the cardholder data environment, and authentication information such as passwords will be properly managed. Shared accounts will generally not be usable, so we will verify if it is possible to switch to individual accounts.
9. Restrict physical access to card information.
If there are devices, storage media, or paper documents handling card information, access to the storage area will be restricted. Entry and exit will be recorded, and when documents or storage media are disposed of, they will be disposed of in a way that prevents the information from being read.
10. Record and monitor access to systems and card information.
We will log all access and operations to system components and card information, and implement a mechanism to detect suspicious access and activity. Audit logs will be stored for at least 12 months, with the most recent three months readily available for analysis.
11. Regularly test the security of the system and network.
We will conduct vulnerability scans and penetration tests applicable to our environment. If any problems are found, we will fix them and record the actions taken and the results of further verification. On the payment page, we will also verify whether unauthorized changes can be detected.
12. Support information security with organizational policies and programs.
We will document our information security policy and ensure that employees are aware of and educated on it. We will establish incident response procedures and confirm roles and responsibilities with our contractors, such as payment processing companies.
Level classification for verifying PCI DSS compliance
Card brands categorize merchants based on factors such as annual transaction volume to verify their PCI DSS compliance. Generally, the higher the transaction volume, the stricter the review process and conditions become. While the categorization methods vary by card brand, the following is a general guideline.
Estimated number of transactions per year
Examples of verification methods
Level 1
Over 6 million items
The company undergoes an annual audit by a PCI SSC-accredited Quality Assurance Officer (QSA) and submits reports and certificates.
Level 2
1 million or more and 6 million or less
Compliance will be assessed annually based on the Self-Assessment Questionnaire (SAQ), and a report will be submitted.
Level 3
20,000 to less than 1 million
Conduct an annual self-assessment and submit a certificate of compliance.
Level 4
Less than 20,000
An annual self-assessment is recommended.
Compliance levels, required verification methods, and documentation may vary by card brand. Always check with your card company or acquirer to confirm the requirements and documentation applicable to your company.
Why you should choose an e-commerce platform that complies with PCI DSS.
Meeting and maintaining PCI DSS compliance requirements on your own requires specialized knowledge and continuous operation. By choosing an e-commerce platform that is already PCI DSS compliant, you eliminate the need to directly handle card information yourself, and also eliminate the need to individually manage servers and monitor networks.
Shopify is PCI DSS Level 1 compliant, and all stores using Shopify are provided with a PCI DSS compliant environment by default.
However, even if the platform is compliant, this does not mean that all actions on the business side are unnecessary. For example, measures such as properly managing accounts on the management screen and verifying the security of apps and systems that are linked to the e-commerce site are still required.
Compliance with PCI DSS is practically essential for implementing credit card payments. It's crucial to review the 12 requirements to understand the necessary measures and verification methods for your company's payment environment.
On the other hand, these standards are strict and detailed, making it difficult for companies to comply on their own. Therefore, choosing an e-commerce platform that already complies can reduce the burden on your company. Using the checklist in this article as a reference, and while also consulting with card companies and acquirers, ensure you have a secure payment environment.
Frequently Asked Questions about PCI DSS
What is PCI DSS?
PCI DSS is a payment security standard developed and managed by the PCI SSC to protect credit cardholder data.
How can I prove PCI DSS compliance?
In addition to audits by rating agencies, companies are required to perform self-assessments based on questionnaires and submit certificates and reports. Since requirements vary depending on the card brand and acquirer, you should check with your contractor to determine the necessary methods and documents for your company.
If the number of transactions is small, is self-assessment sufficient for PCI DSS verification?
Transaction volume alone is not sufficient for making a judgment. There are eligibility requirements, and your company's payment environment must meet those requirements.
Share this article
- Share on Facebook
- Share on X
- Share on LinkedIn




