The Payment Card Industry Data Security Standard (PCI DSS) was first introduced in December 2004, which was around the time when companies all around the world realised how valuable the internet was as a tool. As the internet era reached its maturity, companies started leveraging it as a means to receive payments from their customers online.
As this feature became commonplace amongst consumer behaviour, an increasing number of people became comfortable making purchases online via their credit cards. Although the ability to make payments online was seen as a convenience it made businesses and customers alike extremely vulnerable to a plethora of risks - malicious actors had more ways to steal credit card information from unaware prey whose networks hadn’t been secured.
As data theft reached an all-time high, five major card brands; Visa, Mastercard, Discover, American Express and JCB chose to implement the Payment Card Industry Data Security Standard (PCI DSS) to help prevent customer and business security breaches. With the birth of this standard and the PCI Security Standards Council - PCI compliance became an important step towards securing credit card payments all around the world.
To manage the standard, the payment brands established the PCI Security Standards Council in 2006, whose responsibility was to manage the ongoing evolution of the Payment Card Industry Data Security Standard. The current version is PCI DSS v4.0.1, published in June 2024.
PCI compliance soon became a self-regulated mandate, meaning that organisations and sellers are now liable for maintaining compliance through all stages of the payment process.
So while the council sets the standards and requirements, it became the payment brand’s responsibility to enforce them on sellers and organisations that chose to receive payments via their credit cards. For Australian businesses, this usually means your acquiring bank (the provider of your merchant facility) tells you how to validate compliance.
If you are an organisation that accepts, processes, transmits or stores credit card payments from customers, you’re required to comply with the Payment Card Industry Data Security Standard (PCI DSS). PCI DSS compliance helps organisations secure cardholder data from a potential data breach. It is not one-off compliance, but an ongoing process of ensuring an organisation has the necessary structures in place to protect customer data.
Cardholder or payment data is at stake if your organisation isn’t compliant with the PCI Data Security Standard, this data includes:
PCI DSS v4.0.1 calls this account data. The first three items are cardholder data, while sensitive authentication data must not be stored after a payment is authorised, even if it is encrypted.
If your organisation is required to store the above sensitive data, it is extremely important to make sure that you take appropriate steps to ensure the data is secured and safe from any malicious activity. To identify how your organisation may be vulnerable to any breach, it is useful to educate yourself on how these attacks may happen. Below are a few examples of how your valuable data can be stolen:
These are just a few of the ways valuable data can be stolen. As malicious actors get smarter, it is important for your organisation to level up its own efforts towards securing its payment life cycle, from accepting credit cards from customers at the point of sale to processing the payment till it reaches your merchant account.
The PCI Standards applies to all entities that store, process or transmit cardholder data including:
Not sure whether PCI DSS applies to your business? StickmanCyber’s PCI DSS compliance service deploys a 5-step methodology to help you build trust with your customers and secure your card transactions with PCI DSS compliance. Book a free consultation to talk to one of our experts.
Yes, in most cases. PCI DSS applies to any business that stores, processes or transmits cardholder data, or that could affect its security. If you never store the primary account number, the rules for stored card data don’t apply, but others still do, such as securing the systems that handle payments, managing the service providers that handle card data for you and having an incident response plan.
Yes. Card details read out over the phone are in scope, including any call or screen recordings that capture them. Sensitive authentication data, such as the card verification code, must not be kept after authorisation, even if it is encrypted. The PCI Security Standards Council’s guidance on protecting telephone-based payment card data describes ways to keep card details out of recordings, such as pause-and-resume recording and DTMF masking.
Yes. Requirement 9.4 of PCI DSS v4.0.1 covers media with cardholder data, and that includes paper. Printed or handwritten card details must be physically secured and kept in secure containers until they are destroyed. Once they’re no longer needed for business or legal reasons, they must be cross-cut shredded, incinerated or pulped so the data can’t be reconstructed.
The primary account number is the unique number on a credit, debit or prepaid card that identifies both the card issuer and the cardholder’s account. Under PCI DSS, the PAN is what defines cardholder data: if your systems store, process or transmit it, the cardholder data requirements apply, and details kept with it, such as the cardholder’s name or expiry date, must be protected too.
Start by mapping every way your business accepts, stores or passes on card data, including terminals, websites, phone orders and paper records. PCI DSS v4.0.1 asks you to confirm this scope at least once every 12 months. Your acquiring bank will tell you how to validate compliance based on your merchant level and, if you’re eligible to self-assess, the self-assessment questionnaire that matches your payment channels lists the requirements that apply.