When you counter a dispute on Stripe, you get one submission. Stripe says it forwards your response and all supporting files to the issuing bank immediately, and that you cannot edit the response or add files afterwards. So the work is in the preparation: gather everything, check it against the dispute reason, format it so a bank reviewer can read it quickly, then submit once.
This checklist follows Stripe's published guidance. It does not change who decides: Stripe states that the outcome is at the sole discretion of the cardholder's bank. For background on the process itself, start with disputes and chargebacks basics.
Before you gather anything
- Note the response deadline. Stripe says it is usually 7 to 21 days depending on the card network, and that if you miss it you automatically lose the dispute.
- Read the dispute category on the dispute details page. Stripe says each category has different response requirements, so this decides what evidence is relevant.
- Open the claim documents from the bank, if provided, and note exactly what the cardholder says went wrong.
- Decide whether to counter or accept. Stripe says that if you believe the payment really was fraud, the appropriate action is to accept the dispute or decline to challenge it. If you agree the buyer should keep the money, accepting is also the right call.
- Contact the buyer if the Dashboard gives you a way to, and keep a record of every message. Stripe notes this can help you understand the complaint and becomes evidence in its own right.
- Check for a Visa Compelling Evidence 3.0 eligibility notice or liability shift coverage. In those cases Stripe pre-populates some fields, and it advises not editing pre-populated Compelling Evidence 3.0 fields because that might affect eligibility.
Evidence to include in most responses
Stripe lists background evidence that is relevant to most dispute types. Where your integration supports it, Stripe fills in much of this automatically, so check what is already there before adding more.
- The receipt or message that notified the buyer of the charge, showing date, currency and amount.
- The customer's name and email address.
- The billing address, if the address verification (AVS) check passed.
- The IP address used for the purchase.
- A description of the product and how it was presented at the time of purchase.
- Any document or contract the buyer signed.
- Relevant customer communication, combined into one file, with only the relevant excerpts of long email threads.
Evidence by dispute category
Fraudulent or unrecognized
Stripe says you need to show that the legitimate cardholder, or an authorized representative such as an employee, made the payment.
- Evidence linking the person who received the products to the cardholder.
- The shipping address, which Stripe says must match an AVS-verified billing address or be the address of a business connected to the cardholder.
- Shipping documentation, ideally the label or shipment receipt, showing the full shipping address.
- Shipping date, carrier and tracking number.
- The 3D Secure result, if the payment was authenticated. Stripe adds the Electronic Commerce Indicator automatically.
- Evidence of one or more earlier payments on the same card that were not disputed.
- Any message in which the buyer recognizes the charge or says the dispute was filed in error.
Product not received
- Proof of shipment and delivery with the full delivery address, not just the city and postal code.
- Shipping date, carrier and tracking number. Stripe expands tracking numbers into carrier delivery details when it compiles your evidence.
- Whether the buyer contacted you before disputing. If they did not, Stripe says to state that clearly.
- If relevant, evidence that the agreed delivery date has not yet arrived, or that the shipment is held by customs.
Product unacceptable
- Evidence that the product was accurately represented before purchase, such as the product page as it read on the order date.
- Evidence that the product was not damaged or defective.
- Your relevant return policy and the buyer's communication about the issue.
Credit not processed or duplicate
- Proof that you already issued the refund the buyer was entitled to, with amount and date.
- The policy section showing why the buyer was not entitled to a refund, if that is your argument.
- For duplicate claims, evidence that each payment was for a separate product or order.
Policies and terms
- Include a clean screenshot of how your terms were presented at checkout, with the relevant section emphasized.
- Upload only the relevant policy section, not your entire terms of service. Stripe says issuers will not read through a full document to find the relevant part.
- Use the version of the policy that was live when the buyer ordered. If your policy has changed since, this is where versioned policies and checkout statements pay off.
Format and file rules
- Use PDF, JPEG or PNG files only.
- Keep the combined file size within 4.5 MB.
- Stay within the page limit. Stripe says limits apply and can vary by dispute, and it returns an error if your evidence exceeds the applicable limit.
- Submit one file per evidence type. Combine several items of the same type, such as multiple emails, into one multi-page file.
- Use a 12 point font or larger, US Letter or A4 pages in portrait orientation, and bold text, callouts or arrows rather than color highlighting.
- Crop screenshots to the area that matters and circle key details such as a delivery confirmation.
- Do not include links, audio or video, or requests to call or email for more information. Stripe says banks will not review external content.
Organize and explain
- Present evidence in the order events happened, so the reviewer sees a clear timeline.
- Group it by type: receipts, communications, policies, system records.
- Add a short summary of what each piece shows.
- Write the explanation in a neutral, professional tone, and say plainly why the claim does not hold and which evidence shows it. Stripe warns that a long explanation does not make a response more convincing.
- Leave out evidence that does not address the dispute reason. Stripe's example: a return policy is not relevant to a claim that the product never arrived.
- Describe products exactly as your product page and labels do. A dispute response is not the place to describe a product any differently from your storefront.
After you submit
- Expect a status of under review. Stripe says the issuer's decision can take up to 3 months, and it notifies you by email when the outcome arrives.
- If you win, the disputed amount is returned to you, along with the dispute countered fee. If you lose, the outcome is final.
- Record the outcome against the order, along with a note of what evidence you submitted. Over time this shows which records actually help.
Where the records come from
Most of this checklist depends on records you kept at the time of the order. The list in payment records to keep covers what to capture. Claddr stores buyer checks, signed attestations, holds and payments against each order, and each signature points to the exact statement text the buyer saw. You can export that record for a date range as a PDF summary and a CSV. It gives you material to work from; it does not determine whether a dispute is won.
Sources
- 01Stripe Docs: Respond to disputesdocs.stripe.com/disputes/responding
- 02Stripe Docs: Dispute evidence best practicesdocs.stripe.com/disputes/best-practices
- 03Stripe Docs: Dispute reason code categoriesdocs.stripe.com/disputes/categories
- 04Stripe Docs: How disputes workdocs.stripe.com/disputes/how-disputes-work