#__rob1986__
hidden impBOT
Hello rob1986, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• rob1986, 2 hours ago, 4 messages
• rob1986, 3 hours ago, 11 messages
• rob1986, 3 days ago, 8 messages
quartz oxide
You might be able to create two separate portal configurations for this.
You can check if the customer is subscribed to plan 2 then you can disable subscription_update in the features
https://stripe.com/docs/api/customer_portal/configurations/create#create_portal_configuration-features-subscription_update-products
This should prevent them from switching
whole field
aaaaahhhhh... perfect! thanks!!
quartz oxide
NP! 🙂 Happy to help
whole field
do i create the configuration and then create the portal session?
not sure how to connect the configuration with the session
quartz oxide
yes, you'd need to create the configuration first.
also you don't need to re-create it each time, you can just create two portal configs in the beginning and re-use them
just pass the ID to configuration param when you create portal session
https://stripe.com/docs/api/customer_portal/sessions/create
whole field
so in my code, i have the session create call, do i make the configuration just before the call to session create
so every time session create is called, it also calls the config create?
or are you saying i create the config once, store the config id in my local database and then use that id with the session create call?
quartz oxide
or are you saying i create the config once, store the config id in my local database and then use that id with the session create call?
This