filip-subscriptions | Stripe Developers | Page 1

frigid veldt Oct 29, 2021, 11:42 AM

#

sum I think does what you describe

#

it's the sum of usage during the period being billed for(I think you assume it's the sum of all usage of all time, but it's not )

Specifies a usage aggregation strategy for prices of usage_type=metered. Allowed values are sum for summing up all usage during a period, last_during_period for using the last usage record reported within a period, last_ever for using the last usage record ever (across period bounds) or max which uses the usage record with the maximum reported usage during a period. Defaults to sum.

hoary fossil Oct 29, 2021, 11:46 AM

#

The reason why that doesn't make sense in my case, is that it can also go down. From, 5 to 3 for example

#

And what happens if nothing is being reported in the period? (user count didn't change)

frigid veldt Oct 29, 2021, 11:48 AM

#

ah ok, did you test it and confirmed it doesn't work for your use case? Sorry, I'm not very familiar our metered billing product either actually

#

it's quite possible we don't natively support this use case, there are a lot of limitations in how things are modeled unfortunately!

hoary fossil Oct 29, 2021, 11:50 AM

#

Yeah, I'm trying to use your samples in order to confirm my assumptions

#

(code samples)

#

Seems like pretty obvious case to support. Fair billing for per-seat.
Basically prorated seats

shut portal Oct 29, 2021, 11:52 AM

#

@hoary fossil - I guess that you are trying to do is not available in Stripe. I had the same issue

frigid veldt Oct 29, 2021, 11:53 AM

#

yep it's quite possible we don't support it, the Subscriptions product is fairly flexible but it has things that don't work.

#

I'm thinking though. I guess I'm trying to figure out first if metered billing even makes sense here.

hoary fossil Oct 29, 2021, 11:55 AM

#

Coupons should work with standard pricing. Just I wanted to see if we can avoid implementing that in our system, better to offload as much to you guys, lowers chance of a bug 😅

frigid veldt Oct 29, 2021, 11:56 AM

#

like you could use a normal per-seat subscription and increase the quantity https://stripe.com/docs/billing/subscriptions/quantities . That way the amount charged each month is the current quantity. But then it means you'd have to set the quantity to just the amount the customer added. So in your example, set the quantity to 10 so the billing works out, and not 15 (even though they technically have 15 seats), and track the real amount somewhere else like metadata or external to Stripe.

#

or yeah, add the real amount, with a dynamic coupon to artificially lower things

shut portal Oct 29, 2021, 11:57 AM

#

Sorry I don't know how to use discord much so I'm posting screenshots instead of tagging/mentioning

#

hoary fossil Oct 29, 2021, 11:59 AM

#

Yup, I would avoid tinkering with number of products purchased because they show up on invoice and that can cause legal issues (someone bought 15 but it says 10) . And for coupon we can specify something in the name, so users can understand why we lowered the price.

#

@shut portal Thankyou for sc. I'll see what I can do with this. The thing is that, per-seat is not only thing we want to bill in prorated way, so it get's a lot more complicated when you bundle stuff together 😅

#filip-subscriptions