#Mallain23

1 messages · Page 1 of 1 (latest)

tender steepleBOT
rain cypress
#

Hello 👋
Can you share the request ID for the request you're making to upcoming invoice endpoint? What POST parameters are you passing to the API?

thick orbit
#

Sure one sec

#

how can I find the request ID

rain cypress
thick orbit
#

req_KI8rdijUMaKUvs

rain cypress
#

and can you share the response object you're receiving?

thick orbit
rain cypress
#

Thanks, looking..

thick orbit
#

Thanks

rain cypress
#

sorry its taking a while to look.. asking a colleague to take over so they can help you faster.. hang on

thick orbit
#

Thanks

viscid moss
#

👋 taking a look

#

So the reason for this is if you want to use this data in the future.

#

We basically talk about this here: https://stripe.com/docs/api/invoices/upcoming

You can preview the effects of updating a subscription, including a preview of what proration will take place. To ensure that the actual proration is calculated exactly the same as the previewed proration, you should pass a proration_date parameter when doing the actual subscription update. The value passed in should be the same as the subscription_proration_date returned on the upcoming invoice resource.

#

So you can basically just ignore that if you are just going to start a new Subscription here and don't care about doing any backdating or anything based on the date that you previewed

thick orbit
#

I am just trying to determine (based on the invoice) if the total reflects a prorated amount or not

#

and thought that property might be a way to tell that

#

The reason being is that we sometimes settings a billing anchor date in the future and prorating first invoice - but this is dynamically calculated

viscid moss
#

Yeah that's not going to be a good property to look at for that

#

What I'd recommend instead is looking at the returned invoice line items. The description for those line items will indicate whether it is a proration item or not

thick orbit
#

Ok thanks!