PCI Compliance for Practice Payments 2026

Identify where the practice handles card data, choose a safer payment route and confirm the processor’s validation and recordkeeping requirements.

Published
Updated

PCI compliance means meeting payment-card security requirements for how your practice handles card data. Use a hosted payment route that keeps card details out of ordinary practice records.

Your payment provider’s compliance covers its service. Your practice still needs to understand its own responsibilities and complete the validation required by its acquiring bank or payment provider.

What PCI Compliance Means

The Payment Card Industry Data Security Standard (PCI DSS) sets requirements for protecting payment account data. PCI DSS v4.0.1 is the standard listed in the PCI Security Standards Council’s document library.

Card data includes the primary account number, commonly called the card number. Card security codes are sensitive authentication data and have stricter retention rules. Treat the card number differently from a payment receipt reference.

PCI DSS operates through payment-industry agreements. For example, BankSA’s merchant guidance makes compliance a condition of its merchant facility. Australian privacy and other legal obligations apply separately where relevant.

The Council develops standards. Payment brands manage their compliance programmes, including merchant levels and validation requirements. The acquiring bank is the financial institution supporting your merchant facility. It or your payment provider tells you what evidence to submit.

A compliant processor does not make every practice payment method compliant. If staff copy card numbers into email or record security codes in call notes, those actions sit outside a provider-hosted checkout.

Ask the provider which tasks it performs and which remain with your practice. Keep that written allocation beside evidence covering the exact service you use. A logo saying “PCI compliant” does not describe your practice’s setup.

Map the Card Data and Validation Route

Map every way a client can pay, including occasional telephone payments. Record where card details first arrive, which device or service handles them and what remains after payment.

Prefer a provider-hosted payment link for remote payments when it meets your billing needs. The client enters details directly with the provider, so staff can reconcile the receipt without collecting card credentials.

Payment Routes Compared

Payment routeData the practice touchesValidation question
Provider-hosted payment pageStaff send a link and receive payment references, without collecting card detailsDoes the arrangement meet every SAQ A eligibility criterion?
Physical terminalThe card interacts with the terminal; staff handle the device and receiptDoes the approved setup qualify for B-IP or a listed P2PE solution’s questionnaire?
Browser-based virtual terminalStaff receive and manually enter card details on a practice deviceDoes the isolated device and the entire channel meet C-VT eligibility?
Telephone or manual collectionStaff hear or see credentials; recordings and notes can retain themWhich receiving systems, documents and entry method fall within scope?

A telephone payment is a collection method. Its scope depends on what happens next. Typing details straight into an approved virtual terminal differs from storing them in a spreadsheet for later processing.

Choose the Questionnaire by Eligibility

A Self-Assessment Questionnaire (SAQ) records the practice’s assessment against requirements for an eligible payment environment. An Attestation of Compliance (AOC) declares eligibility and the assessment result. Completing a form does not fix a security gap.

The Council’s SAQ instructions for PCI DSS v4.0.1 set different criteria for different channels. Use the full criteria with your provider, including any additional payment method.

SAQ A covers eligible fully outsourced card-not-present channels without electronic account-data handling on merchant systems. For online payments, all payment-page elements must come directly from the compliant provider.

An embedded payment form also needs confirmation that the merchant page is protected against script attacks. The Council’s script eligibility explanation distinguishes embedded forms from redirects and emailed links to the provider’s own payment page.

Outsourcing does not remove every website requirement. The Council confirms that SAQ A scanning requirements include merchant webpages that redirect clients to a provider or embed its payment form. Required external scans use an Approved Scanning Vendor.

C-VT eligibility includes single-transaction manual entry through a hosted virtual terminal on an isolated device. It excludes electronic account-data storage and other electronic receiving channels. An ordinary shared office computer does not establish eligibility.

Terminal eligibility depends on the terminal and its connections. B-IP requires qualifying standalone IP-connected devices. SAQ P2PE applies to eligible use of a PCI-listed point-to-point encryption solution. An encrypted terminal alone does not establish that listing.

Confirm the Practice’s Validation Obligations

Merchant levels describe validation obligations under a payment brand or acquirer’s programme. They are separate from SAQ types. Transaction volume and payment channels affect the level. A small practice’s size does not select its questionnaire.

BankSA, for example, describes levels 1 to 4, with a Report on Compliance for level 1 and self-assessment routes for lower levels. Its guidance also specifies vulnerability scanning. Your own acquirer’s requirements govern your merchant facility.

Send the provider your payment-channel map and obtain written confirmation of the required assessment, attestations and scans. Record where to submit them and when they must be renewed. Resolve unmet requirements before attesting that they are in place.

Keep Credentials Out of Practice Records

Give staff an approved payment route and a written rule against collecting card credentials in ordinary client records. Keep reconciliation evidence, such as the invoice and provider transaction reference, separate from card credentials.

  • Send payment links instead of asking clients to email card details or attach a card photograph.
  • Remove card-number and security-code fields from ordinary client forms. Use the provider’s approved payment page for payment entry.
  • Keep card credentials out of call notes and document uploads. Configure any telephone-payment arrangement to prevent recording credentials, including call transcripts.
  • Use the provider’s card-on-file service for authorised repeat payments instead of keeping credentials in a spreadsheet or client folder.

The Council prohibits retaining card security codes after authorisation, even when encrypted. A client’s request to keep the code does not make it acceptable. Paper notes and recordings also need to follow that rule.

If a client sends card details unexpectedly, do not forward the message or include the details in your reply. Follow the Council’s unintended-channel guidance: secure or remove the data under an approved procedure and stop further capture through that channel.

Keep Evidence and an Incident Contact

Retain the practice’s completed validation documents and evidence that they were submitted. Keep the provider’s relevant AOC or equivalent evidence, service scope and responsibility allocation. Retain required scan results and records showing that identified issues were resolved.

Give the principal or nominated payment owner responsibility for renewals. Review the channel map when staff add a payment method, change a website payment form or start recording calls.

For suspected compromise, contact your acquirer or processor immediately through its established incident channel. Notify the practice’s security lead and preserve evidence. BankSA explicitly warns merchants against changing or removing evidence that could affect a forensic investigation.

Record the affected service and when the problem was noticed, without copying exposed card data into an incident email. Follow the provider’s containment instructions and obtain specialist help where needed. A questionnaire or this guide cannot certify the practice’s compliance.

Before staff collect the next payment, confirm that the approved route works, the payment owner holds its validation instructions and ordinary client records contain only the payment evidence they need.

One client form. One finished return.

Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.

See how Tax Genie works

Made for Australian accounting firms

Tax GenieSee how Tax Genie works