#metaelango
1 messages · Page 1 of 1 (latest)
Hi! Let me help you with this.
Yes, I think it's the default behaviour.
Are you running into any issues?
Yes @modest hamlet we want to just update the next billing date and time
i mean next billing date and the amount
Wait, I understood that you only want to update the next period's amount, but not the date.
no we want to update both amount and the next billing cycle
Oh, sorry I've misread the initial message.
The billing cycle is based on the Price, so you will need to update with a different one.
you mean i need to update the price ?
You can't update the Price object. You need to create a different Price with weekly cycle and another unit_amount, and use the new Price ID on the Subscription.
if I create a new Price object and add the new Price on the subscription will it not charge the client immediately?
It depends on the proration_behaviour: https://stripe.com/docs/api/subscriptions/update#update_subscription-proration_behavior
lets say we are keeping the proration behaviour proration_behavior: "none"
You will need to try this, as I suspect it might always be always_invoice if you change the billing period.
Please try this in Test mode and let me know if this works.
You can use test clocks for this: https://stripe.com/docs/billing/testing/test-clocks
can you please explain the always_invoice a bit ?
where i need to change the billing period ?
in the price object ot subscription object ?
The billing period is defined on the Price object. You will need to create a new Price with a different billing period.
always_invoice will create an Invoice with the prorations related to your update