An invoice is paid in full.
When this fires
The creator's tier invoice is paid in full and the account is marked current.
Caveats
- Expect two deliveries per payment. Subscriby maps both Stripe invoice.paid and invoice.payment_succeeded onto this event. De-duplicate on data.invoice_id.
- Recovery is not driven by this event. past_due_since, locked_at and the warning stamps are cleared when Stripe reports the subscription back at active/trialing on customer.subscription.updated, which emits no billing.* event of its own, so a consumer tracking lock state should treat this event as a hint, not the unlock signal.
- A creator's lockdown never suspends their subscribers' billing (only new signups are blocked), so there is nothing to resume here.
Related events
- billing.invoice_created: predecessor.
- billing.payment_failed: alternative outcome.
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.