Winning Chargebacks on WooCommerce

Platform Fee $15 per dispute · refunded if you win (WooPayments)

Response Window 7–21 days depending on network

Review Period 60–75 days after submission

File Limit 4.5 MB combined · one file per upload slot

Submissions 1 one shot · can save draft

How WooCommerce's Chargeback System Actually Works

WooCommerce is not a payment processor. It is an open-source e-commerce plugin for WordPress. Understanding who actually handles your disputes — and where — is the first step toward winning them.

The process, step by step (WooPayments)

A customer disputes a charge with their issuing bank.
The bank initiates the chargeback. WooPayments (powered by Stripe) debits the disputed amount plus a $15 fee from your account balance.
WooPayments notifies you by email and inbox notification in your WooCommerce dashboard.
You have 7–21 days (depending on the card network) to respond through WooPayments' 3-step evidence form.
WooPayments forwards your response to the card network via Stripe's infrastructure. The issuing bank reviews your submission over 60–75 days.
A decision is made — and it is final. If you win, the disputed amount and the $15 fee are credited back. If you lose, both are gone permanently.

Critical Insight

WooCommerce is open-source with multiple gateway options. If you use WooPayments, disputes flow through the built-in 3-step evidence form. But if you use Stripe directly, PayPal, Authorize.net, or another gateway, the dispute process is entirely different — you respond through that gateway's own dashboard, with its own constraints and deadlines. This guide focuses on WooPayments, the most common setup, but always verify which gateway processed the disputed transaction before you start building your response.

What WooPayments auto-collects

Because WooPayments is built on Stripe, it automatically pulls basic order and transaction data into your dispute response: order number, transaction amount, date, customer name and email, billing address, and fulfillment status. This data is included when your response is forwarded to the card network.

This establishes that a transaction occurred. It does not prove the chargeback is invalid. That case is yours to build with additional evidence.

The "Save for Later" feature

Unlike Shopify, WooPayments allows you to save a draft of your dispute response and come back to it. This is valuable — but comes with a critical caveat: if you save a draft and do not submit before the deadline, WooPayments auto-submits whatever you have saved. An incomplete draft submitted automatically is worse than a deliberate, structured response submitted on time.

Watch out

The auto-submit safety net creates a false sense of security. Treat your internal deadline as 48 hours before WooPayments' deadline. Use "Save for Later" to build incrementally, but always do a final review and click Submit yourself.

Evidence Formatting for WooPayments

WooPayments' evidence form has specific constraints inherited from its Stripe infrastructure. Know these before you start building your response.

Constraint	Limit	What This Means for You
File formats	PDF, JPEG, PNG only	No Word docs, spreadsheets, audio, video, or external links. Convert everything to PDF before you start.
Combined size	4.5 MB total	Your entire evidence package across all upload slots must stay under 4.5 MB. Plan your budget before uploading.
Files per slot	One file per upload button	Each evidence category has one upload slot. If you have multiple documents for a category, merge them into a single PDF.
Evidence form	3 sections	Section 1: Evidence uploads. Section 2: Shipping details. Section 3: Cover letter preview. Complete all three.
Cover letter	Auto-generated from inputs	WooPayments generates a cover letter based on what you enter. Review it carefully — it is part of your submission.

Formatting best practices

Format all documents so they can be read without zooming. Reviewers will not enlarge your screenshots — if they cannot read it at standard size, it does not count.
Highlight important details with callouts, arrows, or boxes. Draw the reviewer's eye to delivery dates, tracking numbers, and customer statements.
Combine multiple pieces of evidence into consolidated PDFs per upload slot. Three tracking screenshots become one "Delivery Confirmation" PDF.
Never include audio files, video files, external links, or requests for the reviewer to contact you. These are ignored.

Pro Tip

Use the "Save for Later" feature to upload evidence incrementally as you gather it. But set a personal deadline 48 hours before the platform deadline, and always do a complete final review of all three sections — including the auto-generated cover letter — before clicking Submit.

WooPayments Categories vs. Network Reason Codes

WooPayments uses seven dispute categories that simplify the underlying card network reason codes. Like Shopify, this is convenient for display but dangerous for response strategy. Each category maps to specific network codes with different evidence requirements.

WooPayments Category	Visa	Mastercard	Amex
Fraudulent	10.4	4837, 4863	F29
Product Not Received	13.1	4853	C08
Product Unacceptable	13.3	4853	C31
Subscription Canceled	13.7	4841	C28
Duplicate	12.6.1	4834	P08
Credit Not Processed	13.6	4860	C32
Non-compliant (Visa Compliance)	varies	N/A	N/A

Visa Compliance Warning

WooPayments has a seventh category that Shopify does not surface: "Non-compliant" (Visa Compliance). These disputes carry a $500 fee if you challenge and lose — on top of the standard $15 dispute fee. Only challenge Visa Compliance disputes when your evidence is ironclad. If there is any doubt, accepting the chargeback at $15 is far cheaper than losing the challenge at $515.

How to identify the actual network code

WooPayments does not always surface the underlying reason code directly. To find it:

Check the chargeback notification email — the network code is usually included in the dispute details.
Open the dispute in your WooCommerce dashboard under WooPayments > Disputes. The detail view may show the underlying code beneath the category label.
If you have direct Stripe dashboard access, check there — Stripe surfaces the exact network reason code in the dispute details.
Contact WooPayments support and ask for the specific reason code. They have access to the full dispute record through Stripe.

The One-Shot Submission Problem

On WooPayments, once you click "Submit Evidence," your response is final. You cannot revise it, add to it, or correct mistakes. The "Save for Later" feature lets you build incrementally, but the moment you submit, that is the response the bank reviews. There is no draft review step, no confirmation from WooPayments that your submission is strong enough.

This makes the pre-submission process the most critical part of fighting a WooCommerce chargeback.

Pre-submission checklist

Run through every item before clicking submit. Once it is sent, it is final.

Evidence completeness

Every claim the customer made has been directly addressed with evidence, not just assertions
All files are in PDF, JPEG, or PNG format
Combined file size across all upload slots is under 4.5 MB
All text in screenshots and documents is legible at standard viewing size
Key data points (dates, tracking numbers, amounts) are highlighted or annotated
All three sections of the evidence form are complete (evidence uploads, shipping details, cover letter)

Response quality

Your evidence addresses the specific network reason code, not just the WooPayments category
Each piece of evidence is labeled and explained concisely
Language is factual and specific — no accusations, frustration, or emotional appeals
The auto-generated cover letter accurately represents your case and does not contradict your evidence
No external links, audio, video, or requests for the reviewer to contact you

Final review

Read the cover letter preview as if you know nothing about the case. Does it make sense on its own?
Open every uploaded file — confirm they are the correct files and they render properly
Verify the order number, transaction date, and dollar amount match across all documents
Confirm shipping details in Section 2 are accurate and match your evidence
If this is a Visa Compliance dispute, verify your evidence is strong enough to justify the $500 fee risk

Pro Tip

Preview the auto-generated cover letter in Section 3 before submitting. If it does not accurately represent your case — if it omits key details or introduces inaccurate framing — go back and revise your inputs in Sections 1 and 2. The cover letter is built from what you enter, so improving your inputs improves the letter.

Critical Mistakes WooCommerce Merchants Make

These are the patterns we see repeatedly in losing WooCommerce chargeback responses. Every one of them is avoidable.

Mistake #1: Responding through the wrong gateway's dashboard

Merchants running multiple gateways — WooPayments for cards, PayPal for alternative payments — sometimes respond to a dispute through the wrong system. A PayPal dispute cannot be resolved through WooPayments, and vice versa. Responding in the wrong place means the actual dispute goes unanswered and you lose by default.

What to do instead

Before you start building your response, confirm which gateway processed the disputed transaction. Check the order details in WooCommerce — the payment method is listed there. Then respond through that specific gateway's dispute interface.

Mistake #2: Ignoring the evidence matrix

WooPayments maps each dispute reason to specific evidence categories based on your product type (physical goods, digital products, services, subscriptions). The system tells you exactly what evidence to submit. Merchants who ignore this matrix and upload generic evidence are working against the system designed to help them.

What to do instead

When you open a dispute in WooPayments, note which evidence fields are shown — these are tailored to your dispute reason and product type. Fill every relevant field. The evidence matrix exists because issuers expect specific documentation for each dispute category. Give them what they are looking for.

Mistake #3: Challenging Visa Compliance disputes without strong evidence

The $500 fee on Visa Compliance disputes makes them uniquely dangerous. Some merchants challenge every dispute on principle, not realizing that this category has a dramatically different risk profile. Losing a standard dispute costs $15 plus the transaction. Losing a Visa Compliance challenge costs $515 plus the transaction.

What to do instead

Evaluate Visa Compliance disputes separately from all others. Accept the chargeback unless you have unambiguous evidence that the transaction was fully compliant. The break-even math requires near-certainty of winning to justify the $500 risk.

Mistake #4: Relying on WooPayments auto-collected data alone

WooPayments automatically includes basic order and transaction data. Some merchants assume this is their full response and submit without adding anything else. Auto-collected data proves a transaction occurred and an item may have shipped. It does not prove delivery to the right person, product quality, or customer authorization.

What to do instead

Treat WooPayments' auto-collected data as your foundation, not your response. Build on it with carrier delivery confirmation, customer communications, post-delivery engagement evidence, and evidence tailored to the specific reason code. The auto-data gets the reviewer oriented; your additional evidence wins the case.

Mistake #5: Not reviewing the auto-generated cover letter

WooPayments generates a cover letter from the inputs you provide across all three sections of the evidence form. Many merchants never preview this letter before submitting. The result is a cover letter that may omit key arguments, present information in a confusing order, or fail to reference the strongest evidence.

What to do instead

Always preview the cover letter in Section 3 before submitting. Read it as a standalone document. If it does not tell a clear, compelling story that references your evidence, go back and revise your inputs. The cover letter is the first thing the reviewer reads — it frames everything that follows.

Win Rates and Benchmarks

Win rates on WooCommerce are gateway-dependent, not platform-dependent. The evidence quality and network rules determine outcomes. These benchmarks reflect WooPayments merchants specifically.

Industry benchmarks for WooCommerce merchants

Vertical	Estimated Win Rate	Notes
Apparel & fashion	~35%	Strong delivery evidence and carrier confirmation drive wins. WooCommerce's plugin ecosystem helps with automated tracking.
Consumer electronics	~18%	Higher transaction values make issuers cautious. Signature confirmation and serial number documentation are essential.
Digital goods	~20–25%	No physical delivery proof. Access logs, download records, IP matching, and usage data significantly improve outcomes.
Subscriptions	~25–30%	Cancellation disputes dominate. Clear terms and documented opt-in are the differentiators.

What drives higher win rates

Using the evidence matrix: Merchants who follow WooPayments' dispute-reason-specific evidence suggestions win at measurably higher rates than those who submit generic evidence.
Lower transaction values have meaningfully higher win rates. Issuers scrutinize high-value disputes more carefully.
Friendly fraud disputes — where the customer made a legitimate purchase — are the most winnable because you have real transaction evidence.
Net recovery reality: WooCommerce merchants win roughly 45% of challenged disputes, but net recovery averages only 18% after fees and operational costs. Fight strategically, not universally.

Chargeback rate thresholds

Card network monitoring programs apply regardless of platform. Keep your dispute rate below 0.65% — roughly six disputes per 1,000 transactions. Above 0.9%, Visa's Dispute Monitoring Program (VDMP) triggers escalating fines. Mastercard's Excessive Chargeback Program (ECP) kicks in at 1.5%. Above these thresholds, you risk losing your ability to process cards entirely — and WooPayments may restrict or terminate your account.

WooCommerce-Specific Response Framework

This framework accounts for WooPayments' 3-section evidence form, one-shot submission, auto-generated cover letter, and Stripe-inherited file constraints. Use it alongside our reason-code-specific guides for the underlying network code.

Step 1 — Identify the gateway and reason code

Before you write anything, confirm two things: which payment gateway processed the disputed transaction, and the actual network reason code behind the WooPayments category. Check the order payment method in WooCommerce, then find the reason code in the dispute notification email or WooPayments dashboard.

Step 2 — Check the evidence matrix

Open the dispute in WooPayments and note which evidence fields are displayed. WooPayments tailors these fields based on your dispute reason and product type. This matrix tells you what the issuing bank expects to see. Use it.

Step 3 — Build your evidence within constraints

Structure your submission to maximize impact within WooPayments' 4.5 MB combined limit:

Evidence Slot	Contents	Target Size
Primary evidence uploads	Consolidated PDF per category: delivery proof, customer communications, product documentation — annotated and cropped.	< 2 MB
Shipping details	Carrier name, tracking number, delivery confirmation, signature records. Fill all fields in Section 2.	< 1 MB
Supporting documentation	Policies, terms, product descriptions — only pages relevant to this dispute.	< 1 MB
Cover letter inputs	Clear, factual text in each field that will generate an accurate cover letter in Section 3.	< 500 KB

Step 4 — Write your inputs for the cover letter

WooPayments generates a cover letter from the text you enter. Write your inputs as if they will be read verbatim — because they will be. Use this structure:

Template Language

Re: Dispute [CASE NUMBER] — Order [WOOCOMMERCE ORDER NUMBER] We are responding to the dispute filed against the [MM/DD/YYYY] transaction by [CUSTOMER NAME] in the amount of [$XX.XX]. [SUMMARY: Two to three sentences stating your case. Lead with your strongest evidence. Address the specific network reason code, not the WooPayments category.] The following evidence has been uploaded in support of our response: Evidence 1: [Label] — [One-sentence description] Evidence 2: [Label] — [One-sentence description] Evidence 3: [Label] — [One-sentence description] [CLOSING: One sentence requesting the dispute be resolved in your favor based on the evidence provided.]

Step 5 — Preview cover letter, final review, submit

Navigate to Section 3 and preview the auto-generated cover letter. Read it as a standalone document. If it does not tell a clear, compelling story, go back and revise your inputs. Then run through the pre-submission checklist. Submit well before the deadline — do not rely on auto-submit.

Preventing Chargebacks on WooCommerce

The best chargeback response is the one you never have to write. WooCommerce's open-source ecosystem gives you more prevention tools than any other platform — if you use them.

Action	Why It Matters
Use a clear billing descriptor	"Unrecognized" chargebacks are often legitimate customers who do not recognize the charge. Set your billing descriptor to your store name, not your legal entity name. Include your URL or phone number if your processor allows it.
Send proactive fulfillment emails	Configure WooCommerce to send shipping confirmation with tracking numbers immediately on fulfillment. Customers who can track their package file significantly fewer "not received" disputes.
Require signature above your threshold	Set a dollar threshold (common: $100–$250) above which you require signature confirmation. The shipping upcharge is small relative to the chargeback risk on high-value orders.
Review the WooPayments risk level column	WooPayments grades every transaction with a risk level in your dashboard. If you see anything other than "Normal," do not fulfill the order before verifying with the cardholder. No response? Consider refunding without shipping.
Install fraud prevention plugins	WooCommerce's WordPress ecosystem offers fraud prevention plugins (WooCommerce Anti-Fraud, etc.) that score transactions in real time. Use them to flag and hold high-risk orders before fulfillment.
Make returns and cancellations frictionless	Customers who can easily return a product or cancel a subscription are far less likely to dispute through their bank. Every obstacle in your return process increases your chargeback rate.
Follow up after delivery	Send a post-delivery email 5–7 days after the carrier confirms delivery. Ask for a review, offer support, or share product tips. Any customer reply becomes evidence of receipt and satisfaction.

About This Guide

This playbook is updated to reflect changes in WooPayments' dispute system, card network rules, and merchant best practices. Document Version: 2026.1 · Last Updated: March 15, 2026 · Platform: WooCommerce / WooPayments

Related Guides

Pair this platform guide with reason-code-specific playbooks for your most common dispute types: