#jaym - prorations

1 messages · Page 1 of 1 (latest)

random cape
#

Do you have the request ID from when you made this call? (req_123)

oblique wave
#

let me try to get that

#

req_FEoo1457Xas656

random cape
#

Thank you

oblique wave
#

looking at the full response, it looks like its putting the new item in twice, once prorated and then again in full cost

random cape
#

Interesting. I will work on reproducing that. Can you try again but with the more standard upgrade form of modifying the existing subscription item?

#

Like in our docs we typically show replacing the price ID of the existing item

items := []*stripe.SubscriptionItemsParams{
  {
    ID: stripe.String(subscription.Items.Data[0].ID),
    Price: stripe.String("price_CBb6IXqvTLXp3f"), // Switch to new price
  },
}
oblique wave
#

yea, let me try that

#

i think what might be happening is that its showing me the next payment will be in a month, and it will charge the remaining of this billing cycle + a new one for the next billing cycle

#

same result if i update the existing subscription item: req_OzmM8RNPuoqhrg

#

i think i needed this:

                SubscriptionProrationBehavior: stripe.String(string(stripe.SubscriptionProrationBehaviorAlwaysInvoice)),
random cape
#

Yes, that makes more sense and yes that would be the parameter for if you want to charge for the proration noww

oblique wave
#

awesome

#

thanks for the help

random cape
#

If you want to not upgrade until they have made the payment

oblique wave
#

👍

#

the charge would be automatic besides that, correct?

#

or should i be linking them to the stripe customer portal