WooCommerce Chargebacks: How to Respond and Win

WooCommerce powers roughly 28% of all online stores worldwide. Unlike Shopify, which has a payments product and handles disputes through a single interface, WooCommerce is just the storefront. The payment gateway — Stripe, WooPayments, PayPal, Square, or others — is where chargebacks happen, and each has its own dispute process, timeline, and evidence requirements. This guide covers how chargebacks work for the three most common WooCommerce payment setups: WooPayments (powered by Stripe), standalone Stripe, and PayPal. For each, you'll find exactly where to find the dispute, what the timeline is, and what evidence to gather.

How Chargebacks Work with WooCommerce

WooCommerce itself doesn't handle chargebacks — it's a plugin, not a payment processor. Your gateway is where disputes appear and are resolved. When a customer files a chargeback, the card network (Visa, Mastercard, Amex) contacts your payment processor, not WooCommerce. WooCommerce has no visibility into this process by default unless a gateway plugin surfaces that information in the admin interface, which only WooPayments does natively.

WooCommerce will notify you of orders and send you fulfilment and payment confirmation emails. The chargeback notification, however, comes from your gateway — an email from Stripe, WooPayments, or PayPal — not from WooCommerce itself. If you're only monitoring your WooCommerce Admin inbox for alerts, you're likely missing dispute notifications entirely, which means you're missing response deadlines.

The most important first step when you receive a chargeback notification is to identify which gateway processed the disputed transaction, then go to that gateway's dashboard. Don't look in WooCommerce Admin for the dispute interface — it won't be there for most setups. The gateway is where you'll find the reason code, the evidence submission form, and, critically, the response deadline.

WooCommerce + WooPayments Disputes

WooPayments is WooCommerce's native payment product, built on top of Stripe's infrastructure. Because it's integrated directly into WordPress, it's the only gateway that surfaces dispute management inside your WooCommerce Admin — which means you can see and respond to disputes without leaving your WordPress dashboard. Go to WordPress Admin → Payments → Disputes to see all open cases.

The Disputes screen shows the reason code, the disputed amount, the original transaction date, and the response deadline. One practical advantage of WooPayments over standalone Stripe is that it pre-populates some evidence automatically from your WooCommerce order data: order details, customer information, and the product description are pulled directly from the order record. This saves time but doesn't eliminate the need to add your own evidence — delivery confirmation, customer correspondence, and a written rebuttal still need to come from you.

Step-by-step: responding to a WooPayments dispute

1. Go to WordPress Admin → Payments → Disputes
2. Click the dispute to open the evidence submission form
3. Review what WooPayments has pre-populated — confirm it's accurate and complete
4. Add the evidence that's missing: carrier delivery confirmation, customer email history, and any fraud signals
5. Write your response in the “Additional information” field — be specific about why the claim is incorrect
6. Submit before the deadline shown in the interface

WooCommerce + Stripe (Standalone) Disputes

When Stripe is installed as a WooCommerce plugin — using the WooCommerce Stripe Payment Gateway extension — disputes are handled entirely in the Stripe Dashboard, not in WooCommerce. There's no dispute management interface inside WordPress Admin. Stripe sends dispute notifications by email, and all evidence submission happens at dashboard.stripe.com.

In the Stripe Dashboard, navigate to Balances → Disputes or search directly for the charge ID included in the notification email. Stripe presents the dispute with the reason code, the evidence requirements specific to that reason code, and the submission deadline. Unlike WooPayments, Stripe does not pull order data from WooCommerce — you must gather it manually. This means pulling the order from your WooCommerce Admin and uploading the relevant data to Stripe's evidence form yourself.

Step-by-step: responding to a standalone Stripe dispute

1. Open Stripe Dashboard → Balances → Disputes (or search for the charge ID)
2. Click the dispute to see the reason code, evidence requirements, and deadline
3. Pull the order from your WooCommerce Admin: order number, items, customer name, email, billing and shipping addresses, and order date
4. Get carrier tracking confirmation from the carrier's website — not just the tracking number, but a screenshot or export showing “Delivered” status with date, time, and delivery location
5. Fill in Stripe's structured evidence fields with the order data and tracking information
6. Add your rebuttal in the “Rebuttal text” or “Response” field, explaining clearly why the claim is invalid — referencing the reason code and your specific evidence
7. Submit through Stripe's interface before the deadline

WooCommerce + PayPal Disputes

PayPal disputes go through the PayPal Resolution Center, separate from any card network chargeback process. If a customer pays via PayPal and files a dispute, you'll receive an email from PayPal — not from your card network. To find and manage the case: log in to PayPal, go to Activity → Open Cases, or use the Resolution Center link in the notification email.

PayPal has a two-stage process. At the Claim stage, you have 10 days to respond. This is an opportunity to resolve the issue directly with the customer — offer a refund, a replacement, or additional proof of delivery — before it escalates. Resolving at this stage avoids a formal chargeback record and keeps the dispute off your card network chargeback rate. If the claim isn't resolved within 10 days, it escalates: PayPal either makes a decision itself (for PayPal Buyer Protection claims) or passes it to the relevant card network for a standard chargeback process.

Step-by-step: responding to a PayPal dispute

1. Log in to PayPal → Resolution Center → find the open case
2. Check whether it's a “PayPal Buyer Protection” claim or a card dispute — the process and decision-maker differ
3. At the claim stage: respond within 10 days with your order details, shipping tracking confirmation, and any customer communications
4. If the customer is contactable, consider whether a direct resolution (refund or replacement) is faster and cheaper than contesting the dispute
5. If escalated to a formal dispute: prepare a full evidence package — order records, delivery confirmation, communication history, fraud signals — as you would for any standard chargeback
6. Submit through the PayPal Resolution Center interface by the deadline shown in the case

Evidence Checklist for WooCommerce Merchants

The evidence requirements for WooCommerce chargebacks are identical to those for any e-commerce dispute. What differs is where the data lives and how much manual work is required to pull it together. Use this checklist for every dispute response.

1. 1. ✅ WooCommerce order details

   Export or screenshot the order from WordPress Admin → Orders. Include: order number, date, amount, line items, customer name, email, billing address, shipping address, and IP address. The customer's IP address at checkout is available in WooCommerce order details if logged by your setup or a security plugin — it's valuable for fraud disputes.

2. 2. ✅ Carrier delivery confirmation

   Get this directly from the carrier's website — not the tracking number alone, but a page showing “Delivered” status with the date, time, and delivery location. This is required for Visa 13.1 (goods not received) disputes and the equivalent codes from other networks.

3. 3. ✅ Proof of shipment

   The shipping label PDF or carrier receipt from when you dispatched the order. This establishes that you sent the package before the dispute was filed and confirms the address shipped to.

4. 4. ⭐ Customer email history

   Export any email correspondence about this order from your email client or WooCommerce's email logs. WooCommerce logs outbound system emails on the order page — check the “Email log” section of the order. This is particularly useful if the customer contacted you before filing the dispute, which weakens their claim.

5. 5. ⭐ Signature confirmation

   For orders above $100, carrier signature confirmation is worth including. Request the signature record from your carrier if you required it at delivery — it's strong evidence that the package was received by a person at the delivery address.

6. 6. ⭐ 3DS authentication result

   If you have Stripe Radar or 3DS enabled, the authentication result for this transaction is valuable for Visa 10.4 and Mastercard 4837 fraud disputes. Check Stripe Dashboard → charge detail → Payment Method for the 3DS outcome.

7. 7. ○ WooCommerce fraud analysis data

   If you use a plugin like WooCommerce Fraud Prevention or Signifyd, include the fraud assessment for this order. Risk scores, device fingerprints, and IP reputation signals add weight to your response for fraud-coded disputes.

8. 8. ○ Terms and conditions acceptance

   If you log customer acceptance of T&Cs at checkout — some WooCommerce plugins do this — include it. A timestamped record of the customer accepting your no-refund policy or subscription terms is directly relevant to disputes filed as “not as described” or billing disputes.

How WooCommerce Differs from Shopify for Chargebacks

Shopify Payments auto-populates significant evidence when a dispute arrives — order data, fulfilment records, shipping confirmation, and product descriptions are pulled automatically from Shopify's internal records and pre-filled into the dispute form. WooCommerce gateways, especially standalone Stripe, require you to do this manually. WooPayments bridges some of the gap by pre-filling order data, but it doesn't match Shopify's depth. The practical consequence is that WooCommerce disputes take longer to respond to — and merchants who don't have a systematic process are more likely to submit incomplete evidence packages or miss deadlines.

WooCommerce also doesn't have a built-in fraud analysis layer comparable to Shopify's. Shopify includes basic fraud detection in its checkout flow and surfaces risk signals in the order view. With WooCommerce, you need a third-party plugin — WooCommerce Fraud Prevention, Signifyd, or Kount — to get device-level and behavioural fraud signals at checkout. Without this, you won't have the fraud data that card network rules like Visa's Compelling Evidence 3.0 require for fraud disputes.

Where WooCommerce has an advantage is full control over data collection. Because WooCommerce is open-source and extensible, you can add plugins that capture device fingerprints, IP addresses, and checkout metadata in formats that map directly to CE 3.0 evidence requirements. Shopify's data collection is fixed to what Shopify exposes. A well-configured WooCommerce store with the right plugins can actually produce stronger dispute evidence than Shopify — but it requires deliberate setup rather than working out of the box.

How to Reduce WooCommerce Chargebacks

Prevention is more cost-effective than dispute management. These five changes have the biggest impact on WooCommerce chargeback rates.

1. Configure your billing descriptor

The most common trigger for “I don't recognise this charge” disputes is an unrecognisable billing descriptor. When customers see an unfamiliar name on their card statement, they call their bank instead of you. In Stripe: go to Dashboard → Settings → Business settings → Statement descriptor. Make it match your store name as customers know it — not your legal entity name, not an abbreviated code, but the trading name your customers associate with their purchase.

2. Enable 3DS authentication

In Stripe Dashboard, go to Settings → Radar → Rules and enable 3D Secure for all transactions, or configure rules to trigger it for high-risk transactions. 3DS-authenticated transactions shift fraud liability away from you to the card-issuing bank, making them essentially immune to Visa 10.4 and Mastercard 4837 chargebacks. The tradeoff is a small increase in checkout friction, but for most WooCommerce stores the reduction in fraud disputes is worth it.

3. Install a fraud prevention plugin

WooCommerce doesn't have built-in fraud analysis. Plugins like Signifyd, Kount, or WooCommerce Anti-Fraud add a risk assessment layer at checkout that flags high-risk orders before they're fulfilled. This gives you the option to add extra verification, hold the order for review, or cancel it outright — rather than fulfilling an order that will become a chargeback 60 days later.

4. Log IP addresses and checkout metadata

Use a security plugin or custom code to capture and store the IP address, device type, and checkout metadata for every order. WooCommerce doesn't do this by default. This data is required for Compelling Evidence 3.0 on Visa 10.4 disputes — specifically, prior undisputed transactions from the same device and IP address. If you don't collect it at checkout, it's gone when you need it months later.

5. Send proactive shipping updates

Use a plugin like Shipment Tracking for WooCommerce or AfterShip to send automatic tracking emails when orders ship and delivery confirmations when they arrive. Customers who receive tracking information proactively are significantly less likely to file “where's my order?” disputes with their bank. Many goods-not-received chargebacks are filed not because the package didn't arrive, but because the customer had no visibility into its status and assumed the worst.

Conclusion

WooCommerce chargebacks aren't harder to win than Shopify chargebacks — the evidence requirements are identical. The difference is that WooCommerce requires more manual work to assemble that evidence. Know which gateway processes your payments, know where to find disputes in that gateway's dashboard, and have a process for pulling order data from WooCommerce quickly when a dispute arrives. The merchants who lose avoidable WooCommerce chargebacks aren't losing because of bad evidence — they're losing because they were slow, submitted incomplete packages, or missed the deadline. See our rebuttal letter templates for structured examples of what a complete response looks like for the most common reason codes.