Fight a chargeback only when the claim appears invalid, the case can be challenged, relevant evidence can be submitted on time, and the expected incremental value is positive. Accept it when the claim is valid or the best-case economics are negative. Escalate cases whose reasonable value range crosses zero.
Start with the fight-or-accept formula
Compare challenging with accepting from this moment forward. Do not add a dispute-received fee, product cost, shipping cost, or labor already incurred merely because it appears in the full loss ledger. A cost that is the same under both choices is sunk for this decision.
- R — recoverable value: the amount the case system says can return if the challenge succeeds. Do not assume every fee or cost is recoverable.
- P — evidence-based outcome range: a low and high probability grounded in your own mature, comparable cases—not a provider headline or a portfolio-wide win rate.
- D — deadline readiness: an internal factor from 0 to 1 for completing review and submission before the actual portal cutoff. Use 0 when the response right or deadline has ended.
- H — remaining handling cost: analyst and reviewer hours still required, multiplied by fully loaded hourly cost.
- F(x) — expected incremental challenge fees: follow the current platform and contract. A fee charged only on challenge and returned on a win becomes fee × (1 − x); a nonrefundable fee stays at its full amount.
Stripe currently distinguishes a dispute-received fee from a dispute-countered fee and documents regional exceptions. That is one platform model, not a universal fee rule. Enter zero when your contract has no incremental challenge fee, and verify whether any fee is returned before modeling it.
Use a range, not a single win-rate guess
First group settled cases by factors that actually change the response: processor, network, reason, product type, region, and evidence pattern. Use only mature outcomes with a consistent denominator. Set a low and high range from that comparable set, then document why this case belongs inside or outside it.
| Case signal | Decision treatment | Guardrail |
|---|---|---|
| Claim appears valid | Accept | Do not manufacture a contradiction or submit irrelevant volume. |
| Reason-matched records directly contradict the claim | Use the comparable-case range | Strong evidence still does not guarantee an issuer decision. |
| Records show fulfillment but not authorization | Lower the fraud-case range | Delivery or use does not establish who authorized payment by itself. |
| Required record is missing or illegible | Lower the range or accept | Do not substitute an internal score for the requested proof. |
| No response right or deadline has passed | Set D to 0 | The live case system and processor instructions control. |
If you do not have enough comparable cases, do not invent P. Calculate the break-even probability instead, and ask whether the available evidence supports confidence above that threshold. Keep the answer as a documented judgment until mature internal data exists.
Worked example: a range that supports challenging
This hypothetical case has $320 of recoverable value. The team assigns a 35% to 55% evidence-based range from comparable mature cases and a 0.90 deadline-readiness factor. Forty minutes of remaining work at a fully loaded $36 per hour costs $24. The example assumes a $15 incremental counter fee that is returned on a win. These figures are illustrative inputs—not a provider price, benchmark, or expected performance claim.
Low case: ($320 × 0.35 × 0.90) − $24 − [$15 × (1 − 0.35 × 0.90)] = $66.53. High case: ($320 × 0.55 × 0.90) − $24 − [$15 × (1 − 0.55 × 0.90)] = $126.83. Both ends are positive, so the economics support challenging if the claim is invalid and the case is eligible.
With a challenge fee returned on a win, the evidence-based break-even probability is (H + fee) ÷ [D × (R + fee)]. Here that is $39 ÷ (0.90 × $335) = 12.9%. If the fee is never returned, use (H + fee) ÷ (D × R), which is 13.5% for these illustrative inputs.
Apply the three-way decision rule
The claim is valid, the case cannot be challenged, D is zero, or even the high expected-value case is negative.
The claim appears invalid, relevant evidence is ready, and both the low and high expected-value cases are positive.
The range crosses zero, a required fact is unresolved, or a non-economic consideration requires an authorized decision.
Save the inputs, choice, owner, submission confirmation, and mature outcome so the next range improves.
Run five gates before using the formula
- Validity: read the issuer claim and case reason. If the customer was owed the disputed amount, accept rather than treating representment as a collection tactic.
- Eligibility: confirm that the case can be challenged. Stripe notes that some disputes cannot be challenged; processor and payment-method rules vary.
- Evidence: identify the records that directly answer this claim. Adyen states that requirements vary by reason and that meeting them does not guarantee a win.
- Deadline: use the case-specific date and an internal review buffer. Stripe and Shopify describe usual 7-to-21-day windows, while Adyen publishes flow- and region-specific timeframes. None of those ranges overrides the date in your portal.
- Economics: calculate both ends of the range using only value and cost that change between accepting and challenging.
Do not treat customer withdrawal as a completed win
A customer may tell the issuer they no longer dispute the transaction, but the merchant still needs to follow the formal case workflow. Stripe specifically advises submitting evidence even after a withdrawal and says the network rules do not allow evidence after the deadline. Keep the withdrawal record, but do not close the internal case until the platform shows a final outcome.
If the case reopens, make a new decision
The formula above decides whether to build the first response. If the issuer or provider renews the case after reviewing that response, do not treat the original decision as approval to continue automatically. Use the chargeback pre-arbitration decision guide to confirm that a merchant action exists, compare the renewed claim with the original packet, and model only the cost and risk that change at the reopened stage. The live case workflow still controls whether the available action is to respond, accept, decline, contact the provider, or stop.
What this framework leaves out
The cardholder's issuer or the applicable dispute process—not this model, the processor, or a service provider—controls the outcome. Visa advises merchants to respond swiftly and to work through their acquirer or processor. Mastercard and platform documentation show that reason-specific rights and supporting documents differ.
The formula also excludes effects that are real but not reliably attributable to one response: monitoring status, reserves, customer lifetime value, precedent, and future fraud. Add one only when finance or risk has an approved, case-level method. Winning a dispute should not be assumed to erase the dispute from a network or processor count.
Once the decision is to challenge, use the reason-specific chargeback evidence checklist. If the event might still be handled before a formal dispute, compare alerts and representment. To reconcile the loss already incurred regardless of this decision, use the true chargeback cost formula.
Challenge only an invalid claim with an eligible, on-time, reason-matched response and positive case economics. Keep the range, assumptions, and final outcome so judgment becomes measurable over time.