Stripe plugin variable pricing based on quantity (# of seats purchased / plan length)

Hello,

I’m trying to set up functionality for users to select # of seats and the pricing plan they want, of which each plan has a monthly rate (paid monthly), and a yearly rate (paid yearly in one bulk payment).

So far I have set the ‘subscribe the user to plan’ workflow set up:

For this example, I selected 10 seats on the $24.99 (per month, per seat, paid yearly rate), which then produces the below at checkout…

This is incorrect as it should be $2,998.8 per year, since the subscription was purchased on the paid-yearly rate, ie. the 10 users are subscribed for a year period of time, paid up front.

So i guess my question is, how do I pass or control the subscription’s period of time, while also keeping the QTY variable for the user to select?

Any advice is appreciated!

1 Like

The plan you’ve created on stripe is for 1 month. You need to create a yearly plan within the same product on the stripe dashboard and then select that subscription plan in your workflow

Right now the user is subscribing to your monthly plan

I believe I’ve tried that and no luck, see below:

Then when I test it with 10 seats:

its still charging the same amount, but just says per year, when really it should be $249.9 per month (breakdown), but billed and charged as $2,998.8 per year.

Consider instead embedding a Stripe Pricing Table in your Bubble app’s page.

For anyone else looking for the answer, I reached out to Bubble support and they responded with:

As a workaround, you can determine the cost of one seat on the Teams plan for the whole year on an annual cadence and create this as its own subscription (for example, for your Teams plan, $14.99*12 = 179.88), and set the quantity to the number of seats you’re purchasing (let’s say, if you’re purchasing 3 seats for the year, the cost will come out to the cost of one seat for the year multiplied by the number of seats = 179.88 * 3 = $539.64).

This topic was automatically closed after 70 days. New replies are no longer allowed.