dantheman

[winged stirrup]

that event only fires for the first payment on a subscription. For each subsequent payment you should listen for the invoice.paid event

[inland orchid]

ok and is invoice.paid on all invoices

including subscriptions?

[winged stirrup]

Yes. Each Subscription will have an Invoice which must be paid for the subscription to remain active

[inland orchid]

whats the difference between invoice.paid and invoice.payment_succeeded?

[winged stirrup]

invoice.payment_succeeded could fire for partial payments and also wouldn't capture any out-of-band payments. invoice.paid will fire if the invoice is paid in full

[inland orchid]

ok and how would i link the invoice to the subscription?

oh is there a subscription in the object?

[winged stirrup]

Yup! Invoices have a subscription attribute: https://stripe.com/docs/api/invoices/object#invoice_object-subscription

[inland orchid]

and if im using checkouts how would i get some kind of id from the invoice to the session

[winged stirrup]

You would have to get the Invoice ID from the Checkout Session by listening to checkout.session.completed : https://stripe.com/docs/api/checkout/sessions/object#checkout_session_object-invoice

[inland orchid]

perfect, thanks you so much!

[winged stirrup]

Of course!

[inland orchid]

wait would the
checkout.session.completed be triggered before the invoice.paid?

cause i saw somewhere that its never guarenteed

[winged stirrup]

The ordering is never guaranteed, that's correct

[inland orchid]

thats gunna be difficult

[winged stirrup]

You could always build in a sleep statement to the checkout.session.completed webhook handler in order to guarantee that your system actions invoice.paid first. That's one idea for simplifying, but obvs it may not work for your use-case

[inland orchid]

that seems kinda rough i will see what i can do

[winged stirrup]

Yeah, it's not ideal as a the long-term solution. Anyway, best of luck! Let us know if we can help some more

[inland orchid]

👍 appreciate it