#Rob.Clayton
agile salmon
past pilot
Do you mean "roll over" as the subscription entering the next billing cycle, i.e. change in current start date and current end date to next billing cycle?
If so, you may look for customer.subscription.updated event. To test this, test clock can be used to advance subscription to the next billing cycle: https://stripe.com/docs/billing/testing/test-clocks
fringe gulch
Thanks river!
Yes, that's exactly what I mean.
I'll run the test as you suggest, but just as a heads up for me, does the updated event for subscription entering the next billing cycle get triggered some time before the day of the beginning of the next cycle ... or exctly at midnight on the previous day?
past pilot
The event will be triggered after the end date of current cycle. current_end_date is an epoch timestamp
fringe gulch
How long after the end date will the customer.subscription.updated be triggered?
Just because we have the end dates stored locally, I need to ensure that the way we monitor if our customers have a current subscription or not is updated in a timely fashion so they are not locked out when the subscription moves into the next cycle.
past pilot
Stripe doesn't provide ETA about how long will the event be sent after the current cycle ends. It can be seconds up to minutes