#tymm
latent jackalBOT
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.
junior cobalt
Looks like it's for the unused time on the plan you're upgrading/downgrading from. We apply credit for that time: https://dashboard.stripe.com/test/logs/req_qzdIv7r66e4h99
stone linden
i am using the subscriptionupdate api but im not sure what "now" means exactly in billing_cycle_anchor. does stripe takes my proration_date as the anchor or it literally means the exact time that this api was called?
i have tested with test clock it seems like the billing cycle anchor was not set to the latest frozen test clock time. because if it did i would expect the final payable amount to be different
junior cobalt
What is the desired outcome?
stone linden
ok so i am using InvoiceUpcoming api to preview the cost of the subscriptionupdate. i was trying to set billing_cycle_anchor to an epoch but that is not possible, so i set it to now expecting it to literally mean when the api is actually called. then i get back X as payable amount.
then i call to subscriptionupdate, with the same params i passed to InvoiceUpcoming/ as shown in the previous screenshot. and i get X as payable amount.
i just want to understand how this actually works so that i know this behavior is actually reliable.
the desired outcome is that i want both the final payable amount from invoiceupcoming and subscriptionupdate to be the same.
then i call to subscriptionupdate, with the same params i passed to InvoiceUpcoming/ as shown in the previous screenshot. and i get X as payable amount.
i have advanced the time of test clock by like 20 mins, before calling subscriptionupdate.
junior cobalt
I'd need to see your upcoming invoice API call/parameters to compare
What I mean by 'what is desired outcome' is whether or not you want proration (i.e. credit applied) or not?
stone linden
the outcome that i got is what i want. but from what i see in the api doc "now" actually means current time. so if it indeed is the current time, i would expect the final amount to be different from what i can see during invoiceupcoming
stone linden
I'd need to see your upcoming invoice API call/parameters to compare
req_WSKXUt4TmwJKcG