#coder99
1 messages · Page 1 of 1 (latest)
You can look at the previous_attributes fields, and compare a few scenario to see how they are different
i got these two attributes, both come with customer.subscription.updated`
The right side is subscription renewal
left side seems to be some changes on cancelling schedule
okay, also i am not sure which events should i process on subscription update
the invoice payment succeeded comes in both cases
when the subscription created (new)
when the subscription renewed (update)
so the question is, is there a way to differenciate the invoice payment succeeded in order to handle update properly ?
Okie, in its content is it an Invoice?
In invoice payment succeeded context?
yes, in JSON, there is an invoice object
is there a flag on invoice that identifies that it is a new or update subscription ?
?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yep that one
great ! thanks mate !
@agile jasper or @whole spear one last question, so if i can distinguish new/update subscription requests from billing_reason
with subscription_create or subscription_cycle this means that customer.subscription.updated event is redundant for this exact purpose. correct ?