customer_portal | A customer portal for Sonar | Portal library

So I have 2 apps that are supposed to work together. I have app1 which is an app only our employees will be using and app2 which is a customer_portal app where customers can log in and pay their balance. I'm trying to make it so that in app1 we can create a customer account and link it up to specific customers. This process will use devise_invitable to create an account for app2 and email the selected customer a link to set up their portal app (which just accepts the invite) but for some reason, the invite link doesn't work and just redirects to the home page. So basically app2 can't sign up for an account, the account has to be created through app1 and sent to the customer via email.

I heard from someone that it should only be redirecting if the URL is incorrect. But it's a URL that's generated via the invite function

I'm trying to create a Stripe billing portal configuration using the CLI: https://stripe.com/docs/api/customer_portal/configurations/create?lang=cli

For this particular configuration I want to block updates to the subscription, ie I'm passing -d "features[subscription_update][enabled]"=false

But under subscription update there are some other required fields: features.subscription_update.default_allowed_updates is an array of enums, and features.subscription_update.products is an array of nested objects.

As I want to disable the feature, I'd like to set both of these arrays to empty: no update types are allowed, and no products can be updated. But I can't figure out how to do this.

I've tried:

• Excluding the fields from my request. I get an error saying they're required (as documented)
• Passing an emtpy string eg. -d "features[subscription_update][default_allowed_updates][]"=. I get an error indicating that this is not allowed:

I am exploring the possibility of implementing a Stripe Customer Portal (https://stripe.com/docs/billing/subscriptions/customer-portal) using the Stripe PHP API (https://stripe.com/docs/billing/subscriptions/integrating-customer-portal).

The Portal call would be made available on a button once users are authenticated so that customer IDs can be retrieved from external DB using the session's log-in credentials.