Cybersecurity Blog for Australian Businesses | StickmanCyber

PCI DSS Requirements and Merchant Levels for Australian Businesses

Written by Ajay Unni | Nov 16, 2026, 12:09:13 PM

If your organisation or business accepts credit card payments from any of the five major credit card brands; American Express, Visa, Mastercard, Discover and JCB then you are expected to be PCI compliant within a range of levels depending on the volume of your transactions. PCI DSS applies to merchants, service providers, processors, acquirers, issuers and all other entities that store, process or transmit cardholder data, or that could affect its security. Our past blog outlined what is PCI DSS and the benefits of PCI DSS compliance.

In this blog, we share a breakdown of the PCI DSS requirements, the various merchant and service provider levels, how each level validates compliance and the steps to becoming compliant.

6 Goals and 12 Requirements of PCI DSS Compliance

The PCI Security Standards Council sets out six goals and 12 principal requirements in place in order to reach those goals. The titles below are from the current version of the standard, PCI DSS v4.0.1.

They are as follows:

Goal 1: Build and Maintain a Secure Network and Systems

  • Requirement 1: Install and Maintain Network Security Controls
  • Requirement 2: Apply Secure Configurations to All System Components

You’ll need to have effective network security controls, such as firewalls, in place to keep customers’ sensitive financial information secure. When it comes to creating passwords, they should always be strong and unique. They should not be passwords that the software vendor already had in place because this can create vulnerabilities.

Goal 2: Protect Account Data

  • Requirement 3: Protect Stored Account Data
  • Requirement 4: Protect Cardholder Data with Strong Cryptography During Transmission Over Open, Public Networks

If you store customers’ data for any length of time, you’ll need to have multiple levels of defence in place to protect it. This can include both digital security such as authorisation and authentication as well physical security such as guarding servers/equipment and monitoring who can access them. Sensitive authentication data, such as the card verification code, must not be stored after authorisation.

In terms of encryption, this simply means that plaintext is converted into ciphertext so that it cannot be decoded by unintended parties. Although this doesn’t eliminate threats entirely, it significantly reduces any risks.

Goal 3: Maintain a Vulnerability Management Program

  • Requirement 5: Protect All Systems and Networks from Malicious Software
  • Requirement 6: Develop and Maintain Secure Systems and Software

Not only must you install effective anti-malware software, it must be regularly updated in order to thwart attacks. You should remember that this isn’t a one-off type of deal. Malware and other attacks become increasingly advanced over time, so maintaining anti-malware best practices is a must.

When it comes to systems and applications, you’re responsible for using a hosting provider who is PCI compliant and for using a system that automatically alerts you whenever threats or vulnerabilities are detected. This way you can act quickly and hopefully prevent a minor issue from escalating into a major one.

Goal 4: Implement Strong Access Control Measures

  • Requirement 7: Restrict Access to System Components and Cardholder Data by Business Need to Know
  • Requirement 8: Identify Users and Authenticate Access to System Components
  • Requirement 9: Restrict Physical Access to Cardholder Data

This mainly relates to physical security and restricting who has access to sensitive information. Limiting the number of individuals who have access to cardholder data reduces the chance of an incident occurring.

Identifying users involves providing each individual with a unique ID and following authentication best practices. PCI DSS v4.0.1 requires passwords of at least 12 characters, multi-factor authentication for all non-console access into the cardholder data environment, and password changes every 90 days only where a password is the sole authentication factor. As for restricting physical access, this can include taking serious security measures when accessing servers such as implementing biometrics systems (e.g. fingerprint and retinal scanning) as well as surveillance cameras.

Goal 5: Regularly Monitor and Test Networks

  • Requirement 10: Log and Monitor All Access to System Components and Cardholder Data
  • Requirement 11: Test Security of Systems and Networks Regularly

This is pretty straightforward and involves using systems that log whenever someone accesses them and tracking who those individuals are. You’ll also want to get into the habit of routinely testing all aspects of security to ensure that it’s functioning properly, including external vulnerability scans by an Approved Scanning Vendor (ASV) at least once every three months and penetration testing at least once every 12 months.

Goal 6: Maintain an Information Security Policy

  • Requirement 12: Support Information Security with Organizational Policies and Programs

Incorporating information security into your company’s policies will provide both employees and contractors with a detailed set of guidelines to follow. This will highlight which behaviours are and are not acceptable, how to address potential threats, which procedures to follow and so on.

It’s also smart to educate employees and contractors on information security best practices. The Office of the Australian Information Commissioner (OAIC) found that human error caused 37% of the data breaches notified to it between January and June 2025. Equipping these individuals with the right knowledge can be a tremendous asset.

What are the levels of PCI Compliance?

There are four unique levels of PCI compliance that merchants are divided into based on card transaction volume (credit, debit and prepaid) per annum. Australian acquirers such as Westpac count Visa or Mastercard transactions per year. Card brands can also move a merchant to a higher level: Mastercard, for example, can require any merchant to meet its Level 1 requirements to minimise risk to the payment system.

Level 1 Merchants

This level consists of merchants that process more than 6 million transactions over a period of 12 months through all channels (card present, card not present, eCommerce).

If you are a level 1 merchant you need to:

  1. Complete an annual Report on Compliance (ROC) through a Qualified Security Assessor (QSA) company
  2. Complete quarterly network scans by an Approved Scanning Vendor (ASV)
  3. Complete the Attestation of Compliance Form

Level 2 Merchants

This level consists of merchants who process between 1 and 6 million transactions over a period of 12 months through all channels (card present, card not present, eCommerce).

If you are a level 2 merchant you need to:

  1. Complete an Annual Self-Assessment Questionnaire (SAQ)
  2. Complete a quarterly network scan by an ASV
  3. Complete the Attestation of Compliance Form

Depending on how you handle card data, you may also need a QSA.

Level 3 Merchants

This level consists of merchants who process more than 20,000 and up to 1 million transactions over a period of 12 months via eCommerce processing methods.

If you are a level 3 merchant you need to:

  1. Complete an Annual Self-Assessment Questionnaire (SAQ)
  2. Complete a quarterly network scan by an ASV
  3. Complete the Attestation of Compliance Form

Level 4 Merchants

This level consists of all other merchants, whatever their acceptance channel.

If you are a level 4 merchant you need to:

  1. Complete an Annual Self-Assessment Questionnaire
  2. Complete a quarterly network scan by an ASV
  3. Complete the Attestation of Compliance Form

Service Provider Levels

Service providers are divided into two levels:

LevelMastercardVisa
Level 1All Third Party Processors (TPPs), plus Data Storage Entities (DSEs) and Payment Facilitators with more than 300,000 total combined Mastercard and Maestro transactions a yearAny service provider that stores, processes or transmits 300,000 or more Visa transactions a year
Level 2DSEs and Payment Facilitators with 300,000 or fewer total combined Mastercard and Maestro transactions a yearAny service provider that stores, processes or transmits fewer than 300,000 Visa transactions a year

Level 1 service providers validate with an annual assessment by a QSA that results in a Report on Compliance, while Level 2 service providers validate with an annual SAQ.

Validation of Compliance at Each Level

Every merchant and service provider must validate its compliance with the PCI DSS every year, through either a ROC by a QSA or an SAQ, together with an Attestation of Compliance (AOC) and quarterly ASV scans where they apply. The third-party payment application validation that used to sit alongside these requirements no longer applies: the PCI Security Standards Council retired the Payment Application Data Security Standard (PA-DSS) on 28 October 2022 and replaced it with its Software Security Framework.

Identifying what merchant level your organisation comes under

Merchants can consult with their merchant services provider to help assign a level of PCI compliance or utilise the tools provided to them by their merchant services provider.

Organisations that fall under levels 1-3 tend to have compliance requirements of higher complexity, mainly because of the size and nature of their business. Many organisations that fall under these levels tend to take the help of internal IT and compliance teams to implement and monitor their compliance programs.

On the other hand, smaller to medium-sized businesses fall under the level 4 category. Unlike the higher levels, level 4 merchants may find their compliance requirements to be simpler. However, without the help of an internal IT infrastructure (assuming your business doesn’t have one) small to medium-sized businesses can find it challenging to meet their compliance requirements.

About the SAQ Questionnaire

A Self-Assessment Questionnaire (SAQ) is designed as a self-validation tool to assess security for cardholder data. The questionnaire includes a set of questions for each applicable PCI DSS requirement. There are a number of questionnaires to meet different merchant environments.

Achieving PCI DSS Compliance

All merchants, service providers and third parties that are involved in storing, processing or transmitting cardholder data are expected to comply with the PCI DSS. Although the PCI Security Standards Council manages the PCI DSS, every card brand has its own strategy to enforce compliance on its clients, and acquirers decide how their merchants validate. Requirements for validation of compliance vary for each card brand, but in general, the level of the organisation determines what path should be taken to achieve PCI DSS compliance.

Usually the following steps must be taken by an organisation in order to achieve PCI DSS compliance:

  1. Determine the scope of the PCI DSS’s relevance to the organisation.
  2. Test compliance to the standard on a sample of system components.
  3. Get compensating controls validated by a QSA in case the organisation cannot meet a particular requirement due to a legitimate and documented technical or business constraint.
  4. Submit the Report on Compliance (ROC) or SAQ, together with the Attestation of Compliance (AOC).
  5. Clarify any ambiguities in the report, if requested by the acquiring bank.

PCI DSS Requirements Scope

Achieving PCI DSS compliance can be a daunting process, but will be much worse if a proper scoping exercise is not done before starting to complete the requirements. It is very important for organisations to understand and minimise the scope of the PCI DSS in order to make the process as easy as possible. The Cardholder Data Environment (CDE) forms the scope of the PCI DSS and consists of the processes, people and technology used for storing, processing and transmitting cardholder data or sensitive authentication data. System components with unrestricted connectivity to the CDE, or that could affect the security of account data, are also included in the scope. These include servers, network devices, end-user devices, cloud components, applications and any other components connected to cardholder data.

Once the scope is defined, it must be checked for accuracy to ensure that all flows and locations of cardholder data are included in the scope. The following steps should be carried out:

  1. Identify and document the flows in the CDE and verify that no data exists outside the currently defined CDE.
  2. Any data that is not currently defined as a part of the scope should either be deleted, safely migrated elsewhere or included in the scope.
  3. Keep all documentation showing how the scope was determined to hand it over to the assessor for scope verification.

PCI DSS v4.0.1 asks merchants to confirm their scope at least once every 12 months and after significant changes, and service providers at least once every six months.

Choosing a Qualified Security Assessor for your PCI DSS Compliance

Once an organisation has taken all necessary measures to implement the PCI DSS on its systems, it may need to hire the services of a Qualified Security Assessor (QSA) to conduct on-site compliance verification and security assessment. QSA companies are qualified by the PCI SSC, and their assessors are trained and qualified by the Council.

The QSA serves to verify a merchant’s compliance to the PCI DSS by completing a Report on Compliance (ROC), which is then sent to the acquiring bank of the merchant. The bank then reports the merchant’s compliance status to the relevant card brand.

Always select a QSA that has past experience of working with similar organisations and understands your business well. Also, maintaining goodwill and a long-term relationship with your QSA is important to help you with ongoing vulnerability assessments and remediation measures.

The Benefits

Besides the obvious advantage of having more secure payment processors and protecting cardholders’ data, there are some distinct benefits that compliance with the PCI DSS can have for your company. Perhaps the biggest relates to finances.

Non-compliance can lead to fines or penalties from your acquiring bank or the card brands, depending on the nature of the penalty and the time and resources required to investigate it. You can find further details in our blog on the consequences of PCI DSS non-compliance. By staying compliant, you greatly reduce the odds of your organisation getting hit with costly fines.

It’s also important to note that there are other costs that can stem from a data breach, which can include damages from lawsuits, loss of business and so on. Being compliant can save you from financial backlash and even factor into your company’s longevity.

This is also critical for gaining the trust of your customers. Shoppers are more wary than ever and want to ensure that their sensitive financial and personal information is being safeguarded.

Baymard Institute’s checkout research lists not trusting a site with credit card information among the top reasons for online shopping cart abandonment, cited by 19% of shoppers who abandoned an order. PCI compliance and being diligent about transaction security is a huge selling point and is likely to increase your overall conversion rate.

Finally, there’s the issue of brand equity. Even a minor data breach can quickly sour your organisation’s reputation. Consumers will become sceptical and may choose to go with competitors with whom they trust.

In a world where nothing is secret and negative press can go viral in hours, protecting your brand reputation is essential.

How StickmanCyber Can Help

StickmanCyber is a PCI DSS Qualified Security Assessor (QSA) company recognised by the PCI Security Standards Council. This was made possible with the help of a hardworking and experienced team, after thorough inspection and scrutiny by the PCI Security Standards Council. We carry out assessments for merchants and service providers across Australia.

As a QSA company, we can help you to:

  • Verify the technical information provided by the merchant
  • Provide support in achieving compliance
  • Carry out independent assessment to confirm compliance
  • Define the assessment scope
  • Ensure observance of PCI DSS assessment procedures
  • Provide onsite validation of compliance
  • Evaluate compensating controls
  • Produce a final report

At StickmanCyber, we ensure that our clients are equipped with the necessary knowledge, tools and processes that are needed to develop a secure network. Our specialist team of consultants has experience working with organisations across sectors including finance and government.

The Bottom Line

Like it or not, cybercrime and data breaches are a new reality for organisations in the 21st century. Although payment cards offer convenience, they can also compromise security. That’s why the PCI DSS was set into place.

It provides a universal standard for protecting cardholder data and gives companies a detailed sequence of steps to follow. Regardless of size, your organisation is expected to comply with the PCI DSS if it stores, processes or transmits customer payment card data.

Doing so protects your customers’ sensitive financial and personal information and significantly minimises the threat of a data breach occurring. At the same time, this mitigates risk for your company as well and can potentially mean the difference between its longevity and going out of business.

Is your business looking to get PCI DSS compliant? 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.

Frequently asked questions

What is the difference between a ROC and an SAQ?

A Report on Compliance (ROC) is a detailed assessment report completed by a Qualified Security Assessor using the PCI SSC’s ROC template. A Self-Assessment Questionnaire (SAQ) is a validation tool that eligible merchants and service providers complete themselves. Which one you need depends on your level and on what your acquirer or the card brands require.

What is a PCI DSS Attestation of Compliance (AOC)?

The Attestation of Compliance is the form an organisation submits to declare its PCI DSS validation status. It accompanies either a ROC or an SAQ and is available only from the PCI SSC website. Customers and acquirers often ask service providers for their AOC as evidence of compliance, but it reflects a point-in-time assessment.

What is the difference between cardholder data and sensitive authentication data?

Cardholder data includes the primary account number (PAN), cardholder name, expiry date and service code. Sensitive authentication data includes full track data from the magnetic stripe or chip, the card verification code and PINs or PIN blocks. Together they make up account data, and sensitive authentication data must not be kept after a payment is authorised.

Can a merchant’s PCI DSS level change?

Yes. Levels are based on annual transaction volume, so a growing business can move into a higher level and face stricter validation. Card brands can also raise a merchant’s level: Mastercard, for example, can require any merchant to meet its Level 1 requirements to minimise risk, and treats any merchant that meets Visa’s Level 1 criteria as Level 1.

What replaced PA-DSS?

The PCI Security Standards Council retired the Payment Application Data Security Standard (PA-DSS) on 28 October 2022. It was replaced by the PCI Software Security Framework, which includes the Secure Software Standard and the Secure Software Lifecycle Standard. Payment software is now validated against these standards and listed on the PCI SSC website.