Offer

3 months of free support on every e-commerce package

See Details
GLOBAL

PCI-DSS Certification: A Step-by-Step Guide for E-Commerce

Why is PCI-DSS certification mandatory for e-commerce? A guide to compliance levels, the 12 core requirements and the annual process.

GLOBAL 5 November 2026 9 min read Toserof Tech.
Contents

PCI-DSS certification for e-commerce is one of the fundamental security standards of e-commerce operations. Known as the Payment Card Industry Data Security Standard, this framework covers every business that processes, stores or transmits cardholder data. For every business operating in the global e-commerce market, getting to know this standard closely and achieving compliance is critically important.

What Is PCI-DSS and Who Must Comply?

PCI-DSS is a security standard jointly created in 2004 by the major payment card brands such as Visa, MasterCard, American Express, Discover and JCB. The standard aims to protect cardholder data and covers every business that processes credit card, debit card or prepaid card transactions. E-commerce sites, physical retail stores, payment service providers and fintech companies are the main stakeholders that fall within its scope. E-commerce businesses in Turkey must also comply with PCI-DSS if they process domestic or international card transactions.

  • E-commerce sites: Every website that accepts online payments falls within the scope of PCI-DSS regardless of transaction volume and must use a compliant payment infrastructure.
  • Payment service providers (PSPs): Payment intermediaries such as iyzico, PayTR and Stripe must also maintain their own PCI-DSS certification and provide merchants with a compliant infrastructure.
  • SaaS and marketplace platforms: Software platforms that manage the payment flow or have access to card data are also considered within the scope of the standard.
  • Physical retailers: Traditional retail businesses that use POS terminals or store card information also carry PCI-DSS obligations.

PCI-DSS Compliance Levels: Level 1 to Level 4

PCI-DSS compliance requirements are divided into four levels according to a business's annual card transaction volume. Each level requires different validation methods and audit processes. Determining the appropriate level is of great importance for both cost and operational burden.

Level 1: The Highest-Volume Businesses

Businesses that process more than 6 million card transactions a year fall under Level 1. Businesses at this level must undergo an annual on-site audit (ROC - Report on Compliance) by an independent QSA (Qualified Security Assessor) approved by the PCI SSC. In addition, a network scan must be carried out every three months by an accredited ASV (Approved Scanning Vendor). Amazon, major banks and global e-commerce giants are at this level.

Levels 2, 3 and 4: Medium and Small Businesses

Businesses that make 1-6 million transactions a year are classed as Level 2, those that make between 20,000 and 1 million e-commerce transactions as Level 3, and those that make fewer than 20,000 transactions as Level 4. Businesses at these levels are required to complete a self-assessment questionnaire known as an SAQ (Self-Assessment Questionnaire) instead of an on-site audit. However, some card payment companies may make a QSA audit mandatory for Level 2 businesses as well.

The 12 Core PCI-DSS Requirements

The PCI-DSS standard is structured around 12 main requirements in order to protect cardholder data. These requirements are grouped under six core security categories, and each covers specific technical and operational controls.

  • Requirements 1-2 (Secure Network): Firewalls must be installed and configured, and vendor-supplied default passwords and security parameters must be changed.
  • Requirements 3-4 (Cardholder Data Protection): Stored cardholder data must be protected and data transmitted over open networks must be encrypted. PAN (Primary Account Number) data may never be stored in plain text.
  • Requirements 5-6 (Vulnerability Management): Anti-malware protection systems must be used, and secure systems and applications must be developed and maintained.
  • Requirements 7-8-9 (Access Control): Access to cardholder data must be restricted on a need-to-know basis, access to system components must be defined and physical access must be brought under control.
  • Requirements 10-11 (Monitoring and Testing): Access to network resources and cardholder data must be monitored, and security systems and processes must be tested regularly.
  • Requirement 12 (Information Security Policy): An information security policy covering all personnel must be established and regular training must be carried out.

SAQ Types: Which Business Uses Which Questionnaire?

The Self-Assessment Questionnaire (SAQ) is the documentation tool used to self-assess PCI DSS compliance. Different SAQ types exist for different payment acceptance methods. Choosing the right SAQ type is critical for both ease of process and compliance.

SAQ A and SAQ A-EP for E-Commerce

SAQ A is the most suitable option for e-commerce businesses that fully outsource card data to third-party payment providers (iframe or redirect method). With this method, the payment page is hosted entirely by the payment provider, so the scope of the standard narrows considerably. SAQ A-EP is for businesses whose payment page is hosted on their own server but which leave card data processing to a third party. This form contains far more extensive technical controls.

SAQ B, C and D Types

SAQ B is only for businesses that use an imprint machine or a dial-up terminal and whose card payment system is not connected to the internet. SAQ C covers internet-connected businesses that use payment application systems. SAQ D is the most comprehensive self-assessment form and is mandatory for businesses and service providers that do not fall into any other category. With more than 329 questions, SAQ D requires an assessment of a depth almost equivalent to a full ROC audit.

Card Data Storage Rules and Tokenisation

One of the most critical rules of PCI-DSS is the strict limitation on storing cardholder data. CVV2/CVC2 security codes may not be stored under any circumstances; violating this rule is one of the most serious cases of non-compliance. If PAN (Primary Account Number) data is to be stored, it must be masked, encrypted or tokenised. Tokenisation is one of the most effective ways of minimising the storage scope from a PCI-DSS perspective by using a randomly generated token value in place of the real card number. This way, even in the event of a data breach, real card data is not put at risk.

Network Security and DMZ Architecture

Systems that process cardholder data must be hosted in a secure Cardholder Data Environment (CDE) isolated from other network segments. Firewalls must separate the CDE from the internet and from internal networks. DMZ (Demilitarised Zone) architecture is a commonly used approach for achieving this separation. All network traffic must be logged, and abnormal activity must be monitored in real time with SIEM (Security Information and Event Management) systems. If wireless networks exist, strong encryption protocols such as WPA2/WPA3 are mandatory.

Penetration Testing and ASV Scans

PCI-DSS compliance is not a static state but a continuously updated process. For this reason, regular security testing is mandatory. Penetration testing must be carried out at least once a year, and after major system changes, to measure how resilient systems are against a real attack. ASV (Approved Scanning Vendor) scans, on the other hand, are automated vulnerability scans carried out externally by an accredited security firm, and are mandatory on a quarterly basis for Level 1-3 businesses.

  • Internal network tests: Whether unauthorised access to systems within the CDE can be gained must be tested manually.
  • External network tests: Vulnerabilities in systems accessible over the internet must be examined from the perspective of an external attacker.
  • Application security tests: Payment applications must be tested against the OWASP Top 10 and similar vulnerabilities.

Working with a QSA: What Is It and What Does It Do?

Qualified Security Assessors (QSAs) are independent audit organisations accredited by the PCI SSC. They carry out the annual ROC audit for Level 1 businesses. QSAs also guide businesses at other levels in completing the SAQ, identify security vulnerabilities and offer remediation recommendations. The main criteria to look for when choosing a QSA are experience, sector expertise, references and being listed on the PCI SSC's current accreditation list. There are also QSA firms with PCI SSC accreditation in Turkey.

The Annual Compliance Process

PCI-DSS compliance is not a certificate that is obtained once and forgotten; it is a dynamic process that must be renewed every year. The annual process covers self-assessment or QSA audit, ASV scans, penetration tests, policy updates and staff training. Sharing compliance documents with card brands and banks is also an integral part of this process. PCI DSS v4.0, which came into force in 2024, brought significant changes and new controls to some requirements; businesses need to assess their compliance against the current version.

Non-Compliance Penalties and Risks

PCI-DSS non-compliance can create serious financial and operational risks. Payment card brands may impose fines of between 5,000 and 100,000 dollars a month on non-compliant merchants. In the event of a data breach, these penalties multiply, and forensic investigation costs, customer notification expenses and reputational damage come into play as well. The most severe outcome is the complete revocation of card processing authority; for an e-commerce business, this can mean a de facto shutdown. In an age when cybercrime is becoming ever more sophisticated, delaying PCI-DSS compliance is a major operational risk factor.

Frequently Asked Questions

How long does it take to obtain PCI-DSS certification?

The time varies according to the size of the business and its existing infrastructure. For small businesses using a ready-made payment infrastructure, completing the SAQ process can take anywhere from a few days to a few weeks. For Level 1 businesses, the QSA audit and meeting the requirements can take between 3 and 12 months.

Are businesses that use Stripe or iyzico exempt from PCI-DSS?

No, you are not fully exempt, but the scope narrows significantly. If you use the iframe or redirect method of these providers, completing SAQ A may be sufficient. The fact that card data never touches your own servers makes this simplification possible. You still need to verify technically how the payment page is integrated.

What changed with PCI-DSS v4.0?

PCI DSS v4.0, which became mandatory in March 2024, offers a more flexible approach to compliance (the Customized Approach). Multi-factor authentication requirements have been expanded, new controls against e-commerce skimming attacks have been added and risk-based approaches have been strengthened. Businesses were required to comply with all v4.0 requirements by the end of 2025 at the latest.

What happens in the event of PCI-DSS non-compliance?

Payment card brands may impose monthly fines; the bank or payment institution may suspend the account. If a data breach occurs, forensic investigation costs may be passed on to the business and card reissuance costs for affected customers may have to be paid. In the worst-case scenario, card processing authority is revoked entirely.

Conclusion

PCI-DSS certification is both a legal obligation for e-commerce businesses and a strategic investment that strengthens customer trust. Managing the compliance process correctly prevents potential data breaches and supports the long-term sustainability of your business. Get in touch with Toserof Tech. for global operations consulting.

Share