Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
To win a Stripe chargeback, send evidence that answers the dispute reason and ties the payment to the order. For fraud, show who made the purchase. For non-receipt, show delivery. For a subscription, show the cancel terms and dates. The cardholder’s bank decides, and no packet guarantees a win.
Written by Chargeflow Experts. Updated 12 November 2026.
| Allegation | Relevant Records | Question to Answer |
|---|---|---|
| Unauthorized payment | Authentication results and past orders on the same card. | What proves the cardholder made this purchase? |
| Not received | Carrier delivery or digital access records. | How does the record tie to this order? |
| Duplicate charge | Separate order and payment records, or a refund. | Were these two purchases, or a fixed error? |
| Canceled subscription | Agreement, cancel request, and billing dates. | Did the charge come before the cancel took effect? |
| Not as described | The listing at purchase, plus delivery or service records. | How do the records answer the claimed difference? |
Stripe’s dispute-category guidance lists what to send for each reason. Use this table as a starting map, not a full network checklist.
Good Stripe dispute evidence is short and on point. For the wider case workflow, see the Stripe dispute process, fees and deadlines next to this checklist.
Stripe sorts hundreds of network chargeback reason codes into a few categories. The Stripe chargeback reason code from the network shows on the dispute object, so you can see both. Use the category to pick evidence and the code to check network rules.
| Stripe category | Visa codes | Mastercard codes | Evidence that wins |
|---|---|---|---|
| Fraudulent | 10.1 to 10.5 | 4837, 4849, 4870, 4871 | Proof the cardholder bought it: CE 3.0 history, 3D Secure, AVS and CVC, purchase IP |
| Product not received | 13.1 | 4855 | Delivery to the full address, or an access log after payment |
| Product unacceptable | 13.3, 13.4, 13.5 | 4853 | The listing as shown at purchase, delivery condition, and the return policy |
| Subscription canceled | 13.2 | 4841 | Cancel policy, where the buyer saw it, and the billing and cancel dates |
| Credit not processed | 13.6, 13.7 | 4860 | The refund record, or the policy showing no refund was owed |
| Duplicate | 12.6.1, 12.6.2 | 4834 | Both receipts and both charge IDs, showing two separate orders |
| Unrecognized | None | 6321, 4863 | Customer name, email, purchase IP, and proof of delivery or use |
| General | 11.x and other 12.x codes | 4808 and others | Contact the customer first; Stripe says these are rare for cards |
Source: Stripe’s reason code categories. For full code lists, see our guides to Visa chargeback reason codes and Mastercard chargeback reason codes.
Collection and final submission are separate
Check the case before the final Stripe send
Current case and requested fields
Open the dispute details, read the bank’s claim, and note the due date, usually 7 to 21 days out. Fill in the fields Stripe asks for. Gather evidence first and submit last.
Final response and confirmation
Stripe’s response instructions say a sent response is final and cannot be added to. Check the full response before you send it, and keep the confirmation.
Explain what the record actually establishes
Combine accurate meaning with readable files
Verification and communication limits
A CVC match shows the card details passed a check. It does not prove the buyer held the card. Customer emails show what was said, not who said it. Call records or transcripts can help when you collected them properly.
Readable purchase-time evidence
Send readable files, not links to outside documents. Keep the listing and terms from the time of purchase. Stripe takes PDF, JPEG, or PNG files up to 4.5 MB in total. See its evidence best practices.
Check whether the payment used 3D Secure or qualifies for Visa CE 3.0, as shown below. Neither applies to every payment or complaint. After you submit, the case shows as under review until the bank decides, usually within 60 to 75 days.
Use digital-goods proof, the evidence-panel guide, and dispute-outcome diagnosis. Our representment guide covers the wider process.
Chargeflow’s Stripe integration and chargeback recovery workflow can build these packets for you.
Fraud is the most common dispute type. Stripe says fraud claims make up over half of all disputes, and many are friendly fraud from real customers. Two defenses carry the most weight.
Visa Compelling Evidence 3.0 applies to Visa reason code 10.4 (card-absent fraud). You qualify when all of these are true:
Stripe checks your history for you. When a dispute qualifies, it says so in the Dashboard and email, adds the past payments, and pre-fills the fields.
Sample check (made-up dates): a customer disputes a payment from 20 September 2026. Earlier orders from 10 January (253 days before) and 2 March (202 days before) used the same device and login, so they count. An order from 1 August (50 days before) is too recent to count.
3D Secure liability shift: if the payment was authenticated with 3D Secure, Stripe adds the result, such as the ECI code, to your evidence. You may still get a dispute, so add your own records on top.
| Illustrative allegation | Relevant packet | Field examples |
|---|---|---|
| Digital course not received | The link between payment and course, access events, failed access or use, and support history. | product_description; access_activity_log; receipt; customer_communication. |
| Two charges for one purchase | Both payment IDs, proof of separate orders or the fix, and refund dates. | duplicate_charge_id; duplicate_charge_documentation; duplicate_charge_explanation. |
Pick fields based on the real case and Stripe’s evidence field reference. For a Visa fraud claim that qualifies, follow Stripe’s current CE 3.0 requirements. A delivery packet is not a fraud defense.
Check every record before the final send: Stripe says a sent response cannot be edited or added to. Use the chargeback evidence source map to close record gaps first.
The cardholder’s bank, called the issuer, decides a Stripe chargeback under card network rules. Stripe passes your evidence along and reports the result. The bank usually decides within 60 to 75 days.
No. Stripe says a submitted dispute response cannot be edited or added to. Put every record in before you submit, and combine files of the same type into one file.
No. AVS and CVC matches do not guarantee a win or prove who made the purchase. For Visa fraud claims, they work best next to CE 3.0 history or 3D Secure data.
To win a Stripe dispute, answer the exact reason with evidence tied to the payment, submit before the due date, and keep it short. For fraud claims, Visa CE 3.0 eligibility or 3D Secure authentication gives you the strongest case.
When a chargeback arrives, Stripe takes the disputed amount plus a USD 15 dispute fee (in the US) from your balance and tells you by email and in the Dashboard. You then have 7 to 21 days to accept or counter, and the bank decides.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Track dispute performance across multiple accounts with clear rate definitions, a reconciled case register, weighted win rates, net recovery after fees, and a fixed report schedule.
Standardize chargeback evidence with one core record set, a module for each dispute category, a fixed file format, and a check that each response was sent.
Align customer support and payments with a shared case record, complaint-to-dispute playbook, refund and dispute overlap rules, and subscription habits that cut disputes.
Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..
Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.
Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.
Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.
Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.