Compliance Guide

PCI Compliance in Canada

PCI DSS compliance for Canadian businesses that take card payments: who it applies to, the 12 requirements, merchant levels and a practical checklist.

Book a Toronto consultation

PCI Compliance in Canada

PCI DSS compliance for Canadian businesses that take card payments: who it applies to, the 12 requirements, merchant levels and a practical checklist.

What This Guide Covers

  • What is PCI DSS?
  • The 12 PCI DSS Requirements, in Plain Terms
  • Which Merchant Level Applies to You?
  • Where Toronto Businesses Typically Fall Short

Home

Blog

PCI DSS compliance for Canadian businesses that take card payments: who it applies to, the 12 requirements, merchant levels and a practical checklist.

What is PCI DSS?

The Payment Card Industry Data Security Standard (PCI DSS) is a security standard maintained by the PCI Security Standards Council, founded by Visa, Mastercard, American Express, Discover, and JCB. It applies to any business, retailers, clinics, law firms, professional offices, that stores, processes, or transmits cardholder data, regardless of size.

PCI DSS v3.2.1 was retired at the end of 2024, making v4.0.1 the sole active version of the standard. A set of requirements that had been "future-dated" best practices under v4.0 became mandatory on March 31, 2025, including expanded multi-factor authentication requirements and authenticated internal vulnerability scanning. Toronto businesses that treated PCI compliance as a one-time checklist are now expected to run it as an ongoing program, not an annual event.

The 12 PCI DSS requirements, in plain terms

PCI DSS organizes its controls into 12 requirements across six objectives. Most of them are things managed IT already handles, the gap is usually documentation and consistency, not technology:

  • Install and maintain firewalls and network protections around systems that touch card data
  • Remove vendor-default passwords and unnecessary services from every system
  • Protect stored cardholder data, encrypted at rest wherever it's kept
  • Encrypt cardholder data in transit across public or open networks
  • Deploy and keep anti-malware protection current on all relevant systems
  • Develop and maintain secure systems, with a disciplined patching schedule
  • Restrict access to cardholder data to employees who need it for their job
  • Require unique logins and multi-factor authentication for anyone accessing the cardholder data environment
  • Restrict physical access to card data and the systems that store it
  • Track and log all access to network resources and cardholder data
  • Regularly test security systems with vulnerability scans and penetration testing
  • Maintain a written information security policy and run annual staff awareness training
  • Which merchant level applies to you?

    Most GTA small and mid-sized businesses fall into Level 3 or Level 4, which only require an annual self-assessment questionnaire (SAQ) rather than a full on-site assessment by a Qualified Security Assessor (QSA), that's reserved for Level 1 merchants processing over roughly six million card transactions a year. Which SAQ type you fill out depends on how your business actually handles card data:

    Fully outsourced payment processing

    If customers pay through a hosted checkout page or iframe from your processor (Stripe, Square, Moneris, and similar), you likely qualify for the shortest questionnaire, SAQ A, card data never actually touches your own systems.

    Card-present terminals

    Standalone, IP-connected, or dial-out terminals in a retail or clinic setting generally fall under SAQ B or B-IP, simpler, but still requiring documented controls around the terminal itself.

    Card data touching your own network

    If your website's own servers handle any part of the payment page, or you store cardholder data in your own systems, you're into longer questionnaires (SAQ A-EP, C, or D) that look closely at your network, access controls, and logging, this is where most IT gaps show up.

    A practical PCI checklist

    Use this list to see whether the IT side of the questionnaire is ready. It does not replace the questionnaire your acquirer assigns.

  • Confirm how card data flows: hosted checkout, a terminal, or your own website and servers.
  • Ask the acquirer which merchant level and which self-assessment questionnaire apply.
  • Put payment systems on a separate network from everyday office computers.
  • Remove shared and vendor-default logins. Give each person a unique account.
  • Turn on multi-factor authentication for remote access to anything that can reach payment systems.
  • Keep logs of access to the cardholder environment and know who reviews them.
  • Schedule vulnerability scanning and, where the questionnaire asks for it, penetration testing.
  • Write the security policy and the date staff last reviewed it.
  • Store the diagram, the questionnaire and the evidence in one folder.
  • PCI questions

    Where Canadian businesses typically fall short

  • Point-of-sale or payment terminals left on the same flat network as general office computers, instead of a segmented cardholder data environment
  • No multi-factor authentication on remote access to systems that touch payment data, now explicitly required under v4.0.1
  • Vendor-default or shared logins on POS systems, rather than unique accounts per employee
  • No documented, repeatable vulnerability scanning or penetration testing schedule
  • Written security policy and staff training that exist on paper but haven't been reviewed since the system was first set up
  • How SecureIT Solutions helps

    PCI-DSS is one of the compliance frameworks built into our compliance management service: network segmentation around payment systems, access controls and MFA, log retention, and scan/penetration-testing schedules, documented in a way that maps directly onto your SAQ, so renewal season isn't a scramble.

    Not sure which SAQ applies to you?

    Talk to our team about a PCI readiness review. We will start with how cards actually move through the business.

    Talk to Our Team

    On This Page

    Related Reading

    PIPEDA Compliance Guide

    PHIPA Compliance Guide

    Compliance Management Services

    Who does PCI DSS apply to in Canada?

    PCI DSS applies to any business that stores, processes or transmits cardholder data, including small retailers, clinics and professional offices. The size of the business does not remove the duty. The way you take cards changes how much of the environment is in scope.

    What are merchant levels?

    Card brands group merchants by how many transactions they process. Most small and mid-sized Canadian businesses fall in the lower levels and complete a self-assessment questionnaire rather than an on-site assessment. Your acquirer confirms the level that applies to you.

    What is a self-assessment questionnaire?

    A self-assessment questionnaire is the form a merchant uses to attest that PCI DSS controls are in place. The questionnaire type depends on how card data flows. A hosted checkout is a shorter form than a site that handles the payment page itself.

    Do small businesses need all 12 requirements?

    The 12 requirements are the standard. Scope shrinks when card data never touches your systems, which is why a hosted payment page is simpler. Where your own network, terminals or servers are involved, the relevant requirements still have to be met and documented.