#ayyokami_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1421152888394354778
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi nobs, let me type out my full query
Is there a way to either add days to a subscription or perhaps have it start at a later date (that's not a scheduled subscription but an actual subscription object but some sort of delayed start). The context being is that we are moving away from manually invoicing our clients to online billing on our platform. The plan was to set a date for a user, let's say that their subscription expires in 7 days time. During this time they will get a message on login to say x days remaining until expiry. But let's say they decide to "renew" their subscription today (with 7 days left) which would migrate them from being on a manual invoice billing process to automated stripe billing, By going through the checkout process, this would create them a subscription starting for today and they would essentially be missing out on the 7 days they had left
Is there a way to deal with this type of use case?
My first instinct would have been to recommend subscription schedules, which are designed for future dates
https://docs.stripe.com/billing/subscriptions/subscription-schedules
Is there a reason you don't want to use this?
You could also create a free trial that ends on the date you want to start billing
You could also set a future billing cycle anchor
https://docs.stripe.com/api/subscriptions/create#create_subscription-billing_cycle_anchor
Maybe that's the cleanest approach
Yeah, maybe we've boxed ourselves in a little bit with this. We avoided implementing and integrating the future sub schedule stuff as it won't be necessary for us once all users have been onboarded to online billing
The billing cycle anchor may be a potential approach
OK, I'll have a play and see if that fits, if not, we may have to rethink
Appreciate your time and response
For sure, glad I could help!
Enjoy the rest of your day!
You as well!