Industry Insights

什么是PCI DSS?企业支付安全合规完整指南

James Carter
Business Finance Writer

PCI DSS sets the security standard for every business that handles card payments. Learn what the four compliance levels mean, who is responsible for what, and how to verify your payment provider actually meets the standard.

2026.08.21 11:39:14 · 5minute(s)
If your business accepts card payments — online, in-store, or through a payment platform — PCI DSS applies to you. Most business owners know the acronym. Very few understand what it actually requires, who is responsible for meeting it, and what happens when something goes wrong.
This guide covers what PCI DSS is, how the compliance levels work, where your responsibility ends and your payment provider's begins, and how to check whether the platform you're using actually meets the standard.

What PCI DSS Actually Is

PCI DSS stands for Payment Card Industry Data Security Standard. It's a set of technical and operational security requirements created in 2004 by the major card networks — Visa, Mastercard, American Express, Discover, and JCB — through a body called the PCI Security Standards Council (PCI SSC).
The standard exists for one purpose: to protect cardholder data from being compromised. It covers how card data is stored, transmitted, and processed, and it applies to every entity in the payment chain that touches that data.
PCI DSS is not a government regulation. No law directly mandates compliance. But non-compliance creates contractual liability with card networks and acquiring banks — meaning your ability to accept card payments can be terminated, and you can be fined, if you fail to meet it. In practice, that makes it as binding as most regulations.

The Four Compliance Levels — and Which One Applies to You

PCI DSS assigns merchants to one of four compliance levels based on annual card transaction volume. The level determines how rigorously you must demonstrate compliance.
Level
Transaction Volume (per year)
Validation Requirement
Who This Typically Covers
Level 1
Over 6 million Visa/Mastercard transactions
Annual on-site audit by a Qualified Security Assessor (QSA) + quarterly network scan
Large merchants, payment processors, major platforms
Level 2
1 to 6 million transactions
Annual Self-Assessment Questionnaire (SAQ) + quarterly network scan
Mid-size e-commerce and retail businesses
Level 3
20,000 to 1 million e-commerce transactions
Annual SAQ + quarterly network scan
Growing online merchants
Level 4
Fewer than 20,000 e-commerce or up to 1 million other transactions
Annual SAQ (recommended) + quarterly scan (if applicable)
Most small businesses
Most small and mid-size businesses fall into Level 3 or Level 4. If you process payments through a hosted payment platform rather than building your own checkout infrastructure, your compliance burden is significantly reduced — but it is not eliminated.

The 12 Requirements, Summarized

PCI DSS version 4.0 (released in 2022 and fully mandatory as of March 2025) organizes its requirements into six control objectives and 12 core requirements. You don't need to memorize them, but understanding the categories tells you what the standard is actually protecting against.
  1. Install and maintain network security controls: Firewalls and network segmentation to prevent unauthorized access to cardholder data environments.
  2. Apply secure configurations: No vendor-supplied default passwords or unnecessary system functionality that broadens the attack surface.
  3. Protect stored account data: Cardholder data must be encrypted, truncated, or tokenized at rest — and most data should not be stored at all.
  4. Protect data in transit: All cardholder data transmitted over open networks must be encrypted using strong cryptography (TLS 1.2+).
  5. Protect systems against malware: Anti-malware controls on all systems that could be exposed to malware, with regular updates.
  6. Develop and maintain secure systems and software: Vulnerability management, patch cadence, and secure development practices for payment-facing code.
  7. Restrict access to system components: Access to cardholder data limited to business need-to-know, with formal access control systems.
  8. Identify users and authenticate access: Unique user IDs, strong authentication (MFA required for all administrator access in v4.0), and password policies.
  9. Restrict physical access: Physical controls on access to systems that store or process cardholder data.
  10. Log and monitor all access: Comprehensive audit logs for all access to network resources and cardholder data, with tamper-evident mechanisms.
  11. Test security of systems and networks regularly: Quarterly vulnerability scans, annual penetration testing, and intrusion detection.
  12. Support information security with policies: Documented security policies, risk assessments, and an incident response plan.

Who Is Responsible: Your Payment Provider or You?

This is the question most businesses get wrong. The answer depends on how you've integrated payments into your operations.
When you use a hosted payment page or a third-party checkout managed entirely by your payment provider, your exposure to cardholder data is minimal — the data flows directly into the provider's environment, not yours. In this model, the provider carries the bulk of PCI DSS responsibility, and your compliance scope is narrow (typically SAQ A, the simplest self-assessment form).
When you build a custom checkout that collects card data on your own servers before passing it to a processor, you own that data environment and inherit its compliance requirements — potentially up to a Level 1 audit.
The boundary matters because many businesses assume using a reputable payment provider means they have no PCI obligations. That assumption is wrong. You're always responsible for the parts of the payment flow that touch your systems.
Integration Type
Your PCI Scope
Typical SAQ Form
Hosted payment page (redirect)
Minimal — card data never touches your servers
SAQ A
iFrame or embedded form (provider-managed)
Low — card data captured in provider's iFrame
SAQ A-EP
JavaScript-based card capture on your page
Moderate — your page code executes during card entry
SAQ A-EP
API integration (card data posted to your server)
Full — your servers process card data directly
SAQ D (most demanding)
For most businesses using a modern payment platform with a hosted checkout flow, the right question is not 'are we PCI compliant?' but 'is our payment provider PCI compliant, and have we implemented our side of the integration correctly?'

How to Verify Your Payment Provider Is PCI DSS Compliant

The PCI SSC maintains a public list of validated service providers. Any payment provider that has completed a Level 1 audit by a Qualified Security Assessor will appear on the Visa or Mastercard global registry of compliant service providers.
To check:
  • Go to visa.com/splisting or the Mastercard SDP (Site Data Protection) registry
  • Search by company name (legal entity, not brand name)
  • Confirm their compliance status is current — entries expire annually
  • Check which services are in scope for their compliance certificate (a provider may be PCI compliant for some services but not others)
Beyond the registry, ask your provider directly for their Attestation of Compliance (AOC) — the formal document issued after a successful QSA audit. A compliant Level 1 provider will produce this without hesitation. If they can't or won't share it, that's a problem.
PhotonPay holds SOC 2 Type I certification alongside its multi-jurisdiction payment licenses, and operates with PCI DSS-aligned security controls including encryption in transit, tokenization of card data, and AI-driven fraud monitoring. For businesses evaluating a payment provider's security posture, the combination of regulatory licensing and independent security certification is the baseline to look for — not marketing claims about 'bank-grade security.'

What Non-Compliance Actually Costs

PCI DSS non-compliance is a contractual issue before it's a financial one. The card networks and acquiring banks set the penalties, not regulators — which means enforcement happens through your payment account, not through fines issued by a government body.
The cost structure for non-compliance breaks into three categories:
Monthly non-compliance fees. Acquiring banks pass PCI non-compliance fees down to merchants who fail to submit their annual SAQ or scan results. These typically range from $10 to $100 per month depending on the acquirer.
Post-breach fines and forensic costs. If a data breach occurs and a forensic investigation finds you were non-compliant at the time, card network fines range from $5,000 to $100,000 per month — retroactively applied from when non-compliance began. You also pay for the mandatory forensic investigation, which can run $20,000 to $100,000+.
Card replacement and fraud reimbursement. After a breach, you may be liable for the cost of replacing compromised cards (around $5–$15 per card) and reimbursing fraud losses on those cards. For a breach involving tens of thousands of cards, this can reach millions.
The 2013 Target breach — which compromised 40 million credit and debit cards — resulted in an $18.5 million multi-state settlement. The business that was actually breached was a third-party HVAC vendor, not Target's core payment systems. PCI scope extends wherever cardholder data travels, including vendor access points.

What PCI DSS Does Not Cover

PCI DSS is a card data security standard. It does not address every security risk a business faces in payments, and understanding its limits matters for building a complete fraud and security strategy.
It does not prevent all fraud. PCI DSS protects cardholder data from being stolen at rest or in transit. It does not prevent card-not-present fraud, account takeover, or social engineering attacks. A PCI-compliant business can still experience significant fraud losses. Layering in real-time fraud detection and strong authentication is a separate requirement.
It does not cover bank transfers or alternative payment methods. PCI DSS applies to payment card data — card numbers, CVVs, PINs. ACH transfers, wire payments, and digital wallets operate under different security and regulatory frameworks. If your business uses multiple payment rails, each has its own compliance requirements.
It does not equal regulatory compliance. Being PCI DSS compliant does not mean your business meets AML requirements, data protection laws (GDPR, CCPA), or payment institution licensing requirements. These are separate frameworks that operate in parallel.
A comprehensive approach to payment security covers all three layers: regulatory licensing (your provider is authorized to operate), PCI DSS compliance (card data is handled securely), and fraud controls (transactions are monitored in real time). For more on how these work together, see our guides on fraud prevention strategy and online payment fraud detection.

FAQ

Does every business that accepts card payments need to be PCI DSS compliant?
Yes, if you accept, process, store, or transmit credit or debit card data, PCI DSS applies. The compliance level and validation requirements vary by transaction volume — small businesses typically complete a self-assessment questionnaire rather than a full audit — but there is no exemption based on size.
If I use Stripe, PayPal, or another major payment provider, am I automatically PCI compliant?
No. Using a PCI-compliant payment provider reduces your compliance scope significantly, but it does not eliminate your responsibility. You still need to complete the appropriate self-assessment for your integration type and ensure your own systems and processes don't introduce vulnerabilities — such as logging card data, storing CVVs, or building insecure checkout flows.
What is the difference between PCI DSS and SOC 2?
PCI DSS is a payment industry standard specifically focused on card data security. SOC 2 is a broader framework assessing a service provider's security, availability, processing integrity, confidentiality, and privacy controls. A company can hold both certifications — they address different aspects of security and are not substitutes for each other.
How often does PCI DSS compliance need to be renewed?
Annual revalidation is required — either through a new self-assessment questionnaire or a new QSA audit for Level 1 merchants. Quarterly vulnerability scans are also required throughout the year. The PCI SSC released version 4.0 in 2022, with all v3.2.1 requirements retired as of March 2024.
What should I do if I suspect a card data breach?
Contain the breach immediately by isolating affected systems. Notify your acquiring bank within 24 hours — they will initiate the mandatory forensic investigation. Do not attempt to investigate the breach yourself, as this can compromise forensic evidence and increase your liability. If the breach is confirmed, the card networks will determine whether a PCI compliance failure contributed to it.

Power Your Global Growth with PhotonPay