Glossary

What is PCI DSS: the security standard for handling credit-card data

PCI DSS is the security standard for businesses that handle card data. Who it applies to, what it requires, and the safest option: not holding card data.

Published 2026-07-04 Updated 2026-10-06 8 min read
On this page

PCI DSS is unavoidable if you handle card data. Here's the scope and the essentials, and the safest choice of all ("don't hold it"), in defensive terms.

Hold card numbers yourself — Scope: large

Encryption at rest, access control, monitoring, vulnerability management — all of it lands on you

Tokenise through a compliant payment provider — Scope: small

Design so you never touch the card number and the scope itself shrinks

Scope is decided by design. Data you never hold cannot leak.

What it requires (broadly)

Less about one technology than an operating posture: protect sensitive data in the smallest scope, in depth, and keep records.

1

Protect (encryption, access control)

Encrypt stored data with key management, encrypt data in transit, and enforce least-privilege access control (narrow who may touch card data). Authentication vs authorization is the basis.

2

Harden (no defaults, vulnerability management)

Eliminate default passwords and weak credentials, and monitor dependency CVEs and patch. Anti-malware included.

3

Record (logging, monitoring, regular testing)

Keep logs of who did what and when, and monitor. Scan and test regularly to maintain the standard.

The 12 requirements (v4.0.1)

PCI DSS groups 12 requirements under six goals.

#Requirement (summarized)
1Install and maintain network security controls (firewalls, etc.)
2Apply secure configurations to all system components (no default passwords)
3Protect stored account data (never keep the security code after authorization)
4Protect card data with strong cryptography over public networks
5Protect systems from malware
6Develop and maintain secure systems and software (patching, payment-page script management)
7Restrict access to those with a business need
8Identify users and authenticate access (including multi-factor)
9Restrict physical access to card data
10Log and monitor all access
11Test security regularly (vulnerability scans, payment-page tamper detection)
12Support information security with policies and programs

The current version is v4.0.1 (published June 2024). Requirements introduced in v4.0 that became mandatory on 31 March 2025 include authorizing and inventorying the scripts that run on payment pages (Requirement 6.4.3) and a mechanism to detect unauthorized changes to payment pages (Requirement 11.6.1).

How you integrate payments changes your scope

The self-assessment questionnaire (SAQ) an online merchant uses depends on how card numbers pass through its systems.

IntegrationPath of the card numberMain questionnaire
Redirect to the provider's page, or embed the provider's page (iframe)Touches neither your server nor your pageSAQ A (fewest items)
Your page sends it directly to the provider with the provider's JavaScript or formNot your server, but your page takes part in the submissionSAQ A-EP
Your server receives the card numberPasses through your serverSAQ D (most items)

In the January 2025 revision of SAQ A, Requirements 6.4.3 and 11.6.1 were replaced with an eligibility condition: the merchant must confirm its site is not susceptible to script attacks that could affect its e-commerce systems. Even the smallest-scope option still requires you to look after the site that sends customers to payment.

How it relates to Japan's rules

ItemPCI DSSInstallment Sales Act and Credit Card Security Guidelines
NatureIndustry standard from the card brands (required by contract)A law (Article 35-16) and its practical guide
What e-commerce merchants must doMeet the requirements for their scopeNon-retention or PCI DSS compliance, plus vulnerability measures (since v6.0) and EMV 3-D Secure (cardholder authentication)
Payment-page tamperingRequirements 6.4.3 and 11.6.1Five vulnerability measures (admin-panel access restriction, vulnerability assessments, etc.)

Non-retention alone does not stop malicious code planted on a payment page. That is why Japan's rules now require vulnerability measures on top of non-retention.

Real cases

  • APORITO online store (RIZAP) (2026): a malicious script was planted on the store, and card numbers, expiry dates and security codes entered between 1 May and 5 August may have been exposed. This kind of theft happens on the input page even when card data is not stored
  • ShopServe (E-store) (2026): malicious code ran on the servers and up to 8.85 million buyer records (cumulative) leaked. Card data was limited to partial numbers (first 6 and last 4 digits) and expiry dates; security codes were not held. Limiting what was stored limited the damage
  • British Airways (2018): card details entered on its website's payment pages were sent to a third party, affecting about 429,612 people. The UK authority fined it GBP 20 million under GDPR in 2020 (→ GDPR)

How to check your own online store

1

Find out where card numbers travel

Check your contract or the provider's dashboard for the integration type (redirect, iframe, JavaScript, or your own server). If unsure, ask your payment provider which SAQ applies to you.

2

List the scripts on your payment pages

List the external scripts loaded on the payment page and the order pages before it, and remove those you don't need. The Site Transparency Checker shows where a page can send data.

3

Restrict which scripts can load

Use a Content-Security-Policy (CSP) to limit where scripts can load from and where data can be sent. Check your current setup with the CSP Builder / Checker and the Security Headers Check.

4

Review the admin panel and tamper detection

Restrict the IP addresses that can reach the admin panel and turn on multi-factor authentication. Set up alerts when payment-page files or content change (tamper detection).

5

Look for card numbers or security codes left behind

Check order data, access logs, error logs, support emails and backups for recorded card numbers or security codes.

The safest choice: shrink the scope

This site's view: the best defense is not holding it

Meeting each PCI DSS requirement one by one is a lot of work; what helps most is the design where you don't hold card numbers in your own system at all. Hand card processing to a compliant provider and work only with a tokenized reference, and your environment's scope shrinks sharply. Same principle this site follows: with sensitive data, don't hold it, don't place it, minimize it. That's both compliance and the most effective defense. Check that card-handling screens and traffic never land in public directories or logs (→ keep secrets out of public directories).

Widening your scope (hard)

  • storing card numbers in your own DB
  • many servers and people can touch card data
  • audit and encryption surface grows, burden balloons

Shrinking your scope (safe)

  • hand card processing to a compliant provider
  • you only work with a tokenized reference
  • scope minimized, leak risk shrinks with it

Sources

FAQ

QWho does PCI DSS apply to?
A

Any business that stores, processes, or transmits credit-card data (card numbers, etc.) — e-commerce sites, physical stores, payment-handling SaaS. The rigor of proof scales with transaction volume, but 'small volume' doesn't mean 'exempt.' The moment you touch card data, the standard is in play.

QWhat does PCI DSS actually require?
A

Broadly: protect the network (firewalls, etc.), encrypt stored data with key management, eliminate defaults and weak credentials, least-privilege access control, encrypt data in transit, vulnerability management (patching, anti-malware), logging and monitoring, and regular testing. Less about one technology than an operating posture: protect sensitive data in the smallest scope, in depth, and keep records.

QWhat's the best way to reduce the compliance burden?
A

Don't hold card numbers in your own system in the first place. Hand card processing to a compliant payment provider and work only with a tokenized reference, and your environment's scope shrinks dramatically. Data you don't hold can't leak. That is the most effective defense, well beyond cards.

QWhat is the latest version of PCI DSS?
A

As of October 2026 the current version is v4.0.1 (published June 2024). v4.0 (published March 2022) was retired on 31 December 2024. v4.0.1 mainly corrects wording and clarifies intent; no requirements were added or removed. The requirements v4.0 marked as 'future-dated' (such as managing scripts on payment pages) became mandatory on 31 March 2025.

QDo e-commerce sites in Japan have to comply with PCI DSS?
A

In Japan, the Installment Sales Act requires card merchants to manage card numbers properly, and the practical guide is the Credit Card Security Guidelines from the Japanese credit-industry council. E-commerce merchants are generally expected either to achieve 'non-retention' (card data is never stored, processed or passed through their own systems) or to comply with PCI DSS. Since version 6.0 (March 2025), they must also take 'vulnerability measures' such as restricting admin-panel access and running vulnerability assessments, even with non-retention.

QCan I store the card security code (CVV)?
A

No. PCI DSS does not allow 'sensitive authentication data', such as the security code or magnetic-stripe data, to be retained after authorization (Requirement 3.3), even if encrypted. Also check that it isn't sitting in order data, logs or support emails.

QWhat does 'non-retention' of card data mean?
A

It means card numbers are never stored, processed or passed through your own servers and network. It is achieved by redirecting to the payment provider's page, or by sending the card number directly to the provider with its JavaScript (tokenization). But non-retention covers the server side only: if malicious code is planted on your payment page, card numbers typed into the customer's browser can still be stolen.