Website card skimming rarely announces itself. Orders keep coming in, the homepage looks the same, and the payment page still takes cards, while a few extra lines of code copy every card number your customers type.
Most store owners hear about it the same way. A customer calls about a strange charge, a bank flags a pattern, or a stranger posts about your checkout page online.
Here is the part people get wrong. The attack does not need to break into your database or your card processor. It runs in the shopper’s own browser, on a page you serve, so the store can look fine while the checkout page is not.
What Website Card Skimming Is
The PCI Security Standards Council, the body that sets the card industry’s data security standard, calls this e-skimming. In its March 2025 announcement of new guidance on payment page security, the Council says scripts running in consumers’ browsers are now a significant target for attackers seeking to steal payment card data.
The same announcement says these attacks have become more common as e-commerce platforms grow more complex and businesses rely more on external scripts. Think of the chat widget, the analytics tag and the marketing pixel. Each one is outside code running on your pages.
In a website card skimming attack, one of those scripts is replaced, or a new one is slipped in. It reads what the shopper types into the payment form and sends a copy to a server the attacker controls. The real payment still goes through, so nothing looks broken.
A Canadian Case From January 2026
Canada Computers & Electronics, a computer retailer headquartered in Richmond Hill, Ontario, is the clearest recent Canadian example. In a statement in its press room, the company says it became aware on January 22 of unauthorized access to its system supporting its retail website, and that personal customer information, including credit card information, was compromised.
The company says customers who checked out as guests between December 29 and January 22 and entered their personal information were affected. Customers who checked out with a member account were not affected, and in store purchases were not affected. Affected customers were notified on January 25 and offered two years of credit monitoring and identity protection.
The company told CBC News on February 3 that its investigation indicated 1,284 customers were affected, a figure also reported by Inside Halton for Metroland Media. CBC News also reported that the breach was reported to the federal privacy watchdog and to police in York Region.
What was reported, and what the company said
The company has not described how the attack worked. Its statement says it engaged an independent forensic firm to confirm the incident’s origin and scope.
The method in news coverage came from a shopper. According to Inside Halton, a Reddit user said he found a card skimmer on the checkout page. MobileSyrup and iPhone in Canada reported that he spotted it on January 18, and VideoCardz reported he was shopping with his browser’s developer tools open.
Inside Halton quotes the user’s January 22 update saying the skimmer appeared to have been removed from the live site.
The dates do not all line up, and that is worth saying plainly:
- Discovery date: the company first told CBC News it became aware on January 23, then its website statement said January 22.
- Exposure window: the company says December 29 to January 22. The Reddit user claimed archived copies of the page showed the code from December 8, according to Inside Halton.
- Method: “card skimmer” is the user’s description, repeated in coverage. The company has not confirmed it.
None of this is a criticism of one retailer. The lesson about website card skimming for every online store is the order of events: an outside shopper saw the problem before anything else flagged it.
Why Website Card Skimming Is Hard to See
Website card skimming is quiet by design. The store keeps working, and the real payment goes through. Fraud shows up later on someone else’s statement, so the link back to your site is slow to form.
Three things make it easy to miss:
- The code runs in the browser, not on your server. Server logs and antivirus on your office computers do not see what a script does inside a shopper’s browser.
- It hides among legitimate scripts. A modern checkout loads code from many places, and few teams keep a list of what should be there.
- It can target one page only. If the skimmer loads only on checkout, a quick look at the homepage tells you nothing.
The Canadian Centre for Cyber Security’s guidance on security considerations for your website makes a point every store owner should read twice. It says your organization is legally responsible for protecting all customer data that is processed on your website, even if your organization does not host the website.
What PCI DSS Now Asks of Payment Pages
PCI DSS version 4.0.1 includes two requirements written for website card skimming: Requirement 6.4.3 and Requirement 11.6.1. According to the PCI Security Standards Council’s guidance announcement, they focus on making sure payment page scripts are properly authorized, checked for integrity and monitored for tampering, along with the security-impacting HTTP headers on the page.
The Council’s January 2025 post on updates to Self-Assessment Questionnaire A says both requirements became effective as of 31 March 2025. That post also removed them from SAQ A, the short questionnaire for merchants that fully outsource card handling.
In their place, SAQ A merchants must now confirm their site is not susceptible to attacks from scripts that could affect their e-commerce systems. The Council says the change does not remove or diminish the underlying requirements in PCI DSS.
If your checkout embeds a payment form from a processor, the Council’s FAQ on the new SAQ A eligibility criteria gives two ways to make that confirmation. You can use techniques like those in 6.4.3 and 11.6.1 yourself, or get confirmation from your PCI DSS compliant processor that its solution protects your payment page from script attacks when set up as instructed. Your acquirer or payment brand decides which questionnaire applies to you, so ask them.
How to Spot Website Card Skimming Early
You do not need a large security team to catch website card skimming sooner. You need a short list, an owner, and a schedule.
- Write down every script on your payment page. For each one, record where it loads from, who added it and why it is there. Anything nobody can explain gets removed.
- Watch the payment page for changes. A script that appears, changes or starts sending data to a new domain is the signal. The PCI requirements describe this as change and tamper detection.
- Lock down who can edit the site. The Canadian Centre for Cyber Security recommends multi-factor authentication for all account types and a separate login interface for administrators. Apply both to your store platform, your tag manager and your hosting account.
- Patch the platform and its plugins. The same guidance asks you to prioritize patches for components exposed to the internet, which describes every online store.
- Test the web application, not only the network. The Canadian Centre for Cyber Security’s website guidance recommends vulnerability scanning in your deployment process and penetration testing by people outside your development team.
- Make reports easy to reach the right person. In the Canada Computers case, the Reddit user said in an email to Metroland Media that he contacted the company twice and both support requests were closed without a response. A security contact page and a rule that card reports go straight to the owner can save days.
Guest checkout deserves its own line. In this case, member checkouts were not affected, according to the company. If your guest flow uses a different page or different scripts, it needs the same website card skimming checks as the rest of the checkout.
If You Find a Skimmer
Treat website card skimming as a privacy breach from the first hour, not only a website bug. Remove the script, keep a copy of it for the investigators, and record the date and time you found it.
Under PIPEDA, the Office of the Privacy Commissioner of Canada’s breach reporting guidance says organizations must report breaches that pose a real risk of significant harm to the commissioner, notify affected individuals, and keep records of all breaches. To decide, the OPC asks you to assess the sensitivity of the information and the probability of misuse.
Call your payment processor or acquirer the same day as well, and keep your notes on who you told and when.
Where Secur-IT Data Fits
Our team looks at your store the way an attacker would. Our penetration testing covers your websites and applications, carried out by OSCP-certified testers, with a written report ranked by what to fix first and a retest so you know the fixes worked.
Our vulnerability assessment includes web application and database vulnerability testing, quarterly rescans with trend analysis, and compliance reporting for PCI DSS and PIPEDA that you can share with your acquirer or your board.
For small offices, the questionnaire-based assessment is free. Testing of a live store is quoted after a short scoping call, because scope drives the work, and one checkout is not the same job as fourteen sites.
Frequently Asked Questions
Q: What is website card skimming?
Website card skimming is malicious code placed on an online store’s payment page that copies card details as shoppers type them and sends them to an attacker. The PCI Security Standards Council calls it e-skimming and says scripts running in shoppers’ browsers are now a significant target.
Q: Can a shopper tell that a checkout page has a skimmer?
Usually not. In the Canada Computers case, VideoCardz reported that the shopper who spotted the code was buying with his browser’s developer tools open, which most people never do.
Q: Does PCI DSS cover payment page scripts?
Yes. PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1 cover authorizing payment page scripts, checking their integrity and detecting tampering. The PCI Security Standards Council says they became effective as of 31 March 2025.
Q: My processor hosts the payment form. Am I still exposed?
Possibly. The Council’s updated SAQ A asks merchants with an embedded payment form to confirm their site is not susceptible to script attacks, either through their own controls or through confirmation from their PCI DSS compliant processor.
Q: Do I have to report a skimming incident in Canada?
Under PIPEDA, you must report to the Office of the Privacy Commissioner of Canada and notify affected people when a breach poses a real risk of significant harm, and you must keep a record of every breach. Stolen card data calls for that assessment.
If you want to know what is running on your checkout page today, and what to remove first, our team at Secur-IT Data can walk you through it.
References
- Canada Computers & Electronics: Press Room statement on the data breach incident
- Inside Halton (Metroland Media): Canada Computers breach exposes customers’ personal information
- PCI Security Standards Council: Information Supplement, Payment Page Security and Preventing E-Skimming
- Canadian Centre for Cyber Security: Security considerations for your website (ITSM.60.005)
- Office of the Privacy Commissioner of Canada: What you need to know about mandatory reporting of breaches of security safeguards
Ready to Strengthen Your Cybersecurity?
Secur-IT Data Solutions is a Toronto-based MSSP providing enterprise-grade cybersecurity for Canadian businesses. Whether you need OT security, AI threat protection, penetration testing, or full managed security services, our team is ready to help.
Talk to our team:
- 📞 Call us: +1 (647) 948-6768
- 📧 Email: info@securitdata.ca
- 🌐 Book a scoping call →

Krikor Tengerian is the CEO and founder of Secur-IT Data Solutions, a Toronto-based cybersecurity firm focused on helping Canadian organizations secure their infrastructure and critical systems. With over 25 years of experience across cybersecurity and IT infrastructure, he has supported organizations in hardening networks, protecting critical workloads, and aligning security controls with business and regulatory requirements.
Krikor actively shapes the direction and themes of Secur-IT’s educational content, collaborating with AI tools to structure, refine, and expand articles while providing the real-world context, use cases, and review to keep them accurate and practical for readers. He regularly shares insights on OT security, threat detection, incident response, and Canadian cybersecurity compliance to help industrial and commercial organizations better understand and reduce their cyber risk.




