|
Data Security: Minding the Small Stores |
|
|
|
Anyone involved in the development or integration of software that stores, processes, or transmits payment-card transaction data for commercial products or internal systems knows that application security compliance is required of some but only recommended of others. Service providers, for example, have long been required to assess and demonstrate secure software developmental practices to successfully prove PCI compliance. Many commercial- product companies that develop stand-alone, deployed payment applications and point-of-sale (POS) systems, however, are not contractually obligated to become compliant and see payment application security as a recommended best practice. But in the past two years, several companies have voluntarily updated their application systems to adhere to Payment Application Best Practices (PABP) standards. Why? Because they understand that helping merchants become PCI-compliant makes good business sense for everyone.
Recent industry developments made payment application security compliance a standard requirement. With representation from major payment card brands, the PCI Security Standards Council recently adopted Visa’s PABP as the Payment Application Data Security Standard (PADSS).
Download the full PDF
|
Transaction Trends Home 
