A specific charge is refunded, fully or partially.
When this fires
A per-payment refund settles. Pairs with subscription.refunded when the refund covers the entire subscription.
Settled refunds only. A refund a provider has queued but not yet paid out raises nothing; access is never revoked for money that has not actually moved.
Caveats
- Emitted by Stripe, PayPal, Paystack, Razorpay and Skrill. CoinPayments and CeyPay expose no refund notification.
- Raised for partial refunds as well as full ones. Read full_refund to tell them apart; a partial refund leaves the subscription and its access untouched.
- Stripe reports a running total across refunds; the amount here is this refund, not the cumulative figure.
- Distinct from subscription.refunded, which represents the subscription's reaction. A refund may emit only payment.refunded if the subscription itself is unaffected.
- Partial refunds are represented by amount being less than the original charge.
Related events
- payment.succeeded: predecessor.
- subscription.refunded: subscription-level analogue.
Headers
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.