#qwerty-subscription-status
blazing loom
sand lintel
but if it does require addational steps and the status is incomplete - will the next even be subscription.updated?
magic nexus
yes the next one would be customer.subscription.updated
sand lintel
Is there something I need to worry about differinty and detecting or just making sure the plan matches the one they have and the status matches in our db
if we are not allowing users to change plans at this stage
magic nexus
I would say no but really in the customer.subscription.updated you're going to get the previous_attributes property that exposes everything that changed in that Event. So if the items hash is there it means something changed in it
sand lintel
right perfect, thank you so much