#xu_unexpected
solemn orchidBOT
👋 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/1474006678109159475
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
alpine grotto
req_1uCRIf4CGTRCAw
charred cypress
hey there, looking into your question now
ok, the reason the full price was paid is because of how you set the proration_date parameter in your request
that parameter basically overrides the time of the subscription update, for proration
so it tells Stripe to treat proration as if the subscription was updated at the exact timestamp set
https://docs.stripe.com/api/subscriptions/update#update_subscription-proration_date
the value you set (1771449529) is the same as the subscription's current_period_end, so that basically means that Stripe treated it as if the update happened exactly at the end of the billing period
as such, no proration is due - the amount due is simply the full amount for the next billing period
alpine grotto
Ahh okay thanks! This gives me something to look into
charred cypress
np! is there a reason that you set the proration_date to match the period end?
alpine grotto
cant recall, I'll write back if I have some follow up questions 🙂
charred cypress
sure thing, we'll be here!