#nukesforbreakfast_unexpected
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/1496582370411679754
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
Hello as well ๐ , the last time I looked into this, this was a known limitation with cancel_at . When it cuts a period short, there will always be a proration. The prorate: false param actually only applies to the call itself that you are passing the param to, because this is scheduling something for later that is considered separate enough that the param doesn't apply.
I think the workaround here would be to create a subscription schedule with that end date and then set end_behavior to cancel along with setting prorate to false on the phase
https://docs.stripe.com/api/subscription_schedules/object#subscription_schedule_object-end_behavior
do you know if subscription schedules existed in 2019-02-19 of the API?
Yep yep they exist that version
ok