Payment succeeded
Fires when a payment succeeds: when Stripe collects an invoice, when you record a posted payment with Record a payment, or when an invoice is marked paid in the dashboard. A credit or zero-total invoice settled as it's posted, or reported paid by Stripe with nothing paid by card (such as one it settled from the customer's Stripe balance), has no payment and doesn't send this event. data.payment is the payment, as Get a payment returns it, with status: posted.
Headers
- Type: stringX
- Webhook - Signature requiredt=<timestamp>,s=<signature>.tis when the delivery was signed, in Unix milliseconds; each attempt is signed afresh, so a retry has a newt.sis the Base64 (standard alphabet, padded) HMAC-SHA256 of the string<t>.<raw request body>, keyed with your signing secret: the wholewhsec_…string as UTF-8. To verify, recompute it over the raw body exactly as received and compare in constant time, then reject attoo far from now (5 minutes is a good limit) so an old delivery can't be replayed.scan end in=, so split each part on its first=only.
Body
Every delivery's body.
- Type:datarequiredProperties: 1
The event's payload, under the key the event names.
- enumeventconst:billing-payment-succeededrequired
A billing event you can receive.
billing-invoice-paid,billing-invoice-posted,billing-invoice-refunded,billing-checkout-created,billing-checkout-completed,billing-checkout-expired,billing-payment-succeeded,billing-payment-failed,billing-credits-depleted,billing-overage-incurredandbilling-credit-cap-reached; each is described in the Webhooks section.values- billing
-invoice -paid - billing
-invoice -posted - billing
-invoice -refunded - billing
-checkout -created - billing
-checkout -completed - billing
-checkout -expired - billing
-payment -succeeded - billing
-payment -failed - billing
-credits -depleted - billing
-overage -incurred - billing
-credit -cap -reached
- billing
- Type: stringidrequired
The delivery's ID (
whd_…), the same on every retry of it: keep the IDs you've handled and ignore a delivery whose ID you've seen. A test delivery has an ID of its own. - Type: booleanis
Test requiredtruefor a delivery sent with Send a test delivery, whosedatais placeholder;falseotherwise. - Type: stringFormat: date-timetimestamprequired
When the event happened, and the delivery was first queued; the same on every retry.
Responses
- 200
Return any 2xx to acknowledge. Any other status, a redirect (redirects aren't followed), or no answer within 5 seconds is a failed attempt, recorded in the webhook's
lastStatus. A failed delivery is retried 1 minute, 5 minutes, 30 minutes, 2 hours and then 12 hours after each failed attempt in turn (retries are sent by a sweep that runs every minute, so each can be up to a minute later), and dropped after the sixth failed attempt. A retry carries the sameidandtimestampand goes to the webhook's current URL; a delivery whose webhook has since been switched off is dropped. Because of retries, an event can arrive more than once or after a later one: useidto ignore repeats. The response body is ignored.
{
"id": "whd_Fk9Vn1Yb5Lx3Gm7T",
"event": "billing-payment-succeeded",
"timestamp": "2026-11-03T14:06:49.377Z",
"isTest": false,
"data": {
"payment": {
"id": "pay_F2HpDLr2UuqAUC8k",
"number": 43,
"customerId": "cus_Z8rT3nW6yP0aJc5E",
"invoiceId": "inv_dmdae6RsVMaW7T5I",
"orderId": "ord_2Lp9Xc4Vb7Nm1Qz6",
"amount": 10692,
"allocatedAmount": 10692,
"balance": 0,
"currency": "USD",
"paymentDate": "2026-11-03T14:06:49.362Z",
"paymentType": "creditCard",
"status": "posted",
"metadata": null,
"createdAt": "2026-11-03T14:06:49.362Z",
"updatedAt": "2026-11-03T14:06:49.362Z"
}
}
}