#luizcarlosfx - pricing options
1 messages · Page 1 of 1 (latest)
hi
You could not achieve this in a single API request. I would recommend storing local copies of these records so you could build the interface you are looking for.
hmm
one other question
I know there's a pricing table feature already
but there's one big problem for me
I can't show it to unlogged users or to users that are already subscribed to my service
is there a way to have the pricing table as it is but without the "subscribe" button?
I'd show the table without the button in these cases
I'm sorry but that isn't making much sense to me. Can you describe the case where you do and do not want to show specific features to your users?
no problem, let me try to be a little bit more specific
I don't want to allow users that are not logged in to my system to buy the subscription plans, but I want them to be able to see the prices
It doesn't make much sense to me to force the user to create a valid account so that he can see the prices
Okay, yeah that is a specific custom use-case. Would having the buttons disabled work?
It would, I'd have more instructions in the page saying that you must create an account before buying, and when they create the account I'd enable the buttons
That isn't a feature currently but I can add it as a feature request for that product. The only problem I could see is that you would need to have a JavaScript function that toggles the state of the buttons and that might be a security concern.
yeah
makes sense
or maybe you could have 2 different pricing tables, one that's "read-only" and the other that you can actually use to buy stuff
is there a way to deny a subscription in case the user isn't registered? I mean, let's say that I handle an event with a webhook and respond saying that I don't want to allow it, idk (I'm pretty new to stripe)
The trouble is, the pricing table is a set custom web component. I guess you could restrict access to the working one to authenticated users.
I don't think that is available presently. The pricing table is brand-spanking-new and the idea is to reduce the amount of UI the user needs to build themselves.
This does mean the amount of control is limited though.
I can and will pass along your feedback though. User feedback is one of the ways we improve our products.
thank you. I think you can see the problem there, even though we don't know the perfect solution
Yes I get it and I will ask what a feasible solution may be. So for now you would still need to build this yourself using either local records or a number of API calls to gather the info. However, I would keep an eye on the Pricing Table feature as we continue to develop the capabilities.
thanks
just one last small question
I didn't find a way to get the feature list used in the pricing table via api request
is it available?
if so I guess I can make a set of requests for every hour or so and then cache the results
The "features' section below each product/price?
yeah
I am not seeing that property in the API either presently.