#Tejesh
sick pagoda
zealous wing
@tropic leaf since both plans has the same billing period (annual), the next invoice date remains the same unless you change the billing_cycle_anchor https://stripe.com/docs/api/subscriptions/update#update_subscription-billing_cycle_anchor
tropic leaf
Yes but that's after upgrading subscription
I need to get the next billing date and I need to show the user
So if you upgrade then the next billing date will be blabla
zealous wing
You can just refer to the peroid_start property https://stripe.com/docs/api/invoices/object#invoice_object-period_start
zealous wing
Can you share the request ID (req_xxx)? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
tropic leaf
req_f0ru82Efxfy0ue
zealous wing
OK. You should refer to the created property. This is the timestamp of the invoice creation time.
tropic leaf
I want next billing date
zealous wing
The created property of the upcoming invoice is the next invoice date.
tropic leaf
That's giving me next billing date but it's not prorated date
Whenever an user changing his subscription from basic to pro
Obviously he the next billing date should not be the same
zealous wing
No. the invoice date stays the same, and the prorated charge will be included in the upcoming invoice.
tropic leaf
We can't let user use all the professional sercvices withohut paying for it.
We should be either reducing the current subscription period on prorated basis or let user do payment for next subscription period.
rich birch
i'm not entirely sure what's the ask here now. if you want to show the user the changes assuming they upgrade, then use the upcoming invoice and pass in the relevant parameters like the new price, whether you want to prorate etc
tropic leaf
const invoice = await stripe.invoices.retrieveUpcoming({
customer: customer_id,
subscription: subscription_id,
subscription_items: items,
// subscription_proration_behavior: 'always_invoice',
subscription_proration_date: proration_date,
});
Fetching the upcoming invoice from this api
rich birch
alright, what's the issue with this?