Connect, collect, transform, visualise, and interact with your Industrial Data in a single platform. Use FlowFuse to manage, scale and secure your Node-RED solutions.
We currently configure Stripe to cancel a user's subscription after a number of failed payments. That leaves us in the position that if they then setup a new subscription for the team, all existing debts are forgotten.
Stripe puts the subscription into the unpaid state before this happens - something we don't track.
We should:
modify our subscription handling to not cancel the subscription when it goes unpaid.
track the unpaid state and take appropriate action.
That could be to prevent the user from doing anything billable in the platform until they pay their bills.
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
Bumping this issue into my queue as questions have been asked around our handling of unpaid subscriptions. Need to revisit the general area to see what makes sense - so starting with a research/design phase.
Description
This is a follow-up to https://github.com/flowforge/flowforge/issues/1878, raising as its own task for planning purposes.
We currently configure Stripe to cancel a user's subscription after a number of failed payments. That leaves us in the position that if they then setup a new subscription for the team, all existing debts are forgotten.
Stripe puts the subscription into the
unpaid
state before this happens - something we don't track.We should:
Epic/Story
No response
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate