Frequently Asked Questions

< Back to search page

Is it acceptable to make minor changes to a PA-DSS validated application and retain the existing version number?

FAQ Response

All changes to the software of a validated PA-DSS application must result in a new version number, even if there is no impact on PA-DSS requirements. This is necessary to ensure all parties involved can clearly determine whether a particular version of an application is PA-DSS validated.   Note that an application may have multiple versions listed as PA-DSS validated, but only those specific versions listed on the PCI SSC website are considered PA-DSS validated.        
 
If an Administrative Change  (as defined in the PA-DSS Program Guide) is made to an application such that there is no change to the software itself (for example, corporate entity name change), then the version number of the application may remain unchanged at the application vendor’s discretion. The application vendor should follow the process set out in the PA-DSS Program Guide in order for the List of Validated Payment Applications to be updated.

November 2012
Article Number 1182

Related Articles

If a merchant develops an application that runs on a consumer’s device (e.g. smartphone, tablet, or laptop) that is used to accept payment card data, what are the merchant’s obligations regarding PCI DSS and PA-DSS for that application?

What are the PA-DSS Expiry Dates?

What is the difference between a Validated Payment Application which is shown on the PCI SSC website as “Acceptable for New Deployments” and one which is shown as “Acceptable only for Pre-Existing Deployments”?

What is the Council’s guidance on the use of SHA-1?

How does use of an expired PTS device affect my PCI DSS compliance?