#trueinviso
1 messages · Page 1 of 1 (latest)
I think that is expected. The next Invoice for the Customer would occur during the next billing cycle in most cases, so it would have the next iteration of the Subscription's items, plus the ones you added in the Upcoming Invoice API call.
What are you trying to do specifically?
I want them to have access to the new items immediately
So they should pay the difference for the new items through the end of the current billing period
Ah, it sounds like you want to create prorations immediately. I'd recommend passing in subscription_proration_behavior mentioned here: https://stripe.com/docs/api/invoices/upcoming#upcoming_invoice-subscription_proration_behavior
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
That's actually one of the most recent things I've tried, am I doing it correctly?
I tried passing the "always_invoice" parameter here which seems to do what I want, but I don't really understand the ramifications of that.
"Always invoice immediately for prorations."
That essentially creates a new Invoice to use for the current billing cycle. It ensures the new items that you added are immediately invoiced.
cool, that sounds like what I need then
Keep in mind, this isn't a real Invoice. The Upcoming Invoice API just simulates what some update to the Subscription might do, so you'll just want to make sure you pass the same parameters when actually updating the Subscription
yeah, I think I got confused because I've been getting this behavior by using subscription schedules, but updates made directly to a subscription behave differently.