How to Use TrustLens’s Dispute Evidence Report to Win a WooCommerce Chargeback
Plugin Guide · TrustLens Pro
One Click. One Report. One Chance.
When a chargeback arrives, you get one submission window. TrustLens Pro’s Dispute Evidence Report turns your customer’s full behavioral history into a print-ready document — designed to be attached to a Stripe or WooPayments dispute response on the day it lands.
The hardest part of a chargeback dispute is not knowing what to submit. Most store owners have the right instinct — they know behavioral history matters, that prior orders and refund patterns tell a story a tracking number cannot — but pulling that history together under a 7-to-21-day deadline is slow, manual work. By the time you have assembled it, you have often already missed the best submission window.
TrustLens Pro includes a feature built specifically for this moment: the Dispute Evidence Report. It is a Pro-only, one-click behavioral risk report accessible directly from the customer’s profile page or from the WooCommerce order metabox. The output is a print-optimized HTML document that you can save as a PDF and upload to a payment processor dispute portal alongside your other evidence.
This guide covers what the report contains (verified against the plugin code, TrustLens 1.3.22), how its Visa Compelling Evidence 3.0 matching and independent verification work, how to generate it from both entry points, how to attach it to Stripe and WooPayments dispute submissions, and how to assess honestly whether the report will strengthen your case before you submit.
Part of the chargeback cluster
This post is the TrustLens-specific workflow layer. For the general evidence strategy — what four layers of evidence a dispute response needs, and why behavioral history is the layer most merchants skip — see How to Fight a WooCommerce Chargeback and Actually Win. For the upstream signals that typically precede a chargeback, see The WooCommerce Chargeback You Could Have Seen Coming. If you are not yet familiar with how chargebacks affect your payment processor relationship and account standing, WooCommerce Chargebacks: How a Few Disputes Can Trigger a Payment Gateway Ban covers the mechanics from the start.
What This Report Is For — and What It Is Not
The Dispute Evidence Report is a behavioral history document. It is not a tracking number, a delivery confirmation, or a product description — those are the transaction-documentation layer of a dispute package. This report is the behavioral layer: it tells the bank who this customer is on your store, what their history looks like, and whether their current dispute claim fits that pattern or contradicts it.
That distinction matters for how you use the report. A customer who has placed eight orders over two years and is disputing their most recent one produces a report that directly supports a Compelling Evidence argument: prior non-disputed transactions, an established purchasing relationship, a pattern that is inconsistent with “I don’t recognise this charge.” A first-time buyer with no prior history produces a report that shows exactly that — limited behavioral data — which tells you the report adds little to this particular dispute and you should focus on identity linkage and transaction documentation instead.
The Dispute Evidence Report does not fabricate evidence. It documents the behavioral history that TrustLens has tracked through its eight detection modules and the customer’s actual order history in your WooCommerce store. Good behavioral history strengthens a dispute. Thin behavioral history tells you something different: that this dispute is not a behavioral history fight, and you should adjust your strategy accordingly.
What the Dispute Evidence Report Actually Contains
The TrustLens Dispute Evidence Report is generated by the TrustLens_Dispute_Report class (Pro-only, requires the Chargebacks module to be active). It is a print-optimized HTML page that saves cleanly to PDF via the browser’s print dialog. The sections below appear top to bottom; two of them — the prior-order match table and the disputed-order detail — appear only when you open the report from a specific order. For a field-by-field reference, see the Dispute Evidence Report documentation.
1. Report header
The header carries the TrustLens mark, the document label “Chargeback Evidence Report”, your store name, and the date the report was prepared; a footer line records the exact generation time. (It’s the same feature: the buttons that open it in the admin are labelled “Dispute Report”, and the document it produces is headed “Chargeback Evidence Report”.) The formal framing matters — a bank reviewer working through dozens of responses sees a structured document, not a manual note.
2. Verdict banner
The first thing a reviewer sees. Opened from a disputed order, the banner gives an evidence assessment: “Compelling evidence: Strong” when two or more prior orders qualify under Visa CE3.0, “Compelling evidence: Moderate” when one does, and “Limited matching evidence” when none do. Under the headline sits a one-sentence continuity statement built from the data — along the lines of “This customer has placed 14 orders totaling $2,340 since March 2023, 6 of them shipped to the same address as the disputed order, and only this order has been disputed.” A row of figures follows: CE3.0-qualifying prior orders, identifier types matched, the trust score with segment, and the customer’s return rate against your store average.
Opened from a customer profile instead, the banner switches to a customer risk assessment — “Risk profile: [segment]” with the trust score and a recommendation: “strong representment candidate” (score 70 or above), “review before representment” (45–69), or “representment not advised” (below 45). The figures row then shows lifetime orders and lifetime value in place of the CE3.0 counts.
3. Prior orders from this same customer (order entry point only)
A table of every earlier order that shares at least one identifying detail with the disputed order: order number, date, total (flagged if refunded), chips showing which details matched — Address, Billing, IP, Device, Card, Phone — and either a green CE3.0 badge or the number of days before the dispute it was placed. How an order earns the badge is covered in the CE3.0 section below.
4. Customer risk profile
Three data points displayed prominently in a grid:
- Trust score: the customer’s current TrustLens score on a 0–100 scale
- Risk segment: their classification in the six-tier system — VIP, Trusted, Normal, Caution, Risk, or Critical
- Customer since: the month and year of their first order
Below the grid, the report lists every active risk signal currently contributing to the customer’s score — each signal labelled with a plain-English description and its point value (positive signals in green, negative in red). These signals come directly from TrustLens’s eight detection modules: return abuse, order patterns, coupon abuse, category-aware risk, linked accounts, shipping anomalies, chargebacks, and card-testing exposure.
5. Disputed order (order entry point only)
If you generate the report from the WooCommerce order edit page rather than from the customer profile, TrustLens adds a Disputed order section with the specific transaction: order number, date, total, status, payment method, ship-to address, and a line-item breakdown. This section is skipped when you generate from the customer profile without a specific order context.
Including the disputed order context is useful when you want the reviewer to see the disputed transaction directly alongside the customer’s behavioral history — making the contrast explicit.
6. Order history
A table of up to 50 of the customer’s most recent orders, showing order number, date, total, status, and any refund amount on each order. This is the behavioral history layer that most directly supports a Compelling Evidence argument: prior completed orders, each with its date and status, showing that this customer has transacted with your store repeatedly without disputing.
For a customer with a long history, the reviewer sees a clear pattern. For a new customer with one or two orders, the table is short — but it is still accurate, and its brevity is itself informative.
7. Return analysis
A comparison of the customer’s return rate against your store-wide average, including:
- Customer return rate vs. store average return rate (percentage)
- Total refund count, broken down into full refunds and partial refunds
- Total refund value in currency
When the customer’s return rate exceeds the store average, TrustLens adds an explicit note with the multiplier — for example, “This customer’s return rate is 4.2x the store average (38% vs 9%).” (A below-average rate gets a green note saying so.) That phrasing is directly quotable in your summary statement to the bank, providing context that a shipping confirmation screenshot cannot.
8. Linked accounts
If TrustLens’s linked accounts detection module has identified other customer accounts sharing fingerprint data with this customer — same shipping address, billing address, phone number, IP address, payment method, or device — those linked accounts appear in this section. Each shows the linked account’s trust score, risk segment, blocked status (if applicable), and the specific match types that created the link. When no other account shares the customer’s identifiers, the section says so, which is itself a useful statement for a reviewer.
Linked accounts are relevant in dispute responses involving suspected systematic fraud. If the disputing customer is part of a multi-account cluster that has previously received refunds or placed disputes across your store, that pattern is documented here.
9. Event timeline
A chronological log of the customer’s 12 most recent events tracked by TrustLens — counted orders, refunds (with amounts), order cancellations, blocks and unblocks, and disputes opened and closed — with a count of any earlier events beneath it. Each entry shows the event type, date, time, and the associated order number where applicable.
Negative events (refunds, cancellations, disputes opened, blocks) are visually marked in red; positive events (counted orders, unblocks, dispute closures) in green. The timeline makes it possible to see, at a glance, the sequence of orders, refunds and disputes leading up to the chargeback.
10. Verification block
At the foot of the report: the Report ID (in the form TL-XXXX-XXXX-XXXX), the report’s SHA-256 fingerprint and — while Report Verification is on — the verification address and a “Scan to verify” QR code. What that block lets a reviewer confirm is explained in Independent verification below.
Historical sync makes this meaningful from day one
TrustLens’s Historical Sync builds customer profiles from your existing WooCommerce order history — not just orders placed after installation. This means the order history, refund analysis, and event timeline in the report reflect your actual customer relationship, going back as far as your store data does. If you installed TrustLens last month, the report for a long-standing customer still contains their full prior history. The sync runs in the background in small batches and does not affect site performance.
How Visa CE3.0 Matching Works in the Report
Visa Compelling Evidence 3.0 (CE3.0) is Visa’s framework for answering “I didn’t make this purchase” disputes — card-absent fraud claims, Visa dispute condition 10.4 — with transaction history. If the same cardholder made earlier, undisputed purchases from you using the same identifying details, that history can be submitted as compelling evidence that the disputed purchase fits an established pattern. It is the formal version of the argument the order history section makes informally, which is why the report leads with it whenever there is a disputed order to match against.
When you open the report from a disputed order, TrustLens compares that order with each earlier order in the customer’s history. A prior order earns the CE3.0 badge only when all four conditions hold (checked in the plugin’s TrustLens_Dispute_Evidence class):
- It was placed 120 to 365 days before the disputed order.
- It shares at least two identifying details with the disputed order.
- It was not refunded — a full or partial refund disqualifies it.
- It was not itself disputed.
The details compared are shipping address, billing address, IP address, device fingerprint, saved payment token, and phone number. They are matched as one-way hashes — the same pseudonymized fingerprints the linked accounts module uses — so the comparison never needs the raw values, and the report’s footer says as much. Matching orders that miss a condition still appear in the table with their day count, so you can see why each one fell short; qualifying orders are sorted to the top. Two or more qualifying orders produce the “Strong” verdict, one produces “Moderate”.
The window is strict, and TrustLens doesn’t round up
An order placed 115 days before the dispute doesn’t count; neither does one placed 400 days before. A customer who ordered every month for two years can still show a CE3.0 count of zero if the orders inside the window were refunded or match on only one detail. Visa’s own rules also define which data elements count and how they must be submitted, and your processor makes the final call — so treat the badge as a well-founded pre-screen, not a ruling.
Two practical consequences. First, for a fraud-coded dispute, always open the report from the disputed order — the customer-profile version skips CE3.0 matching entirely. Second, the continuity statement under the verdict is written to be lifted straight into the opening line of your rebuttal: it is specific, factual, and drawn directly from your order data.
How to Generate the Report: Two Entry Points
TrustLens Pro surfaces the Dispute Evidence Report from two places in your WordPress admin. Both produce the same report. The difference is context: one includes the specific disputed order — and with it the CE3.0 verdict and match table — and one does not.
Entry point 1: TrustLens customer profile
Open TrustLens and find the customer
Go to TrustLens in your WordPress admin menu. On the customer list page, search by email address or customer name. Click through to the customer’s profile page. You will see their trust score, segment, signal breakdown, and behavioral history.
Click “Dispute Report”
In the action buttons on the customer profile page, TrustLens Pro adds a “Dispute Report” button. Clicking it opens the report in a new browser tab. The report opens immediately — there is no loading step or configuration prompt.
Save as PDF
At the top of the report page, a sticky toolbar tells you how: click “Print Report”, choose “Save as PDF” as the destination, set Margins to “None”, and turn on “Background graphics” for full color. On Windows, “Microsoft Print to PDF” also works. The report’s print stylesheet hides the toolbar and renders cleanly for PDF output. If Report Verification is on, a status line under the toolbar confirms whether the report was registered with the verification service.
Entry point 2: WooCommerce order edit page
Open the disputed order in WooCommerce
Navigate to WooCommerce → Orders and open the order that has been disputed. TrustLens Pro adds a metabox to the order edit page showing the customer’s trust score and segment. Within that metabox, you will see a “Dispute Report →” link.
Click “Dispute Report →”
The link opens the report in a new tab with the disputed order’s context loaded: the CE3.0 evidence verdict and prior-order match table at the top, and the Disputed order section further down. This is the recommended entry point for almost every dispute, as it makes it easier for the bank reviewer to correlate the behavioral history with the specific transaction in question.
Save as PDF
Same procedure as above: use the “Print Report” button in the toolbar, select “Save as PDF,” and save the file. Name it clearly — something like “CustomerBehavioralRiskReport-[CustomerEmail]-[Date].pdf” — so it is identifiable when you upload it to the dispute portal.
Also accessible from the Chargeback Monitor
TrustLens Pro’s dedicated Chargeback Monitor page (TrustLens → Chargeback Monitor) links to the report from two more places. Each row of the Open Disputes worklist has an “Evidence” button that opens the report with that dispute’s order context — so CE3.0 matching runs — and shows whether the report has been registered with the verification service (“Registered” or “Verify pending”). The top disputed customers list links to the customer-level version. For the full monitor walkthrough — ingestion, ratio thresholds, the deadline worklist and auto-block — see WooCommerce chargeback tracking with TrustLens.
Reading the Report Before You Submit
Before attaching the report to a dispute, spend two minutes reading it. What you are looking for is whether the behavioral history it documents actually helps your case — because a report that shows a customer with no prior orders, no red flags, and no meaningful history does not strengthen your dispute. It just adds a document that tells the reviewer there is nothing unusual about this customer, which is not the argument you want to make.
Start with the verdict banner
If you opened the report from the disputed order, the banner has already done the first triage. “Strong” means you have the two qualifying prior orders a CE3.0 response needs. “Moderate” means one — worth filing, with realistic expectations. “Limited matching evidence” means CE3.0 is off the table for this dispute and the rest of the report has to carry the argument. Making that call in two minutes, before you write anything, saves building a case the evidence can’t support. Then work through three questions:
Does the order history show prior non-disputed transactions?
This is the core of a Compelling Evidence argument. If the customer has two or more completed orders that predate the disputed one, and those orders were not disputed, that history is directly usable in your dispute summary. Note the number of prior orders, the total order value over time, and the dates — you will want to reference these in the summary statement you write for your processor.
Does the return analysis show elevated behavior?
If the customer’s return rate is materially higher than your store average, the report flags this explicitly with the multiplier (e.g. “3.8x the store average”). That figure is quotable. It does not prove fraud, but it establishes that this customer’s behavior is statistically atypical relative to your customer base — relevant context for a bank reviewer assessing a friendly fraud claim.
Does the event timeline show a suspicious sequence?
A customer who received a shipping notification, received the goods (per your delivery confirmation), and then filed a dispute within days — without any contact with your support team — has a timeline that is inconsistent with genuine confusion about the charge. The event log in the report shows order completion, any refund events, and dispute-related events in sequence. If the pattern is there, it is visible without you having to construct it manually.
If the report shows a thin history, adjust your strategy
A report showing a first-time buyer with no red flags is honest — it means TrustLens does not have behavioral history to document. That is not a failure of the report; it is accurate information. For this dispute, focus on identity linkage evidence (matching email, IP, billing address, prior communication) and transaction documentation rather than behavioral history. Submitting a behavioral report that shows nothing unusual is not harmful, but it adds no persuasive weight. Save your effort for the layers that do.
Independent Verification: Proving the Report Is Unaltered
Every document in a dispute response comes from the merchant, and a reviewer has no direct way to tell whether a PDF of order history was produced on the day or edited the night before. When the report renders, TrustLens computes a SHA-256 fingerprint of the report’s key facts: your store URL, the disputed order, the customer’s trust score and segment, the CE3.0 count, lifetime order count and value, return rate, and every matched prior order with its shared identifiers. The generation time is deliberately left out, so regenerating a report from unchanged data gives the same fingerprint, while any change in the data gives a new one. The first 12 characters become a human-readable Report ID (TL-XXXX-XXXX-XXXX). The verification block prints both, along with the verification address — webstepper.io/verify/[Report ID]/ — and a QR code that TrustLens draws itself in PHP, with no external library or network call.
What a reviewer sees at webstepper.io/verify
While Report Verification is enabled (the default), generating a report registers its fingerprint with the TrustLens verification service at webstepper.io. Anyone holding the printed report can scan the QR code or enter the Report ID — no login, no account — and see the record on file: the Report ID, the fingerprint, the generation date, the merchant’s domain, and the reported figures (CE3.0 count, trust score, segment and return rate), labelled as submitted by the merchant. A paste-to-compare field checks a fingerprint copied from the report against the one on file. Records are write-once: the service rejects any attempt to register a different fingerprint under an existing Report ID.
What verification confirms — and what it doesn’t
The verification page is explicit about its scope: it confirms that a fingerprint was received and stored, and Webstepper does not certify, endorse or guarantee the report’s figures, which come from your store. So the honest claim is narrow — the report in the reviewer’s hands matches the version registered when it was generated. Because the fingerprint covers the report’s key facts rather than every table row, the practical check is whether the Report ID, fingerprint and four headline figures match the printed copy. In your rebuttal, say the attached report can be independently verified at the address printed on it — not that a third party has certified the customer’s behavior.
If registration fails
Registration never blocks the report. If the service can’t be reached, the toolbar says so and TrustLens retries — when you reopen the report, and through an hourly background job (up to 48 attempts). The Report ID and fingerprint are computed locally, so the printed report stays valid; if a lookup finds no record, the verification page says the printed fingerprint remains the source of truth.
Ed25519 signing on the verification service
The service also signs each record it stores — Report ID, fingerprint and receipt time — with an Ed25519 key, and shows the signature on the verification page. The public key (webstepper.io/wp-json/trustlens/v1/pubkey) and each signed record (/wp-json/trustlens/v1/attestations/[Report ID]) are published, so a developer or legal team can check the signature offline with any Ed25519 library — making the stored record tamper-evident too, not just the printed report.
Privacy: What Leaves Your Server, and What Doesn’t
Report Verification is disclosed in the External Services section of the TrustLens readme. Each time a report is generated while it is enabled, TrustLens sends webstepper.io:
- the Report ID and SHA-256 fingerprint (one-way — it cannot be reversed into report contents)
- the generation timestamp and your site URL
- the disputed order number, as a reference only
- four figures: CE3.0 count, trust score, risk segment and return rate
No customer personal data is sent — no names, email addresses, postal addresses, IP addresses, email hashes, device fingerprints or payment tokens. The identifier matching behind the CE3.0 table happens on your server, on hashed values.
To turn verification off, open TrustLens → Chargeback Monitor and switch off the toggle in the Chargeback settings card (labelled “Verify dispute reports” there; the readme calls it Report Verification). With it off, nothing is sent; reports still print the Report ID and fingerprint for your own records, but leave out the verification address and QR code.
Attaching the Report to a Stripe Dispute
Stripe’s dispute response interface is structured around the dispute reason code. When you open a dispute in the Stripe Dashboard under Payments → Disputes, you will see the reason code (e.g. “Unrecognized” for code 4853 or “General” for code 10.4), and a step-by-step evidence submission form that presents fields relevant to that code.
The Dispute Evidence Report maps onto Stripe’s evidence categories as follows:
| Report section | Stripe evidence field | Notes |
|---|---|---|
| Verdict banner and CE3.0 match table (prior orders sharing identifiers) | Additional evidence (text) + file upload | Paste the continuity statement and the number of CE3.0-qualifying prior orders into your summary; if your processor offers a dedicated CE3.0 submission, the match table lists the orders to use |
| Risk Summary (trust score, segment, signals) | Additional evidence (text) + file upload | Upload the PDF; reference the score and segment in your text summary |
| Order History (prior non-disputed orders) | Customer communication or uncategorized evidence | Upload the PDF and cite specific prior order numbers in your text summary |
| Return Analysis (elevated return rate vs. store average) | Additional evidence (text) | Quote the multiplier directly: “Customer’s return rate is 3.8x store average” |
| Linked Accounts (if present) | Additional evidence | Mention in your text summary; the PDF documents it visually |
| Event Timeline (sequence showing dispute vs. communication pattern) | Customer communication | Reference specific events in your text summary — e.g. “Customer received delivery notification on [date] and filed dispute [N] days later without contacting support” |
The evidence text field
Stripe gives you a text area for a summary statement — this is where the report pays off most directly. Write 4–6 sentences that walk the reviewer through the most persuasive points from the behavioral report alongside your transaction evidence. A structure that works:
- State the dispute reason code claim and what your transaction evidence shows directly contradicts it.
- State the number of prior non-disputed orders from this customer and the date range they span.
- If the return rate is elevated, quote the comparison: “Customer’s return rate of [X]% is [N]x the store average of [Y]%.”
- Note the timeline gap between delivery and dispute filing, and whether the customer contacted your support before filing.
- State that a full behavioral risk report is attached as an additional document, and that it can be independently verified at the address printed in its verification block.
File upload limits
Stripe accepts a combined total of 5MB across all evidence attachments, in PDF, JPG, or PNG format. The TrustLens Dispute Evidence Report saved as a PDF is typically well under 1MB. Leave room in the file budget for your shipping confirmation, order screenshot, and any customer communication records.
Attaching the Report to a WooPayments Dispute
WooPayments is built on Stripe’s infrastructure, so the underlying dispute mechanics — reason codes, evidence categories, response windows — are identical. The user interface for managing disputes appears in your WooCommerce admin rather than the Stripe Dashboard, but the submission process follows the same structure.
In WooCommerce, disputes for WooPayments-processed orders appear under Payments → Disputes. Click “Challenge” on an open dispute to access the evidence submission interface. The fields map to the same Stripe evidence categories described above. Save the TrustLens Dispute Evidence Report as a PDF and upload it in the additional evidence section, with a matching text summary referencing the behavioral history it documents.
Chargeback tracking is automatic for Stripe and WooPayments
If you use Stripe or WooPayments, TrustLens automatically ingests dispute events as they arrive — no manual setup required. Chargeback events appear in the customer’s event timeline immediately and feed into their trust score. This means the Dispute Evidence Report for a repeat disputing customer will include their dispute history as part of the event timeline, which is useful context for a bank reviewer assessing whether this specific dispute fits a pattern.
Other Processors: PayPal, Square, and Manual Gateways
The Dispute Evidence Report works for any processor — it is a PDF document, and any dispute portal that accepts file uploads can receive it. The mechanics differ by processor.
PayPal
PayPal’s Resolution Center allows merchants to upload evidence files and write a response statement when challenging a dispute. Navigate to Resolution Center → Activity → the disputed transaction → Respond, and submit your evidence package including the PDF. PayPal’s evidence form is less structured than Stripe’s — you will primarily be writing a summary and uploading supporting files, rather than filling categorised fields. Keep your summary concise and anchor it to the specific claim the buyer made.
Square
Square surfaces dispute challenges through its Dashboard under Disputes. Upload the PDF and write your summary statement in the response field. Square’s timelines are typically shorter than Stripe’s — some dispute types have a 7-day window from notification, so respond immediately when you receive the alert.
Manual gateways (PayPal Here, offline, custom)
TrustLens includes a manual chargeback entry form on the WooCommerce order edit page for gateways that do not automatically push dispute data into the system. If you have recorded manual chargebacks for a customer, those entries appear in the event timeline. This matters for the accuracy of the behavioral report: a customer who has previously disputed orders through a non-integrated gateway will have that history reflected in the report if you recorded those chargebacks manually.
When the Report Helps Most — and When It Does Not
The Dispute Evidence Report adds the most value in disputes where the behavioral history is substantive and the dispute claim is inconsistent with that history. Here is a realistic assessment of when it moves the needle and when it does not:
| Scenario | Report value | Why |
|---|---|---|
| Fraud-coded (“unauthorized”) dispute, verdict reads “Compelling evidence: Strong” (2+ CE3.0-qualifying prior orders) | High | Prior undisputed orders sharing identifiers are exactly what Visa CE3.0 asks for; the match table and continuity statement do the assembly |
| Repeat customer, 5+ prior orders, no prior disputes, disputing their most recent order | High | Order history directly supports Compelling Evidence; prior non-disputed orders are the strongest behavioral signal |
| Customer with elevated return rate (significantly above store average), disputing instead of requesting a refund | High | Return rate comparison is concrete and quotable; establishes atypical behavioral pattern |
| Linked accounts detected — customer part of a multi-account cluster with prior dispute or refund history | High (for pattern) | Documents systematic behavior; linked account section of report is directly relevant evidence |
| Customer is in Caution, Risk, or Critical segment — multiple negative signals active | Moderate | Risk summary gives reviewer clear behavioral context; combined with transaction evidence this strengthens the package |
| First-time buyer, clean history, dispute on first order | Low | No meaningful behavioral history to document; focus on identity linkage and transaction evidence instead |
| Genuine customer service failure — item not delivered, wrong item shipped | None | Behavioral history is irrelevant when the dispute reflects a legitimate service problem; issue a refund rather than fighting |
The underlying logic is consistent with how banks assess friendly fraud disputes: they are looking for evidence that contradicts the stated claim. Behavioral history that shows a long-standing customer relationship, a pattern of completed orders, and a dispute that does not fit prior behavior is the most relevant evidence you can add to a transaction-documentation package. The report does not create that evidence — it documents it efficiently so you can submit it within your response window.
Frequently Asked Questions
Is the Dispute Evidence Report available in the free version of TrustLens?
No. The Dispute Evidence Report is a Pro-only feature. It requires TrustLens Pro to be licensed and the Chargebacks module to be active. The free version of TrustLens includes chargeback tracking (automatic ingestion from Stripe and WooPayments, plus manual entry for other gateways), per-customer dispute counters, and a dashboard alert when a card brand’s monthly chargeback ratio crosses its line — but the one-click report generation is Pro only.
Where exactly do I find the Dispute Report button?
Two places. First: the TrustLens customer profile page — after navigating to TrustLens and searching for the customer, the “Dispute Report” button appears in the action area of their profile. Second: the WooCommerce order edit page — TrustLens Pro adds a metabox to each order showing the customer’s trust score, and within that metabox there is a “Dispute Report →” link. Using the order page entry point includes the specific disputed order’s details in the report; using the customer profile entry point generates the behavioral history without a specific order section.
How do I save the report as a PDF?
The report opens in a new browser tab with a sticky toolbar containing a “Print Report” button. Click that button (or use your browser’s print function directly), select “Save as PDF” as the destination, set Margins to “None”, and turn on “Background graphics” so the colored verdict banner and badges print. The report has a dedicated print stylesheet that hides the toolbar and renders the content cleanly for PDF output. Most modern browsers — Chrome, Edge, Firefox, Safari — support this natively without additional software. On Windows, “Microsoft Print to PDF” also works. Save the PDF with a descriptive filename before uploading it to your dispute portal.
What if TrustLens was installed recently — will the report have meaningful data?
Yes, if you have run the Historical Sync. TrustLens’s Historical Sync builds customer profiles from your existing WooCommerce order history — not just orders placed after installation. After running the sync (which runs in the background and does not affect site performance), TrustLens customer profiles reflect your store’s full historical data. A customer who has placed orders with your store for three years will have a three-year behavioral history in TrustLens after the sync completes, even if you installed the plugin last week.
Will submitting this report guarantee I win the dispute?
No. There are no guarantees in chargeback disputes — the process is tilted toward the cardholder by design. Industry estimates suggest merchants win around 20–30% of disputes they contest. The Dispute Evidence Report gives you the behavioral history layer that most merchants skip, which strengthens a dispute package when the history is substantive. But it works alongside transaction documentation (delivery proof, order confirmation, identity linkage) rather than replacing it. A complete evidence package with a strong behavioral history layer gives you the best realistic chance; it does not guarantee an outcome.
What is the difference between generating the report from the customer profile versus from the order page?
The behavioral content is identical — the same trust score, signals, order history, return analysis, linked accounts, and event timeline. The difference is the disputed-order context. Generated from the WooCommerce order edit page, the report opens with a CE3.0 evidence verdict and a table of prior orders that share identifiers with the disputed one, and includes a Disputed order section (order number, date, total, status, payment method, ship-to address, and line items). Generated from the customer profile, the verdict becomes a customer risk assessment and there is no CE3.0 matching. For most dispute responses — and every fraud-coded one — the order page entry point is preferable.
Does report verification send customer data to Webstepper?
No. With Report Verification on, TrustLens sends only the Report ID, the one-way SHA-256 fingerprint, the generation timestamp, your site URL, the disputed order number, and four figures — CE3.0 count, trust score, segment, and return rate. No names, emails, addresses, IP addresses, email hashes, or payment details leave your store. You can switch verification off on the TrustLens → Chargeback Monitor page; reports then still print their Report ID and fingerprint but omit the verification link and QR code.
Does TrustLens track chargeback history for customers who dispute through PayPal or other non-Stripe gateways?
TrustLens automatically tracks chargebacks for Stripe and WooPayments (which uses Stripe’s infrastructure). For other gateways — PayPal, Square, offline payment methods, or custom integrations — TrustLens provides a manual chargeback entry form on the WooCommerce order edit page. Manually recorded chargebacks appear in the customer’s event timeline and feed into their trust score, so if you record them consistently, the Dispute Evidence Report reflects a complete dispute history regardless of which gateway the original transaction used.
Key Takeaways
- TrustLens Pro’s Dispute Evidence Report is a print-ready behavioral risk document — accessible from the customer profile page or the WooCommerce order metabox — that compiles a customer’s full history into a single PDF for dispute submission.
- The report opens with a verdict banner and — when generated from the disputed order — a Visa CE3.0 match table, followed by the customer risk profile (trust score, segment, signals), disputed order details, order history, return analysis vs. store average, linked accounts, a chronological event timeline, and a verification block.
- A prior order qualifies for CE3.0 only if it was placed 120–365 days before the disputed order, shares at least two identifying details with it, and was neither refunded nor disputed. Two qualifying orders make the verdict “Strong”, one “Moderate”; TrustLens doesn’t round up, and your processor makes the final call.
- Every report carries a SHA-256 fingerprint, a Report ID, and (with Report Verification on) a QR code to webstepper.io/verify, where a reviewer can confirm it matches the registered version. Verification confirms integrity, not the underlying claims — and only the fingerprint, order number, site URL, and four figures leave your server, never customer personal data.
- Save the report as a PDF using your browser’s print-to-PDF function, then upload it to Stripe or WooPayments dispute portals alongside your transaction documentation and a concise text summary.
- The report’s value scales with the customer’s behavioral history. A customer with five prior non-disputed orders and an elevated return rate produces a report that directly supports a Compelling Evidence argument. A first-time buyer with clean history produces a report that honestly shows limited data — useful information, but not the basis for a behavioral dispute.
- Chargeback tracking is automatic for Stripe and WooPayments. For other gateways, use TrustLens’s manual chargeback entry form on the order edit page to keep dispute history accurate in customer profiles.
- The report does not create evidence that does not exist. It documents what TrustLens has tracked — efficiently, in a format designed for dispute submission, without manual assembly under deadline pressure.
The report does not decide the dispute — your preparation does
What the Dispute Evidence Report solves is an assembly problem. The behavioral history that makes the difference in a friendly fraud dispute — prior orders, refund patterns, linked accounts, event timeline — exists in your WooCommerce data. Extracting it, formatting it, and submitting it within a 7-day response window is where merchants typically fail, not because they lack the data but because they run out of time.
TrustLens Pro gives you that layer ready to go when the dispute notification arrives. You still need the transaction documentation — the order confirmation, delivery proof, identity linkage — and you still need to write a clear summary statement. But the behavioral layer, which is the most distinctive and persuasive evidence in a friendly fraud dispute, is one click away rather than an hour of manual work.
Use it for the cases where the history is substantive. Be honest with yourself when it is thin. And build the habit of running the historical sync early, so that when a dispute eventually lands — and for most stores, it will — the behavioral history is already there, accurate, and ready to submit.
If you want to explore the full TrustLens Pro feature set, the TrustLens plugin page covers the complete free and Pro feature breakdown. The free version includes all eight detection modules and chargeback tracking; Pro adds the Dispute Evidence Report, the Advanced Chargeback Monitor with per-brand ratio analytics, automation rules, and ten additional notification types.
Know which customers to trust
TrustLens scores every WooCommerce customer for refund abuse, coupon misuse, and chargeback risk — with eight detection modules and card-testing defense built in. Free on WordPress.org.
