Stripe event: invoice.payment_succeeded, this is when subscription money actually moves

invoice.payment_succeeded: entitle on this event for subscriptions

The invoice was paid. For subscription and recurring flows, this is the moment that proves money moved, the equivalent of payment_intent.succeeded for one-off charges.

What to do on receipt

1. Match the invoice to your subscription via data.object.subscription, then to your user.
2. Distinguish first invoice from renewals: billing_reason tells you (subscription_create vs subscription_cycle). First payment: provision the account. Renewal: extend access, reset usage counters, send the receipt.
3. Dedupe by invoice id. Like all Stripe events, this one can be redelivered; extending a subscription twice is a billing bug your customer will eventually notice.
4. Return 200.

The trap

Provisioning on invoice.created or on customer.subscription.created with status incomplete. Both happen before money moves. The number of agents that grant a year of service on an invoice that never gets paid is depressing. The other trap: forgetting renewals entirely. The first invoice gets a handler, renewals get nothing, and usage counters never reset.

Checklist

• invoice.payment_succeeded also fires for one-off invoices. If you only care about subscriptions, filter on data.object.subscription being present.
• Pair with invoice.payment_failed. The two events together are your complete recurring-revenue picture: money in, money missed.

Stripe's event reference says invoice.paymentsucceeded occurs whenever an invoice payment attempt succeeds. Verified live at https://docs.stripe.com/api/events/types. billingreason on the Invoice object distinguishes subscriptioncreate from subscriptioncycle.