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

Document the Stripe subscription past due and Tenanat Fagged warnings in the Subscription and Billing Management guide #1303

Closed
Siva-7482 opened this issue Apr 6, 2024 · 0 comments · Fixed by #1310
Assignees
Milestone

Comments

@Siva-7482
Copy link
Contributor

Summary

Generally, The Thing Stack Console displays a warning Stripe subscription past due upon payment past due. If the payment is past due for 3 weeks, the tenant enters into a flagged state and further restricts the functionality via automatic deactivation. Also, the tenant will be active automatically immediately (say ~2 to 5 min) upon clearing the payment due.

Why do we need this?

To assist users with understanding Stripe subscription past due and Tenant Flagged warnings in The Things Stack Console.

What is already there? What do you see now?

Subscription and Billing Management

What is missing? What do you want to see?

Information on Stripe subscription past due and Tenant Flagged warnings in the Subscription and Billing Management
guide.

How do you propose to document this?

Insights:

  • When a user's tenant subscription has an overdue payment, they receive these warnings upon logging in to the console, i.e., Stripe subscription past due and possibly Tenant Flagged. Also, they may have received an email regarding the overdue payment if any.
  • If they don't take any action, the tenant enters into a flagged state and further restricts the functionality via automatic deactivation. And the tenant becomes inactive.
  • Users may check the email associated with their Subscription and Billing Management account for any pending invoices. Once the payment due is cleared the tenant will be activated automatically.

cc: @KrishnaIyer

Can you do this yourself and submit a Pull Request?

No, @nejraselimovic

@github-actions github-actions bot added the needs/triage We still need to triage this label Apr 6, 2024
@nejraselimovic nejraselimovic self-assigned this Apr 7, 2024
@nejraselimovic nejraselimovic removed the needs/triage We still need to triage this label Apr 7, 2024
@nejraselimovic nejraselimovic added this to the Apr 2024 milestone Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants