 |
Data SecurityAt Radiant we take the security of our systems very seriously and recognize that, as a provider of hardware and software designed to process electronic payments, we have an obligation to provide our clients with systems that meet the highest standards for protecting consumer information. In an age where theft of consumer data is an issue that is receiving intense media scrutiny, we deliver systems to our customers that meet or exceed the toughest cardholder security guidelines. Our security effort begins with a commitment to ensuring that our systems are validated as meeting the Payment Card Industry (PCI) Payment Application Data Security Standard (PA DSS). The PA DSS program defines industry best practices for security of cardholder data and includes requirements for encryption and storing of that data by payment applications, such as point-of-sale systems. Radiant maintains PA DSS validation of our point-of-sale software in all four of our industries, ensuring that all latest versions meet these guidelines. In each industry Radiant was among the first applications to achieve validation. More specific information about the security of each industry’s applications can be found on the individual industry security pages:It is important to note that using a PA DSS validated payment application is only one of many requirements that merchants are responsible for meeting under the PCI Data Security Standard (PCI DSS). Attached are two documents from Coalfire, a PCI Qualified Security Assessor (QSA), which provide a compliance overview of the payment card industry and some information on common PCI expenses for merchants. These documents demonstrate the scope of merchants’ responsibilities under the PCI DSS, which go well beyond the products provided by payment application vendors. Radiant’s commitment to data security goes beyond meeting PA DSS requirements. Throughout each industry we serve we are a leader in offering our clients new services designed to protect cardholder information. We are a leader in deploying:
|
 |