PCI compliance for ecommerce checkout and chat

Understand PCI compliance for ecommerce. Map card-data handling, compare checkout routes and keep payment details out of shopping and support chat.

PCI compliance means meeting the Payment Card Industry Data Security Standard (PCI DSS) for the card data your business handles. For an online store, the practical starting point is to map who collects payment details and what reaches your systems. Keep ordinary shopping and support conversations separate from card entry, then establish the validation evidence your acquirer requires.

What PCI compliance means for an online store

PCI DSS sets security requirements for protecting payment account data. Compliance is the work of meeting the applicable requirements. Validation is the assessment and reporting used to demonstrate that work.

The PCI Security Standards Council’s document library lists PCI DSS v4.0.1. References to PCI DSS 4.0 compliance still require attention to the applicable current documents and their eligibility criteria.

Outsourcing card collection reduces the card data your store handles. It doesn’t establish that your own website, staff practices and other payment channels meet their requirements. Record which controls the provider performs and which remain yours.

PCI compliance in Australia

PCI DSS is an industry security standard, not an Australian statute. Your card-acceptance contract and the payment brands’ programmes determine your PCI validation obligations. The Council explains that payment brands run their own compliance programmes. Your acquirer is the merchant bank or organisation that accepts your validation evidence.

Australian legal duties apply separately. For businesses covered by the Privacy Act, the Office of the Australian Information Commissioner’s security guidance explains obligations to protect personal information. It also explains disposal duties when information is no longer needed, subject to exceptions.

The Australian Competition and Consumer Commission explains consumer guarantees under Australian Consumer Law. A PCI assessment doesn’t replace those obligations or other laws applying to your business. Keep legal responsibilities and card-contract requirements as separate items in your responsibility register.

Map where card data can enter your systems

Trace a payment from the customer’s browser to the payment provider, then through the order record and support tools. Identify who can read the full card number, also called the primary account number (PAN), at each step.

For a provider-hosted collection route, the customer enters card details in the provider’s component. The provider processes the payment and returns a result or reference. Your order system can record the purchase and payment status without retaining the full card number.

Map more than the visible checkout page. Review storefront scripts, embedded components, browser error reporting, server logs, email, chat transcripts, support tickets and exports. Include call recordings, screen recordings and any software that copies information between these systems.

For each system, record its owner, the information it receives, who can access it and where copies go. Include backups and analytics exports in that account. A field removed from the staff screen can still exist in the underlying record.

Use provider test data in a test environment when checking this flow. Don’t create screenshots or support tickets containing live card details to demonstrate where the data travels.

Hosted checkout, payment fields and merchant collection

Hosted checkout and provider-controlled fields can reduce merchant scope by sending card details directly to the payment provider. Merchant-generated collection forms need a different assessment, even when they send the payment straight to a processor.

A self-assessment questionnaire (SAQ) is a validation form for eligible merchants. The Council’s SAQ guidance explains that the appropriate form depends on how the merchant handles card data. Eligibility and the acquirer’s requirements decide the route.

Collection routeWho supplies card entry?What the merchant must establish
Redirect to hosted checkoutThe payment provider supplies the payment pageWhether all SAQ A eligibility conditions are met, including the other payment channels
Provider-controlled embedded payment formThe provider supplies the card-collection elements inside its frameSAQ A eligibility, correct installation and the applicable script-attack protection confirmation
Merchant-generated form posting directly to the providerThe merchant supplies payment-page elementsWhether SAQ A-EP fits the actual flow and every eligibility condition
Card details passing through merchant serversThe merchant receives raw card dataThe broader environment requiring assessment, commonly through SAQ D for eligible self-assessing merchants

The Council explains the distinction between provider-controlled payment elements and merchant-generated forms. A form’s appearance doesn’t establish who controls its inputs.

For embedded forms, SAQ A includes a script-attack eligibility criterion. Merchants can use suitable protective techniques or obtain the payment provider’s confirmation that its correctly implemented solution supplies those protections. That particular criterion doesn’t apply to a redirect or a fully outsourced payment-link route. Other applicable requirements remain.

What changes across Stripe, Shopify and Magento

Stripe’s PCI integration guidance maps Checkout and Elements to SAQ A for eligible merchants. It distinguishes merchant-hosted collection through older Stripe.js forms from those provider-controlled inputs. Its security guide explains the shared responsibility and annual merchant attestation.

Shopify states that its hosted stores have Level 1 PCI DSS compliance. With Shopify Payments in the supported checkout, the platform manages the checkout environment. A separate telephone payment process or card details collected in a support app still needs its own review. The platform statement doesn’t describe those additional channels.

Magento PCI compliance depends on the deployed payment extension and hosting arrangement. Adobe’s Payment Services security documentation states that Credit Card Fields keep PCI-regulated data from passing through the merchant’s services. A custom extension that sends raw card details through the merchant’s server creates a different flow.

Adobe’s cloud responsibility model leaves merchants responsible for custom code, third-party integrations and incident response. Installing Adobe Commerce or Magento Open Source doesn’t identify the collection route by itself.

Before selecting a questionnaire, obtain the integration name and version, field-hosting details, server data flow and relevant provider compliance evidence. Record whether any extension changes those facts. Broader provider selection belongs in the guide to ecommerce payments.

Tokens and card-paid trade invoices

Tokenisation replaces a card number with a reference used by the payment system. The Council’s tokenisation guidance makes scope depend on the implementation, including access to the underlying card data. A token doesn’t erase the obligations of systems that still handle raw card details.

For a hypothetical business-to-business trade order, the retailer emails an invoice with a provider-hosted payment link. The buyer enters card details on the provider’s page. The retailer matches the payment reference to the invoice and keeps card numbers out of accounts emails.

If staff instead take the card by telephone, that telephone process becomes part of the card-data review. If the buyer pays through checkout, assess that checkout route. Invoice finance is a separate funding arrangement. Calling a card payment a trade invoice doesn’t change how its card data must be handled.

Keep card details out of shopping and support chat

Use chat to discuss products and the order, then route card entry to the supported secure payment component. An embedded payment component can sit beside a conversation while keeping card input separate from the ordinary message box.

A hypothetical shopping conversation can say, “Your basket is ready. Use the secure payment form to pay.” The message box must not ask customers to type a full card number or security code. The separate guide to agentic payments covers how authorised agents make payments.

Train staff to send the approved payment route and request only the information needed for support. Limit transcript access by role and set a documented retention period. Review integrations that copy conversations into email, tickets, recordings or exports.

The Council explains that sending card numbers through messaging brings that channel into scope. Ordinary chat isn’t automatically a compliant payment channel because its connection is encrypted.

When a customer volunteers card details

Follow the Council’s unintended-channel guidance. Card data must be removed immediately or secured under PCI DSS and brought into the cardholder data environment.

  1. Stop further copying or forwarding. Don’t quote the sensitive message in your reply.
  2. Alert the designated security or payment lead through the incident procedure, without copying card details into that alert.
  3. Use the approved secure-removal process, or secure the affected channel under PCI DSS. Account for copies already sent to connected systems.
  4. Direct the customer to the supported payment component and prevent repeat collection through ordinary messages.

If details have spread or exposure is suspected, escalate promptly to the provider and acquirer under your incident plan. Record the affected systems and actions without reproducing the card data.

Telephone and interactive voice response payments

An interactive voice response (IVR) system can route card entry to a dedicated payment service. Establish whether keypad tones, spoken digits or screen content reach the agent, recording system or transcription service. Obtain the provider’s documented controls and test the configured route with test data.

The Council’s call-recording guidance requires efforts to prevent sensitive authentication data from being recorded. Enable supported audio suppression or redaction during entry. Security codes must not remain in recordings after authorisation. Where prevention fails, apply the documented response and seek assessor guidance on any legitimate retention constraint.

For an order-status enquiry, staff can use an order number and permitted payment reference to locate the provider’s transaction. Follow the store’s identity checks before disclosing order details. Keep the payment record in the order and payment systems, without asking the customer to repeat their card details in chat.

Confirm the validation route and responsibilities

Agree the validation route with the acquirer using your documented payment flow. Keep merchant assessment evidence separate from the payment provider’s own evidence.

Mastercard’s merchant programme uses merchant levels to set validation requirements. Transaction volume affects the level, and risk-based designation can also affect it. Level 1 requires a Report on Compliance (ROC) under that programme. Use the relevant payment brand’s rules instead of treating one threshold as universal.

A qualified security assessor (QSA) conducts independent assessment where required. Eligible merchants use the applicable SAQ for self-assessment. An Attestation of Compliance (AOC) records the assessment declaration. A provider’s AOC describes the assessed provider services and scope, rather than certifying every merchant integration.

The Council states that unofficial compliance certificates are not recognised validation evidence. Request official reporting documents. A completed form still needs to reflect implemented controls and the real environment.

PCI compliance checklist

  • Record every card-acceptance channel and its collection architecture, including telephone and invoice payments.
  • List payment service providers and obtain compliance evidence covering the services you use.
  • Assign each applicable responsibility to the merchant, provider or both. Name the accountable person inside your business.
  • Confirm the merchant level, SAQ eligibility or independent assessment requirement with the acquirer.
  • Complete the required controls and retain supporting evidence, including staff procedures and relevant technical checks.
  • Submit the requested validation documents and record the acquirer’s response. Schedule reviews and remedy outstanding issues.

Scanning and network checks

SAQ A can still require external vulnerability scans for ecommerce webpages, including redirects and embedded frames. The Council’s ASV scanning clarification confirms this applies despite outsourced processing. An Approved Scanning Vendor (ASV) must perform the required ASV scan using its approved solution.

For your selected assessment, list the required scan scope and frequency, remediation and rescans. Separately identify applicable internal vulnerability checks, penetration testing, network security controls and firewall configuration reviews. Assign responsibility for each to the party operating that environment.

A passing scan covers its defined targets and checks. It doesn’t validate the complete store, staff procedures or every PCI DSS requirement.

What compliance software can and cannot do

Compliance software can organise evidence and reminders, while people remain accountable for scope and validation decisions. Choose software by the merchant task it supports.

ResourceMerchant taskLimit
Assessment questionnaireRecord responses to applicable assessment requirementsAnswers must reflect controls actually operating
Responsibility registerTrack who performs each merchant and provider obligationAn assigned name doesn’t prove the work happened
Evidence-management softwareStore reports and approvals with their ownersUploaded files can be outdated or cover the wrong service
Reminder automationRequest reviews, renewed documents and remediation follow-upA reminder doesn’t complete or approve the task
Monitoring toolsDetect specified changes or suspicious activityMonitoring doesn’t replace an assessment or required scan

Automate requests for renewed provider attestations and reminders for scheduled reviews. Keep a person responsible for checking document scope, resolving failed controls and deciding whether a changed integration alters the assessment.

A checklist result is a workflow record. An active vulnerability scan tests a defined target. Acquirer acceptance concerns the validation evidence submitted. This guide explains those tasks and supplies no scan result or compliance certification for your store.

Recheck the flow after a checkout change

Revisit the card-data map whenever a checkout component, payment method, storefront script or support integration changes. A change that looks cosmetic can alter who supplies the payment fields or where information is copied.

Sample review of a changed checkout

In this hypothetical review, a retailer adds a provider-controlled payment form beside shopping chat. The expected flow sends card input directly to the provider. The order record receives a transaction reference and payment status. Support uses the order number to follow up.

The retailer tests payment success and failure with provider test data. It then inspects the saved order, chat transcript, support export and error log. The expected result is payment references where needed, with full card numbers and security codes absent from those merchant records.

An unexpected card number in a log fails that review. Stop the affected collection route under the incident procedure and escalate to the payment provider or acquirer. A QSA can resolve uncertainty about scope or the required assessment. Resume only through an agreed payment route with the exposed-data issue addressed.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup