# `Stripe.Params.BillingPortal.ConfigurationUpdateParams`
[🔗](https://github.com/jeffhuen/tiger_stripe/blob/main/lib/stripe/params/billing_portal/configuration_update_params.ex#L2)

Parameters for configuration update.

# `t`

```elixir
@type t() :: %Stripe.Params.BillingPortal.ConfigurationUpdateParams{
  active: boolean() | nil,
  business_profile:
    Stripe.Params.BillingPortal.ConfigurationUpdateParams.BusinessProfile.t()
    | nil,
  default_return_url: map() | nil,
  expand: [String.t()] | nil,
  features:
    Stripe.Params.BillingPortal.ConfigurationUpdateParams.Features.t() | nil,
  login_page:
    Stripe.Params.BillingPortal.ConfigurationUpdateParams.LoginPage.t() | nil,
  metadata: map() | nil,
  name: map() | nil
}
```

* `active` - Whether the configuration is active and can be used to create portal sessions.
* `business_profile` - The business information shown to customers in the portal.
* `default_return_url` - The default URL to redirect customers to when they click on the portal's link to return to your website. This can be [overriden](https://docs.stripe.com/api/customer_portal/sessions/create#create_portal_session-return_url) when creating the session.
* `expand` - Specifies which fields in the response should be expanded.
* `features` - Information about the features available in the portal.
* `login_page` - The hosted login page for this configuration. Learn more about the portal login page in our [integration docs](https://stripe.com/docs/billing/subscriptions/integrating-customer-portal#share).
* `metadata` - Set of [key-value pairs](https://docs.stripe.com/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to `metadata`.
* `name` - The name of the configuration.

---

*Consult [api-reference.md](api-reference.md) for complete listing*
