#yathartha_api
errant pilotBOT
đ 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/1266344854091206774
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
static tinsel
hi! hm, let me think about it
errant pilotBOT
silk junco
Okay
alpine rover
Where do you see $34.39? Is this in the upcoming invoice?
alpine rover
For sub_1PglR6IG8Ha7XjkSoH1U1hgH?
silk junco
the first one
silk junco
For `sub_1PglR6IG8Ha7XjkSoH1U1hgH`?
yes
alpine rover
OK, we're looking into this
silk junco
Thank you
static tinsel
I think what I'd suggest here is not updating the Schedule, just update the Subscription directly, since you'e making an immediate change. That would just avoid the problem entirely. https://docs.stripe.com/billing/subscriptions/upgrade-downgrade
silk junco
We have a ui where one can update the price so, when it is in subscription it is working fine but while it has not released the schedule then the issue came up. So at that moment subscription may not have been created?
static tinsel
I'm sorry, I don't completely understand what you mean by that
if you're updating a Schedule where the start_date is in the future then AFAIK there can't be any proration, you're just changing the state of what the Subscription will be when it does start.
silk junco
{ "end_behavior": "release", "phases": { "0": { "billing_cycle_anchor": "phase_start", "proration_behavior": "none", "default_payment_method": "pm_1PglPYIG8Ha7XjkSh0renyCw", "start_date": "1721989838", "items": { "0": { "quantity": "1", "price": "price_1PglSmIG8Ha7XjkSa0uNbB57" } }, "collection_method": "charge_automatically" } } }
wrt above payload having "proration_behavior": "none", it is still behaving like it had proration in it. While updating subscrition schedule is this the intended behavior?
static tinsel
I'm not sure, it does seem weird I agree
so I'm suggesting bypassing the issue by just updating the subscription directly instead of updating it via the Schedule
silk junco
I think what I'd suggest here is not updating the Schedule, just update the Subs...
Yes we are updating it immediately but when we create a subscription it may have time in the future
say 2024-07-30
and on 2024-07-28 we are updating the price of the subscription or subscription schedule, at this instance of time will there be subscription?
static tinsel
don't know, is 2024-07-28 after the start_date of your first phase? if so, yes. Also you can retrieve the Schedule object and check if the subscription field has a value to know if it's started
silk junco
i will test this scenario and query later
I have created a subscrition sub_sched_1PgmSuIG8Ha7XjkS9iZJRCyX, And it is starts on future, can I update its subscription rather than schedule as you suggested?
static tinsel
you can when a Subscription exists, naturally.