#bjartekl-billing-portalmax
1 messages · Page 1 of 1 (latest)
Unfortunately I am not seeing a way to do that either.
Where are you currently setting the mins and maxes?
We're not, but the alternative to being able to dynamically prorate is to limit downgrading and force the customers that want to downgrade to support so that they can handle downgrades manually.
We can do this by only showing higher tiered + the current plan in the customer portal. The issue currently would be the number of seats.
You seem to be able to limit it per product basis in the web configurations, so we're looking for the same functionality when creating a billing portal configuration object.
Do you know if the API is there to do so currently? If so we should be able to intercept the request and add the required data.
Oh it is available in the web portal?
Double checking on what can be done here...
Yes, through the web portal you can add restrictions. We're looking for a way to do the same through the API.
Thank you. Have you tried setting that and retrieving the configuration in the API?
No let me try and see what I get
Nothing is returned.
I don't get the products or the pricing ID's in return either.
This is the only returned update data.
Unfortunately it looks like that can't be set by the API at the moment. If you configure through the portal and use that configuration ID it should still work. I will put in a feature request for making it usable via the API
It seems like it's doing this:
features[subscription_update][products][0][min_quantity]: 7
features[subscription_update][products][0][max_quantity]: 10
I will try to see if passing the values the same way has any effect.
The Dashboard has features that the API doesn't support and right now that feature isn't supported. I'd recommend registering your interest with our support team https://support.stripe.com/contact
Do you know if the API will accept sending those fields?
If so I wouldn't mind forking and adding those fields myself and creating a PR against the libraries.
You're misunderstanding the issue. This is unrelated to client libraries. Our public API doesn't support this feature.
I think I understood, the reasoning behind the question is that from my assumption looking at the billing portal on the dashboard versus the API that is documented, the request itself seems identical except for the differences in the endpoints.
Which makes me wonder if it's the same underlying API just not documented publicly.
The crude way to do it would be to create it with the public api and then to update the BPC against this address (which may or may not be possible):, https://dashboard.stripe.com/v1/billing_portal/configurations/bpc_XXXXXXXXXXXX
I'll send an interest to the support team, for the first mentioned issue and this one.
Which makes me wonder if it's the same underlying API just not documented publicly.
It's the same API. It's not "not documented" it's completely blocked unless you use the Dashboard. I'll flag too, this seems like a valuable feature to have parity for!
Would be great to get this addition for sure!
Thanks for the help.