#arggh-subscriptions
1 messages ยท Page 1 of 1 (latest)
it does yes, at the end of one cycle, an invoice is generated, and the current_period_*s change, the period doesn't wait for the invoice to be paid
Ok, thank you ๐ ๐
I assume that current_period_* s change also when the subscription is in unpaid state?
I'm trying to figure out
a) correct way to mark paid services as active in our own DB
b) the trigger when to actually cut off the service from customers who don't pay
...and it seems active-status can be just the copied current_period_end value (+ some threshold), and the cut-off-trigger can be the subscription being canceled (either by the user or admin), so we can investigate before any consequences to the customer.
I wonder if that sounds reasonable?
the period is not influenced by the status becoming unpaid โ it's generally like, the period starts and an invoice is created. If the payment of that invoice fails, it's retried a few times depending on your settings to give the customer some grace time. When that's all complete, the subscription could move to unpaid
so I think the answer in both cases is overall to listen for the customer.subscription.updated webhook event for when the status has changed to unpaid