#alexelba

1 messages · Page 1 of 1 (latest)

young pelicanBOT
#

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.

viscid spoke
#

Upcoming invoice will only compare the changes from the current one and the information set in the request. If the (1) hasn't been made, you won't be able to see the changes in (2) based on (1).

fluid glen
#

how would I do what I wanna do?

#

should I run with two versions of proration

#

should I do proration_behavior for a call to get new upcoming

#

or is there better way to do

viscid spoke
#

Why do you need (2)? If you know the price that will be updated to, the subscription will charge the full amount in next cycle. Invoice preview shouldn't be necessary

fluid glen
#

subscription has other items which are not updated in this window only "core" product

#

and prices for each client change

#

so only source of current price is stripe subscription

#

I can get subscription and do all math or I can think just do second call with "proration_behavior=none" to get full price?

viscid spoke
#

If you make subscription_items with new price and subscription_proration_behavior: none , you should be able to get the full price. I'd recommend giving a try

fluid glen
#

req_aqRmIE98USndaI it still return for 1

viscid spoke
#

Stripe doesn't store response for GET requests. Can you share the response you received?

fluid glen
#

one sec