If your software touches card payments, the Payment Card Industry Data Security Standard (PCI DSS) will shape parts of your architecture, whether or not your organization is the one being assessed. Developers rarely need to read the whole standard, but they do need to understand which design choices pull systems into scope and which requirements land directly on application code.
This guide covers the current version and dates as the PCI Security Standards Council (PCI SSC) states them, how software design affects scope, and the payment page requirements that most often surprise web teams. It is an engineering overview, not a compliance opinion: your acquirer, payment brands and assessor decide what applies to you.
What PCI DSS is and who it applies to
The PCI SSC describes PCI DSS as a baseline of technical and operational requirements designed to protect payment account data. It applies to entities that store, process or transmit cardholder data or sensitive authentication data, and to entities that could affect the security of the cardholder data environment. That includes merchants, processors, acquirers, issuers and service providers.
The Council also notes that whether a particular organization must comply, or validate compliance, is decided by the programs that manage compliance, such as the payment brands and acquirers. That is why the first conversation in any payment project should be with whoever owns your merchant relationship.
The current version and key dates
| Date | What happened, per PCI SSC |
|---|---|
| 11 June 2024 | PCI DSS v4.0.1 published as a limited revision |
| 31 December 2024 | PCI DSS v4.0 retired |
| 31 March 2025 | Effective date for the future-dated requirements introduced in v4.0 |
The Council describes v4.0.1 as a limited revision that corrects formatting and typographical errors and clarifies the intent of some requirements and guidance. It states that there are no added or deleted requirements in this revision, and that it does not change the 31 March 2025 effective date for the new requirements. The Council’s own pages refer to the standard as “PCI DSS v4.x”. Before you scope a project, check the PCI SSC Document Library for the version in force.
How software design drives scope
Scope is where engineering decisions matter most. Any system that stores, processes or transmits account data, or could affect its security, is a candidate for assessment. Every component you keep out of that path is one less component to secure, document and assess.
Common design patterns that reduce how much of your system handles card data include:
- Hosted payment pages or embedded payment fields from your payment provider, so card numbers are entered into the provider’s page or frame rather than your own form.
- Tokenization by the provider, so your systems store a token that is meaningless outside that provider, never the card number.
- Segmented networks and services, so the components that do touch payment data are isolated from the rest of your estate.
- No storage by default. If your business does not need to keep card data, design so it never lands in databases, logs, analytics events, error reports or support tickets.
None of these makes a system “compliant” on its own. They reduce the area that must meet the requirements, and your assessor confirms the result. Be especially careful with logs and observability tools: a single debug statement that prints a request body can bring a whole logging platform into scope.
Payment page scripts: Requirements 6.4.3 and 11.6.1
Web teams most often meet PCI DSS v4.x through two requirements about the payment page itself. On 10 March 2025, the PCI SSC published an information supplement titled Payment Page Security and Preventing E-Skimming, giving guidance for Requirements 6.4.3 and 11.6.1.
The Council explains the threat this way: e-skimming attacks target scripts running in the consumer’s browser to steal card data, and modern checkout pages rely on many external scripts. According to the Council, the two requirements focus on making sure payment page scripts are properly authorized, checked for integrity and monitored for tampering. They also address managing security-impacting HTTP headers, to prevent unauthorized changes to pages on the server or as rendered in the browser.
The guidance is aimed at any entity that processes e-commerce transactions, including those whose webpage can affect payment security by embedding a provider’s iframe. In other words, using an embedded payment frame does not automatically remove your page from the conversation; the page that hosts the frame still matters.
What this means in practice
For a development team, these requirements translate into engineering habits:
- Keep an inventory of every script that loads on payment pages, including third-party tags, with the business reason for each.
- Authorize changes. Adding or changing a script on a payment page should go through review, like any other code change.
- Check integrity. Browser features such as Content Security Policy and Subresource Integrity can help restrict which scripts load and detect changes. Confirm with your assessor how your chosen approach maps to the requirements.
- Detect tampering. Put a mechanism in place to alert on unauthorized changes to the payment page and its security-relevant headers as the browser receives them.
- Minimize scripts. The simplest way to secure a script is not to load it. Payment pages rarely need marketing tags.
A checklist for software teams
- Map the data flow. Draw where card data enters, moves and leaves. Mark every system it touches.
- Prefer provider-hosted capture and tokenization, so your systems handle tokens rather than card numbers.
- Scrub logs and telemetry. Add automated checks that block card-number-like strings from logs, analytics and error reports.
- Treat payment pages as sensitive code, with script inventories, change review and tamper detection.
- Secure the development lifecycle. Code review, dependency updates and security testing apply to every component in scope.
- Control access to production systems in scope, with individual accounts and strong authentication.
- Document decisions. Assessors ask why a system is in or out of scope; written design notes save time.
- Revisit scope with every major change, such as a new payment method, a new provider or a redesign of checkout.
Common pitfalls
- Assuming the provider covers everything. A provider can take on much of the burden, but your pages, integrations and operations still have responsibilities.
- Card data in unexpected places, such as customer support notes, screenshots, call recordings or spreadsheet exports.
- Third-party scripts added outside the release process, for example through a tag manager, directly onto checkout.
- Using the word “compliant” about a component. Compliance is assessed for an entity and its environment, not granted to a library or an API.
How Devacon can help
We design and build payment integrations that aim to keep card data out of your systems, using provider-hosted capture, tokenization and careful logging, and we implement payment page controls such as script inventories and change monitoring. A typical engagement includes a data-flow map and design notes your assessor can review. Learn more about our fintech integration services.
Sources
Facts in this article were checked against the sources above on November 17, 2026. Standards and products change, so check the source before relying on a detail. Related service: Fintech Integrations.