Back to all case studies
CASE STUDY PCI Standards

How We Delivered a First-Time PCI SSF Validation, Accepted by PCI SSC at First Submission, for a UK Retail Systems Provider

A UK provider of point-of-sale systems for retail chains develops a payment switch that routes transactions to the right acquirer or payment service provider. After PA-DSS was retired, it needed its first validation against the PCI Secure Software Standard. We completed the assessment in 3 months, going down to code level, and PCI SSC accepted the report at first submission.

Read the Full Story
CLIENT CONTEXT

Who the client is and the challenge they brought to us

Industry

The client is a UK integrator and provider of point-of-sale systems for retail chains. Its application works as a payment switch: it receives transactions from tills and terminals and routes them to the appropriate acquirer or PSP (Payment Service Provider). Until now, the application was validated against PA-DSS, the standard PCI SSC retired in favour of the PCI Software Security Framework (SSF).

The Challenge

The team knew PA-DSS, but the PCI Secure Software Standard follows a different logic. Instead of cardholder data alone, it protects “sensitive assets”, which include the critical functions and data that transaction security depends on, and this can widen the scope of requirements. The client was wary of documentation written only for the assessor and never used again. Midway through, it also changed the application architecture and how card data was processed.

What Was at Stake

Retail chains and their acquirers expect payment software vendors to hold a current validation. Without a PCI SSC listing, the application was losing ground in tenders and in conversations with existing customers. On the client side, the CTO and the Lead Developer were involved while continuing to drive product development.

OUR APPROACH

3 months of assessment and 2.5 months of PCI SSC review

  1. What PCI SSF Really Changes

    We started with the differences between the programmes. PA-DSS focused mainly on cardholder data, while the PCI Secure Software Standard asks which of the application’s assets are sensitive and how they are protected throughout its lifecycle. For a payment switch, that includes routing integrity and the credentials used to connect to acquirers. From day one, the team knew where the scope widened and why.

  2. Documentation for Everyday Use

    The client’s team wrote the documentation, and we advised on what the standard expects and how to describe it. We made sure nothing ended up “on the shelf”: the secure implementation guide for deployment engineers and the vulnerability handling process were written so the team would use them daily. Where an existing practice already met the purpose of a requirement, we described it rather than inventing a new one.

  3. Architecture Change Midway

    During the work, the client changed the application architecture and the way card data was processed. We replanned the assessment to cover the target version rather than the one being retired, and identified which earlier findings remained valid. The change neither stopped the project nor forced work to be repeated.

  4. An Assessment That Went Down to Code

    We did not stop at declarations. We reviewed the code of modules that process card data and handle routing, checked the cryptographic functions in use and tested the implementation guide instructions in a running environment. We looked at the application from its own perspective: what it receives, what it stores, what it passes on and who can change it.

  5. Report to PCI SSC

    We prepared the Report on Validation (ROV), with every conclusion clearly linked to evidence. The report passed our internal quality review before submission to PCI SSC.

  6. Acceptance and Listing

    The PCI SSC review took 2.5 months, and the report was accepted at first submission, with no round of corrections. Throughout, the client’s team could call us to discuss a solution without anyone counting the hours.

RESULTS & SUCCESS METRICS

Concrete figures showing the impact of the engagement

  • 3 months of PCI Secure Software assessment
  • 2.5 months of review by PCI SSC
  • 1st report submission accepted by PCI SSC
  • 100% of implementation guide instructions verified in practice
  • 0 rounds of corrections at PCI SSC

The board gained a current validation that strengthens conversations with retail chains and acquirers. Financially, acceptance at first submission meant no extra weeks of work and no cost of further rounds. The technical team has documentation it uses every day, and the architecture change midway did not stall validation.

What Our Client Says

Feedback from the client's team after the engagement

"After PA-DSS, we assumed PCI SSF was just a new version of the same thing, and at the first meeting Patronusec showed us what really changes and why. When we changed the architecture midway, they replanned the assessment to cover the target version. I could always pick up the phone and discuss a solution, without feeling that someone was counting every hour. This was a partner who cared about our outcome, not about the report for its own sake. The report went through PCI SSC at the first attempt, and for me that is the clearest measure of the work."

CTO UK retail systems provider

"For the first time, an assessor actually read our code. They understood the functions we use, asked about specific decisions in the routing module and tested the implementation guide instructions in a running environment, not on paper. They pushed us to write documentation we would use ourselves, and today the implementation guide is used on every deployment. Talking to someone who puts themselves in the application’s shoes changes how you look at your own code. Since this project we write more secure code, because we know what will be asked and why."

Lead Developer UK retail systems provider
Frequently Asked Questions

Answers to the questions people in a similar position ask us

The PA-DSS programme has closed, and PA-DSS validated applications can no longer be used in new deployments. Its successor is the PCI Software Security Framework with the PCI Secure Software Standard. Payment software vendors need the new validation to keep acquirers and customers confident.

The PCI Secure Software Standard is objective-based and protects the application’s sensitive assets, not just cardholder data. This places more weight on the integrity of critical functions, cryptography and vulnerability handling across the software lifecycle. In practice, the scope is often wider than under PA-DSS.

In this project, the assessment took 3 months and the PCI SSC review a further 2.5 months. Timing depends on the application’s complexity and the quality of its documentation. A report prepared so that PCI SSC has no need to request corrections shortens the whole process.
START THE CONVERSATION

Facing a Similar Challenge?

Moving from PA-DSS to the PCI Secure Software Standard, or building a new payment application? Let’s talk about an assessment that checks the code, not just the declarations.

Free 20-min scoping call
No obligation
Senior assessor not sales