#ibgoldbergs-trials-and-billing-cycles
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.
- gold-schedule-phases, 1 day ago, 8 messages
Hi 👋
Does the customer still need to pay for the remaining 9 months after the trial?
Well since they are credited that amount, then yes.
However, maybe it would be acceptable not to credit the customer and have the system know they are already paid for that product.
Because you cannot "interrupt" the annual billing cycle with a free trial mid-way through without restarting the annual billing cycle. So what I"m trying to figure out is, could you switch to a monthly price with 9 iterations and either use a customer balance or discount to avoid charging them.
I think the "you cannot interrupt the annual billing cycle with a free trial mid-way through without restarting the annual billing cycle" tells me all I need to know.
I don't necessarily think its worth engineering some complex system if it's not possible. The credit is graceful enough.
If there is another way to solve, let me know. Otherwise all good.
I'm not seeing another way to address that concern that doesn't involve some sort of work-around.
If the credit suites your use case then I think that is a good option here.
Yeah it is acceptable, although a customer may end up pushing back that their billing cycle was reset and they have to pay for a full year again
But if they push hard, we can always convert them to a monthly price
Exactly and you could credit them for the 9 months with a reference to the earlier annual invoice they paid: https://stripe.com/docs/invoicing/integration/programmatic-credit-notes
yeah or just do a subscription update with prorations
Yes that would also work. IF you aren't already, you can use test clocks to validate all this behavior
https://stripe.com/docs/billing/testing/test-clocks
Yeah I used a test clock to understand the default behavior