#twiddlecoding
1 messages · Page 1 of 1 (latest)
Can you share the subscription ID (sub_xxx) of the scenario you described?
Where did you see that the subscription has ended? The subscription is still active and will only end at current billing cycle ends. The invoices have all made successfully, so the subscription wouldn't be in past_due status
The subscription got a new current_end_date before the invoice was paid
To me that is unexpected behaviors
Which specific event ID (evt_xxx) that your system listened and the field that you're looking at? current_end_date isnt' a field in Subscription object ?
evt_1OmN5XG0R9s4x2g4uNByGel8
as you can see, this subscription update prolongs the current_period_end, but at that point, no payment had been made
Maybe you could point me to a guide on how and when to provision access with a subscription service
I think I read somewhere in your docs that I should look at the invoice.paid webhook when provisioning access. But I can't find it anymore. Maybe you have changed the recommended way.
Thats how I have done my implementation
To be clear, this is expected. The subscription will update and transition to the next billing period irregardless of whether the invoice is paid (hence why you track status via the invoice.paid events)
I see
What if I want to provide the user access to their subscription features until their subscription status is canceled?
Like, if their payment has failed or if, like in this case, they need to update some payment details
They still expect access to their subscription
Then provision access based on the status field on the subscription and only remove it when you get customer.subscription.deleted event
Are there downsides to using that approach compared to the timestamp approach that you recommend in the docs?
Yeah, they'd have access to your service/product even if they have unpaid invoices and the subscription is past_due
In that case, you'd just send them to the customer portal
I see