#cynefin_30
1 messages ยท Page 1 of 1 (latest)
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.
- cynefin_30, 2 hours ago, 11 messages
- cynefin_30, 19 hours ago, 22 messages
- cynefin_30, 23 hours ago, 23 messages
Hello ๐
Just to rephrase, you're trying to charge the customer for prorated amount at the time of upgrade and then charge the full upgraded price on the next recurring cycle, correct?
Correct
We have docs that cover this ๐
https://stripe.com/docs/billing/subscriptions/upgrade-downgrade#proration
It mentions about updating the existing subscription with new items, but in my case I want that a new subscription needs to be created during checkout with the above feature and I will cancel the user's existing subscription manually via the cancel subscription API, which would give me more control over the billing cycle because changing the items will not update the billing cycle right ?
but in my case I want that a new subscription needs to be created during checkout with the above feature and I will cancel the user's existing subscription manually via the cancel subscription API
Ah, I don't think Checkout can support that today.
The only workaround I can think of is,
You preview the prorated amount using this
https://stripe.com/docs/billing/subscriptions/prorations#preview-proration
Then you create a checkout session for one-off payment for the prorated amount
Once that one-off payment succeeds, you cancel the existing subscription & create a new one
One follow up to this is that, does creating a new subscription for a customer makes sense ? lets think of this way I have the customer's payment method associated. If that is so, and I create N no of subcriptions for that customer and I can collect payment automatically as per I need N no of times is this not a security breach ?
Don't know I am making sense but just had this thought so asking to clarify
I don't believe its considered a security breach since the customer has to provide consent to be charged later on.
Right does that means, creating a new subscription with collection_method set tocharge_automatically will have customer consent ?
If the payment method was set up correctly, it should be fine.
However, issuers can ask for 3DS auth anytime. So you'd likely want to consider that and build a flow where the customers can come back on-session and authenticate the payment for the new subscription
Taking a step back, can you explain a bit more about the billing cycle update you want to control?
want to make sure I am on the same page
an example would help
Yep framing !! just a bit
lets say I am subscribing to a product on a 30 days basis, the billing cycle would start from (now) and end at (now + 30 days) and the renew period will be exactly at (now + 30 days)
But lets say I upgraded at (now + 24th day) and as per the above feature the new upgraded billing cycle date would start from (now + 24th day) and end 30days ahead of the upgraded date
Which is not possible as we can't change the billing cycle for a subscription stripe handles all of that I guess
I'll need to step away now so I won't be able to provide a comprehensive answer but you can control the billing cycle anchor using a trial too
https://stripe.com/docs/billing/subscriptions/billing-cycle#changing
Okay thanks for the support what's your availability in a day ?
This channel is open twice a day on weekdays during the hours below. We're closed on weekends and holidays.
UTC/GMT
5:00 AM โ 1:00 PM
3:30 PM โ 11:30 PM
Eastern Standard Time
12:00 AM โ 8:00 AM
10:30 AM โ 6:30 PM
Pacific Standard Time
7:30 AM โ 3:30 PM
9:00 PM โ 5:00 AM
Japan Standard Time
12:30 AM โ 8:30 AM
2:00 PM โ 10:00 PM
Cool