#programming_cat
1 messages · Page 1 of 1 (latest)
Hi there!
If the customer downgrade their subscription, then it means they originally paid too much. So what exactly do you want the user to pay?
On the other hand, if the customer upgrade their subscription, then they need to pay the difference.
If the customer downgrade their subscription, then it means they originally paid too much. So what exactly do you want the user to pay?
I want them to pay the full price of the new plan they are selecting.
I have disabled this by disabling proration
@viscid fern ^^
Got it. Can you share a subscription ID (sub_xxx) where you did a downgrade?
I'm testing it out using test mode.
Yes, can you share a test mode subscription ID?
Hi. Any update?
I see that adding billing_cycle_anchor='now' causes the expected behaviour. but not sure why is that?
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
There's many parameters that go into updating a Subscription.
Do you want the new plan to start immediately? What happens with the unused time on the old plan?
e.g. they paid for $10 plan starting on 1st of June, and on 15th they downgraded to $5 plan. Will you refund them the $10? Will the next billing date be 15th of July?
so with each plan, users get a certain minutes of download of an asset. We are assuming if users are trying to change their plan, they have used up all their downloads. So the plan should take effect immediately.
What if they didn't? The customers might get confused why you took away their unused credits.
In any case, you will need to use billing_cycle_anchor='now' to reset the billing date to today.
we have certain measures like checking if users have used up their downloads or not. Asking for confirmation, etc.
ah got it. Can you provide me the reason as to why not providing this argument will result in no charges?
Because the question here is when will the customer be billed for the upgrade. If the billing_cycle_anchor remains the same, and proration_behavior='none' the customer will just pay the new amount from next month. If proration_behavior='always_invoice' - bills immediately for proration, and then bills the new amount next month. However, if you reset billing_cycle_anchor it starts the next billing period immediately, so the next charge arrives now.
ah, got it. Thank you so much!
Happy to help!