#NikZB-subscriptions

1 messages · Page 1 of 1 (latest)

crystal kernel
#

Hello! Starting up a thread for you

#

Yup! You're exactly on the right path - licensed usage is exactly what you want since it's billed at the start of the period and allows for prorations

#

Actually backing up for a second here

#

To clarify - per-seat pricing models can be modeled as licensed usage. The two types of usage are licensed vs metered usage, which is separate from the question of whether you want per-seat, tiered, etc

flint nova
#

Ok, on that note, there is "per-seat" listed as a price model in the docs, but it says the user chooses the number of users up front.

I assumed that wouldn't really work in my situation because they aren't really choosing the number of users per say, but more just adding the users in the app, and then the app communicates to Stripe how many users there are.

Is that possible with just the "per-seat product" in Stripe or do I have to use licensed usage to make this work?

#

Sorry, getting a bit mixed up here, actually says for "per seat" you just use "Standard pricing" with a price of $25 or whatever the price is per user

#

Is "per-seat" an actual thing in Stripe or is it just a concept that is implemented using different techniques?

crystal kernel
#

Let me make sure we're on the same page - your billing model is just that you want your customers to pay a flat fee + some additional cost that is calculated based on how many users they have at the START of the period. If they add more users in the middle of the period you want to charge them a prorated cost (either immediately or at the start of the next period). Is that right?

flint nova
#

Yeah, that's right

crystal kernel
#

Gotcha - so I believe the best way to model this is to split it into two separate prices. One for the flat fee, and an additional one for the per-user cost. For both of these prices all you have to do is set currency, recurring[interval], product, and unit_amount.

#

These prices will both be licensed usage prices, since this is what we default to if you don't specify recurring.usage_type (see https://stripe.com/docs/api/prices/create#create_price-recurring-usage_type). Having a licensed usage price just means that you want to charge up-front (at the start of the period) based on the quantity set for the price on the subscription, which is exactly what you want

#

Does that make sense? I was worried you were getting a bit too focused in on licensed prices, when it's really not something you have to worry about for your use case - worrying about the usage type is usually more important if you're deciding between metered (billing at the end based on usage) vs licensed. But in your case it's clear you want a licensed price

flint nova
#

Ah, ok. I think that all makes sense now. I think I misinterpreted the pricing models page as describing options in Stripe when it's really just describing conceptual pricing models and how you might approach them in Stripe.

crystal kernel
#

Exactly 👍

flint nova
#

The point that all recurring purchases are either licensed or metered is clear to me now

#

So the default license will work for my use case, and then I just update the quantity as needed and the default proration will add the charges to the next invoice.

#

(or credit if quantity goes down)

#

That seems pretty straightforward

crystal kernel
#

yup!

#

also quick question when you get the chance - can you share the name of the sales rep that sent you here?

flint nova
#

Sure: Austin Sellers