Online Store Hacked? Do These 7 Things in the First Hour
If you have just found out your online store was hacked, what you do first decides how much evidence survives and who has to be told. Work through these seven steps in order.
TL;DR: Stop card payments, call your payment provider, and change nothing on the store until they say whether an investigator must look. Then work through the steps below.
- Stop taking card payments on the affected store. Do it from your payment provider's dashboard, or ask your host or platform support to pause checkout; if the only way is the store's own admin, tell your provider first. Do not shut down, restart or rebuild anything. On a hosted platform (Shopify, Wix, Squarespace) there is no server for you to touch, so ask the platform's support.
- Call your payment provider or acquirer now. The acquirer is the bank or company that processes your card payments; for many small stores the payment provider is the one to call. Say you suspect a compromise, and ask what they need from you and whether an investigator must look before anything is changed.
- Leave the evidence alone. Do not delete files, clear logs, restore a backup, or update and "clean" anything yet.
- Ask your host or platform support to keep the logs and take a snapshot of the files and database. Make your own copy and store it off the server if you can.
- Start a written log: what you saw, what you did, the date and time, and who did it.
- From a clean device, change the passwords and turn on two-factor authentication for accounts that are not the hacked store itself: your email, the payment-gateway dashboard and your domain registrar. For your hosting control panel login, ask your provider first if you are not sure whether an account counts as part of the compromised system. Change passwords and keys on the store only after your provider has said whether an investigator needs it untouched, and after the copy exists.
- Find your platform in the table below and open its guide.
Should I take my online store offline?
Pause card payments first. The PCI Security Standards Council tells businesses to know how to isolate systems without simply powering them off, because turning systems off "may make the investigation more difficult and result in lost evidence or data." Visa's guidance says to disconnect the system from the internet, stop using it to process payments, and not turn it off, restart or reboot it.
On a hosted platform, neither document says how to isolate a store, and we will not invent steps. Ask the platform's support what pausing checkout means on their side.
If your checkout embeds a provider's payment form (an iframe) or sends customers to the provider's page, you are still responsible for part of it. In the PCI Council's e-skimming guidance, the merchant remains responsible for the scripts on the pages that include the iframe or the redirection. Only with a fully outsourced site does it list nothing for you under PCI DSS requirements 6.4.3 and 11.6.1.
What kind of hack is it?
The longer list of signs is in how to tell if your website has been hacked.
- Customers report card fraud, or odd fields or scripts appear at checkout → card skimmer. Check first: every script that loads on checkout and payment pages. Card payments: stop them.
- Pages you never created show in Google → SEO spam. Check first: search Google for your domain and look for pages you did not publish. Card payments: stop them if checkout or admin could be touched.
- Visitors land on another site → redirect. Check first: open the store on a phone in a private window; only some visitors may be sent away. Card payments: stop them if checkout or admin could be touched.
- An admin you did not create, orders or refunds you did not make, changed payout or bank details → account takeover. Check first: the admin user list, recent orders and refunds, payout details. Card payments: stop them. Someone with admin access can change the checkout, so treat it as a possible skimmer.
- A browser or antivirus warning, but you find nothing wrong → a flag, possibly with no hack (see this guide). Check first: which vendor flags the domain. Card payments: stop them only if you also see a sign above.
You cannot rule out a skimmer by looking at the page. The PCI Council notes that silent skimming attacks "may go undetected for long periods of time", and Sansec's June 2026 research describes a skimmer loaded from a real Google Tag Manager container that fetched its payload on checkout pages.
Who do I contact, and in what order?
- Payment provider or acquirer (immediately): say you suspect a compromise. Ask what they need, whether an investigator must look first, and how to notify the card brands.
- Host or platform support (same hour): keep logs, snapshot, retain system images, suspend if needed.
- Your developer or agency, and your shopping-cart vendor (after the copy exists): give them your written log and ask them to change nothing until your provider answers. Tell the vendor if a flaw in the payment system looks involved.
- A lawyer or your data-protection contact (same day): notification clocks can start when you become aware.
- Law enforcement or your country's cybercrime reporting service (immediately): your log. Visa strongly recommends notifying local or national law enforcement immediately.
- Cyber insurer, if you have one (before paying for any work): check your policy for notice requirements.
Visa's guidance tells a compromised entity to notify its acquiring bank immediately, so the acquirer is your route to the card brands. If you do not know your acquirer, the document names Visa's regional Global Risk Investigations group as the contact.
What must I not touch before the copy is made?
- Do not log in as admin on the compromised system and start changing things. Unless your investigator says otherwise, the PCI Council and Visa both say not to log onto compromised systems, change passwords or log in as admin.
- Do not turn it off, restart or reboot it.
- Do not delete suspicious files, clear logs, apply updates or remove software to recover quickly. The PCI Council says careful preservation of evidence is vital for finding the root cause and the perpetrators.
- Do not restore a backup over the site. It overwrites what you are supposed to preserve.
- Do not keep taking payments on the compromised system.
- Do not pick the investigator yourself. The PCI Council says the card brands may require an independent forensic investigation by an investigator listed on its website, and Visa says not every compromise needs one. Ask your acquirer; an investigator must be independent of the business it investigates, so do not hire your usual consultant for the role without checking.
What to preserve: the PCI Council lists original evidence, security events, and web, database and firewall logs, and Visa says to ask a hosting company to retain logs and system images. We would also keep the injected code itself, unknown admin accounts, API keys, order and refund history, and payment-gateway logs.
You will want to change every password at once, but the PCI Council and Visa say not to change passwords on the compromised system before the investigator has looked. Step 6 puts the accounts around the store first.
Where do I start on my platform?
| Platform | Look here first |
|---|---|
| WooCommerce | The checkout in a private window on a phone, and unknown WordPress admin users |
| Magento / Adobe Commerce | Whether the StyleSmuggler hotfix and the October patch are installed, then PHP files in pub/media |
| PrestaShop | Your checkout while logged out, then modules/ and theme templates for code you did not add |
| OpenCart | PHP files in image/catalog, extensions you cannot account for, unknown admin users |
| Shopify | Staff accounts and permissions, the store activity log, installed apps |
| Wix | Content, pages or redirects you did not publish, which point to account access |
| Squarespace | DNS records, nameservers, email routing and account access |
For any other platform, start with how to clean a hacked website.
Do I have to tell my customers, and when?
This page is not legal advice. A lawyer or your data-protection contact decides what applies to you; these are the facts that make you call them on day one.
Regulators and customers.
- GDPR, if it applies to you. The controller must notify the supervisory authority "without undue delay and, where feasible, not later than 72 hours after having become aware of it", unless the breach is unlikely to result in a risk to people (Art. 33). When the risk to them is high, you must also tell the people affected without undue delay (Art. 34). Art. 33 also requires you to document the breach, its effects and the action taken.
- Elsewhere. The FTC's guide for businesses says US states have their own breach-notification laws and advises notifying law enforcement.
Card brands. Visa's rules require a compromise to be reported to Visa within three calendar days of evidence that raises a reasonable suspicion (Visa). Ask your acquirer how that applies to you and who files the report.
Practical advice for your message to customers, not a rule from the sources: say what happened, what you have done, and what they should watch for. Never ask customers for card details or passwords by email, and do not promise a date you do not control.
When can I take payments again?
Confirm each of these with your provider rather than deciding alone:
- Your provider, and the investigator if one was required, has cleared the store.
- The way in is found and closed.
- Every password, API key and payment credential on the store is rotated.
- Every script on the checkout, and on the pages that embed or redirect to payment, is one you can account for.
- A test order works.
My store is clean but still flagged — what now?
A flag is a separate event from the hack: it can arrive later, or with no hack at all, and it can remain after the store is clean. See why an online store is blocked and why a cleaned site is still blacklisted. If vendors still flag the domain after the cleanup, the free check shows which ones. A correctly formatted removal request is sent to every flagging vendor that accepts one by email, within 48 hours of payment (in practice within the first hour). Vendors that only take a web form or manual review get a ready-to-paste request on the dashboard. The removal service costs a one-time €49 per domain, and it does not clean sites, scan for malware or investigate incidents.
Pause card payments first, from your payment provider's dashboard or by asking your host or platform support to pause checkout. Taking the whole site down is a separate decision: the PCI Security Standards Council says turning systems off may make the investigation more difficult and result in lost evidence, and Visa's guidance says not to turn off, restart or reboot a compromised system. Ask your payment provider and your host how to isolate the store without powering anything off.
Your payment provider or acquirer, immediately: say you suspect a compromise and ask what they need and whether an investigator must look before anything is changed. Visa's guidance tells a compromised entity to notify its acquiring bank immediately. Then call your host or platform support to keep the logs and take a snapshot, and speak to a lawyer or your data-protection contact the same day.
It depends on where you and your customers are, and this is not legal advice. Under the GDPR the supervisory authority must be notified not later than 72 hours after you become aware of a breach, unless it is unlikely to result in a risk to people, and affected people must be told without undue delay when the risk to them is high. Visa's rules require a compromise to be reported to Visa within three calendar days of evidence that raises a reasonable suspicion, so ask your acquirer how that applies to you and who files the report. US states have their own breach-notification laws, so ask your provider and a lawyer on day one.
Neither yet. Restoring a backup overwrites the evidence the PCI Council and Visa say to preserve, and cleaning changes it. Make a copy first, ask your payment provider whether an investigator must look, and then use the guide for your platform to clean the store and close the way in.
A flag is a separate event from the hack: it can arrive later, or with no hack at all, and it can remain after the store is clean. Google's Search Console Help says a security review can take a few days to a few weeks, and a review should be requested only after the site is cleaned and the vulnerability fixed. The free blocklist check shows which vendors still flag the domain.