We've moved discussions to Discord

Different Types of Pricing

Jim Jones
Thoughts on including 1) per seat and 2) metered pricing options?  Seems like these options would align JumpStart with typical Enterprise pricing.

Metered changes the flow a bit, as it requires billing/payment in arrears. 
Chris Oliver
Certainly would be nice, but I haven't implemented them personally. First place to start would be adding support for them to the Pay gem.
Nathan Rofkahr
+1 for per seat pricing
+1 for per seat pricing
Ferenc Fekete
+1 for per seat pricing
+1 for per seat pricing
+1 for one time payment
Thanks!
Ferenc Fekete
I just wanted to bump this one - has anyone successfully implemented per seat pricing?

Chris Oliver any thoughts on whether this feature is coming? Thanks!
Chris Oliver
Quantities work in the Pay gem. They've been working in master, but I cut a new release with it today.

You'd just need to make a couple tweaks to Jumpstart Pro to submit quantity (with whatever calculation you need) and show it wherever it's relevant.

Also confirmed that Stripe plans can be either a Plan ID or Price ID (these are new) when subscribing.
Ferenc Fekete
Chris Oliver  thanks for the insights, will check it out! 
Ferenc Fekete
Chris Oliver Implementing quantities for a new subscription was fairly straightforward, where the quantity is set to the number of account users. 

This works well with the Pay gem, however, the number of users could change anytime. It's possible to update the Subscription quantity, but it doesn't appear to update the subscription on Stripe. Do you happen to know if this is possible? Or will the updated quantity be synced at some point? Thanks!
Chris Oliver
Ferenc Fekete When the quantity changes in the app, you should update the subscription through the Stripe API which will then sync back to the app via webhooks. If you only update the record in the app's database, Stripe won't know about it.

Right now Pay doesn't have a method for doing this, so you'd have to go through the Stripe API directly for that piece. We should add that to Pay so it can support that. Might want it to be called like "change_quantity" or something so that we can implement it similarly for Braintree, etc.
Notifications
You’re not receiving notifications from this thread.