PCI DSS compliance is easier to manage when treated as a recurring security process rather than an annual form. This checklist helps online merchants identify their cardholder-data environment, choose an appropriate self-assessment path, secure payment pages, document controls, and establish monthly and quarterly checkpoints. Use it alongside the applicable PCI DSS materials, your payment processor’s instructions, and any requirements from your acquiring bank.
Overview
The Payment Card Industry Data Security Standard (PCI DSS) applies to organizations that store, process, or transmit payment card data, as well as systems and services that can affect the security of that data. The exact validation method depends on factors such as transaction volume, payment channels, card brands, acquirer expectations, and how your checkout is designed.
There is no single PCI compliance checklist that fits every merchant. A business using a fully hosted payment page may have a different scope from one that collects card details in its own browser form or sends card data directly through a payment API. A merchant using tokenization may reduce the systems that handle card data, but tokenization does not automatically remove all PCI responsibilities.
Begin with three questions:
- Where can cardholder data enter, move through, or leave the business?
- Which people, systems, vendors, and payment pages can affect its security?
- What validation document does the acquirer or payment brand require?
Confirm the applicable PCI DSS version, reporting deadline, and validation method before completing an assessment. The relevant Self-Assessment Questionnaire (SAQ) depends on the payment flow; selecting one based only on the name of a processor or gateway can produce an inaccurate result.
What to track
1. Scope and payment-flow inventory
Maintain a simple diagram for each checkout route, including ecommerce pages, mobile applications, hosted payment pages, payment gateways, payment APIs, recurring billing jobs, customer-support tools, fraud systems, webhooks, databases, and administrative consoles. Mark whether each component stores, processes, transmits, or can influence the security of cardholder data.
Record the processor, gateway, merchant account relationship, tokenization method, hosting provider, payment-page domains, and relevant third-party scripts. Review the inventory whenever a new payment method, plugin, integration, domain, or subscription workflow is introduced.
2. Payment-page security
- Keep an approved list of scripts that load on payment pages.
- Document why each script is needed and who can change it.
- Restrict publishing access to payment-page code and configuration.
- Monitor for unauthorized changes, unexpected redirects, and injected code.
- Use a controlled change process with a ticket, reviewer, date, and rollback plan.
- Confirm that hosted fields, redirects, iframes, or API integrations behave as intended in production.
Third-party JavaScript deserves particular attention because a script that can read or alter checkout content may affect payment security even when your server never stores the full card number.
3. Access control and authentication
Keep a current access list for payment dashboards, cloud accounts, code repositories, databases, customer-support tools, and security systems. Assign access according to job need, use unique accounts, remove access promptly when roles change, and review privileged accounts separately. Protect administrative access with strong authentication controls required by your applicable PCI DSS obligations and internal policy.
Track the owner, purpose, last review date, and approval for each privileged account. Shared credentials make investigations and access reviews difficult; replace them with individual accounts wherever the system permits.
4. Vulnerability management
Track operating systems, applications, dependencies, payment integrations, endpoint protection, vulnerability scans, penetration tests where applicable, and remediation owners. Record the discovery date, affected asset, severity, compensating action if used, target date, and closure evidence.
Do not treat a clean scan as proof that the entire environment is secure. Review configuration, unsupported software, exposed administration interfaces, secrets in code, and dependencies used by payment pages or payment APIs.
5. Evidence and records
Store evidence in a restricted, organized location. A practical evidence register can include:
| Control area | Useful evidence | Review point |
|---|---|---|
| Scope | Data-flow diagram, asset inventory, payment-flow description | After every architecture change |
| Access | User list, approvals, termination records, access-review signoff | Monthly or quarterly, according to policy |
| Payment pages | Script inventory, change tickets, monitoring alerts, test results | At each release and scheduled review |
| Vulnerability management | Scan reports, patch records, exceptions, remediation proof | According to the applicable control schedule |
| Security awareness | Training assignments, completion records, policy acknowledgments | At onboarding and recurring refresh |
| Incident readiness | Contact list, response plan, exercise notes, incident tickets | At least during planned exercises and after incidents |
Cadence and checkpoints
Use a calendar rather than relying on memory. The following schedule is a practical operating model; adapt it to the applicable requirements, risk profile, and assessor or acquirer instructions.
For every release or payment-flow change
- Update the data-flow diagram and asset inventory.
- Review new scripts, SDKs, vendors, permissions, and webhooks.
- Test success, decline, refund, cancellation, and authentication paths.
- Confirm logs and alerts still identify relevant administrative and payment events.
- Attach approval and test evidence to the change record.
Monthly
- Review privileged users and remove unnecessary access.
- Check payment-page monitoring alerts and unresolved security findings.
- Review failed logins, unusual administrative activity, and dormant accounts.
- Check that backups, security tools, and endpoint controls are reporting as expected.
- Review open remediation items and escalate overdue high-risk gaps.
Quarterly
- Reconfirm the payment-flow inventory with engineering, finance, support, and operations.
- Review vendor responsibilities, processor documentation, and service changes.
- Test a sample of access removals, change approvals, and vulnerability closures.
- Review incident contacts and perform a tabletop exercise or equivalent readiness check.
- Reassess the selected SAQ or reporting path if the checkout architecture has changed.
Before annual validation
Allow time to reconcile evidence, resolve inconsistent dates, confirm signatures or approvals, and explain exceptions. Start with scope, because an incomplete scope statement can undermine otherwise well-documented controls.
How to interpret changes
A change in payment technology is a compliance signal, not merely an engineering detail. Moving from a hosted page to embedded fields, adding a mobile SDK, introducing recurring billing, or enabling a new payment API may change which systems and people are in scope.
Look for patterns rather than isolated findings. Repeated late access reviews may indicate weak ownership. Recurring script changes without tickets may indicate an uncontrolled release process. A growing list of vulnerability exceptions may indicate that asset ownership or patch planning needs attention. Several chargebacks or suspected account-takeover events may justify reviewing authentication, fraud rules, logging, and customer-support verification together.
When a gap is found, document it in a remediation register:
- Gap: State the missing or ineffective control in one sentence.
- Risk: Describe what could be exposed or disrupted.
- Owner: Name the accountable team or individual.
- Action: Specify the technical or procedural fix.
- Due date: Set a date based on risk and dependencies.
- Interim measure: Record temporary restrictions, monitoring, or review.
- Closure evidence: Define the report, ticket, test, or approval needed to close it.
Do not label a gap resolved solely because a policy was written. Verify that the control operates in practice and retain evidence of that operation.
When to revisit
Review this checklist at least monthly for operational items and quarterly for scope, access, vendor, and readiness checks. Revisit it immediately after a payment processor or gateway change, a new payment page or domain, a major software release, a migration to cloud infrastructure, a new recurring-billing flow, a security incident, or a change in the required validation document.
Refresh the article’s references and internal procedures whenever PCI SSC publishes revisions or updated guidance, and verify the applicable requirements at least every six months. Keep the current SAQ instructions, reporting timelines, payment-page expectations, and assessor or acquirer requests with the compliance calendar rather than relying on an old copy.
For the next review, assign one owner and complete these actions: export the current payment-flow inventory, list every payment-facing domain and integration, run an access review, reconcile open vulnerabilities, sample recent payment-page changes, and save the evidence in one controlled location. If the scope or payment flow is unclear, pause the assessment and confirm the correct approach with your acquiring bank, payment provider, or qualified assessor.
For related implementation controls, see the Payment API Integration Checklist, the 3D Secure 2 and Strong Customer Authentication guide, and the Chargeback Prevention Guide.