Examples of using Cardholder data in English and their translations into Thai
{-}
-
Colloquial
-
Ecclesiastic
-
Ecclesiastic
-
Computer
Protect your cardholder data.
Payment applications should not be saving any sensitive cardholder data.
Restrict access to cardholder data by business need-to-know.
Restrict physical access to cardholder data.
PCI Compliance protects cardholder data by maintaining a secure network for all cards, prevents fraud and other security breaches.
Restrict physical access to cardholder data.
Whenever you need to send us sensitive cardholder data, the first step is to create a token from your user's browser using the public key.
Track and monitor all access to network resources and cardholder data.
Encrypt transmission of cardholder data across open, public networks.
Install and maintain a firewall configuration to protect cardholder data.
Encrypt transmission of cardholder data across open, public networks.
Install and maintain a firewall configuration to protect cardholder data.
Best practices for securing cardholder data in a processing environment.
Use tokenization to track sales data across retail locations and limit access to sensitive cardholder data.
Learn how to ensure your cardholder data is secure.
It's the best way to confirm cardholder data is being safely handled and to expose any weaknesses that need to be addressed.
Acquirers and processors should experience a reduced threat of sensitive cardholder data being usable by fraudsters if compromised.
Visa has identified that certain payment applications are designed by software vendors to store sensitive cardholder data(i.e. full magnetic stripe data, CVV2 or PIN data) subsequent to transaction authorization. Storage of these cardholder data elements is in direct violation of the PCI DSS and Visa rules. Criminals are targeting merchants and agents that use these vulnerable payment applications and are exploiting these security vulnerabilities to find and steal cardholder data.
This guide provides the latest information and best practices to help merchants process Visa transactions, understand Visa products and rules and protect cardholder data while minimizing the risk of loss from fraud.
Stay alert and monitor all systems that have cardholder data or may have connections to the cardholder data environment.
On January 1, 2008, Visa implemented a series of mandates to eliminate the use of vulnerable payment applications from the Visa payment system. These mandates require acquirers to ensure that their merchants and agents do not use payment applications known to retain sensitive cardholder data(i.e. full magnetic stripe data, CVV2 or PIN data) and require the use of payment applications that are compliant to the PA-DSS.
Visa developed the Payment Application Best Practices(PABP) in 2005 to provide software vendors guidance in developing payment applications that help merchants and agents mitigate compromises, prevent storage of sensitive cardholder data(i.e. full magnetic stripe data, CVV2 or PIN data) and support overall compliance with the PCI DSS. In 2008, the PCI Security Standards Council adopted Visa's PABP and released the standard as the PA-DSS. The PA-DSS now replaces PABP for the purpose of Visa's compliance program.
