PCI DSS by region
PCI DSS in Australia: acquirers, QSAs, APRA CPS 234 and data breach rules
What is different about PCI DSS compliance in Australia: who sets your validation route, finding a QSA, and how card data security sits beside APRA CPS 234, CPS 230 and the Notifiable Data Breaches scheme.
Key points
- PCI DSS reaches Australian merchants and service providers through the contract with their acquiring bank and the card brands' programmes; no Australian regulator certifies or validates it.
- Banks, insurers and superannuation trustees regulated by APRA must also meet CPS 234 Information Security, which extends to information assets that their service providers manage for them.
- A compromise of card data can also be an eligible data breach under the Notifiable Data Breaches scheme, so the PCI DSS incident plan and the Privacy Act 1988 response need to be one plan.
- Validation is by a QSA company on the PCI Security Standards Council's list, or by self-assessment where your acquirer allows it. There is no accreditation body in the chain and no certificate at the end.
Why Australian organisations pursue PCI DSS
For most Australian businesses the first request comes from the acquiring bank that settles their card payments. The bank sets out, usually in the merchant agreement and its onboarding checks, which validation it expects and when it wants the documents back. Retailers, hospitality groups and online stores often meet it when they add a channel such as a mobile app or a phone payment line.
Service providers meet it through their customers. A contact centre taking payments for an Australian telco, a hosting company running a payment platform or a software business whose product touches card data will find an Attestation of Compliance requested in the vendor questionnaire.
Financial services add a regulatory layer. APRA's CPS 234 applies to authorised deposit-taking institutions, general and life insurers, private health insurers and RSE licensees. It asks them to assess the security capability of third parties that manage their information assets. Providers to Australian banks and insurers should expect PCI DSS evidence and CPS 234 questions in one due diligence pack.
The local landscape: acquirers, card brands and QSAs
The PCI Security Standards Council writes the standard but does not enforce it. Enforcement sits with the card brands and acquirers, so your acquiring bank decides your level and validation route, applying the brand rules to your annual transaction volume. The decision guide explains how levels are set.
Unlike ISO certification, there is no national accreditation body in this route. JASANZ accredits management system certification bodies; it has no role in PCI DSS. QSA companies and Approved Scanning Vendors are qualified or approved by the PCI SSC itself, and each has a public list.
When you shortlist assessors, confirm the company appears on the PCI SSC's QSA list, then ask who will perform the fieldwork, whether they can attend your Australian sites, and how sampling will work across states. The guide to choosing a QSA covers the full set of questions.
Local practice that changes the project
One incident plan for the card brands and the OAIC
The Notifiable Data Breaches scheme, created by the Privacy Amendment (Notifiable Data Breaches) Act 2017, applies to organisations and agencies covered by the Privacy Act 1988. Where a breach is likely to result in serious harm, affected individuals and the Office of the Australian Information Commissioner must be notified. Card numbers usually travel with names and contact details, so write one incident response plan whose first hours cover containment, the notifications your acquirer and card brands require, and the NDB assessment.
APRA-regulated clients and their providers
CPS 234 expects incident notification to APRA no later than 72 hours after becoming aware of a material information security incident, systematic testing of controls by functionally independent specialists, and internal audit of controls, including those run by third parties. CPS 230 Operational Risk Management, in force from 1 July 2026, adds substantial provisions on material service providers. For a bank's payment provider, one control set and evidence library can answer both the QSA and the bank's reviewers.
Multi-state and trans-Tasman operations
A group with stores or contact centres in several states, or across Australia and New Zealand, needs one agreed map of card data flows and sites first. Decide early which sites are in scope, which tokenisation or a hosted payment page can remove, and which need an on-site visit.
Local items to check, and where
| Local item | What it means for your project | Where to verify it |
|---|---|---|
| Your level and validation route | Decides whether you need a QSA-led ROC or a self-assessment questionnaire, and the date the documents are due | Your merchant agreement and your acquiring bank's compliance team |
| Your QSA company | Only a listed company can sign a Report on Compliance your acquirer accepts | The QSA list on the PCI Security Standards Council website |
| Your scanning vendor | Quarterly external scans must come from an approved vendor where they apply | The ASV list on the PCI Security Standards Council website |
| Data breach obligations | A card data compromise may also be notifiable to individuals and the OAIC | The Notifiable Data Breaches pages on the OAIC website |
| APRA requirements, if you are regulated or serve a regulated entity | CPS 234 and CPS 230 shape testing, incident notification and third-party reviews | The prudential standards pages on the APRA website |
How Sterling works in Australia
Sterling supports Australian clients from its Sydney office, with consultants working on site in Sydney and remotely with teams in other states. The team draws on 8,100+ client engagements in 60+ countries since 2003. Sterling does not validate compliance: a QSA company assesses and attests, or your acquirer accepts your self-assessment, and we help you prepare for whichever applies.
How Sterling supports Australian organisations
A cardholder data environment your acquirer, your QSA and your regulator can follow
We confirm your level and route with your acquirer, map and reduce the card data scope across your sites, close the gaps with your team, align the incident plan with the NDB scheme and, where it applies, CPS 234, run the programme in Effivity and stay with you through fieldwork and every annual cycle. We ensure successful validation for our clients.
Book a free discovery callPCI DSS in Australia: questions buyers ask
Is PCI DSS compliance mandatory in Australia?
For any business that accepts or handles card payments, it is required by contract rather than by statute. PCI DSS itself is not a law; your acquiring bank and the card brands require it through the merchant agreement, and your customers may require it through service contracts.
Does APRA CPS 234 replace PCI DSS for banks and insurers?
No, the two apply side by side. CPS 234 is a prudential standard APRA supervises across all information assets, while PCI DSS covers card data and is validated each year for the acquirer and the card brands.
Do we have to report a card data breach to the OAIC?
You do if the breach involves personal information, your organisation is covered by the Privacy Act 1988 and serious harm is likely. That notification sits alongside, not instead of, what your acquirer and the card brands require, so your incident plan should cover both.
How do we find a QSA that works in Australia?
Start with the QSA list on the PCI Security Standards Council website and confirm the company's listing is current. Then ask which assessors will do your fieldwork and whether they will attend your Australian sites.
PCI DSS by region
Every guide in the PCI DSS series is written for one question and links back to the hub for the whole picture.
- The PCI DSS annual cycle
- PCI DSS assessor questions
- PCI DSS compliance in Australia
- PCI DSS for banks and financial services
- PCI DSS for call centres and BPOs
- PCI DSS checklist
- PCI DSS compliance in India
- PCI DSS compliance in the Netherlands and Europe
- PCI DSS compliance in Singapore and South East Asia
- PCI DSS compliance in the Philippines
- PCI DSS compliance in the United Kingdom
- PCI DSS compliance in the UAE and GCC
- Which SAQ applies to you
Keep exploring
Explore more about PCI DSS
Watch a video on how to implement PCI DSS here.
Watch a video on PCI DSS requirements here.
PCI DSS resources
Services for PCI DSS
Talk to a consultant
Plan your PCI DSS compliance in Australia with confidence.
Tell us your goals, locations and target date. We’ll help you define the scope, timeline and next steps.
hello@sterling-grc.com+1 201 263 4443 (global headquarters) · your nearest office and its number are at the top of this page
What would you like to achieve?
Choose a starting point. The enquiry form takes about a minute.
Book my free discovery callContinue to the enquiry form to share your details. Please do not include passwords, sensitive personal information or confidential files. A Sterling consultant replies within one working day. Privacy notice