How to Handle WooCommerce Chargebacks & Disputes: A Store Owner’s Guide

A chargeback notification arrives from your payment processor. You have a few days to respond — or the money disappears and you take the fee on top. If you’ve never handled a dispute before, the whole process can feel bewildering: different portals, cryptic reason codes, evidence requirements that vary by card network, and a timeline that runs whether or not you’re paying attention.

This guide walks through it plainly. What a chargeback is at the mechanics level, why it happens (including the types you might not have expected), what the deadline actually means, what evidence helps and what doesn’t, and how to make a rational decision about whether to fight or accept. There’s also a section on prevention — the habits that reliably reduce disputes over time — and a short note on tooling for stores that need to track this stuff systematically.

No scare tactics here, and no suggestion that chargebacks are inherently catastrophic. Most stores deal with them at a low rate and respond to them competently. The goal of this guide is to make sure you’re one of them.

What a chargeback actually is (and isn’t)

A chargeback is a forced payment reversal initiated by a cardholder through their bank, not through you. When a customer disputes a charge, their bank credits the amount back to them immediately and then reaches out to your payment processor demanding that you justify the transaction. If you don’t respond — or if your response doesn’t satisfy the card network’s review — the bank keeps the money, you absorb the loss, and you pay a dispute fee (typically $15–$35 per case, depending on your processor and plan).

It is important to separate chargebacks from refunds. A refund is a merchant-initiated action: you decide to give the customer their money back, and the money flows from your account to theirs. You control the timing, and there’s no fee attached (beyond any payment processing that can’t be recovered). A chargeback is the customer going around you — they’re asking their bank to take the money back without your agreement. The two paths are completely independent. A customer can dispute a charge even after you’ve already issued a refund, which is why proactive, documented refunds often make more sense than waiting for a dispute to arrive.

Why customers file disputes

Understanding why a dispute was filed matters because the reason code shapes what evidence you need to provide. There are broadly four categories:

True fraud — unauthorized transactions

The cardholder genuinely didn’t make the purchase. Their card details were stolen — through a data breach, phishing, or physical theft — and someone else used them in your store. These disputes are typically filed under codes like “unauthorized transaction” or “fraud.” The cardholder is telling the truth. You shipped to a fraudster, not a legitimate customer. Fighting these cases is rarely productive unless you have strong evidence that the real cardholder did authorize the order (device fingerprint matching, account age, prior purchase history from the same card).

Friendly fraud — disputed claims about a legitimate purchase

The cardholder made the purchase but disputes it anyway, claiming the item never arrived, was not as described, or that they didn’t recognize the charge on their statement. This is the most contentious category because it sits on a spectrum from honest misunderstanding to deliberate exploitation. An elderly customer who forgot they bought something is at one end. A calculated shopper who files a dispute every few months to recover money from purchases they received and kept is at the other. Friendly fraud is, by many industry estimates, the dominant driver of chargebacks for most e-commerce merchants — though precise figures vary widely by product category and store type.

Processing errors

The merchant made a mistake: a customer was charged twice, the wrong amount was charged, or a subscription was billed after cancellation. These are the most avoidable category. They don’t require a dispute at all when the error is caught quickly and a refund is issued before the customer reaches their bank. If you see this pattern repeatedly, the fix is operational — cleaner subscription management, duplicate-charge detection, faster customer service response — rather than dispute strategy.

Customer service failures

The item arrived broken. The order never shipped. The return was refused when it shouldn’t have been. The customer emailed you three times and got no response. These disputes reflect a customer who felt they had no other option. They are painful because they’re usually preventable — a faster or more generous customer service response would have converted this into a refund instead of a chargeback. The dispute fee is almost always more expensive than the refund would have been.

The dispute timeline: what happens and when

Every chargeback moves through a defined lifecycle. The exact steps vary slightly by card network (Visa, Mastercard, American Express, and Discover each have their own programs), but the general flow is consistent:

1. Dispute filed. The cardholder contacts their issuing bank. The bank evaluates the claim and, if it passes their initial screen, files a formal dispute with the card network.
2. Funds pulled from your account. Almost immediately — before any review. Your processor debits the disputed amount and the dispute fee from your settlement balance. This is not a final decision; it’s a provisional reversal while the case is reviewed.
3. You receive a notification. Your processor notifies you, typically by email and through your processor dashboard. The notification includes the dispute reason code, the deadline for your response, and instructions for submitting evidence.
4. You respond (or don’t). If you submit evidence before the deadline, the case goes to the card network for a review cycle. If you do nothing, the dispute closes automatically in the cardholder’s favor and the funds don’t return.
5. First ruling. The card network issues a finding. If it’s in your favor, the funds are reinstated. If it’s in the cardholder’s favor, the dispute is closed and you’ve lost. Depending on the network and the case, one or both parties may escalate.
6. Pre-arbitration / arbitration (optional). Either party can sometimes escalate the decision to a second review. This extends the timeline by weeks or months, adds fees, and is generally only worth pursuing for large amounts. Most disputes are settled at the first ruling.

The entire timeline from notification to final decision runs anywhere from a few weeks to three months, depending on whether the case escalates. During all of that time, the funds are held by the card network — not in your account.

Deadlines — the one thing you cannot miss

The response deadline is printed in your dispute notification. It is the single most important piece of information in that email. Miss it, and the dispute closes against you automatically — regardless of how strong your evidence is, regardless of how clearly you were right. There is no grace period and no appeal based on “I didn’t see the email in time.”

Response windows are short. Stripe, for example, typically gives merchants seven days from when the dispute is created to submit evidence (for most card types). WooPayments uses a similar window. Other processors vary, but you should assume you have less than two weeks from the notification date. In practice, the evidence collection and submission process takes longer than people expect the first time, so treat the deadline as something that needs to move to the top of your priority list the moment the notification arrives — not “something I’ll handle this weekend.”

What the deadline resets look like in practice

Many processors show deadlines in their dispute portal as a countdown: “7 days remaining,” “3 days remaining.” Do not interpret “7 days remaining” as “I have 7 days.” Shipping confirmations need to be gathered. Customer communication needs to be pulled from your email system. If a delivery confirmation PDF needs to come from a carrier’s website, those systems have their own downtime. Treat it as “I have 7 days to have everything submitted” — which functionally means starting today.

What evidence wins a dispute

The card networks give you a brief window to submit a written rebuttal and supporting documentation. What you include depends heavily on the dispute reason code, but some evidence types carry weight across nearly every category.

Evidence that consistently helps merchants

• Delivery confirmation with tracking. A carrier tracking number showing the package was delivered to the cardholder’s address is one of the strongest pieces of evidence for “item not received” disputes. Include a screenshot or PDF of the tracking history, not just the tracking number.
• Signed proof of delivery. For high-value shipments, signature confirmation eliminates most “I never got it” claims. If your carrier service provides signatures and you didn’t require one, consider whether that changes your policy going forward.
• Customer communication showing acknowledgment. An email thread where the customer confirms they received the item, or a message they sent weeks after delivery with a complaint about something other than non-delivery, undercuts the “never arrived” claim.
• Order details matching the billing address and cardholder name. When the shipping address, billing address, and name all match the card on file, it’s harder for the issuing bank to accept a “I didn’t authorize this” claim.
• Terms of service the customer agreed to at checkout. For “not as described” claims, your published product description, return policy, and terms of sale — which the customer accepted — form the basis of your rebuttal. Include a screenshot of what the product page said at the time of purchase if it’s something that could have changed since.
• Prior order history. A customer who has purchased from you seven times and is now claiming they don’t recognize the transaction is harder to believe than a first-time buyer. Order history — showing that this card, name, and email have been used successfully before — is relevant context.
• IP and device data at the time of checkout. Some processors allow you to submit technical data about the checkout session. This is more relevant for fraud disputes, where you’re trying to show the real cardholder was the one checking out.

Evidence that doesn’t help as much as people expect

• Your return policy alone. Pointing to “all sales final” in your terms doesn’t override a cardholder’s right to dispute — particularly if the dispute is filed as fraud rather than as a return request. Your policy is one piece of context, not a trump card.
• Internal notes or your own recollection. Assertions from you without supporting documentation carry little weight. “I remember this order and I shipped it” is not evidence.
• Screenshots of your own dashboard. Showing that the order is marked “Completed” in WooCommerce confirms you processed it — it doesn’t confirm the customer received it. You need independent confirmation from the carrier.

Step-by-step: responding to a WooCommerce dispute

Here is the practical response workflow, from the moment the notification arrives to submission.

1. Read the notification and note the deadline

   Open the dispute in your processor dashboard (Stripe, WooPayments, PayPal, or whichever gateway you use). Note the dispute reason code and the response deadline. Put the deadline in your calendar right now — before you do anything else. If the deadline is less than 72 hours away, move this to the top of your queue immediately.

2. Pull the order in WooCommerce

   Find the order in WooCommerce. Collect: the order date, the billing name and address, the shipping address, the product or products ordered, the order total, and any notes on the order. Check whether there are any previous orders from the same email address or similar billing details.

3. Get the shipping and delivery confirmation

   If you shipped a physical product, go to the carrier’s tracking page and pull a screenshot or PDF of the full tracking history, including the delivery event and the address it was delivered to. For digital products, pull your delivery logs showing when the file was downloaded or when the licence key was sent and accessed.

4. Pull all customer communication

   Search your email system for every message from that customer’s email address. Include all of it: order confirmations you sent, any queries they raised, any responses you gave. If there’s a message where they acknowledge receipt, or where they raise a complaint about something other than non-delivery, that’s important. If there’s no communication at all after the order, that’s also relevant context.

5. Decide whether to contest or accept

   Before building the full evidence package, decide honestly: is this worth fighting? If you don’t have shipping confirmation, if the product genuinely wasn’t as described, or if contesting a small-value dispute would take more time than it’s worth — accepting may be the right call. See the “when not to fight” section below before spending an hour assembling evidence for a $12 order.

6. Write your rebuttal and submit through the processor portal

   Compose a short, factual narrative explaining why the dispute should be resolved in your favor. Attach your supporting documents — tracking confirmation, email screenshots, order history. Submit before the deadline, not at the deadline. Most processor portals give you a confirmation screen once the submission is received; take a screenshot for your own records. For a full walkthrough of how to structure the rebuttal letter, what evidence to include for each reason code, and the exact Stripe and WooPayments submission steps, see How to Respond to a WooCommerce Chargeback Dispute (and Actually Win).

7. Log the dispute and the outcome

   Regardless of the outcome, record the dispute in a log you maintain. Include the customer identifier, the dispute date, the reason code, whether you contested, and the final outcome (won / lost / accepted). Over time, this log becomes the data that tells you where your disputes are coming from and which product categories or customer types are driving them.

When not to fight — and when accepting makes sense

Contesting every dispute is not always the right decision. Some disputes are not worth the time and attention required to respond to them properly.

Accept when the dispute is accurate. If the customer genuinely didn’t receive their order, if you shipped the wrong item, or if there was a processing error — accept the dispute, issue a refund if you haven’t already, and move on. Fighting a legitimate dispute wastes your time, delays the cardholder getting their money back, and slightly increases the chance that the review goes against you because your evidence can’t support a false claim.

Accept when the order value is very low. For a $10 or $15 dispute, the time spent building and submitting an evidence package often exceeds the value of the dispute itself. Many merchants set an internal threshold — something like “we contest all disputes above $50 with shipping confirmation, and accept below $50 with no prior customer history” — rather than making a case-by-case decision every time. Consistency matters more than heroics on small amounts.

Accept when you can’t produce key evidence. Without a delivery confirmation or meaningful customer communication, a “not received” or “unauthorized” claim is very hard to win on its own. Submitting a weak evidence package doesn’t hurt you directly, but it uses time that could go to cases you can actually win — and it doesn’t change the outcome.

Contest when you have strong delivery and communication evidence. If you have tracking confirming delivery, the customer’s email address matches the billing card, and there’s prior order history — that’s a case worth building. Fight it systematically, not emotionally.

Your chargeback ratio: why it matters more than the individual dispute

Any individual dispute is relatively minor. What actually threatens a WooCommerce store is the chargeback ratio — the percentage of transactions that end up disputed — because card networks use that ratio to decide whether you’re a merchant they want to continue processing payments for.

Visa’s Dispute Monitoring Program (VDMP) and Fraud Monitoring Program (VFMP), Mastercard’s Excessive Chargeback Program (ECP), and the equivalent Amex and Discover programs each define thresholds at which they enroll merchants into monitoring. Once you’re in a monitoring program, your processor typically charges you higher fees per dispute, and if your ratio doesn’t come down over the subsequent months, the card network can direct your processor to terminate your account. Losing the ability to accept credit cards is a business-ending event for most e-commerce stores.

The thresholds vary by network, but a common benchmark people cite for Visa is 0.9% of transactions (by dispute count) in a calendar month. At 1%, enrollment in the early monitoring level begins. At 1.8%, you’re in a deeper program. Mastercard’s thresholds differ. The point is not to memorize specific numbers — they change, and different monitoring levels have different criteria — but to understand that your ratio is the metric that determines whether chargebacks are an inconvenience or an existential problem.

This means every prevention action you take is not just saving money on individual disputes. It’s protecting your ability to process cards at all. Stores that treat chargebacks as individual one-offs, rather than as a ratio to manage, often don’t realize they’re in trouble until they’re already enrolled in a monitoring program and facing accelerating fees. For a deeper look at what triggers account freezes, rolling reserves, and terminations — and how to stay well clear of those thresholds — see How to Avoid Getting Banned by Stripe, PayPal & Payment Processors.

Prevention basics that actually reduce disputes

Prevention is worth more than response. The best-case outcome of a successful dispute response is that you recover money you already had and spent time responding; you’re back to square one. Prevention avoids the dispute entirely. These are the habits that reliably move the needle:

Make your descriptor recognizable

A significant share of chargebacks are filed because customers don’t recognize the charge on their credit card statement. The statement descriptor is the name that appears alongside the charge — and it defaults to something like your legal entity name, which may bear no resemblance to your store name. If your WooCommerce store is “Blue Horizon Home Goods” but your LLC is “BH Holdings LLC,” your customers’ statements show “BH Holdings LLC” and some of them genuinely don’t know what that charge is. Talk to your processor about setting a recognizable statement descriptor. Some processors allow a combined format: a company name plus a phone number or URL, so confused customers can self-resolve before filing a dispute.

Set shipping expectations and fulfill them

The largest single driver of preventable disputes is unmet shipping expectations. If your store says “ships within 1–2 business days” and the order ships in four, you’ll get customer service emails. If those emails don’t get a response, you’ll get disputes. The fix isn’t complex: accurate estimated delivery windows, proactive notifications when something is delayed, and a customer service process that responds to order queries within 24–48 hours. Most “item not received” disputes that go to a card network could have been resolved in 10 minutes of email response.

Require signatures on high-value shipments

For orders above a certain threshold — $100, $200, or wherever your product range makes it sensible — require signature confirmation on delivery. It eliminates a major category of “I never received it” disputes because the carrier now has a signed record of delivery. The threshold should match the point where the dispute fee plus the cost of the goods makes it economically worthwhile to pay the small carrier fee for signature service.

Issue refunds quickly when you’re in the wrong

If a customer contacts you about a legitimate problem — broken item, wrong product, genuine non-delivery — issue the refund immediately. A proactive refund costs you the item value. A dispute costs you the item value plus the dispute fee, plus the time to respond, plus the ratio impact. The math strongly favors refunding first and investigating second in cases where you’re confident you’re in the wrong or where the amount is small. The customer who got a fast refund doesn’t file a dispute, and their view of your store remains neutral or positive.

Watch for repeat disputers

A meaningful fraction of friendly fraud comes from a small number of customers who have learned that disputing works and do it repeatedly. If you can identify customers with a pattern of disputes — or customers who have contested charges with your store before — you can make decisions about future orders before they ship. Many stores have an informal mental list of “customers we don’t serve anymore.” Making that list explicit and systematic is one of the most direct ways to reduce future dispute exposure from known bad actors.

Protect against card-testing attacks

Card-testing attacks — where bots use your checkout to probe stolen card numbers — don’t always result in successful orders, but they generate a flood of fraud-coded declines that affect your fraud ratio. They also run up gateway fees for the declined attempts. If you’re on Stripe or WooPayments, their built-in fraud detection catches some of this. For WooCommerce stores that want more granular control, real-time checkout protection that monitors per-device decline velocity is the appropriate layer. This is distinct from the order-level fraud detection that’s useful for larger purchases — card-testing protection specifically addresses the bot pattern of rapid repeated decline attempts from the same device.

Tracking disputes in WooCommerce

WooCommerce doesn’t have built-in dispute tracking. Your payment processor — Stripe, WooPayments, PayPal — maintains a disputes dashboard within their own platform, but it’s separate from your order management, which means the information about who filed a dispute lives somewhere other than the customer profile you’re looking at.

For stores processing a small number of disputes per month, a simple spreadsheet log is usually enough: customer email, order ID, dispute date, reason code, whether you contested, and the outcome. That gives you the data to spot repeat patterns, track your win rate by reason code, and calculate your approximate dispute ratio manually.

For stores where disputes arrive frequently enough that a spreadsheet starts feeling inadequate — or where you want the dispute data connected to customer profiles so you can see a customer’s full history at a glance — a purpose-built tool makes more sense. TrustLens is a WooCommerce plugin that tracks disputes per-customer, automatically ingests chargeback data from Stripe and WooPayments, and keeps a running Chargeback Ratio Speedometer on the dashboard so you can see your blended ratio against card-network thresholds without doing the math manually. If you use a different gateway, the manual entry form keeps the same records from any source. The free version includes all of this.

The reason per-customer dispute tracking matters — beyond the ratio — is that it connects dispute history to order decisions. If a customer has filed two previous disputes and you can see that at the moment their third order arrives, you can make a different decision about fulfillment. Without that history in one place, that context is invisible.

One practical note about the dispute worklist in TrustLens Pro: version 1.2.7 added a dedicated dispute deadline worklist on the Chargeback Monitor page — every open dispute listed with its response deadline and a live countdown. For stores managing more than two or three simultaneous disputes, that countdown in a single place is significantly less error-prone than tracking deadlines manually across processor emails. The free version shows the dispute data; the deadline worklist is a Pro feature.

For more on what TrustLens tracks and how it fits into a broader chargeback strategy, the guide to WooCommerce chargeback prevention tools covers the full landscape honestly, including where tools genuinely help and where they don’t.

Key takeaways

Common questions

What happens if I just ignore a chargeback notification?

The dispute closes automatically in the cardholder’s favor. The provisional funds reversal becomes permanent, you keep the dispute fee, and the case is recorded as a loss in your processor’s records. Ignoring a notification is almost never the right decision — even if you plan to accept the dispute, you can do that explicitly in your processor dashboard, which at least flags that you acknowledged it. Simply not responding leaves you with no record of your reasoning and no data for your dispute log.

Can I get a chargeback if I already issued a refund?

Yes. A customer can file a dispute even after you’ve refunded the order — though this is less common because there’s no financial motivation to do so once the refund has cleared. In these cases, your evidence submission should include documentation showing the refund was issued, with the date and the refund amount. Most processors will close the dispute in your favor when you can demonstrate a full refund was already processed.

How long does it take to hear the outcome of a dispute I contested?

It varies significantly by card network and whether the case escalates. At the first-round level, many disputes resolve within two to four weeks after you submit your evidence. Cases that escalate to pre-arbitration or arbitration can take several months. Your processor dashboard typically shows a status field for the dispute — watch that rather than waiting for an email, as processor email notifications aren’t always reliable.

What is a “chargeback ratio” and what’s considered high?

Your chargeback ratio is the number of disputes in a given month divided by your total number of transactions in that same period. Visa and Mastercard typically use the prior calendar month’s transaction count as the denominator. A ratio below 0.5% is generally considered healthy for most merchant categories. Above 1% you’re in territory where Visa’s standard Dispute Monitoring Program enrollment is a real risk. The exact thresholds vary by card network, merchant category code, and which monitoring program applies to you — the numbers above are illustrative, not guarantees. Your processor or merchant account representative can confirm the specific thresholds relevant to your setup.

Does fighting a dispute and losing make things worse?

Not meaningfully in most cases. A disputed transaction counts against your ratio regardless of whether you contest it. Contesting and losing doesn’t add an extra penalty beyond the loss itself. The main risk in contesting a case you shouldn’t have is wasted time — not a worse outcome than accepting would have been.

What is “friendly fraud” and how do I handle it?

Friendly fraud refers to chargebacks filed by customers who genuinely received their order but dispute the charge anyway — claiming non-delivery, item-not-as-described, or unauthorized transaction when none of those things are true. The name is obviously a misnomer; it’s fraud. Handling it effectively requires strong evidence: delivery confirmation, communication showing post-delivery contact from the customer, and order history that makes the “unauthorized” claim implausible. Systematic tracking of customers who have done this before is one of the few tools that prevents repeat incidents from the same person, since card networks don’t share that information between merchants.

Should I use an address verification service (AVS) to prevent disputes?

AVS — a system where the billing address entered at checkout is checked against the address on file with the cardholder’s bank — helps with true fraud detection at the point of checkout. It can reduce the number of fraudulent orders that make it through, which in turn reduces fraud-coded disputes. It’s not a chargeback prevention tool in the broader sense; it doesn’t affect friendly fraud claims from legitimate cardholders. Whether to require an AVS match, and how strictly to filter on AVS response codes, is a decision that depends on your customer base and how many orders you’re willing to decline versus how much fraud exposure you have. Your payment gateway’s documentation will outline what AVS responses mean and which are worth blocking on.

The post on when to automate chargeback blocking in WooCommerce goes deeper on the automation side of things — specifically the timing problem that makes manual blocking ineffective for repeat disputers.