Skip to content

Black Friday Scripts: How to Protect Your Store's Checkout

Laís Peixoto

By Laís Peixoto

Growth Marketer, Proteside

Published · 7 min read

Payment QR code with a fake layer peeling off on top, next to the Proteside shield. Payment methods: Credit card, Debit card, Pix, and Boleto.

Pop-ups, pixels, chats and cashback apps installed for Black Friday can widen the checkout's attack surface, especially when the code loads on every page. The goal is not to give up marketing tools, but to define where they can run, who can change them and when they will be removed.

Pop-ups, pixels, chats and cashback apps installed for Black Friday can widen the checkout's attack surface, especially when the code loads on every page. The goal is not to give up marketing tools, but to define where they can run, who can change them and when they will be removed.

Why a campaign tool becomes a checkout risk

To install a pop-up or a countdown timer, the vendor asks you to paste a snippet of code into your theme or enable an app on your platform. From then on, each customer's browser fetches the file from the vendor's server on every visit. If the file changes there, your store changes with it, without your team publishing anything.

The PCI SSC, the council that maintains PCI DSS, states in its March 2025 guidance on the payment page that analytics, marketing, tracking and tag management scripts can be manipulated to capture payment data, and that the vendor can change the file without the store knowing.

On Black Friday, tools go in hastily, through different people (marketing, agency, customer support), and nobody writes down where each one loads. The risk is not limited to intrusions: excessive permissions, wrong settings and altered dependencies also matter. During the promotional week, fast changes make it harder to tell what should or should not be on the checkout.

Two recent cases involving legitimate tools

Chat and tracking. On September 16, 2026, Sansec, a company that investigates attacks on online stores, reported that the tracking script and chat widget of Brevo, a marketing and customer support platform, served malicious code for about four hours on September 14, on more than 100,000 sites by the company's estimate. Visitors saw a fake verification screen asking them to run a command on their computer. According to BleepingComputer, Brevo said the files on its servers were not altered: the swap happened on the way to the browser, and checks done only at the source did not catch it.

Audience measurement on the checkout. On October 26, 2026, Sansec described card-stealing code inserted into the audience analytics script of Convertr, a Brazilian platform that runs checkouts for dozens of fashion brands. The file loaded on every checkout on the platform and acted only on payment pages, copying the card number, expiration date and security code, the cardholder's name and CPF (the Brazilian individual taxpayer number). Convertr removed the code on October 27. Sansec warned that browsers can keep the contaminated file for up to 24 hours after the cleanup.

In both cases, these were common services, installed for good reasons.

How to install campaign tools without opening up the checkout

  1. List what the campaign will bring in. For each pop-up, countdown timer, prize wheel, cashback, chat or pixel, record the vendor, who requested it, who installed it and which pages it appears on.
  2. Ask whether it needs to be on the payment page. Almost nothing does. Countdown timers and pop-ups make sense on the storefront and the product page; cashback usually depends only on the order confirmation, which can be recorded outside the screen where the customer pays. Configure each tool not to load on the checkout. The PCI SSC guidance points to limiting scripts to what is strictly necessary as one of the simplest ways to reduce exposure.
  3. Be careful with one-page checkouts. When the browser does not reload between cart and payment, the PCI SSC notes that scripts loaded earlier remain active. Test whether the tool really disappears at the payment step.
  4. Review the app's permissions. Campaign apps often ask for access to edit the theme or read orders and customers. Accept only what the function requires, turn on two-step verification on the vendor account and don't share the administrator login.
  5. Prefer real isolation. An isolated frame (iframe) can limit a script's reach when it is served from another address and, where applicable, has the appropriate isolation (sandbox) restrictions. An iframe without effective isolation is no guarantee of security. Combine it with a restrictive content security policy (CSP) and with checking the scripts that actually load.
  6. Test before going live. Make a test purchase with each payment method: credit card, debit card, Pix (Brazil's instant payment system) and boleto (a Brazilian bank payment slip). Check that the card form is your provider's, that the QR code and Pix Copia e Cola (the copy-and-paste Pix code) lead to the right recipient and that the boleto's typeable line is the one issued.
  7. Set a removal date. Before installing, decide when each tool comes out (for example, the day after Cyber Monday). Removing means deleting the code from the theme or uninstalling the app, not just ending the campaign in the dashboard. Revoke keys and permissions as well.

For organizations to which these requirements apply, steps 1 and 2 help maintain a script inventory and justification (6.4.3); continuous monitoring, beyond the one-off tests in step 6, contributes to the change detection controls of 11.6.1. The applicable validation, including the SAQ A conditions, must be confirmed separately. The details are in third-party scripts on the payment page and on the PCI DSS compliance page.

Signs that a tool has tampered with payment

  • A pop-up, chat or prize wheel appears on top of the card form or the Pix QR code.
  • Customers say they typed in their card twice. The PCI SSC describes this pattern as a type of attack in which a fake form comes before the real one.
  • Generated but unpaid Pix charges go up, or messages arrive from people who paid and did not see their order approved.
  • A script that nobody remembers approving shows up on the payment page.

Tag managers need separate care, because they let marketing publish scripts without going through the technical team: see Google Tag Manager and data theft at checkout. The full plan for the date is in the guide to protecting your checkout on Black Friday.

Approval checklist for a new campaign tag

Before publishing any marketing script, ask the person responsible to answer:

  • What business problem does the tool solve and on which URLs does it need to appear?
  • Does it need to run on the cart, checkout and post-purchase pages, or only on the storefront?
  • What data and permissions does it request? Who has publishing access?
  • What is the authorized version or origin? Is CSP, SRI or isolation applicable?
  • Who will run the test with Pix and card, who monitors changes and when will the tool be uninstalled?

Keep the answers with the inventory. This record reduces reliance on the team's memory when investigating an incident.

Frequently asked questions

Can a coupon pop-up steal card data?

A malicious script with access to the page can capture data typed into fields the page controls or display a fake form. Simply by being on the main page, it cannot directly read the fields inside a payment iframe protected by another origin.

Does the cashback app need to run on the checkout?

In most cases, no. Ask the vendor whether the purchase can be recorded through the order confirmation; if they require the script on the payment page, ask for the justification in writing and record it in the inventory.

I use my provider's card form. Do I still need to worry?

Yes. The provider's form can isolate card data, but the page around it can still be tampered with. The compliance scope depends on the integration and the validation instrument: the 2025 SAQ A replaced the two explicit requirements with an eligibility criterion regarding scripts in certain embedded forms. In addition, the Pix QR code and the boleto line usually appear on the store's own page.

To wrap up

Campaign tools are welcome on the storefront and unnecessary on the screen where the customer pays. In case a trusted vendor changes the file without warning, Proteside checks, in the payer's browser, whether the QR code, the Pix Copia e Cola, the typeable line and the card form are the ones the store issued, blocks the swap before confirmation and records the evidence, as described in solutions for online stores.

How we create our content

Back to blog