#frallain
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- frallain, 1 day ago, 50 messages
not related
Hi, let me help you with this.
There's other users reporting a similar issue, let me check if there's anything happening on our side...
Hey, checking in here to explain that this is the expected behaviour in this scenario:
If the collection_method is set to send_invoice, and the invoice is past its due date, the state of the subscription is set to past_due.
https://stripe.com/docs/billing/subscriptions/overview#voiding-invoice
Looks like the invoice was voided on 20/10/23 and was due on 27/10/23, which was when we transitioned to past_due
Hi! I'm taking over this thread.
The Subscription will get back to active once the latest Invoice has been paid.
I think the main question is whether you still want your customer to pay the Invoice. If not, you can mark it as uncollectible and the Subscription is supposed to go to active state, according to docs: https://stripe.com/docs/billing/subscriptions/overview#voiding-invoice
but the latest invoice has been voided, and all the other invoices are paid
@stoic marsh but now that the invoice is voided, I cannot change it
(void is a final state)
Yep, I think you need to wait for a new invoice to be generated and then paid.
OK, but our back-end code relies of the subscription status to let the customer have access to our product, and we block access when the customer is in debt i.e. subscription in past_due...
and next invoice is in 1 year,,,
This is quite inconsistent with the fact that status past_due has always meant that the customer was in debt, but here this is not the case..
The only workaround I am now thinking is to manually create an inoice and mark it as paid to have the susbcription get back to the active state... hopefully
and next invoice is in 1 year,,,
Agreed that's not great.
The only workaround I am now thinking is to manually create an inoice and mark it as paid to have the susbcription get back to the active state...
True, that could work! A few other options that come to mind:
- Add some
metadatato the subscription that says it should be considered as active - Contact Stripe support so they set that specific Subscription to
active.
Add some metadata to the subscription that says it should be considered as active
Do you mean "be considered as active in our back-end" ?
OK I see. So far we have based our own subscription entity statuses on the Stripe subscription status, but if there are more inconsistencies like that, indeed we will need to "patch" the Stripe sub status like that. I am just surprised to get in such logical status dead-end from Stripe...
Thanks for the suggestions.
Sorry about this, I agree this is not ideal.
in fact
I just created the "fake" invoice of $1 and manually marked it as paid, but still the subscription is in past_due state...
Can you share the Subscription ID (sub_xxx)?
Ah I know, I used a price that was not linked to this subscription, let me retry
MMh so in fact I would need to change the plans of this subscription with prorations enabled so that an invoice linked to this sub gets generated. This is too tricky and will mess up the UX.
I will contact the Stripe support to manually set the subscription to active then..,.
Have you tried creating a one-off Invoice linked to the Subscription? https://stripe.com/docs/api/invoices/create#create_invoice-subscription
Not sure if that would impact the Subscription status though...
No, thanks for the suggestion. I'd prefer to only do these kind of actions on the Stripe Dashboard UI, and it does not seem possible to create an invoice linked to a subscription from the Dashboard.
- if you are not sure, I'd prefer to go the stripe support way instead of juggling...
Sounds good!
thanks for diving deep on this, much appreciated