billing.invoice_paid
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.paidandinvoice.payment_succeededonto this event. De-duplicate ondata.invoice_id. - Recovery is not driven by this event.
past_due_since,locked_atand the warning stamps are cleared when Stripe reports the subscription back atactive/trialingoncustomer.subscription.updated, which emits nobilling.*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.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
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
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.
How is this guide?
Last updated on