Frequently Asked Question
Is it acceptable to make minor changes to a PA-DSS validated application and retain the existing version number?
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.
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.
Article Number: 1182
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
Are Mobile Payments on COTS (MPoC) solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?
-
How can an entity meet PCI DSS requirements for PAN masking and truncation if it has migrated to 8-digit BINs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?