#Andrew - Pricing model
1 messages · Page 1 of 1 (latest)
Hi 👋
It's not really clear from that diagram what you are trying to accomplish. You can read about subscriptions upgrading/downgrading here: https://stripe.com/docs/billing/subscriptions/upgrade-downgrade
But could you also describe in words what you would want to achieve? Based on what I can gather from the diagram this would require much of the logic be handled by your integration.
Ok, so now we have 2 kind of recurring products for 2 kinds of resources. We also have 3rd recurring product that allows user to use both resources. We want seamless upgrading experience, when user could just press one "upgrade to full" button, pay difference in price between full plan and his current plan immediately, and have access to both resources. I was wondering if Stripe supports such kind of price tiering
Sure, we support tiered pricing: https://stripe.com/docs/products-prices/pricing-models#tiered-pricing
As for the changing and the cost, that you would handle with prorations
Which can be complicated in their behavior so I would highly recommend thorough testing
I wasn't able to find a way to such price tiers. For example, I understand how to use one-dimensional price tiers for these 2 subscriptions: 50 usages of a product per month and 100 usages of the same product per month. Here I want somewhat of a two-dimensional price tiers
Ok, I will look into prorations, thank you. Btw, is it possible to seamlessly change user subscription from one to another with prorations that are not part of the same pricing model?
The proration is generated when a subscription is changed and what determines the amount is the difference between the previous price or billing cycle and the changes being made.
You can test out what prorations would look like using the Upcoming Invoice API endpoint: https://stripe.com/docs/api/invoices/upcoming
You pass in the Subscription ID and the parameters you are thinking of changing. The invoice object returned is what Stripe would generate in response to those changes
You may need to simply create 2 price models to capture what you are after though