Disputing Chargebacks
4 min read
When a customer files a chargeback, you have a window — usually 7 to 14 days — to respond with evidence. The default win rate on disputes industry-wide is around 30%; with strong evidence and behavioral context, that number can be significantly higher. This walkthrough shows how to use TrustLens to maximize your dispute win rate, especially on friendly-fraud cases where the cardholder received the product and is disputing in bad faith.
Why Most Disputes Are Lost #
Card networks tilt slightly toward cardholders by design. Without strong, specific evidence, the merchant usually loses. The categories where merchants lose most:
- Friendly fraud — cardholder claims non-receipt or fraud despite the order being legitimate
- Subscription disputes — cardholder claims unauthorized recurring charges
- Cancellation disputes — cardholder claims order was cancelled but charged
For each of these, the merchant has direct evidence (delivery confirmation, subscription opt-in, cancellation handling) but adjudicators frequently rule for the cardholder anyway because they don’t see the broader behavioral context.
The TrustLens Advantage #
The Dispute Evidence Report (Pro) adds behavioral pattern evidence to your dispute response. It tells the adjudicator: “This customer has filed 3 prior disputes, has a 67% return rate, is linked to 4 other accounts in our records — the pattern of bad-faith activity is documented in our store, not just inferred from this single transaction.”
This kind of evidence is rarely available to merchants. Adjudicators who see it — and recognize it — weigh it heavily.
The Workflow #
Step 1: Dispute Arrives #
You’re notified via:
- Stripe / WooPayments webhook notification
- TrustLens Chargeback Filed Alert email (Pro)
- Your processor’s dispute notification email
The dispute is auto-ingested into TrustLens (Stripe/WooPayments) or needs manual entry (PayPal/Square/other).
Step 2: Open the Customer Profile #
- From the dispute notification, click through to TrustLens
- Open the customer’s detail page
- Note their current trust score and segment
- Review the signal breakdown
- Open the disputes panel — see prior dispute history
- Open the linked accounts panel — see fraud-ring context
Within 60 seconds you have a complete picture of who this customer is.
Step 3: Decide on the Response #
Three paths based on what you see:
| Customer Profile | Response Strategy |
|---|---|
| Critical segment, multiple disputes, abuse signals | Aggressive defense with behavioral evidence; block customer; auto-block-after-N-lost setting (Pro) |
| Risk segment, one or two signals | Standard defense with behavioral context; note for future |
| Trusted/Normal, clean history, isolated dispute | Verify the dispute is legitimate; consider accepting if the cardholder’s claim is plausible |
| VIP, no signals, legitimate-seeming dispute | Often accept or refund proactively — relationship value > dispute cost |
Step 4: Generate the Dispute Evidence Report (Pro) #
- On the customer detail page, click Generate Dispute Evidence Report
- If the customer has multiple disputes, select the one you’re responding to
- The PDF downloads
- Review it — confirm the data is accurate
The report includes:
- Trust score and segment context
- Every signal contributing to the score
- Behavioral comparison to your store-wide averages
- Linked accounts (if any)
- Complete event timeline
- Methodology explanation
Step 5: Submit Your Dispute Response #
Each gateway has its own response form. Generally include:
- Standard evidence: tracking, signed delivery, communications, refund policy
- TrustLens Evidence Report: attached as supporting PDF
- Cover letter (optional but recommended for high-value disputes): one paragraph summarizing the behavioral pattern
Submit before the deadline. Most gateways close the window strictly.
Step 6: Track the Outcome #
Outcomes typically arrive 30–60 days later. TrustLens auto-updates the dispute status when Stripe/WooPayments fires the webhook. For manual-entry gateways, update the status when you hear back:
- Open the disputes panel on the customer’s profile
- Edit the dispute
- Update status (Won / Lost)
- Add a note about the outcome
The customer’s score recalculates on status change.
Per-Reason-Code Strategy #
Fraudulent / Unauthorized #
If the customer claims fraud but TrustLens shows linked accounts, prior disputes, or card-testing involvement — the behavioral evidence is decisive. Win rates are highest here.
Product Not Received #
Standard evidence (tracking, delivery confirmation) is dominant; behavioral evidence supplements. If the customer has prior “not received” disputes, the pattern is suggestive.
Product Not as Described #
Hardest category. Behavioral evidence helps less; product evidence (descriptions, photos, customer service interactions) dominates.
Subscription Disputes #
Subscription opt-in evidence + behavioral context (account age, prior renewals accepted). Behavioral evidence helps when the customer claims “first I heard of this subscription” but their account shows 14 prior renewals.
Cancelled / Refunded but Charged #
Standard refund-policy evidence dominates. Behavioral evidence less relevant.
When to Accept Instead of Fight #
Some disputes aren’t worth fighting:
- Low-value disputes (less than the time cost of evidence preparation)
- VIP customer with clean history disputing in good faith
- Legitimate claims you don’t have evidence to refute
- Disputes where your evidence is weak (no tracking, ambiguous policy)
Accepting a dispute admits liability — the cardholder is refunded, the chargeback fee may still apply, but no fight occurs. For some disputes this is the right call.
Building a Dispute Response Routine #
Treat dispute responses as a recurring workflow, not ad-hoc tasks:
- Daily or every-other-day check for new disputes
- For each: open customer profile, decide strategy, generate Evidence Report, submit response
- Weekly: review status of pending disputes
- Monthly: audit win/loss rate by reason code
Stores doing this consistently see win rates climb steadily as evidence quality and team discipline improve.
Automation Opportunities (Pro) #
| Trigger | Use |
|---|---|
| Chargeback Filed | Auto-generate Evidence Report and email to fraud team for response |
| Dispute Status Changed (Lost) | Increment lost-dispute counter; if >= threshold, auto-block |
| Dispute Status Changed (Won) | Document the win in admin notes for future reference |
Metrics to Track #
- Win rate overall
- Win rate per reason code
- Win rate with vs without Evidence Report
- Average dispute value won
- Time-to-response (faster usually correlates with higher win rate)
- Disputes per customer (catches repeat-disputer pattern)
Long-Term Pattern Recognition #
Over months, you’ll see patterns:
- Specific products or categories generating disproportionate disputes — fix upstream
- Specific reason codes dominating — fix root cause (policy, descriptions, shipping)
- Specific customer cohorts disputing — adjust acquisition or moderation
- Card brands with higher dispute rates — consider payment method controls
The Chargeback Activity Report (Pro) surfaces these patterns automatically. Review monthly.
Updated on June 4, 2026
