Black Friday 2026: How to Secure Your Store's Checkout
By Laís Peixoto
Growth Marketer, Proteside
Published · 13 min read

Checkout security for Black Friday 2026 starts before November 27. Set a controlled change window, inventory your scripts, review access, test Pix, boleto and cards, and monitor changes to the page the buyer receives.
Checkout security for Black Friday 2026 starts before November 27. Set a controlled change window, inventory your scripts, review access, test Pix (Brazil's instant payment system), boleto (a Brazilian bank payment slip) and cards, and monitor changes to the page the buyer receives. Reconciling charges, payments and orders helps detect diversions and confirmation failures, but it does not, on its own, identify code that copies card data when the purchase goes through normally.
This guide organizes the work into three moments (before, during and after Friday, November 27) and points, in each item, to where the details are. It applies to any e-commerce platform and to stores of any size.
Why Black Friday attracts checkout attacks
The simplest reason is volume. Confi, using data from its Neotrust solution and in partnership with E-Commerce Brasil, projected R$ 13.3 billion in Brazilian e-commerce sales between November 26 and 29, 2026, up 20.7% from the same days in 2025. On Pix, Black Friday 2025 (November 28) set the record at the time, with 297.4 million transactions and R$ 166.2 billion moved in 24 hours, according to Banco Central do Brasil data published by Correio Braziliense, on a date that coincided with the payment of the first installment of the 13th salary (Brazil's mandatory year-end bonus).
The second reason is the criminals' own calendar. In December 2020, Sansec, a company that investigates attacks on online stores, reported that attackers had left a hidden backdoor in more than 50 large online stores months earlier and only used it on the eve of Black Friday. The package included a program that copied card data at checkout and another that recorded employees' passwords.
In Brazil, the most recent target is Pix. On September 9, 2026, Kaspersky described a campaign that inserts malicious code into the payment page of online stores to swap the QR code and the Pix Copia e Cola (the copy-and-paste Pix code), with 90 small and medium-sized stores identified. For the merchant, the sale shows up as abandoned or pending; the customer usually notices days later, when asking about the delivery. This type of attack, known as Magecart, is explained in Magecart: what it is and how to protect e-commerce.
Consumers already arrive suspicious. In a survey released in October 2026, Serasa Experian reported that 86% of Brazilians have already given up on a Black Friday deal for fear of fraud, and that fake websites (53%) and Pix scams (42%) are among their biggest fears. Consumer protection agencies are also watching stores: in November 2025, Procon-SP (São Paulo's consumer protection agency) recommended that the companies with the most complaints, among other practices, implement measures to help consumers identify fraud attempts.
One possible reading of this data, ours and not the sources': in the peak week, the store changes more things, the team looks less closely at each order, and one more pending Pix payment gets lost among thousands. That is the scenario that favors whoever tampers with the checkout.
Before Black Friday: what to sort out by Thursday
- Freeze changes to the checkout. Set a cutoff date (for example, the Monday of Black Friday week) after which nothing new goes into the payment page: no app, no script, no theme change. Security fixes are the exception, and even they go through testing. A frozen page makes it easier to notice the change nobody authorized.
- Inventory the scripts on the payment page. List everything that loads at checkout, who provides it, who approved it and why. These are controls addressed in PCI DSS requirement 6.4.3, where applicable; remember that the SAQ A revised in 2025 removed requirements 6.4.3 and 11.6.1 from the form and added an eligibility criterion for certain pages with an embedded payment form. Even where the requirement is not listed, exposure to scripts remains a risk. The step by step is in third-party scripts on the payment page and the summary of the requirements in PCI DSS 6.4.3 and 11.6.1: what they require.
- Review the campaign apps and plugins. Pop-ups, countdown timers, coupon spin wheels, cashback and chat tend to go in at the last minute and, without configuration, also load at checkout. Remove from the payment page whatever does not need to be there and set a removal date for each one. The guide is in promotion scripts on Black Friday. If marketing publishes tags on its own, see also Google Tag Manager and data theft at checkout.
- Lock down administrator access. Turn on two-step verification in the store admin panel, the hosting account and the payment provider, remove the accounts of people who have left (agencies included) and change shared passwords. Kaspersky includes two-factor authentication and regular password changes among its recommendations for merchants in the Pix swap campaign.
- Apply security updates now, not during the week. In the case described by Sansec in 2020, all the affected stores were running an unsupported version of their platform. Update the platform, theme and plugins in advance so you have time to test, and uninstall whatever is not in use.
- Check who provides each external library. An address you trust today can change owners tomorrow, as shown by the case told in Polyfill.io: the trusted script that became an attack.
- Make test purchases with each payment method. On an ordinary device, without an administrator login, pay a real low-value order by credit card, by debit card, by Pix and by boleto. Write down how each screen should look: the card form is your provider's, the QR code and the Copia e Cola lead to the correct name and CNPJ (Brazilian company tax ID), and the typeable line (the numeric code of the boleto) is the one the issuer registered. This record is the reference for comparison during the campaign.
- Show customers who will receive the money. Next to the Pix QR code and in the order email, write the name and CNPJ that the bank app will display. That is exactly what Procon-SP advises consumers to check before paying, and Kaspersky recommends the same to stores.
- Decide who responds and how. Agree in advance on who decides to turn off a payment method, who talks to the provider and who handles customers, with phone numbers and a single channel for the week. The response guide is in how to investigate a diverted payment at checkout.
During Black Friday: what to monitor for each payment method
Requirement 11.6.1, when it applies to the environment and the PCI validation method, covers detecting unauthorized changes to payment pages and relevant HTTP headers at least weekly or at a frequency defined by risk analysis. The PCI SSC's own guidance recommends frequent or real-time monitoring when possible, because a change can act unseen between one check and the next. On Black Friday, a week is the entire campaign. The methods are in how to monitor changes to the checkout; below are the signals for each payment method.
Pix
- Pending Pix rate. Every few hours, track how many charges were generated and how many were paid. A sharp drop in Pix conversion, with no change in price or traffic, matches the symptom described by Kaspersky: the sale shows up as abandoned or pending.
- "I paid and the order didn't go through." Every message like this deserves a look at the receipt. If the recipient on the receipt is neither the store nor your provider, treat it as a possible diversion. How to handle it is in the customer paid by Pix and the order didn't go through.
- A receipt is not proof. Release the order only when your provider confirms the credit for that charge. The details are in fake Pix receipt: how to spot one.
- Repeat the test purchase once or twice a day and compare the QR code displayed with the one issued. The on-screen signs are in altered Pix QR code: how to tell and what to do and the full list in Pix security checklist for online stores.
Credit card
- Customers who typed their card twice. The PCI SSC guidance describes a type of attack in which a fake form appears before the real one, shows an error and leads the customer to enter the data again. Reports like this are a strong signal.
- Visual change in the form. A new field, an extra payment step or a form that looks different from the one recorded in the test.
- Silence is also a signal. The same guidance notes that, in the most discreet type of attack, the purchase works normally for the customer and for the store, and the theft only shows up later, in chargebacks. That is why monitoring the page matters more than waiting for complaints. See credit card protection.
Debit card
- Watch the debit form as closely as the credit form. In practice, when debit is paid on the same page, the code that copies one card copies the other.
- Pay attention to reports of strange debits. In practice, since debit takes money straight from the account balance, the customer tends to notice early and complain to the store and the bank. What changes in the dispute is covered in debit card data theft and on the debit card protection page.
Boleto
- Compare boletos issued and paid. A boleto the customer says they paid that does not appear with your issuer may have been paid to another beneficiary.
- Check the typeable line on screen. In the test purchase, compare the numbers displayed with those registered with the issuer. How the swap happens is in tampered boleto: typeable line swapped on screen; the boleto protection page shows the check.
If the store accepts stablecoins, the same logic applies to the wallet address and the network, detailed in stablecoins at checkout: network, address and memo.
Reconciliation: payment received vs. order
An important control for detecting payment diversion and operational failure is comparing charges, provider confirmations and approved orders, at a frequency that matches the store's volume. Orders without payment, payments without orders and a conversion drop in a single payment method are the three numbers that deserve an alert. For Pix, set up automatic reconciliation between the charge issued, the provider confirmation and the order, with alerts for pending charges above normal or past the expected time. For cards, add monitoring of the scripts and the page: code that copies card data can act without changing the status of the sale.
After Black Friday: reconciliation, response and customer guidance
- Do a full reconciliation. Close out, payment method by payment method, what was charged, paid, approved and delivered between Thursday and Monday. Investigate every difference before filing it away as abandonment.
- If something was swapped, contain it without deleting. Suspend the affected payment method, keep copies of the page, the scripts and the logs, and only then clean up. The 24-hour guide is in how to investigate a diverted payment at checkout. For cards, notify the acquirer or the provider through their incident channel.
- Guide your Pix customers. Procon-SP advises anyone who paid the wrong recipient to contact their bank immediately, report the case as fraud, request a refund through the Special Return Mechanism (Mecanismo Especial de Devolução, MED), notify the store and keep their receipts. The agency says Banco Central do Brasil extended the deadline for using the MED from 30 to 80 days. What changes for the store is in MED 2.0: what changed in Pix refunds, and the agency's alert in Procon warns about altered Pix QR codes.
- Remove the campaign tools. Uninstall apps and delete scripts that went in only for Black Friday, and revoke the permissions they received. Whatever stays unused becomes an open door for the next date.
- Update the inventory and the plan. Record what changed, what triggered alerts and how long the response took. This history becomes evidence for PCI DSS and shortens the response at Christmas.
Scams that do not go through the store's checkout, such as a fake QR code printed or sent by message, follow a different logic; see quishing: the fake QR code scam.
Quick monitoring plan: metrics, triggers and owners
- Pix generated vs. Pix confirmed: a drop may indicate an integration failure or a diversion. Check the charge issued and the beneficiary in the app, and open an investigation if they do not match.
- Payment confirmed vs. order approved: the gap may indicate a failure in the provider's automatic notification, in reconciliation or in operations. Cross-check transaction identifiers, notifications and the provider's statement.
- New script or container at checkout: it may be a forgotten authorized change or malicious code. Compare it with the inventory and contain whatever was not approved.
- Form or QR code that looks different: it may be a test, a site error or tampering. Compare it with the reference from the test purchase and with the site's publishing history.
- Complaints about charges, cards or orders: they may indicate an incident or an operational problem. Gather the evidence and call the designated owner.
Set thresholds based on the store's own history, not on a universal percentage. The routine should include testing in different environments and on different devices, taking care not to interrupt legitimate campaigns without confirmation.
Final checklist
- Cutoff date for checkout changes set and communicated.
- Inventory of payment page scripts, with an owner and a justification.
- Campaign apps off the payment page, with a removal date.
- Two-step verification on the admin panel, the hosting and the provider; old accounts removed.
- Platform, theme and plugins updated and tested.
- Test purchases made by credit card, by debit card, by Pix and by boleto, with a record of how each screen should look.
- Recipient name and CNPJ shown next to the Pix QR code and in the order email.
- Owners and response channel defined.
- Payment vs. order reconciliation several times a day, per payment method.
- Alert for Pix pending past the expected time and for conversion drops per payment method.
- Plan to remove the campaign tools and a review after the date.
Frequently asked questions
When should I freeze checkout changes?
A few days before the campaign starts, with time to test. A practical rule is to freeze at the start of Black Friday week and keep the freeze until Cyber Monday, allowing only tested security fixes.
Does using my payment provider's card form solve the problem?
It reduces the exposure of card data, but it does not automatically protect the rest of the page. PCI scope is not the same for every integration: the SAQ A revised in 2025 replaced the explicit requirements with an eligibility criterion for certain embedded forms. In addition, the Pix QR code and the boleto's typeable line can be tampered with outside the provider's iframe.
Is the weekly PCI DSS check enough on Black Friday?
When 11.6.1 applies, the weekly reference is a minimum control level or the frequency set by a risk analysis. On Black Friday, more frequent monitoring may be prudent; for operations under SAQ A, check the specific eligibility criterion for embedded pages.
What should I do if a customer paid by Pix and the order does not show up?
Ask for the receipt and check the recipient. If it is the store or your provider, the case is likely a reconciliation issue; if it is someone else, treat it as a possible diversion, advise the customer to contact their bank and request the MED, and follow the investigation guide.
To wrap up
Black Friday does not call for new tools at checkout; it calls for fewer changes, more testing and careful reconciliation. For the part no internal process can see, the payer's browser, Proteside checks whether the QR code, the Pix Copia e Cola, the typeable line, the wallet address and the card form displayed are the ones the store issued, blocks the swap before confirmation and records the evidence, on any e-commerce platform, as described in solutions for online stores.


