#Eranga-Subscription
1 messages · Page 1 of 1 (latest)
I assume that billing cycle change would caused by our own API call, right? So handling those changes based on the call itself, and handling the "automatic" status change by listening to this event <-- Will this solve your issue?
The problem is, since this is event driven we don't know whether it changed as a result of our API call or it actually transitioned from trialing to active
You should always rely on the latest state, which is come with this event. It will be a Subscription object. You would want to examine that latest object to decide what to do with the Subscription
Yeah, I understand. So just by the event we can't determine the cause for the trigger, right?
We have to keep the status of the subscription on our end to cross-check with the latest state of the new subscription. Then examine what changed
yeah