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

charge.dispute.closed: reconcile the outcome

The dispute is over. Read data.object.status: won, lost, or warning_closed.

What to do on receipt

1. won: the disputed funds return to your balance (the fee does not). Mark the order paid again and close your tracker case.
2. 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.
3. warning_closed: no money moved and none will. This was an early fraud warning. Log it, keep the customer flagged, no bookkeeping change needed.
4. Return 200.

The trap

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.

Checklist

• 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.

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.