Which event signals that a refund has occurred on a charge?

Which event signals that a refund has occurred on a charge?

• A. charge.refunded
• B. charge.dispute.created
• C. payment_intent.succeeded
• D. balance.available

Answer: (A)

The event that signals a refund has occurred on a charge is charge.refunded. When you issue a refund, Stripe emits this event to notify your system that money has been returned for that specific charge. The charge object in the event shows that refunds have taken place (for example, amount_refunded will reflect how much was returned, and refunded indicates the refund status). This applies whether the refund is full or partial, making it the definitive signal that a refund action has happened. The other events correspond to different situations. A dispute.created event happens when a customer challenges a charge through a dispute or chargeback, not when a refund occurs. A payment_intent.succeeded event indicates a payment completed successfully, with no automatic implication of refunds. balance.available is simply a ledger update about available funds and isn’t specifically tied to refunds.

The event that signals a refund has occurred on a charge is charge.refunded. When you issue a refund, Stripe emits this event to notify your system that money has been returned for that specific charge. The charge object in the event shows that refunds have taken place (for example, amount_refunded will reflect how much was returned, and refunded indicates the refund status). This applies whether the refund is full or partial, making it the definitive signal that a refund action has happened.

The other events correspond to different situations. A dispute.created event happens when a customer challenges a charge through a dispute or chargeback, not when a refund occurs. A payment_intent.succeeded event indicates a payment completed successfully, with no automatic implication of refunds. balance.available is simply a ledger update about available funds and isn’t specifically tied to refunds.