Stripe event: charge.dispute.closed, update your books for won, lost, or warning_closed

TL;DR

Log it, keep the customer flagged, no bookkeeping change needed.

Steps

1. The dispute is over. Read data.object.status: won, lost, or warning_closed.
2. won: the disputed funds return to your balance (the fee does not). Mark the order paid again and close your tracker case.
3. lost: the funds stay with the customer. Mark the order as lost to dispute, write off the amount plus fee, and note the reason on the customer record. If the reason was fraudulent, consider whether this customer should be blocked.
4. warning_closed: no money moved and none will. This was an early fraud warning. Log it, keep the customer flagged, no bookkeeping change needed.
5. Return 200.
6. Only handling charge.dispute.created and never closing the loop. Your dispute tracker fills with stale open cases and your revenue numbers stay wrong. The other trap: treating lost like a refund in your analytics. A lost dispute is not a refund; it is fraud or dissatisfaction, and it belongs in a different bucket when you review churn.
7. - Match the closed dispute to the open case by dispute id, not by charge id. One charge can theoretically see multiple disputes over time.

• If you submit evidence and hear nothing for weeks, that is normal. The closed event is the resolution; do not poll.

When to use

You are seeing this: Read data.object.status: won, lost, or warning\closed. Use this skill when you run into "Stripe event: charge.dispute.closed, update your books for won, lost, or warningclosed".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Stripe's event reference says charge.dispute.closed occurs when a dispute is closed and the dispute status changes to lost, warning_closed, or won. Verified live at https://docs.stripe.com/api/events/types.