Pick what your dispute is about and get a prioritized checklist: what each document is, how to get it, and whether it's must-have or nice-to-have — so the reviewer sees exactly what they need.
Private by design — everything runs in your browser.
Bank reviewers spend limited time on each file, and the principle that wins is simple: map each document to your allegation. Claiming the item never arrived? The reviewer wants to see the tracking history. Claiming it differs from the listing? They want the listing as of your purchase date next to photos of what arrived. A small stack of documents that answer the dispute's central question usually outperforms a thick folder of loosely related paperwork. The checklist above is built around that principle — every item exists because it answers something the reviewer is likely to ask.
Worked example: a jacket bought from a listing that promised waterproof and size large; what arrived is a thin, unlined jacket in the wrong size. The dispute reason is "not as described," and the file is five documents — each one answering a single question the reviewer will ask:
Five documents, five questions answered. That is the whole method: when a document does not answer a question in your dispute, it is weight, not evidence.
Sometimes the perfect document is simply not available: the seller never sent a shipping email, the listing page has been deleted, the chat was inside an app you have since removed. A missing document is not the end of the file — reviewers work with substitutes that prove the same fact another way. No shipping email? The carrier's own tracking page, reached with the number from your order page, shows the same history. Listing deleted? Your order confirmation and the account's order-history page still name the item, the price, and the date, and a dated screenshot of the seller's current page at least shows what replaced it. No written record of a phone call? Your own dated note of who you spoke to, when, and what was said — written at the time, not reconstructed later — plus the call's entry in your phone log. And where you asked the merchant for a document and they refused or ignored you, send the request itself: proof that you tried to obtain the record is evidence about the merchant, not just about you.
Read the guide on how bank reviewers weigh evidence — the matching principle, cover-letter structure, and how long to keep your records.
It depends on the dispute reason: for non-receipt, order confirmation, tracking records, and merchant correspondence; for not-as-described, the listing as of purchase plus photos of what arrived; for fraud, a prompt report to your bank and a written statement that you didn't authorize the charge. The checklist builder above tailors the list to your situation.
Reviewers generally weigh documents that map directly onto your allegation: proof of the purchase, proof of what was promised, and proof of what actually happened. A document that answers the specific question the dispute reason raises is usually worth more than a thick folder of loosely related paperwork.
Many issuers expect you to have tried resolving the problem with the seller first, and keeping a record of that attempt is itself useful evidence. A short email or chat thread showing you asked for a fix can strengthen your file.
Yes. The checklist builder runs entirely in your browser — your reason and your checked items are never sent to us or stored anywhere.
No. Good evidence is the biggest lever you control, but outcomes depend on the issuer, the network's rules, and the merchant's response. No honest tool can promise a result — the checklist is about giving the reviewer everything they need to decide in your favor.