--- title: Disputing Chargebacks description: "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…" url: "https://webstepper.io/docs/trustlens/use-cases/disputing-chargebacks/" updated: "2026-10-18" category: Use Cases --- # Disputing Chargebacks 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 1. Open the disputed order, or click through from the alert email to the customer 2. Open the customer's detail page 3. Note their current trust score and segment 4. Review the Signal impact panel — the chargeback signal shows lost and pending disputes 5. Check Recent activity for earlier "Dispute created" and "Dispute closed" events — prior dispute history 6. 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) 1. On the disputed order, click **Dispute Report →** in the Customer Trust box — or, on Pro's Chargeback Monitor, click **Evidence** on the dispute in the Open disputes worklist. Opening it for the order is what adds the matched prior orders and the Visa CE3.0 assessment; the **Dispute Report** button on the customer profile opens a customer-level report without them. 2. The report opens in a new tab. Click **Print Report** and choose "Save as PDF" 3. Review it — confirm the data is accurate The report includes: - An evidence assessment, and the prior orders that share identifiers with the disputed one (flagged where they meet Visa CE3.0) - Trust score and segment context - Every signal contributing to the score - The disputed order, order history, and return rate compared with your store average - Linked accounts (if any) - The most recent events on the customer's timeline - A Report ID and fingerprint (and, with verification on, a verify link and QR code) ### 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 records the outcome automatically when Stripe/WooPayments sends the dispute-closed event. For manual-entry gateways, record it when you hear back: 1. Open the disputed order 2. Under the dispute notice, click **Mark won** or **Mark lost** (shown for manual disputes saved as Pending) 3. Add a note about the outcome in the customer's admin notes if useful The customer's score recalculates when the outcome is recorded. --- ## 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: 1. Daily or every-other-day check for new disputes 2. For each: open customer profile, decide strategy, generate Evidence Report, submit response 3. Weekly: review status of pending disputes 4. 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 | Send Email Notification to the fraud team so the response starts right away (the email links to the customer; the Evidence Report is opened from the order) | | Dispute Recorded | Add Tag or Flag for Review on customers with Total Disputes >= 2, so repeat disputers are reviewed | | Lost outcomes | Not a trigger — use the Pro **Auto-block after lost disputes** setting on the Chargeback Monitor page to block after N lost disputes | --- ## 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 Pro Chargeback Monitor helps surface these patterns — its activity feed shows each dispute's card brand, reason, and source, and its per-brand rows show which network is rising. For product and category patterns, review the line items on the disputed orders. Review monthly.