Order and dispute
Evidence you have
Check only what you can actually provide. The output identifies gaps; it never claims an outcome.
Saving is optional and keeps these fields only in this browser. Clear it from this device before sharing or handing it to someone else.
Packet review
Copyable response draft
The JSON download contains the fields and checklist you entered. It stays on your device unless you choose where to save or share it.
Chargeback response FAQ
What evidence should a small seller include?
Start with the order record, payment authorization, fulfillment record, and delivery or customer-contact evidence that relates to the dispute reason. This tool identifies a practical starting checklist; your processor may request different records.
Does this tool submit a chargeback response?
No. It runs in your browser and creates a reviewable draft. You remain responsible for checking the facts, redacting unnecessary personal data, meeting the processor's deadline, and submitting through the processor.
Can it guarantee that a dispute will be won?
No. The packet builder makes no prediction or legal determination. It only organizes the evidence you say you have and points out missing items in its checklist.
What extra evidence does a fraudulent-transaction dispute need that others don't?
The checklist's core set for "Fraudulent transaction" is the payment authorization, AVS/CVV verification result, billing-and-shipping address match, and carrier tracking — because the question there is whether the cardholder authorized the purchase, not whether the goods arrived. That is different from "Merchandise not received," where the core set is the order, payment, fulfillment record, and tracking, because the question is delivery. Device/login history and prior undisputed orders are recommended, not core, for a fraud claim.
How close to the deadline is too late to start?
The deadline field flags "urgent" once 3 days or fewer remain, and switches to a same-day warning when the deadline is today. If the date you enter has already passed, it tells you to contact the processor immediately rather than assume a filing is still possible — this tool only does the day-count arithmetic, it does not know your processor's actual cutoff time or whether a late submission is accepted. Start while the checklist still shows "ahead" so a missing record has time to be requested.
What if my dispute reason isn't one of the seven listed?
Choosing a reason outside the seven modeled ones falls back to a minimal core set — order confirmation and payment authorization — plus customer correspondence and accepted terms as recommended records, and a note to confirm the actual requirement with your processor for that reason code. The seven modeled reasons (merchandise not received, credit not processed, merchandise not as described, fraudulent transaction, duplicate transaction, subscription canceled, incorrect amount) cover the most common reason-code families, not every processor's exact taxonomy.
What evidence does a duplicate-charge, canceled-subscription, or wrong-amount dispute need?
A duplicate-transaction dispute is carried by the order and payment records for each charge, showing two distinct purchases rather than one purchase billed twice. A subscription-canceled dispute is carried by the terms the buyer accepted at signup and any record of when and how they canceled, because the question is whether the charge was still authorized when it posted. An incorrect-amount dispute is carried by the order total as originally agreed and the terms accepted at checkout, set against what was actually charged. None of these three share a core set with each other or with the original four.