Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Billing: Failed Payments should not immediately cancel Stripe Subscriptions #8166

Closed
tghanken opened this issue May 5, 2023 · 1 comment · Fixed by #8285
Closed

Billing: Failed Payments should not immediately cancel Stripe Subscriptions #8166

tghanken opened this issue May 5, 2023 · 1 comment · Fixed by #8285
Assignees
Labels
bug p2 Needs to be addressed on a reasonable timescale

Comments

@tghanken
Copy link
Contributor

tghanken commented May 5, 2023

Issue - Bug

Currently, failed payments for Team subscriptions automatically cancel the Stripe subscription. This can lead to some unexpected billing behavior, such as unpaid balances failing to carry forward, as seen here 🔒. Instead of automatically cancelling the subscriptions, we should allow them to go "Past Due", and allow users to change their payment information on the original subscription.

Acceptance Criteria (optional)

  • Allow payments to fail without the subscription being automatically cancelled for previously stable subscriptions
  • Changing payment information retries billing on failed invoices
  • Continue to ensure new Team subscriptions cannot be created without a valid form of payment

Estimated effort: 1 hour to triage. More if root cause is already identified.

@tghanken tghanken added bug p1 Needs to be addressed fast. Such an issue significantly impacts the majority of users labels May 5, 2023
@github-project-automation github-project-automation bot moved this to To Prioritize in Sprint Board Beta May 12, 2023
@nickoferrall nickoferrall added p2 Needs to be addressed on a reasonable timescale and removed p1 Needs to be addressed fast. Such an issue significantly impacts the majority of users labels May 16, 2023
@drewhousman1010
Copy link

A Team plan customer 🔒 just had this happen to them.

When they got locked out they saw the original lock message from when I was working their deal, which confused them. It said something like "You chose not to pay for the Parabol team plan, so now you are locked." The users didn't know the payment failed, so they weren't sure what to make of that.

If we could change the lock message in these cases to be something related to the failed payment that would be helpful.

@avivapinchas avivapinchas moved this to Stand-alone Issues in 🧁Product Squad Self Raise May 22, 2023
@nickoferrall nickoferrall moved this from Stand-alone Issues to Todo in 🧁Product Squad Self Raise May 23, 2023
@igorlesnenko igorlesnenko self-assigned this May 23, 2023
@igorlesnenko igorlesnenko moved this from To Prioritize to In Progress in Sprint Board Beta May 25, 2023
@igorlesnenko igorlesnenko moved this from Todo to In Progress in 🧁Product Squad Self Raise May 25, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in 🧁Product Squad Self Raise Jun 15, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Sprint Board Beta Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug p2 Needs to be addressed on a reasonable timescale
Projects
No open projects
Status: Done
Status: ✅Done
Development

Successfully merging a pull request may close this issue.

5 participants