Debit Card Data Theft: What Changes at Checkout
By Laís Peixoto
Growth Marketer, Proteside
Published · 4 min read

In debit card data theft at checkout, malicious code works on the same payment page, but the money leaves the account right away. In Brazil, Abecs says unauthorized transactions can be disputed with the card issuer, and merchants should monitor the debit form as its own flow.
Debit card data theft at checkout can happen the same way as credit card theft: malicious code inserted into the payment page copies what the buyer types and sends it to criminals. The difference comes afterward. With debit, the money leaves the account right away, disputes in Brazil go through the card issuer, and the merchant needs to watch the debit form as carefully as the credit one.
Context: debit has become an online payment method
According to Abecs, the Brazilian card industry association, debit use in card-not-present purchases grew 359.8% between the first quarter of 2020 and the first quarter of 2026, compared with 247% for credit over the same period (Abecs data on online card purchases in Q1 2026).
Part of that growth comes from the standardization of online debit. In the flow Abecs described in 2023, the buyer pays directly on the merchant's checkout, without being sent to another platform, at the companies taking part in the program (standardization of online debit). From that comes our own reading, not Abecs's: in this model, debit goes through the same payment page as credit.
The attack: what the source says and what it doesn't
The attack known as Magecart (the name given to groups that insert malicious code into online stores to copy card data at the moment of purchase) is already explained in our guide to Magecart and how to protect e-commerce, in how card data copying happens at checkout and in the article on fake payment forms at checkout.
In January 2026, BankInfoSecurity reported that Magecart-style attacks continue, with researchers detailing an active campaign against WooCommerce stores that imitates the payment provider Stripe. The report refers to payment card data and does not separate credit from debit. The idea that debit is exposed in the same way is our own reading, based on the fact that, in standardized online debit, payment happens on the store's own checkout.
What changes when the card is a debit card
For the buyer, the loss is immediate. With debit, the amount leaves the balance at the time of purchase. The FTC, the US consumer protection agency, recommends checking debit transactions more closely precisely because the money leaves the account right away.
How disputes work in Brazil. Abecs says that all online debit transactions are recorded on the account statement and that unauthorized transactions can be disputed with the card issuer. In 2026, the association cited the chargeback (the dispute of a purchase) in cases of improper charges or commercial disagreement as one of the advantages that help explain the growth of online debit. The Abecs pages we consulted do not state a deadline for this dispute, so the safest move is to contact the issuer as soon as the charge shows up on the statement.
A comparison with the United States, for illustration only. There, the federal law described by the FTC treats credit and debit differently when the card number is used without the card having been lost (the case of data copied at checkout). With credit, the cardholder is not liable for the charges. With debit, that protection depends on notifying the bank within 60 calendar days after the statement is sent. This is a US rule and does not apply to Brazilian buyers. It only shows that credit and debit can come with different protections.
For the merchant, the debit form is one more point to watch. In standardized online debit, payment happens directly on the merchant's checkout. If that form is altered, the problem starts on the store's own page, whichever payment method the customer chose.
What the buyer can do
- Check the account statement often, because with debit the money leaves right away.
- On seeing a charge you don't recognize, contact the card issuer quickly and dispute the transaction.
- Keep the record of the charge on the statement for the dispute.
What the store can do
- Treat credit cards and debit cards as two separate flows. If debit uses a different form or step, it needs to be monitored too. There are pages on protection for debit cards and protection for credit cards.
- Keep your platform, themes and extensions up to date.
- Limit and track the scripts that run on the payment page. PCI DSS requires this in requirements 6.4.3 and 11.6.1, explained in what these requirements demand from the payment page.
- Check what the buyer sees, not just what the server sent. The campaign described above imitated the payment provider itself.
- Have a response plan. If you suspect something, investigate the payment path at checkout and advise affected customers to contact their card issuer early.
Online debit grew 359.8% in six years and is now paid on the checkout itself. The practical question for a store is whether the debit form the customer sees is the same one it published. Proteside runs that check in the browser of the person paying.


