Dispute guide

Chargeback Evidence brings your supplied records into a source-linked workspace. It helps you organize a response and produce files for review. It does not connect to Stripe, submit a dispute, verify current provider status or predict an outcome.

1. Start with the recorded facts

A new dispute lets you record the merchant, dispute and charge references, currency, amount in minor units, reason and status. Unknown deadlines can remain blank. Incomplete draft values are recoverable; the review checks identify missing or malformed information.

Import accepts one Stripe Dispute JSON object, up to 1 MB. The original bytes and SHA-256 are retained alongside a separate imported snapshot. Draft edits do not rewrite that snapshot. Imports are supplied by you and are not live verified. Recheck the current status and response deadline in your provider dashboard; record what you checked in the verification note.

2. Connect the evidence

Evidence accepts JPEG, PNG, PDF and UTF-8 TXT, CSV or JSON. Keep titles specific and describe what a file supports. Link timeline events and response fields to their evidence, or record the limitation when a source is missing. Text previews are inert; PDFs are preserved as opaque downloads. This workspace does not extract PDF text or scan files for malware.

Image previews are bounded display copies. Download original returns the original bytes, including metadata. A file hash identifies those bytes; it does not prove authenticity, delivery or customer identity.

3. Combine screenshots into an attachment

Open Attachment builder. Select 1–16 JPEG or PNG originals from the current dispute and use Move up or Move down to set the page order. Each image gets its own A4 page, portrait or landscape to match its dimensions, without cropping.

The builder creates white-background JPEG copies at quality 0.92, with a maximum long edge of 2,400 pixels. Compression and resizing can reduce detail; this is a prepared copy, not the original. It rejects output above 4.5 MB. It does not combine existing PDFs, text, CSV or JSON files.

Download the prepared PDF and source map. The map records each original hash, output page, dimensions and the finished PDF hash. Open the PDF and inspect every page for readable text and correct orientation. Then attach that PDF in Evidence and select the single prepared PDF for the appropriate file response field. Keep the source map with your records.

Builder selections and generated PDFs are temporary and are not part of the workspace backup until you attach a generated file as evidence. Switching to another dispute cannot select its images into this attachment.

Provider limits apply across all attachments, not just this generated PDF. Stripe documents accepted PDF/JPEG/PNG files, a combined 4.5 MB limit, fewer than 50 pages generally and a 19-page Mastercard limit. Check the current Stripe file guidance and your provider dashboard. A successful build does not certify acceptance.

4. Review fields and freeze a version

Use Response fields to include or omit each field and document its source or reason. File fields need one prepared PDF, JPEG or PNG. A ZIP is an organization packet, not an accepted evidence attachment. The standard field worksheet does not implement enhanced evidence schemas.

Review checks cover the recorded facts, evidence references, required source notes, field decisions and text limits. They do not establish that the argument is complete or correct. A reviewed version freezes the document with the supplied reviewer name and note; this local name is not an authenticated signature. Later draft edits clear field reviews while the earlier version stays available.

5. Export and retain your record

Draft and reviewed ZIP packets include an offline HTML report, JSON report, field map, timeline CSV and originals associated with that case. The field map is a worksheet, not an executable Stripe API request. Browser Print / Save PDF produces a report; original PDFs remain separate. CSV values that look like spreadsheet formulas are escaped.

Export backup preserves the whole workspace. Restore validates the schema, source metadata and original hashes before asking to replace the current workspace. Cancelling leaves current records intact. Shared tabs use expected revisions; if another tab has saved, export your unsaved edits before reloading.

Supported size and storage limits

Up to 8 disputes, 100 events and 10 reviewed versions per dispute; 100 originals totaling 24 MB; each original up to 8 MB, with text/CSV/JSON limited to 1 MB. Images are limited to 20 megapixels and 10,000 pixels per side. Complete backups are limited to 48 MB. Each text response field allows 20,000 UTF-16 units, with a conservative 150,000-unit combined included-text limit.

Device storage can be cleared or fail. Export a backup regularly. Read Privacy & data before adding sensitive originals or sharing a packet.

Current preview scope

The free workspace runs in your browser without GPT calls. Direct email/password and Google accounts, account-owned cloud storage, live provider ingestion/submission and purchases are not available in this preview. Missing setup and full release work are tracked separately.