#ashtray-wasp_unexpected
1 messages ¡ Page 1 of 1 (latest)
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.
- ashtray-wasp_unexpected, 1 day ago, 25 messages
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247865159993655298
đ Have more to share? Add details, code, screenshots, videos, etc. below.
hi! that seems like just a recurring invoice. Where is the API request where you passed prorate:false exactly, what's the request ID req_xxx for that?
Hmm, looking at this case now, it seems that here I didn't actually do immediate cancel with prorate:false, but did a delayed cancel by setting the Subscription cancel_at value. Could that be it? Does this prorate on cancel?
It'll calculate prorations by default unless you pass proration_behavior: 'none' in the update request: https://docs.stripe.com/billing/subscriptions/cancel?dashboard-or-api=api#set-a-custom-cancel-date
Okay, that makes sense. Sorry for confusion here! Thanks for your help