Skip to content
Cyberphore

Compliance and certification

PCI Compliance in Canada: PCI DSS 4.0 and SAQ Types

PCI compliance in Canada explained: who must comply, PCI DSS v4.0.1 status, merchant levels, choosing the right SAQ, payment page script rules and ASV scans.

Published
Updated
Read time
8 min
On this page · 12 sections, 8 min read

Every Canadian business that stores, processes or transmits payment card data must comply with the Payment Card Industry Data Security Standard (PCI DSS), whatever its size (PCI Security Standards Council, 2026). It is not a Canadian law: the card brands set the rules and your acquirer (the bank or processor behind your merchant account) enforces them. As of November 16, 2026, PCI DSS v4.0.1 is the only active version, and merchants not required to file a full Report on Compliance validate with a self-assessment questionnaire (SAQ) chosen by how they take payments (PCI Security Standards Council, 2025).

This guide is general information, not legal or assessment advice.

Who Must Comply, and Who Enforces It

PCI DSS applies to entities that store, process or transmit cardholder data or sensitive authentication data, or that could affect the security of the cardholder data environment (CDE). That includes merchants, processors, acquirers, issuers and service providers (PCI Security Standards Council, 2026). The Council is explicit that small merchants are covered "regardless of their size or transaction volume" (PCI Security Standards Council, 2026).

The Council writes the standard but does not enforce it. Whether an entity must validate compliance is decided by "a payment brand, acquirer, or other entity" that manages a compliance program (PCI Security Standards Council, 2026). Visa, for example, says it "manages all data security compliance enforcement and validation initiatives," that acquirers must ensure their merchants validate at the right level, and that it may impose non-compliance assessments on the acquirer when a merchant does not comply (Visa, 2026).

Canadian law still matters. Under PIPEDA, a breach of security safeguards that creates a real risk of significant harm must be reported to the Privacy Commissioner; the Commissioner lists financial loss and identity theft among the harms (Office of the Privacy Commissioner of Canada, 2025). Our article on whether you have to report a data breach in Canada covers that side.

Sample screen; data is illustrative.

PCI DSS V4.0.1 Status, as of November 16, 2026

The current standard is PCI DSS v4.0.1, published in June 2024. Version 4.0 was retired on December 31, 2024, and v3.2.1 on March 31, 2024 (PCI Security Standards Council, 2024). The Council's document library still lists v4.0.1 as the active version as of November 16, 2026 (PCI Security Standards Council, 2026).

Version 4.0 introduced 64 new requirements, 51 of them future-dated. Those were best practices until March 31, 2025, and since then "they must be fully considered during a PCI DSS assessment" (PCI Security Standards Council, 2025).

A revision may be coming. The Council ran a request for comments on v4.0.1 from June 3 to July 20, 2026, to help decide "whether to revise, and what type of revisions are needed" (PCI Security Standards Council, 2026). We found no announced successor version or release date on the Council's site as of November 16, 2026, so treat any "PCI DSS 5.0" deadlines you see as unconfirmed.

Merchant Levels: Set by the Card Brands

Your merchant level decides how you validate, not whether you comply. Levels are defined by each card brand. For Visa, a merchant's total Visa transaction volume over 12 months determines the level and the validation requirements. Visa counts the corporate entity's total Visa transactions (credit, debit and prepaid) in one country or with one acquirer, and acquirers must make sure their merchants validate at the appropriate level (Visa, 2026).

Visa's page does not list the transaction thresholds for each level, and as of November 16, 2026 we could not confirm Visa Canada's current thresholds from a Visa source. Some Canadian acquirers publish level tables on their own sites; treat those as that acquirer's guidance, not a universal rule. Mastercard and the other brands run their own programs, and the Council advises asking the brands or your acquirer for specifics (PCI Security Standards Council, 2026). Whether a small merchant must validate at all "is determined by the individual payment brands," so check with your acquirer which level you are at and what evidence it expects.

The SAQ Types and How to Tell Which Applies

The SAQ follows your payment channels. The Council's instructions summarize them as follows (PCI Security Standards Council, 2025):

  • SAQ Acard-not-present merchants (e-commerce or mail and telephone order) that fully outsource all account data functions to validated third parties, with no electronic storage, processing or transmission of card data on their own systems.
  • SAQ A-EPe-commerce merchants whose website does not receive card data but does affect the security of the payment page, for example by building the form or loading scripts.
  • SAQ Bimprint machines or standalone dial-out terminals only, with no electronic card data storage.
  • SAQ B-IPstandalone PCI-approved PIN Transaction Security (PTS) terminals connected to the processor over IP.
  • SAQ C-VTstaff key in one transaction at a time into a third-party web-based virtual terminal on an isolated computer.
  • SAQ Cpayment application systems connected to the internet, with no electronic card data storage.
  • SAQ P2PEonly terminals in a validated, PCI-listed point-to-point encryption solution, with no access to clear-text card data.
  • SAQ Devery merchant not covered above, including anyone storing card data electronically.

A ninth form, SAQ SPoC, covers phones or tablets with a validated secure card reader. To choose, list every way you accept cards (online, phone, in person, invoices), match each channel to its SAQ and read every eligibility bullet. A merchant who fails one bullet does not qualify. The Council also warns not to assume your v3.2.1 SAQ still fits, and encourages confirming eligibility with your acquirer (PCI Security Standards Council, 2025).

For online stores, the split is precise. A redirect or an iframe served by a compliant provider can fit SAQ A. If "any element of a payment page delivered to consumers' browsers originates from the merchant's website," SAQ A does not apply and SAQ A-EP may (PCI Security Standards Council, 2025). The same guide lists 139 requirements for SAQ A-EP, so the design of your checkout page has a direct cost.

E-Commerce Script Requirements: 6.4.3 and 11.6.1

These two future-dated requirements target e-skimming, where malicious JavaScript in the shopper's browser copies card details (PCI Security Standards Council, 2025).

  • Requirement 6.4.3every payment page script loaded in the consumer's browser must be authorized, have its integrity assured, and appear in an inventory with a written justification (PCI Security Standards Council, 2024).
  • Requirement 11.6.1a change and tamper detection mechanism must alert staff to unauthorized changes to security-impacting HTTP headers and payment page script content, running at least weekly or at a frequency set by a targeted risk analysis (PCI Security Standards Council, 2024).

In early 2025 the Council removed both requirements from SAQ A and replaced them with an eligibility criterion: the merchant must confirm its site "is not susceptible to attacks from scripts that could affect the merchant's e-commerce system(s)" (PCI Security Standards Council, 2025). The Council says merchants can meet it using techniques such as those in 6.4.3 and 11.6.1, or by getting confirmation from the provider of the embedded payment form that its solution, implemented as instructed, protects the page from script attacks (PCI Security Standards Council, 2025). Both requirements remain in the full standard. A website and application security review can build the script inventory.

Reducing Scope: Tokenization, P2PE and Hosted Payment Pages

The cheapest control is card data you never touch. PCI DSS calls segmentation "strongly recommended" because it can cut the scope, cost and risk of an assessment, and warns that without it "the entire network is in scope" (PCI Security Standards Council, 2024). The main options for a smaller merchant:

  • Hosted payment pages or provider iframesAll elements of the payment form come only and directly from a compliant provider, which is what SAQ A eligibility requires (PCI Security Standards Council, 2025). Ask your processor to return a token for refunds and recurring billing so card numbers never reach your systems.
  • PCI-listed P2PE terminalsA listed solution "can significantly reduce the number of PCI DSS requirements" but does not remove PCI DSS entirely (PCI Security Standards Council, 2026).
  • Tokenization at the processorVisa's Technology Innovation Program can remove the requirement to validate (not to comply) when at least 75% of yearly transactions use EMV chip terminals, a validated P2PE solution or EMVCo-standard tokenization, subject to the program's other conditions (Visa, 2026).

Encrypting stored card data yourself is not a shortcut: the Council says encryption alone "is generally insufficient to render the cardholder data out of scope" (PCI Security Standards Council, 2026). Outsourcing has a limit too. Using a compliant provider "does not make a customer PCI DSS compliant" (PCI Security Standards Council, 2024). Requirement 12.8 still expects you to list providers, hold written agreements and monitor their compliance status at least once every 12 months, a point the Council restated in guidance published on November 10, 2026 (PCI Security Standards Council, 2026).

Quarterly ASV Scans

Requirement 11.3.2 requires external vulnerability scans at least once every three months by a PCI SSC Approved Scanning Vendor (ASV), with vulnerabilities fixed and rescans run until the scan passes under the ASV Program Guide (PCI Security Standards Council, 2024). The Council added the scan requirements to SAQ A in v4.x because breaches were hitting merchant pages that redirect to, or embed, a provider's payment form (PCI Security Standards Council, 2025). A passing ASV scan is not a penetration test; our explainer on vulnerability scans versus penetration tests sets out the difference, and vulnerability management keeps findings closed between quarters.

What to Do Now

  1. Map every payment channel, including any spreadsheet or inbox where card numbers turn up.
  2. Get your acquirer's instructions in writing. Confirm your merchant level, the SAQ it expects and its deadline.
  3. Read every eligibility bullet for the SAQ you think applies, especially the SAQ A script criterion if you sell online.
  4. Inventory payment page scripts, or obtain your payment provider's confirmation of script protection for its embedded form.
  5. Book quarterly ASV scans and schedule time to fix and rescan.
  6. Delete stored card data you do not need, and move remaining channels to hosted pages or P2PE terminals where practical.
  7. Collect your providers' Attestations of Compliance and record who owns which requirement.

How Cyberphore Can Help

Cyberphore's compliance readiness service helps Canadian merchants reduce PCI DSS scope, complete the right self-assessment questionnaire and put the required controls in place, starting with a free scoping call. Every team member holds industry certifications such as CISSP, CISM, OSCP or GIAC, and pricing is quoted after that call.

Services for this topic

Share this article

Questions and Answers

Is PCI compliance mandatory in Canada?

Not by statute. PCI DSS is an industry standard, and Visa states that it manages compliance enforcement while acquirers must make sure their merchants validate at the right level. In practice your merchant agreement makes it mandatory. Separately, a breach involving customers' personal information that creates a real risk of significant harm must be reported under PIPEDA.

What does PCI DSS stand for?

PCI DSS stands for Payment Card Industry Data Security Standard. It is maintained by the PCI Security Standards Council, founded by American Express, Discover, JCB, Mastercard and Visa. It sets baseline technical and operational requirements for any organization that stores, processes or transmits cardholder data, or could affect its security, from small retailers to payment processors.

Which PCI SAQ do I need?

It depends on how you take card payments. A fully outsourced online store or phone order business usually fits SAQ A, a store using only standalone or P2PE terminals fits SAQ B, B-IP or P2PE, and anyone storing card data electronically falls to SAQ D. Read each SAQ's eligibility criteria, then confirm the choice with your acquirer or processor.

Do small merchants have to comply with PCI DSS?

Yes. The PCI Security Standards Council says PCI DSS applies to all entities in payment processing regardless of size or transaction volume. What changes with size is validation: the card brands set merchant levels by annual transaction volume, and merchants not required to file a full Report on Compliance use a self-assessment questionnaire. Ask your acquirer which level you are at and exactly what it needs from you.

Sources (10, primary and official first)

  1. Payment Card Industry Data Security Standard: Requirements and Testing Procedures, v4.0.1 (opens in a new tab) · PCI Security Standards Council,
  2. Document Library (opens in a new tab) · PCI Security Standards Council,
  3. PCI DSS Self-Assessment Questionnaire Instructions and Guidelines, v4.0.1 r1 (opens in a new tab) · PCI Security Standards Council,
  4. Request for Comments (RFC) Instructions: RFC for Currently Published PCI Data Security Standard (PCI DSS v4.0.1) (opens in a new tab) · PCI Security Standards Council,
  5. Coffee with the Council Podcast: Guidance for PCI DSS E-commerce Requirements Effective After 31 March 2025 (opens in a new tab) · PCI Security Standards Council,
  6. Merchant Resources (opens in a new tab) · PCI Security Standards Council,
  7. PCI Data Security Standard (PCI DSS) (opens in a new tab) · PCI Security Standards Council,
  8. PCI SSC Publishes New Guidance on Understanding PCI DSS Third-Party Service Providers (opens in a new tab) · PCI Security Standards Council,
  9. Account information security program and PCI (opens in a new tab) · Visa,
  10. What you need to know about mandatory reporting of breaches of security safeguards (opens in a new tab) · Office of the Privacy Commissioner of Canada,

Changelog

  • Currency named only next to an amount (owner, November 20, 2026): removed 'in CAD' from the pricing line; title shortened to 60 characters or fewer for search results.

General information for Canadian organizations, not legal advice.

Written by

Cyberphore Security Team

Certified security analysts and consultants

  • CISSP
  • CISM
  • OSCP
  • OSCE
  • GIAC GCIH
  • GIAC GCIA
  • GIAC GPEN
  • Microsoft SC-200

Articles are researched and written by Cyberphore's security team. Every team member, from analysts to leadership, holds industry certifications, and the team monitors and responds to threats for Canadian organizations 24/7/365. Every article is fact-checked against its sources and reviewed before publishing.

How we research, fact-check and update articles: editorial standards. Spotted an error? Email Use our contact form.

Incident happening now? Our team answers 24/7: +1 236 665 1165

Keep reading

Continue Reading

Book free assessment