Stripe Dispute

Dispute, chargeback, and refund are not interchangeable

People use all three words for the same event, which is how the accounting goes wrong.

A refund is a payment you reverse voluntarily. You keep control of the timing, there is no penalty fee, and the original sale and its reversal are both ordinary events in your books.

A chargeback is a forced reversal at the card network. Stripe uses dispute and chargeback for the same thing: "A dispute (also known as a chargeback) occurs when a cardholder questions your payment with their card issuer." The money leaves before the merits are considered, and a fee comes with it.

An inquiry sits before a chargeback and is genuinely different. Stripe calls it "a preliminary phase before creating a formal dispute," notes that American Express and Discover are the networks that most often use it, and that Mastercard and Visa no longer do. The reason it matters financially: at the inquiry stage you can resolve the case without incurring a dispute fee, either by providing satisfactory evidence or by issuing a full refund. Once it escalates to a chargeback, the fee is already committed.

What Stripe debits, and when it gives it back

The Dispute object records the money movement in a field that tells the whole story. Stripe defines balance_transactions as a "list of zero, one, or two balance transactions that show funds withdrawn and reinstated to your Stripe account as a result of this dispute." Zero, one, or two. One if the money only ever left. Two if you won and it came back.

The disputed amount is "usually the amount of the charge, but it can differ," per Stripe, because of currency fluctuation or because only part of the order is disputed. The fee is separate and lands at the start: "the fee for receiving a dispute is deducted from your account balance when a cardholder initiates a dispute."

If you win, "the issuer returns the debited chargeback amount to Stripe" and "Stripe passes this amount back to you." Stripe also returns the dispute countered fee. It does not return the dispute received fee, and says so directly: "unless otherwise stated in your Stripe contract, we never return the dispute received fee."

If you lose, Stripe’s framing is that "no money moves from your perspective," because it already credited the issuer when the chargeback was initiated. Losing is not a second debit. It is the first one becoming permanent.

The practical consequence for your books is that winning a dispute does not restore you to where you started. You get the sale back and you are still down a fee.

Status, reason, and the evidence window

A dispute carries a status that moves through the process. Stripe documents warning_needs_response, warning_under_review, and warning_closed for the inquiry stage, then needs_response, under_review, won, and lost for the formal stage, plus prevented for a dispute stopped before becoming a formal chargeback.

The reason field is "the reason given by cardholder for dispute," and the documented values are worth reading once, because they are the cardholder’s claim rather than your assessment: bank_cannot_process, check_returned, credit_not_processed, customer_initiated, debit_not_authorized, duplicate, fraudulent, general, incorrect_account_details, insufficient_funds, noncompliant, product_not_received, product_unacceptable, subscription_canceled, and unrecognized.

Two details in evidence_details set the pace. The due_by field is the "date by which evidence must be submitted in order to successfully challenge dispute," and Stripe notes it "will be 0 if the customer’s bank or credit card company doesn’t allow a response for this particular dispute," meaning some disputes cannot be contested at all. And submission_count comes with a warning: "typically, you may only submit evidence once." There is usually no second attempt after a rushed one.