You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Times are a little off - like by 4 hours in the wrong direction from a standard UTC->Eastern conversion.
Not sure when when subscriptions are ACTUALLY cut off. Some of this is dependent on Stripe logic I don't understand.
For example what I expect is:
At the end of the month, Stripe tries to add you to the next month.
It sets your "end" date to the end of the month, and re-charges you for the month
If that fails, you are "past due"
Eventually, when the end-of-the month hits, we look at this time and set you as "past due". (At this point - you haven't paid in 4 weeks.
We allow you to remain "past due" for 2 weeks - then shut you off. (At this point, you haven't paid in 6 weeks).
If when you re-up - you get turned on immediately. I am not sure how Stripe works a "back billing" you - but for a second lets assume it does it correctly.
If you re-up by creating a new subscription (which either most people seem to - or maybe stripe requires you to?) It will restart your subscription immediately - but you never paid for the previous 6 weeks.
The text was updated successfully, but these errors were encountered:
Time zone issues have separately been dealt with - BUT (an example):
This guy shows up in grace-period because his subscription "expired" today at 1:58 pm, but we won't do the next Stripe update until 3am. So maybe we just need to add one extra day to grace period?
Active
true
Plan
hobbyist (hobbyist)
Rate Plan
hobbyist
Updated
2019-09-11 09:15:14
Created
2019-08-11 13:58:03
Expires
2019-09-11 13:58:03
Two issues:
Times are a little off - like by 4 hours in the wrong direction from a standard UTC->Eastern conversion.
Not sure when when subscriptions are ACTUALLY cut off. Some of this is dependent on Stripe logic I don't understand.
For example what I expect is:
The text was updated successfully, but these errors were encountered: