Start hereMap card data and confirm validation route
~101 days leftOpen step
Guide library
Industry standard Global

PCI DSS

Payment Card Industry Data Security Standard v4.0.1

Scope cardholder data and validate the controls that protect your payment environment.

Who it applies to

Merchants and service providers that store, process or transmit cardholder data, or can affect the security of the cardholder data environment.

What you’ll produce

Validation artifacts accepted by the acquirer, payment brand or other compliance-accepting entity.

A payment service provider can reduce scope. Merchant responsibilities and applicable requirements still depend on the integration and SAQ eligibility.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

How many ways can customers pay?
Ask Finance and Product about embedded checkout, redirects, support calls, invoicing, terminals and refunds. Confirm validation route and due dates with the acquirer or other compliance-accepting entity in writing.
Which integration creates scope and effort?
Ask Engineering to show how the browser and backend handle or can affect card data. Budget for applicable scans, penetration testing, remediation, segmentation work and assessor time.
What does each provider actually cover?
Procurement obtains scope-specific proof and shared responsibility from each service provider. Assign a person to verify the provider’s services, dates and protections for your integration.

How to spend the first week

  1. Run a test purchase, refund and support interaction. Look for card data in the browser, backend, logs, exports and support tickets.
  2. Map each payment channel and confirm the validation route with the accepting entity. Give business owners a list of every connected system that could affect it.
  3. Book the first control and segmentation checks. Agree a schedule for scans, evidence capture and remediation ahead of submission.

What to review each week

Track current provider attestations, unresolved scan or test findings, changes to payment channels and the next validation submission.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

PCI DSS kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Map card data and confirm validation route · Payments lead + acquirer [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Run a test purchase, refund and support interaction. Look for card data in the browser, backend, logs, exports and support tickets.
2. Map each payment channel and confirm the validation route with the accepting entity. Give business owners a list of every connected system that could affect it.
3. Book the first control and segmentation checks. Agree a schedule for scans, evidence capture and remediation ahead of submission.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Where does cardholder data actually flow and what can affect its security?
  • Has your acquirer confirmed your validation method and SAQ eligibility?

Worked scenario

A retailer moves checkout to a payment provider but keeps scripts on its own storefront. Its payments lead maps what the integration can influence before asking the acquirer to confirm the scope and validation route.

What to read next

FROM THE SOURCE

Cases and numbers

Council clarification · February 2025

An embedded checkout changes the SAQ A script question

PCI SSC’s FAQ 1588 explains that a particular SAQ A script-attack criterion applies when the merchant embeds a provider’s payment page or form. It describes a different treatment for redirects and fully outsourced payment links.

What to check Record how checkout actually loads. If you embed a payment form, document the script protections or obtain the provider’s confirmation for your implementation. Confirm the full SAQ choice with the organization that accepts your validation.

PCI SSC FAQ 1588 (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
Plan evidence for PCI DSS and other programs Practice reviewing an evidence packet
The whole journeyabout 101 days across 4 steps
  1. 01Map card data and confirm validation routePayments lead + acquirer · ~14 days
  2. 02Protect the environmentSecurity + engineering · ~45 days
  3. 03Test and validateCompliance lead + QSA or ASV as applicable · ~28 days
  4. 04Maintain scope and monitoringPayments operations · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map card data and confirm validation routePayments lead + acquirerBefore assessmentSet a start dateData-flow diagram; Scope inventory; Validation decisionOpen
Protect the environmentSecurity + engineeringBefore validationSet a start dateControl matrix; Segmentation evidence; Provider attestationsOpen
Test and validateCompliance lead + QSA or ASV as applicableAt required cadenceSet a start dateScan and test reports; SAQ or ROC; AOCOpen
Maintain scope and monitoringPayments operationsOngoingSet a start dateChange log; Recurring validation calendarOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Map card data and confirm validation route

    Who Payments lead + acquirer When Before assessment

    Trace payment flows, inventory systems that can affect the environment and check the exact SAQ eligibility or ROC requirement.

    How to do this step

    Before you start

    Payment channel list, processor contracts, test transaction, integration diagrams, merchant IDs and merchant support procedures.

    1. Trace a transaction end to end, including refunds, manual payments and logs. Record where card data is entered, transmitted and stored, and which systems may affect its security.
    2. Mark the cardholder data environment, connected systems and security-impacting systems. Record how each exclusion is separated or justified.
    3. Compare your flows to the current eligibility criteria and ask the accepting entity which form, reports and timing it expects.

    What a reviewer should see

    The diagram separates browser, merchant and provider functions, and each row in the scope inventory links to a real integration and owner.

    When to escalate

    Raise unexpected card data in support, exports or logs through the incident process. Revisit the validation route if an eligibility assumption fails.

    What to produce

    Data-flow diagramDiagram worksheet

    Gather first

    • System and vendor inventory
    • Examples of live transactions or data events
    • Approved boundaries and information categories

    How to prepare it

    1. Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
    2. Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
    3. Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Source
    Web checkout
    Destination
    Billing API in EU region
    Data and purpose
    Order reference and billing email to send the receipt
    Protocol and boundary
    HTTPS, crosses from public network into hosted production
    Owner and validation
    Billing owner, validated against request logs on 2026-11-12

    Check before handing it over

    An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.

    Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.

    Scope inventorySpreadsheet

    Gather first

    • Asset exports or system discovery
    • Service owner interviews
    • Approved scope and architecture

    How to prepare it

    1. Export a dated baseline from the source system. Give each asset, service or record class a stable ID and remove duplicates without losing links to the source.
    2. Add ownership, purpose, sensitivity and any vendor or system it depends on. Mark unknowns explicitly and assign them to someone to resolve.
    3. Reconcile the register against an independent source such as cloud billing or the production deployment list. Set a refresh cadence and an owner.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    ID
    SYS-014
    Item
    Production billing database
    Owner
    Platform operations
    Location and purpose
    Production EU region, stores invoice and account data
    Impact and dependencies
    High. Identity provider and managed backups.
    Verified on
    2026-11-10, cloud inventory export

    Check before handing it over

    Each item has one accountable owner. The source and as-of date let a reviewer trace it back.

    Share the reviewed inventory with the people building the control, privacy or testing scope.

    Validation decisionSpreadsheet

    Gather first

    • Official rules or contract and version
    • Product, organization or processing facts
    • Jurisdiction and exception criteria

    How to prepare it

    1. Start with one row per rule, decision or authority. Record the citation, scope test and facts that determine whether it applies.
    2. Distinguish a confirmed decision from an open question. Record the obligation, any exception or approved route, owner and timing.
    3. Have technical and legal or program owners review the decision against the source. Revisit on a new market, product change or rule update.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement or decision
    REG-05, determine whether the new processing activity requires an assessment.
    Source and trigger
    Current regulator guidance, high-risk processing indicators
    Facts and evidence
    New dataset includes sensitive attributes. Data map P-024.
    Outcome and rationale
    Assessment required before release. Privacy lead to confirm scope.
    Owner and review
    Product privacy owner, reassess before launch and on new purposes.

    Check before handing it over

    A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.

    Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.

  2. 02

    Protect the environment

    Who Security + engineering When Before validation

    Implement applicable requirements, verify segmentation, secure payment pages as applicable and assign all responsibilities shared with providers.

    How to do this step

    Before you start

    Scope inventory, validation route, provider attestations and current requirement set.

    1. Map each applicable requirement to a system owner, implementation and test. Check actual configurations and payment flows before recording findings as resolved.
    2. Where segmentation reduces scope, document allowed traffic and prove isolation with the required tests. Verify vendor coverage for the specific service and responsibilities.
    3. Have the payment team exercise a safe example of unauthorized script or configuration change detection where applicable. Capture alerts, response and corrective action.

    What a reviewer should see

    Evidence shows tested controls on named production assets and identifies which applicable duties the merchant and providers carry.

    When to escalate

    Escalate a scope dependency without current evidence, unexplained checkout scripts or failed segmentation.

    What to produce

    Control matrixSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Segmentation evidenceMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Provider attestationsIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

  3. 03

    Test and validate

    Who Compliance lead + QSA or ASV as applicable When At required cadence

    Maintain scans and testing where applicable. Complete the correct SAQ or ROC and accompanying Attestation of Compliance.

    How to do this step

    Before you start

    Applicable controls, approved scope, scan and test results, latest reporting forms and acceptance instructions.

    1. Track each required scan and test to the assets and period it covers. Fix and rescan or retest failures under the applicable rules.
    2. Answer each self-assessment item with evidence, or support the assessor’s Report on Compliance. Route unresolved exceptions and any special treatment through the applicable process.
    3. Reconcile the Attestation of Compliance to the assessed legal entity, channels and scope. Submit through the accepting entity’s designated channel and record the receipt.

    What a reviewer should see

    The submission file contains applicable dated test results, the final validation record and receipt, with evidence mapped to responses.

    When to escalate

    Raise any control without support before a signer attests, and tell Finance about anything that threatens the validation deadline.

    What to produce

    Scan and test reportsMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    SAQ or ROCOfficial form

    Gather first

    • Current issuer form and eligibility rules
    • Agreed environment and assessor route
    • Evidence for every applicable response

    How to prepare it

    1. Confirm which current version, form and signing route apply. Download it from the authority or obtain the approved version from your assessor.
    2. Cross-reference each applicable question to evidence. Document the basis for excluded or inapplicable items. Reconcile scope and dates across companion documents.
    3. Have the authorized signatory and assessor review where required. Submit the original completed form using the approved channel and record acceptance.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Form and version
    Current official form for the confirmed validation route
    Question or section
    Identify the item or form section without copying form text.
    Evidence reference
    EV-021, annotated review and scope evidence
    Reviewer and outcome
    Authorized signer and assessor where required
    Submission record
    Keep date, recipient and reference after acceptance.

    Check before handing it over

    The original form version, scope and signers match the validation route and each response has supporting evidence.

    Use the issuer’s official form for validation. The download is a preparation worksheet.

    AOCOfficial form

    Gather first

    • Current issuer form and eligibility rules
    • Agreed environment and assessor route
    • Evidence for every applicable response

    How to prepare it

    1. Confirm which current version, form and signing route apply. Download it from the authority or obtain the approved version from your assessor.
    2. Cross-reference each applicable question to evidence. Document the basis for excluded or inapplicable items. Reconcile scope and dates across companion documents.
    3. Have the authorized signatory and assessor review where required. Submit the original completed form using the approved channel and record acceptance.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Form and version
    Current official form for the confirmed validation route
    Question or section
    Identify the item or form section without copying form text.
    Evidence reference
    EV-021, annotated review and scope evidence
    Reviewer and outcome
    Authorized signer and assessor where required
    Submission record
    Keep date, recipient and reference after acceptance.

    Check before handing it over

    The original form version, scope and signers match the validation route and each response has supporting evidence.

    Use the issuer’s official form for validation. The download is a preparation worksheet.

  4. 04

    Maintain scope and monitoring

    Who Payments operations When Ongoing

    Track changes affecting scope or SAQ eligibility and maintain recurring scans, testing and validation as applicable.

    How to do this step

    Before you start

    Submitted validation, scope diagram, platform change plans, monitoring schedule and provider evidence expiration dates.

    1. Put required recurring work on the owners’ calendars, including applicable scans, reviews and changes needing retest.
    2. Review payment changes before deployment. Update the data flow and revisit SAQ eligibility if the merchant’s frontend, processor or payment channels change.
    3. Record provider validation updates and maintain current contacts for suspected payment compromise.

    What a reviewer should see

    A new checkout change has a documented scope decision and the required testing. Each recurring obligation has an owner, due date and evidence link.

    When to escalate

    Raise a lapse in validation or provider coverage and any new payment channel that might change the agreed route.

    What to produce

    Change logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

    Recurring validation calendarSpreadsheet

    Gather first

    • Current obligations, expiry dates or audit window
    • Delivery dependencies and owner availability
    • Official rules or engagement confirmation

    How to prepare it

    1. Separate official due dates, trigger-based clocks and team target dates. Write down the event or rule that starts each clock.
    2. Work backward from each milestone. Include lead time for review and submission, and name the owner and backup.
    3. Cross-check the dates with the source or reviewer and make reminders actionable. Record the next verification point for changing rules.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Milestone
    Quarterly access review approved
    Date and kind
    2026-12-18, internal target
    Trigger or source
    Internal access control schedule v3
    Prerequisite
    Access export by 2026-12-09
    Owner and reminder
    IAM lead, remind one week before
    Status
    Scheduled

    Check before handing it over

    Every external deadline links to a real source. Planning targets are visibly marked.

    Add approved dates to the team calendar and share them with the people scheduled to deliver or review.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes