#hiroshi-subscription-usagebased
cold inlet
Can you explain a little more what billing model this is?
proper eagle
per-user (seat) and per-month billing model
seat is common word in English instead of user??
I use Next.js for my service homepage
proper eagle
no... I have read it
cold inlet
Ok can you be more specific then? Because that's per-seat pricing
proper eagle
What I fundamentally don't understand is if the user specifies the number of sheets as, say, 10, how do I manage that 10 on my application side?
I don't see an example of this in this document and would like to know the sample code.
cold inlet
That's the quantity parameter on the subscription
The code sample in the doc I linked shows this
So, for example in Python:
customer="{{CUSTOMER_ID}}",
items=[{"price": "{{per_seat_price_id}}", "quantity": 10}],
)```Yeah that is OK, I understand.
My question is, for example, let's say AI bot Q is my service, and you are the admin of Discord here, and you install this bot Q and subscribe to it with seat count 2 (quantity=2).
But you have a lot more than 3 users here. How do I, with my bot Q, control the third and subsequent users so that they can't use the bot Q??
I am looking for this part of sample code 🙂
(FYI, javascript is better for me)
cold inlet
There's not really sample code we have that does that because they way in which you restrict your software to a set number of users varies wildly. That entirely depends on the type of thing you're building. It would be managed on your side via data kept in your database
proper eagle
OK, I give up the sample code. What would you do if you were me? I am having trouble imagining it.
cold inlet
What are you building? Is the above example what you're actually building?
proper eagle
Yes, actually Slack bot though.
cold inlet
I'm not familiar with the Slack API, but based on how many seats the user paid for, you need to find a way to count how many slack channels the bot is applied to (if seat corresponds to channel) or which users can interact with it (if seat is tied to specific people) and restrict adding it to more channels or restrict access to certain people past the threshold they paid for
But that's not a stripe question at this point
You would need to read up on docs on integrating a Slack bot to be able to get all this data and keep track of it
gleaming slateBOT
proper eagle
You don't have to tell me the specific Slack API, of course, I can look that up. By the way, this time sheet = Slack user.
fringe mulch
What's blocking you right now that is Stripe specific?
hiroshi-subscription-usagebased
proper eagle
For example, in the earlier example, I would have a page on the Q home page where you, the admin, can register which users can chat with the bot Q. Is that what I should do?
fringe mulch
that's one way yes! That seems separate from Stripe entirely though in that case
proper eagle
I'm starting to get a vague idea of what Stripe can do and what I need to do.
In this case, does Stripe plan to offer this feature in the near future?
fringe mulch
no
proper eagle
that's one way yes! That seems separate from Stripe entirely though in that case
What other ways are there ?
fringe mulch
I don't really understand what part is confusing you here. We help you accept payments. The usage of your own app is something only you control. If you build a Slack app and some users are in your Slack org and can type commands, they talk to you/your servers. Stripe knows nothing about who those users are, what they do, etc. You control all of this and you're the one that decides who can access what, and record usage and bill the Slack org owner for it