Merchants taking card payments
Any business accepting cards online or in person is covered, in different ways by volume and set-up.
Card brands and acquirers expect proof that your cardholder environment holds up. Sumrite delivers gap analysis, penetration and segmentation testing, and retest evidence mapped to the requirements, so reviews move forward without surprises.
The Payment Card Industry Data Security Standard is maintained by the PCI Security Standards Council and enforced through the card brands and acquiring banks. It applies to any organisation that stores, processes or transmits cardholder data, or whose systems could affect the security of that data.
It is organised into 12 principal requirements under six goals, from network security and secure configuration to encryption, access control, logging and testing. The current version is v4.0.1, and requirements that were future-dated in v4.0 became mandatory on 31 March 2025.
How you prove compliance depends on your size and role. Smaller merchants usually complete a Self-Assessment Questionnaire (SAQ). Larger merchants and service providers generally undergo an on-site assessment by a Qualified Security Assessor, which produces a Report on Compliance (ROC) and an Attestation of Compliance.
These are summaries in plain language. The standard itself contains detailed sub-requirements and testing procedures.
Install and maintain network security controls, and apply secure configurations to all system components. Remove vendor defaults and close what you do not need.
Protect stored account data and use strong cryptography when cardholder data crosses open, public networks. Do not keep sensitive authentication data after authorisation.
Protect systems from malicious software and develop and maintain secure systems and software. For public-facing web applications, you must address new threats on an ongoing basis, for example through reviews or an automated technical solution.
Restrict access by business need to know, identify users and authenticate access, and restrict physical access to cardholder data. Multi-factor authentication is expected for access into the CDE.
Log and monitor all access to system components and cardholder data, and test security regularly. Requirement 11 covers wireless checks, internal and external vulnerability scans, penetration testing and change detection.
Support information security with organisational policies and programmes: a security policy, formal risk assessment, awareness training, incident response and third-party management.
Any business accepting cards online or in person is covered, in different ways by volume and set-up.
Service providers that handle card data for others face the most rigorous validation.
Even with a hosted payment page, your site design can affect scope and the SAQ you complete.
Acquirers and issuers set contractual expectations and ask merchants and providers for evidence.
The work is technical. The consequences of getting PCI DSS wrong show up in revenue, liability and reputation, which is why we report on it in the language of the boardroom first.
Acquirers can raise fees or restrict card acceptance if validation lapses, putting payment revenue at risk.
PCI DSS is enforced through contracts. Gaps can bring penalties and added costs after an incident.
A card data breach is public and costly. Tested controls reduce the chance of that headline.
Testing is due at least every 12 months and after major change. Clear owners avoid last-minute scrambles.
Timelines are typical ranges, not promises. Yours depends on scope, team size and how much is already in place.
Map every place card data is stored, processed or transmitted, including third-party services.
Use tokenisation, hosted payment pages and segmentation so fewer systems fall in scope.
Identify your merchant or service provider level and the SAQ or ROC you need.
Fix configuration, access, logging and policy gaps against the 12 requirements.
Complete vulnerability scans, penetration testing and segmentation testing, then fix and retest.
Complete the SAQ or ROC and submit your Attestation of Compliance to your acquirer or customers.
PCI DSS is one of the few standards that spells out penetration testing. Requirement 11.4 asks for a defined methodology, coverage of the whole CDE and critical systems, application-layer and network-layer tests, and retesting after fixes.
Testing follows an industry-accepted approach, covers the full CDE perimeter and critical systems, and includes both internal and external tests.
Penetration tests are performed at least every 12 months and after significant infrastructure or application changes by qualified testers.
Exploitable vulnerabilities found are corrected and the testing is repeated to verify the fix.
If segmentation reduces scope, it must be tested. Service providers must repeat this at least every six months.
Redirects and embedded forms still change which SAQ applies, and your site can still affect payment page security.
Requirement 11.4 expects expert-led testing and exploitation attempts, not just a scanner export.
If you claim segmentation, a tester must demonstrate it works. Otherwise the whole network can be pulled into scope.
Significant changes trigger a retest. Plan one after major releases or infrastructure moves.
PCI DSS is a team effort between your people, your auditor and your customers. We take the weight off all three.
From the first question about PCI DSS to the final report, you deal with one accountable team and one timeline.
We have taken more than 250 clients through SOC 2 and similar audits, so we know what reviewers ask for and what they accept.
We explain what PCI DSS means for your business, your roadmap and your customers before any technical work starts.
Where a third party issues the report or certificate, we route that step through local partner firms so you never have to manage a second vendor.
One accountable team takes you from scoping to retest. The people who test your systems are the people who explain the findings to your leadership.
Scope and controls compared with the 12 requirements, with a plan to reduce what is in scope.
Internal and external, application-layer and network-layer testing following a defined methodology.
Segmentation testing and checks that network, access and logging controls operate as documented.
Methodology, scope, findings and fix records laid out for your SAQ or ROC reviewer.
Fix guidance for engineers, then a retest confirming exploitable findings are closed.
A plain-language view of card data risk and progress for executives.
Every engagement ends with material written for two audiences: a plain-language view for executives and the board, and full technical detail for the engineers who fix things.
Your card data exposure and top risks in plain language.
Where card data lives and which systems fall in scope.
Reports and retest letters aligned to Requirement 11.4.
Findings with owners, severity and closure status.
The same Sumrite team stays with you while assessors and acquirers ask questions.
No. It is an industry standard enforced through contracts with card brands and acquiring banks. Non-compliance can lead to fines, higher fees or loss of the ability to take cards.
Yes. Requirement 11.4 requires external and internal penetration testing at least once every 12 months and after significant changes, using qualified and organisationally independent testers.
An SAQ is a self-assessment form many merchants complete. A ROC is a detailed report produced by a Qualified Security Assessor, typically for larger merchants and service providers.
PCI DSS v4.0.1 is the current version. The earlier v4.0 was retired at the end of 2024, and its future-dated requirements became mandatory on 31 March 2025.
Use a compliant payment provider with hosted fields or redirects, never store sensitive authentication data, tokenise card numbers and segment the systems that remain in scope.
We run the full engagement for you and route the formal assessment through our PCI QSA partner firms, so you deal with one team and one timeline.
Browse all 23 security and compliance frameworks or see our penetration testing services.
Tell us your scope, your deadline and who is asking. You get a fixed-scope quote and a named lead from day one.
Get a Quote →