#dicbra
1 messages · Page 1 of 1 (latest)
Seems expected given that the status field will likely change between creation and if/when payment succeeds (i.e. transitions to active)
What specifically are you tracking?
I'm creating two different subscriptions. One will be a flat fee monthly subscription where I can switch plans through the customer portal, and the other subscription will be a metered usage subscription for that pricing model. So, I need to be able to listen for plan switches on the first subscription and update the price on the second subscription for metered usage.
Hmm, is there a requirement for 2 separate Subscriptions? As I understand it you could run that model on 1: https://stripe.com/docs/products-prices/pricing-models#flat-rate-metered-usage
I would like to be able to do that, but then my customer portal won't work.
Fair. Yeah there's no easy way to differentiate the .updated event unfortunately
I guess my recommendation would be to check the previous_attributes hash on the event(s)
Because on creation the .updated event should go from default_incomplete (or similar) to active
Where as that wouldn't happen after an upgrade/downgrade