jeff-subscription-fulfillment

[trim fog]

jeff-subscription-fulfillment

@lost heart I would use neither personally because the period end will be before their next payment and you don't want to cut someone's access exactly a second after the end of the period when their new period is starting

[lost heart]

hmm i didn’t know that thanks for pointing out, how are these cases usually handled smoothly

[trim fog]

I don't really have a good answer, it depends on many different things. Mostly I would consider the Subscription active until it's been explicitly canceled personally

[lost heart]

Okay lets say I do use status as a way to grant access to the user, if their payment method on file failed to charge for recurring payments then I believe the customer.subscription.updated event is sent with a subscription status of past_due right? So I can then revoke access.
But if a user cancelled their subscription and my cancellation is set to cancel at end of billing period, do you know if the same event is sent at the end of the billing period to indicate any kind of status change that’s not active?

[trim fog]

I would never revoke access after a failed payment, since we are going to retry multiple times and they would still pay for the full period

I'd recommend keeping access active, letting payment retries play out and then either switch back to active or automatic cancelation

[lost heart]

Hmm yea good call thanks, didn’t think of that. Do you have any idea abt what I said in regards to user cancellation? If an event is sent after customer.subscription.deleted to indicate that the billing period is over.

[trim fog]

the customer.subscription.deleted Event is sent when the Subscription is really canceled so that's what you'd use to clean up your record in your database