How to Fight a WooCommerce Chargeback and Actually Win (The Evidence Most Merchants Get Wrong)

[LAST UPDATED: 2026-04-06]

You shipped the order. You have the tracking number. Delivery was confirmed at the customer’s address. You uploaded all of it to Stripe’s dispute portal, waited 45 days, and lost anyway.

If that sequence feels familiar, you are not alone. Merchants with strong delivery evidence still lose the majority of chargeback disputes they fight. The reason is not that the banks are incompetent or unfair — it is that delivery confirmation answers the wrong question. For the kind of chargeback that dominates e-commerce (friendly fraud, where a real customer disputes a legitimate transaction), banks are not just asking whether the order arrived. They are asking whether this customer has a documented pattern of exploiting the dispute process — and if you cannot show them that pattern, the default position is to rule for the cardholder.

This guide is about how to win a WooCommerce chargeback dispute — specifically the friendly fraud kind, which accounts for an estimated 60-80% of e-commerce disputes. It covers what evidence to submit, how to structure it, what most merchants miss, and why behavioral history changes the calculus entirely.

Why Merchants Lose Disputes They Should Win

The first thing to understand is that chargeback disputes are not evaluated the way a court case is. There is no hearing, no cross-examination, no opportunity to present your case verbally. A reviewer — often at the issuing bank’s dispute team, sometimes an automated system — looks at the documents you uploaded, compares them against what the cardholder claimed, and makes a decision. In many cases, that review takes minutes, not hours.

This means the quality and structure of your submission matters enormously. A stack of screenshots without context loses to a concise, clearly organised evidence package that tells a coherent story. Most merchants upload what is immediately to hand — a shipping confirmation email, a screenshot of the order in WooCommerce — and hope that proves their case. Against a determined or habitual dispute filer, it does not.

Three things tend to determine outcomes in friendly fraud disputes:

Most merchants cover the first point reasonably well, do the second partially, and completely miss the third.

The Friendly Fraud Problem and What Banks Are Actually Looking For

Payment processors and card networks are aware that friendly fraud is a widespread problem. Visa introduced its Compelling Evidence 3.0 framework specifically to give merchants a structured mechanism for submitting behavioral evidence in dispute responses — and its core requirement is exactly what most merchants do not have: documented proof that the same customer transacted with you at least two times previously without disputing.

The Compelling Evidence framework is not available to every merchant for every dispute — it applies to specific dispute reason codes under Visa’s network. But the underlying principle applies broadly: the most persuasive evidence in a friendly fraud dispute is a pattern that shows the customer knows exactly who you are and has transacted with you before without complaint.

Here is why this matters practically. A cardholder who contacts their bank to dispute a charge can select almost any reason code. “Unrecognised transaction” is commonly used even when the customer simply changed their mind or found the bank dispute route faster than your refund process. The bank starts from the assumption that the cardholder is telling the truth — because the system is designed to protect consumers from fraud. Your job in submitting evidence is to give the bank specific, documented reasons to reach a different conclusion. Behavioral history — prior purchases, prior non-disputed transactions, communication from the same account — does that more effectively than any delivery confirmation.

What a Complete Evidence Package Actually Looks Like

A complete dispute evidence package has four layers. Most merchants submit one. Processors like Stripe give you the structure to submit all four — but they do not tell you what those layers are or why each one matters.

Layer 1: Transaction documentation

This is the baseline — the minimum acceptable submission. Every dispute response should include:

• The order confirmation showing the date, items purchased, amount charged, and billing address
• The customer’s email address as entered at checkout, confirming they provided contact information for this specific transaction
• The IP address associated with the checkout session and its geolocation (available in your WooCommerce order data or hosting logs)
• A screenshot of your product page as it appeared at the time of purchase, showing the exact description and price

For physical goods, add:

• Shipping confirmation with dispatch date and carrier
• Tracking showing delivery status and — if available — GPS delivery confirmation or signature
• The shipping address as entered at checkout, confirming it matches the billing address or was explicitly entered by the customer

For digital goods or downloads, add:

• Server logs or plugin records showing the customer accessed, downloaded, or activated the product after purchase
• Login timestamps if account-based access was involved

Layer 2: Customer identity linkage

This layer establishes that the cardholder and the customer who placed the order are the same person. It directly addresses the “unrecognised transaction” claim.

• Prior orders from the same customer account (email, billing address) showing a history of transactions with your store
• Any email communications from the customer using the same contact details — support inquiries, shipping questions, account activity
• Device fingerprint or IP address consistency across the disputed order and prior undisputed orders (this is the Compelling Evidence mechanism)
• If the cardholder used your store’s account system, a screenshot of their account profile showing the account creation date, order history, and last login

Layer 3: Communication records

Any communication that occurred between you and the customer — before or after the disputed transaction — is relevant evidence, even if it seems peripheral.

• Customer service emails or chat logs where the customer referenced the specific order
• Any contact where the customer acknowledged receipt of goods or access to digital products
• Communications showing the customer did not raise a complaint through your support channel before filing the dispute — relevant because it demonstrates they bypassed your resolution process
• If the customer threatened a chargeback in writing before filing, include that communication — it demonstrates intent rather than genuine confusion

Layer 4: Behavioral history

This is the layer most merchants do not have — and the one that makes the difference in friendly fraud disputes. More on this below.

Why Behavioral History Is the Differentiating Factor

Here is the core problem with how most merchants think about chargeback disputes: they approach each dispute as an isolated event. This customer placed an order. This customer is disputing that order. You submit evidence about that order. The bank decides.

But a habitual friendly fraud customer — someone who regularly uses the dispute process to get goods for free — does not appear unusual in any single transaction. The order looks normal. The delivery looks normal. It is only across multiple orders, multiple stores, or multiple dispute history data points that the pattern becomes visible.

When you include behavioral history in your dispute submission, you are doing something different from what most merchants do. You are not just saying “this order was legitimate.” You are saying “this customer has used our store before, has received goods before, has not disputed before, and their current dispute claim is inconsistent with their own documented history with us.” That is a materially stronger position.

Specifically useful behavioral signals to document:

• Prior non-disputed orders: A customer who has placed five orders over twelve months and disputed only this one is a different risk profile from a first-time buyer. Showing the order history makes that contrast visible.
• Refund history: If the customer has a history of requesting refunds through your store before this dispute, it suggests they know how to contact you and resolve problems through normal channels — which undercuts the “I had no other option” framing of a dispute.
• Dispute history (if known): If TrustLens Pro has logged prior chargeback events against this customer through its Stripe or WooPayments integration, that history can be documented and cited.
• Linked accounts: If the same customer operates multiple accounts on your store — a common tactic in systematic friendly fraud — and those accounts have a pattern of disputes or refund abuse, that is relevant context for the evidence package.
• Timeline of activity: A customer who placed an order, received a shipping confirmation, and then filed a dispute three days later — without contacting your support team at any point — has a timeline that does not match the stated claim of genuine confusion.

Building Your Evidence Layer by Layer

In practice, assembling a dispute response looks like this:

The Four Most Common Evidence Mistakes

1. Submitting delivery proof for a non-delivery claim

If the dispute reason code is “unrecognised transaction,” the cardholder is saying they do not know this charge exists — not that the item did not arrive. Uploading a tracking number in response to that claim does not address the stated dispute. It looks like you misunderstood the case. Address the actual claim: show that this cardholder created an account, entered their details at checkout, received an order confirmation email at their address, and has transacted with you before.

2. Submitting evidence for only the disputed transaction

Every piece of evidence you submit should cover the disputed order. But your strongest additional evidence — prior order history, device consistency, account age — is evidence about the customer’s relationship with your store, not the order itself. Merchants who submit only order-specific evidence are leaving the most persuasive layer out.

3. Writing a long narrative in the summary field

Bank dispute reviewers process high volumes. A 400-word explanation of why you believe the customer is being dishonest will not be read carefully. A clear four-sentence summary — “Customer has placed 6 prior orders without disputes. Order confirmation was sent to the same email on file. Delivery was confirmed by GPS scan on [date]. Customer did not contact our support team before filing this dispute.” — is more effective.

4. Waiting until the dispute arrives to gather evidence

The 7-to-21-day response window feels like enough time. It is not, for customers with complex histories. Pulling order history, finding email communications, checking refund records, and compiling linked account data under time pressure is exactly how merchants submit incomplete packages. The merchants who win disputes consistently are the ones who have this information organised before a dispute arrives.

When Not to Fight — and How to Decide Quickly

Not every dispute is worth disputing. Fighting a chargeback costs time, and in processors with a two-tier fee model (Stripe introduced this structure in mid-2025), losing a counter-dispute means paying an additional fee on top of the original chargeback fee. Before you invest in assembling evidence, run a quick triage:

The honest baseline: merchants lose most chargeback disputes they file. Industry estimates suggest merchants win around 20-30% of disputes they contest. That is not a reason to stop fighting winnable cases — but it is a reason to triage carefully and invest in the cases where your evidence is genuinely strong.

How a Behavioral Risk Summary Changes What You Can Submit

The practical problem with the behavioral history layer is assembly time. The information exists in your WooCommerce data. But pulling a customer’s complete order history, refund events, linked accounts, and dispute timeline — consolidating it into a readable summary, formatted for upload to a payment processor portal — takes time most merchants do not have during the dispute window.

TrustLens Pro includes a feature built specifically for this moment: a one-click Dispute Evidence Report, accessible from the customer’s profile in the TrustLens dashboard. It generates a print-ready behavioral risk summary of the customer’s full history — their trust score and the signals that drove it, their complete order and refund timeline, linked account data, and any chargeback events tracked through the Stripe or WooPayments integration.

The output is designed to be uploaded directly to dispute portals. When you are looking at an active Stripe or WooPayments dispute and need to add behavioral context, the report gives you that layer without the manual assembly work.

To be direct about what it does and does not do: it documents the behavioral history that exists in your store’s data. It does not create evidence that isn’t there. A customer with two orders and no red flags will produce a report that reflects that — which tells you there is limited behavioral history to submit, and the dispute should be fought (or not) on transaction evidence alone. A customer with ten orders, a refund pattern, and a prior chargeback event produces a report that is genuinely useful evidence.

The broader principle here applies even if you never use TrustLens: the merchants who win the most disputes are the ones who treat customer behavioral history as a business record worth maintaining — something that can be retrieved quickly, read clearly, and submitted as evidence. Most stores do not do this until they have already lost several disputes. Starting earlier means having the data when it counts.

If you want to see how TrustLens handles customer risk tracking and chargeback evidence, the TrustLens plugin page has a full feature breakdown. The free version includes the scoring engine and full order history; Pro adds the Dispute Evidence Report and chargeback tracking for Stripe and WooPayments.

Frequently Asked Questions

What you submit is what the bank sees

The payment dispute system does not give you the benefit of the doubt. The default position is that the cardholder is right. Changing that outcome requires you to put the right evidence in front of the right reviewer within a tight deadline — and the right evidence is not just a tracking number. It is a coherent package that directly addresses the stated claim, establishes the customer’s identity, and — for friendly fraud — documents the behavioral history that shows this dispute is not what it appears to be.

That is achievable for most disputes. It requires knowing what layers exist, having the data organised before the dispute clock starts, and structuring your submission so a reviewer can follow it in 60 seconds. The merchants who win disputes consistently are not luckier — they are better prepared.

The most useful thing you can do today: open the last chargeback you lost and ask what layer of evidence was missing. That answer tells you exactly where to focus next.