Refund

A refund returns money from a completed payment back to the customer, sent to their original payment method. It reverses a charge you already accepted — either the full amount or a partial refund — because of a return, a cancellation, an error, or goodwill.

How a refund works

You initiate a refund against a captured charge. Stripe returns the funds to the customer's card or bank, and Stripe emits the charge.refunded event so downstream systems know it happened. Processing fees on the original payment are generally not returned to you, so a refund costs you the transaction amount plus those sunk fees.

A refund is not the same as a chargeback. A refund is something you choose to do; a chargeback is forced by the customer's bank and carries a dispute fee. Refunding promptly is often the cheaper path — it can head off a dispute before it's filed.

Refunds vs. disputes

• Refund — you send money back voluntarily. No dispute fee, no hit to your dispute ratio.
• Dispute — the customer goes to their bank. You face a dispute, a fee, and a possible reversal whether or not you agree.

This is why making refunds easy to request matters: a customer who can get their money back from you has no reason to call their bank.

Why it matters

Refunds directly reduce your net revenue and, for subscriptions, can signal churn risk. Watching refunds as they happen — rather than discovering them at month-end — lets you catch a spike, spot a broken product or pricing bug early, and follow up with the customer while the reason is fresh.

Refunds in ChargeBell

ChargeBell posts a Slack alert the moment a refund is sent, so your team sees returned money in real time instead of finding it later in a Stripe report.