Why does a chargeback you already won sometimes come back as a pre-arbitration case?

The dispute lifecycle has more steps than most sellers realize

The version of a chargeback most sellers know is two steps: the cardholder's bank files a dispute, you respond with evidence, and Stripe reports a win or a loss. Under the card network rules that Stripe operates within, the process has more stages. After your response (often called representment), the issuer reviews it and either accepts it, in which case you win, or rejects it. If the issuer rejects it, the networks allow a further exchange, usually called pre-arbitration, where the issuer explains why your evidence was insufficient and gives you or Stripe a chance to accept liability or push the case to formal arbitration with the network itself. Related: Building a Strong Evidence Packet

That is why a win can seem to come undone. A 'won' status in Stripe means the issuer accepted your evidence or let its response window pass. It does not always mean the case is permanently closed. Within the network's time limits, the issuer can escalate with new information from the cardholder or a procedural argument. When that happens, Stripe notifies you, the funds can be debited again, and you are asked to decide whether to continue. It is uncommon compared with first-stage disputes, but it is not rare enough to ignore, and it tends to land on larger transactions where the issuer thinks the effort is worthwhile.

Keep reading: Why Most Chargebacks Are Lost, Building a Strong Evidence Packet, Understanding Chargeback Reason Codes. See how DisputeLoom helps you chargeback evidence packager for stripe sellers.

The common reasons a won dispute gets reopened

The most frequent trigger is the cardholder pushing back with something specific. Your packet said the package was delivered; the cardholder now provides a police report for a stolen package. Your packet said the signature matched; the cardholder says it is not theirs. Your packet said they never cancelled; the cardholder produces an email to your support address dated before the renewal. Issuers are more willing to escalate when the cardholder gives them a concrete rebuttal, especially one that suggests your evidence was incomplete or misleading. A second trigger is the issuer's own read that your evidence did not actually address the reason code, for example answering a not-as-described claim with delivery proof.

Procedural issues cause a share of reopenings too: evidence submitted after the network's deadline, files the issuer could not open, or a response that relied on documents the network does not accept for that reason code. Note that a cardholder filing a new dispute on the same charge under a different reason code is a different situation from pre-arbitration; that is a fresh dispute with its own deadline, and the networks limit how many times a single transaction can be disputed. Either way, the pattern is the same: the gap in the first response is what the second round is about, so the first response is where most of the prevention happens. Related: Preventing Chargebacks in the First Place

What to do when a pre-arbitration notice arrives

Read the issuer's reason for escalating before doing anything else. It almost always names the specific claim you need to answer, and answering a different one wastes your only shot. Then assess whether you can actually rebut it. If the cardholder says the signature is not theirs and you have a delivery photo showing the package at their door, provide it. If the cardholder produces a cancellation email you never saw, check your support inbox honestly; if it is there, the case is over and you should accept. Your response window at this stage is shorter than at the first stage, and Stripe will typically ask you to choose between accepting liability and providing additional evidence.

Understand what formal arbitration costs before choosing to continue. If the case goes to the card network for a ruling, the network charges fees to the losing party, and those fees are substantial enough that for a modest transaction they can exceed the amount in dispute. Stripe reviews pre-arbitration cases with that in mind and may advise or decide against proceeding when the evidence does not justify the risk. As a rule of thumb, continue only when the amount is meaningful and you hold something the cardholder's rebuttal cannot explain away. Otherwise, accept, record the outcome, and move the energy into preventing the next one. Related: What Banks Look For in Evidence

Reducing reopen risk in the first response

Most second rounds are avoidable at the first round. Answer the reason code precisely: delivery proof for not-received, product page and communication for not-as-described, consent and usage for subscriptions, identity links for fraud. Address the cardholder's own claim as stated, not a generic version of it. Prefer evidence that is hard to rebut: authenticated payments, delivery photos, timestamped activity logs, and messages in the customer's own words. Keep the narrative consistent with every exhibit; a mismatch between the email address in your summary and the one on the order is exactly the kind of gap an issuer will use. And never overstate: claiming a signature match you cannot show invites a rebuttal.

Keep every packet you submit, with the date and the Stripe dispute ID, in a place you can reach quickly. When a pre-arbitration notice arrives weeks or months later, you want the original exhibits, the issuer's reason, and the transaction record together in one view within minutes, because the window is short. Track reopened cases separately in your dispute metrics so a reversed win does not silently inflate your win rate. Finally, look at the pattern. If reopenings cluster around one product, one shipping method, or one reason code, the fix is upstream in fulfillment or checkout, not in a better second-round response. Related: Meeting Dispute Deadlines