stripe 20.1.0-beta.1 → 20.1.0

package/types/ApplicationFeesResource.d.ts

@@ -38,7 +38,7 @@ declare module 'stripe' {
       expand?: Array<string>;
 
       /**
-       * Set of [key-value pairs](https://stripe.com/docs/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`.
+       * 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`.
        */
       metadata?: Stripe.MetadataParam;
     }
@@ -64,7 +64,7 @@ declare module 'stripe' {
       expand?: Array<string>;
 
       /**
-       * Set of [key-value pairs](https://stripe.com/docs/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`.
+       * 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`.
        */
       metadata?: Stripe.Emptyable<Stripe.MetadataParam>;
     }

package/types/Apps/Secrets.d.ts

@@ -12,7 +12,7 @@ declare module 'stripe' {
        *
        * A `user` scoped secret is accessible by the app backend and one specific Dashboard user. Use the `user` scope for per-user secrets like per-user OAuth tokens, where different users might have different permissions.
        *
-       * Related guide: [Store data between page reloads](https://stripe.com/docs/stripe-apps/store-auth-data-custom-objects)
+       * Related guide: [Store data between page reloads](https://docs.stripe.com/stripe-apps/store-auth-data-custom-objects)
        */
       interface Secret {
         /**

package/types/Balance.d.ts

@@ -8,7 +8,7 @@ declare module 'stripe' {
      *
      * The top-level `available` and `pending` comprise your "payments balance."
      *
-     * Related guide: [Balances and settlement time](https://stripe.com/docs/payments/balances), [Understanding Connect account balances](https://stripe.com/docs/connect/account-balances)
+     * Related guide: [Balances and settlement time](https://docs.stripe.com/payments/balances), [Understanding Connect account balances](https://docs.stripe.com/connect/account-balances)
      */
     interface Balance {
       /**
@@ -17,7 +17,7 @@ declare module 'stripe' {
       object: 'balance';
 
       /**
-       * Available funds that you can transfer or pay out automatically by Stripe or explicitly through the [Transfers API](https://stripe.com/docs/api#transfers) or [Payouts API](https://stripe.com/docs/api#payouts). You can find the available balance for each currency and payment type in the `source_types` property.
+       * Available funds that you can transfer or pay out automatically by Stripe or explicitly through the [Transfers API](https://api.stripe.com#transfers) or [Payouts API](https://api.stripe.com#payouts). You can find the available balance for each currency and payment type in the `source_types` property.
        */
       available: Array<Balance.Available>;
 

package/types/BalanceSettings.d.ts

@@ -39,7 +39,7 @@ declare module 'stripe' {
           } | null;
 
           /**
-           * Details on when funds from charges are available, and when they are paid out to an external account. See our [Setting Bank and Debit Card Payouts](https://stripe.com/docs/connect/bank-transfers#payout-information) documentation for details.
+           * Details on when funds from charges are available, and when they are paid out to an external account. See our [Setting Bank and Debit Card Payouts](https://docs.stripe.com/connect/bank-transfers#payout-information) documentation for details.
            */
           schedule: Payouts.Schedule | null;
 

package/types/BalanceTransactions.d.ts

@@ -6,7 +6,7 @@ declare module 'stripe' {
      * Balance transactions represent funds moving through your Stripe account.
      * Stripe creates them for every type of transaction that enters or leaves your Stripe account balance.
      *
-     * Related guide: [Balance transaction types](https://stripe.com/docs/reports/balance-transaction-types)
+     * Related guide: [Balance transaction types](https://docs.stripe.com/reports/balance-transaction-types)
      */
     interface BalanceTransaction {
       /**

package/types/BankAccounts.d.ts

@@ -85,7 +85,7 @@ declare module 'stripe' {
       fingerprint: string | null;
 
       /**
-       * Information about the [upcoming new requirements for the bank account](https://stripe.com/docs/connect/custom-accounts/future-requirements), including what information needs to be collected, and by when.
+       * Information about the [upcoming new requirements for the bank account](https://docs.stripe.com/connect/custom-accounts/future-requirements), including what information needs to be collected, and by when.
        */
       future_requirements?: BankAccount.FutureRequirements | null;
 
@@ -95,7 +95,7 @@ declare module 'stripe' {
       last4: string;
 
       /**
-       * Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
+       * 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.
        */
       metadata?: Stripe.Metadata | null;
 
@@ -122,22 +122,22 @@ declare module 'stripe' {
 
       interface FutureRequirements {
         /**
-         * Fields that need to be collected to keep the external account enabled. If not collected by `current_deadline`, these fields appear in `past_due` as well, and the account is disabled.
+         * Fields that need to be resolved to keep the external account enabled. If not resolved by `current_deadline`, these fields will appear in `past_due` as well, and the account is disabled.
          */
         currently_due: Array<string> | null;
 
         /**
-         * Fields that are `currently_due` and need to be collected again because validation or verification failed.
+         * Details about validation and verification failures for `due` requirements that must be resolved.
          */
         errors: Array<FutureRequirements.Error> | null;
 
         /**
-         * Fields that weren't collected by `current_deadline`. These fields need to be collected to enable the external account.
+         * Fields that haven't been resolved by `current_deadline`. These fields need to be resolved to enable the external account.
          */
         past_due: Array<string> | null;
 
         /**
-         * Fields that might become required depending on the results of verification or review. It's an empty array unless an asynchronous verification is pending. If verification fails, these fields move to `eventually_due`, `currently_due`, or `past_due`. Fields might appear in `eventually_due`, `currently_due`, or `past_due` and in `pending_verification` if verification fails but another verification is still pending.
+         * Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending.
          */
         pending_verification: Array<string> | null;
       }
@@ -206,7 +206,6 @@ declare module 'stripe' {
             | 'invalid_url_website_other'
             | 'invalid_value_other'
             | 'unsupported_business_type'
-            | 'verification_data_not_found'
             | 'verification_directors_mismatch'
             | 'verification_document_address_mismatch'
             | 'verification_document_address_missing'
@@ -265,22 +264,22 @@ declare module 'stripe' {
 
       interface Requirements {
         /**
-         * Fields that need to be collected to keep the external account enabled. If not collected by `current_deadline`, these fields appear in `past_due` as well, and the account is disabled.
+         * Fields that need to be resolved to keep the external account enabled. If not resolved by `current_deadline`, these fields will appear in `past_due` as well, and the account is disabled.
          */
         currently_due: Array<string> | null;
 
         /**
-         * Fields that are `currently_due` and need to be collected again because validation or verification failed.
+         * Details about validation and verification failures for `due` requirements that must be resolved.
          */
         errors: Array<Requirements.Error> | null;
 
         /**
-         * Fields that weren't collected by `current_deadline`. These fields need to be collected to enable the external account.
+         * Fields that haven't been resolved by `current_deadline`. These fields need to be resolved to enable the external account.
          */
         past_due: Array<string> | null;
 
         /**
-         * Fields that might become required depending on the results of verification or review. It's an empty array unless an asynchronous verification is pending. If verification fails, these fields move to `eventually_due`, `currently_due`, or `past_due`. Fields might appear in `eventually_due`, `currently_due`, or `past_due` and in `pending_verification` if verification fails but another verification is still pending.
+         * Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending.
          */
         pending_verification: Array<string> | null;
       }
@@ -349,7 +348,6 @@ declare module 'stripe' {
             | 'invalid_url_website_other'
             | 'invalid_value_other'
             | 'unsupported_business_type'
-            | 'verification_data_not_found'
             | 'verification_directors_mismatch'
             | 'verification_document_address_mismatch'
             | 'verification_document_address_missing'

package/types/Billing/AlertTriggereds.d.ts

@@ -35,7 +35,7 @@ declare module 'stripe' {
         /**
          * The value triggering the alert
          */
-        value: string;
+        value: number;
       }
     }
   }

package/types/Billing/Alerts.d.ts

@@ -38,7 +38,7 @@ declare module 'stripe' {
         title: string;
 
         /**
-         * Encapsulates configuration of the alert to monitor usage on a specific [Billing Meter](https://stripe.com/docs/api/billing/meter).
+         * Encapsulates configuration of the alert to monitor usage on a specific [Billing Meter](https://docs.stripe.com/api/billing/meter).
          */
         usage_threshold: Alert.UsageThreshold | null;
       }

package/types/Billing/CreditBalanceSummary.d.ts

@@ -25,7 +25,7 @@ declare module 'stripe' {
         /**
          * The account the balance is for.
          */
-        customer_account?: string | null;
+        customer_account: string | null;
 
         /**
          * Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.

package/types/Billing/CreditBalanceSummaryResource.d.ts

@@ -10,12 +10,12 @@ declare module 'stripe' {
         filter: CreditBalanceSummaryRetrieveParams.Filter;
 
         /**
-         * The customer for which to fetch credit balance summary.
+         * The customer whose credit balance summary you're retrieving.
          */
         customer?: string;
 
         /**
-         * The account for which to fetch credit balance summary.
+         * The account representing the customer whose credit balance summary you're retrieving.
          */
         customer_account?: string;
 

package/types/Billing/CreditBalanceTransactionsResource.d.ts

@@ -17,12 +17,12 @@ declare module 'stripe' {
         credit_grant?: string;
 
         /**
-         * The customer for which to fetch credit balance transactions.
+         * The customer whose credit balance transactions you're retrieving.
          */
         customer?: string;
 
         /**
-         * The account for which to fetch credit balance transactions.
+         * The account representing the customer whose credit balance transactions you're retrieving.
          */
         customer_account?: string;
 

package/types/Billing/CreditGrants.d.ts

@@ -39,9 +39,9 @@ declare module 'stripe' {
         customer: string | Stripe.Customer | Stripe.DeletedCustomer;
 
         /**
-         * ID of the account receiving the billing credits
+         * ID of the account representing the customer receiving the billing credits
          */
-        customer_account?: string | null;
+        customer_account: string | null;
 
         /**
          * The time when the billing credits become effective-when they're eligible for use.
@@ -59,7 +59,7 @@ declare module 'stripe' {
         livemode: boolean;
 
         /**
-         * Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
+         * 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.
          */
         metadata: Stripe.Metadata;
 

package/types/Billing/CreditGrantsResource.d.ts

@@ -20,12 +20,12 @@ declare module 'stripe' {
         category?: CreditGrantCreateParams.Category;
 
         /**
-         * ID of the customer to receive the billing credits.
+         * ID of the customer receiving the billing credits.
          */
         customer?: string;
 
         /**
-         * ID of the account to receive the billing credits.
+         * ID of the account representing the customer receiving the billing credits.
          */
         customer_account?: string;
 
@@ -151,7 +151,7 @@ declare module 'stripe' {
         customer?: string;
 
         /**
-         * Only return credit grants for this account.
+         * Only return credit grants for this account representing the customer.
          */
         customer_account?: string;
 

package/types/Billing/MeterEvents.d.ts

@@ -33,7 +33,7 @@ declare module 'stripe' {
         livemode: boolean;
 
         /**
-         * The payload of the event. This contains the fields corresponding to a meter's `customer_mapping.event_payload_key` (default is `stripe_customer_id`) and `value_settings.event_payload_key` (default is `value`). Read more about the [payload](https://stripe.com/docs/billing/subscriptions/usage-based/recording-usage#payload-key-overrides).
+         * The payload of the event. This contains the fields corresponding to a meter's `customer_mapping.event_payload_key` (default is `stripe_customer_id`) and `value_settings.event_payload_key` (default is `value`). Read more about the [payload](https://docs.stripe.com/billing/subscriptions/usage-based/meters/configure#meter-configuration-attributes).
          */
         payload: {
           [key: string]: string;

package/types/Billing/MeterEventsResource.d.ts

@@ -10,7 +10,7 @@ declare module 'stripe' {
         event_name: string;
 
         /**
-         * The payload of the event. This must contain the fields corresponding to a meter's `customer_mapping.event_payload_key` (default is `stripe_customer_id`) and `value_settings.event_payload_key` (default is `value`). Read more about the [payload](https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage#payload-key-overrides).
+         * The payload of the event. This must contain the fields corresponding to a meter's `customer_mapping.event_payload_key` (default is `stripe_customer_id`) and `value_settings.event_payload_key` (default is `value`). Read more about the [payload](https://docs.stripe.com/billing/subscriptions/usage-based/meters/configure#meter-configuration-attributes).
          */
         payload: {
           [key: string]: string;

package/types/BillingPortal/Configurations.d.ts

@@ -39,7 +39,7 @@ declare module 'stripe' {
         created: number;
 
         /**
-         * 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://stripe.com/docs/api/customer_portal/sessions/create#create_portal_session-return_url) when creating the session.
+         * 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.
          */
         default_return_url: string | null;
 
@@ -58,7 +58,7 @@ declare module 'stripe' {
         login_page: Configuration.LoginPage;
 
         /**
-         * Set of [key-value pairs](https://stripe.com/docs/api/metadata) that you can attach to an object. This can be useful for storing additional information about the object in a structured format.
+         * 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.
          */
         metadata: Stripe.Metadata | null;
 
@@ -198,6 +198,11 @@ declare module 'stripe' {
           }
 
           interface SubscriptionUpdate {
+            /**
+             * Determines the value to use for the billing cycle anchor on subscription updates. Valid values are `now` or `unchanged`, and the default value is `unchanged`. Setting the value to `now` resets the subscription's billing cycle anchor to the current time (in UTC). For more information, see the billing cycle [documentation](https://docs.stripe.com/billing/subscriptions/billing-cycle).
+             */
+            billing_cycle_anchor: SubscriptionUpdate.BillingCycleAnchor | null;
+
             /**
              * The types of subscription updates that are supported for items listed in the `products` attribute. When empty, subscriptions are not updateable.
              */
@@ -229,6 +234,8 @@ declare module 'stripe' {
           }
 
           namespace SubscriptionUpdate {
+            type BillingCycleAnchor = 'now' | 'unchanged';
+
             type DefaultAllowedUpdate = 'price' | 'promotion_code' | 'quantity';
 
             interface Product {
@@ -302,7 +309,7 @@ declare module 'stripe' {
           enabled: boolean;
 
           /**
-           * A shareable URL to the hosted portal login page. Your customers will be able to log in with their [email](https://stripe.com/docs/api/customers/object#customer_object-email) and receive a link to their customer portal.
+           * A shareable URL to the hosted portal login page. Your customers will be able to log in with their [email](https://docs.stripe.com/api/customers/object#customer_object-email) and receive a link to their customer portal.
            */
           url: string | null;
         }

package/types/BillingPortal/ConfigurationsResource.d.ts

@@ -15,7 +15,7 @@ declare module 'stripe' {
         business_profile?: ConfigurationCreateParams.BusinessProfile;
 
         /**
-         * 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://stripe.com/docs/api/customer_portal/sessions/create#create_portal_session-return_url) when creating the session.
+         * 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.
          */
         default_return_url?: Stripe.Emptyable<string>;
 
@@ -30,7 +30,7 @@ declare module 'stripe' {
         login_page?: ConfigurationCreateParams.LoginPage;
 
         /**
-         * Set of [key-value pairs](https://stripe.com/docs/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`.
+         * 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`.
          */
         metadata?: Stripe.MetadataParam;
 
@@ -185,6 +185,11 @@ declare module 'stripe' {
           }
 
           interface SubscriptionUpdate {
+            /**
+             * Determines the value to use for the billing cycle anchor on subscription updates. Valid values are `now` or `unchanged`, and the default value is `unchanged`. Setting the value to `now` resets the subscription's billing cycle anchor to the current time (in UTC). For more information, see the billing cycle [documentation](https://docs.stripe.com/billing/subscriptions/billing-cycle).
+             */
+            billing_cycle_anchor?: SubscriptionUpdate.BillingCycleAnchor;
+
             /**
              * The types of subscription updates that are supported. When empty, subscriptions are not updateable.
              */
@@ -219,6 +224,8 @@ declare module 'stripe' {
           }
 
           namespace SubscriptionUpdate {
+            type BillingCycleAnchor = 'now' | 'unchanged';
+
             type DefaultAllowedUpdate = 'price' | 'promotion_code' | 'quantity';
 
             interface Product {
@@ -288,7 +295,7 @@ declare module 'stripe' {
 
         interface LoginPage {
           /**
-           * Set to `true` to generate a shareable URL [`login_page.url`](https://stripe.com/docs/api/customer_portal/configuration#portal_configuration_object-login_page-url) that will take your customers to a hosted login page for the customer portal.
+           * Set to `true` to generate a shareable URL [`login_page.url`](https://docs.stripe.com/api/customer_portal/configuration#portal_configuration_object-login_page-url) that will take your customers to a hosted login page for the customer portal.
            */
           enabled: boolean;
         }
@@ -313,7 +320,7 @@ declare module 'stripe' {
         business_profile?: ConfigurationUpdateParams.BusinessProfile;
 
         /**
-         * 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://stripe.com/docs/api/customer_portal/sessions/create#create_portal_session-return_url) when creating the session.
+         * 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.
          */
         default_return_url?: Stripe.Emptyable<string>;
 
@@ -333,7 +340,7 @@ declare module 'stripe' {
         login_page?: ConfigurationUpdateParams.LoginPage;
 
         /**
-         * Set of [key-value pairs](https://stripe.com/docs/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`.
+         * 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`.
          */
         metadata?: Stripe.Emptyable<Stripe.MetadataParam>;
 
@@ -488,6 +495,11 @@ declare module 'stripe' {
           }
 
           interface SubscriptionUpdate {
+            /**
+             * Determines the value to use for the billing cycle anchor on subscription updates. Valid values are `now` or `unchanged`, and the default value is `unchanged`. Setting the value to `now` resets the subscription's billing cycle anchor to the current time (in UTC). For more information, see the billing cycle [documentation](https://docs.stripe.com/billing/subscriptions/billing-cycle).
+             */
+            billing_cycle_anchor?: SubscriptionUpdate.BillingCycleAnchor;
+
             /**
              * The types of subscription updates that are supported. When empty, subscriptions are not updateable.
              */
@@ -522,6 +534,8 @@ declare module 'stripe' {
           }
 
           namespace SubscriptionUpdate {
+            type BillingCycleAnchor = 'now' | 'unchanged';
+
             type DefaultAllowedUpdate = 'price' | 'promotion_code' | 'quantity';
 
             interface Product {
@@ -593,7 +607,7 @@ declare module 'stripe' {
 
         interface LoginPage {
           /**
-           * Set to `true` to generate a shareable URL [`login_page.url`](https://stripe.com/docs/api/customer_portal/configuration#portal_configuration_object-login_page-url) that will take your customers to a hosted login page for the customer portal.
+           * Set to `true` to generate a shareable URL [`login_page.url`](https://docs.stripe.com/api/customer_portal/configuration#portal_configuration_object-login_page-url) that will take your customers to a hosted login page for the customer portal.
            *
            * Set to `false` to deactivate the `login_page.url`.
            */

package/types/BillingPortal/Sessions.d.ts

@@ -48,10 +48,10 @@ declare module 'stripe' {
         /**
          * The ID of the account for this session.
          */
-        customer_account?: string | null;
+        customer_account: string | null;
 
         /**
-         * Information about a specific flow for the customer to go through. See the [docs](https://stripe.com/docs/customer-management/portal-deep-links) to learn more about using customer portal deep links and flows.
+         * Information about a specific flow for the customer to go through. See the [docs](https://docs.stripe.com/customer-management/portal-deep-links) to learn more about using customer portal deep links and flows.
          */
         flow: Session.Flow | null;
 
@@ -66,7 +66,7 @@ declare module 'stripe' {
         locale: Session.Locale | null;
 
         /**
-         * The account for which the session was created on behalf of. When specified, only subscriptions and invoices with this `on_behalf_of` account appear in the portal. For more information, see the [docs](https://stripe.com/docs/connect/separate-charges-and-transfers#settlement-merchant). Use the [Accounts API](https://stripe.com/docs/api/accounts/object#account_object-settings-branding) to modify the `on_behalf_of` account's branding settings, which the portal displays.
+         * The account for which the session was created on behalf of. When specified, only subscriptions and invoices with this `on_behalf_of` account appear in the portal. For more information, see the [docs](https://docs.stripe.com/connect/separate-charges-and-transfers#settlement-merchant). Use the [Accounts API](https://docs.stripe.com/api/accounts/object#account_object-settings-branding) to modify the `on_behalf_of` account's branding settings, which the portal displays.
          */
         on_behalf_of: string | null;
 
@@ -191,7 +191,7 @@ declare module 'stripe' {
             discounts: Array<SubscriptionUpdateConfirm.Discount> | null;
 
             /**
-             * The [subscription item](https://stripe.com/docs/api/subscription_items) to be updated through this flow. Currently, only up to one may be specified and subscriptions with multiple items are not updatable.
+             * The [subscription item](https://docs.stripe.com/api/subscription_items) to be updated through this flow. Currently, only up to one may be specified and subscriptions with multiple items are not updatable.
              */
             items: Array<SubscriptionUpdateConfirm.Item>;
 
@@ -216,17 +216,17 @@ declare module 'stripe' {
 
             interface Item {
               /**
-               * The ID of the [subscription item](https://stripe.com/docs/api/subscriptions/object#subscription_object-items-data-id) to be updated.
+               * The ID of the [subscription item](https://docs.stripe.com/api/subscriptions/object#subscription_object-items-data-id) to be updated.
                */
               id: string | null;
 
               /**
-               * The price the customer should subscribe to through this flow. The price must also be included in the configuration's [`features.subscription_update.products`](https://stripe.com/docs/api/customer_portal/configuration#portal_configuration_object-features-subscription_update-products).
+               * The price the customer should subscribe to through this flow. The price must also be included in the configuration's [`features.subscription_update.products`](https://docs.stripe.com/api/customer_portal/configuration#portal_configuration_object-features-subscription_update-products).
                */
               price: string | null;
 
               /**
-               * [Quantity](https://stripe.com/docs/subscriptions/quantities) for this item that the customer should subscribe to through this flow.
+               * [Quantity](https://docs.stripe.com/subscriptions/quantities) for this item that the customer should subscribe to through this flow.
                */
               quantity?: number;
             }

package/types/BillingPortal/SessionsResource.d.ts

@@ -5,7 +5,7 @@ declare module 'stripe' {
     namespace BillingPortal {
       interface SessionCreateParams {
         /**
-         * The ID of an existing [configuration](https://stripe.com/docs/api/customer_portal/configuration) to use for this session, describing its functionality and features. If not specified, the session uses the default configuration.
+         * The ID of an existing [configuration](https://docs.stripe.com/api/customer_portal/configuration) to use for this session, describing its functionality and features. If not specified, the session uses the default configuration.
          */
         configuration?: string;
 
@@ -25,7 +25,7 @@ declare module 'stripe' {
         expand?: Array<string>;
 
         /**
-         * Information about a specific flow for the customer to go through. See the [docs](https://stripe.com/docs/customer-management/portal-deep-links) to learn more about using customer portal deep links and flows.
+         * Information about a specific flow for the customer to go through. See the [docs](https://docs.stripe.com/customer-management/portal-deep-links) to learn more about using customer portal deep links and flows.
          */
         flow_data?: SessionCreateParams.FlowData;
 
@@ -35,7 +35,7 @@ declare module 'stripe' {
         locale?: SessionCreateParams.Locale;
 
         /**
-         * The `on_behalf_of` account to use for this session. When specified, only subscriptions and invoices with this `on_behalf_of` account appear in the portal. For more information, see the [docs](https://stripe.com/docs/connect/separate-charges-and-transfers#settlement-merchant). Use the [Accounts API](https://stripe.com/docs/api/accounts/object#account_object-settings-branding) to modify the `on_behalf_of` account's branding settings, which the portal displays.
+         * The `on_behalf_of` account to use for this session. When specified, only subscriptions and invoices with this `on_behalf_of` account appear in the portal. For more information, see the [docs](https://docs.stripe.com/connect/separate-charges-and-transfers#settlement-merchant). Use the [Accounts API](https://docs.stripe.com/api/accounts/object#account_object-settings-branding) to modify the `on_behalf_of` account's branding settings, which the portal displays.
          */
         on_behalf_of?: string;
 
@@ -158,7 +158,7 @@ declare module 'stripe' {
             discounts?: Array<SubscriptionUpdateConfirm.Discount>;
 
             /**
-             * The [subscription item](https://stripe.com/docs/api/subscription_items) to be updated through this flow. Currently, only up to one may be specified and subscriptions with multiple items are not updatable.
+             * The [subscription item](https://docs.stripe.com/api/subscription_items) to be updated through this flow. Currently, only up to one may be specified and subscriptions with multiple items are not updatable.
              */
             items: Array<SubscriptionUpdateConfirm.Item>;
 
@@ -183,17 +183,17 @@ declare module 'stripe' {
 
             interface Item {
               /**
-               * The ID of the [subscription item](https://stripe.com/docs/api/subscriptions/object#subscription_object-items-data-id) to be updated.
+               * The ID of the [subscription item](https://docs.stripe.com/api/subscriptions/object#subscription_object-items-data-id) to be updated.
                */
               id: string;
 
               /**
-               * The price the customer should subscribe to through this flow. The price must also be included in the configuration's [`features.subscription_update.products`](https://stripe.com/docs/api/customer_portal/configuration#portal_configuration_object-features-subscription_update-products).
+               * The price the customer should subscribe to through this flow. The price must also be included in the configuration's [`features.subscription_update.products`](https://docs.stripe.com/api/customer_portal/configuration#portal_configuration_object-features-subscription_update-products).
                */
               price?: string;
 
               /**
-               * [Quantity](https://stripe.com/docs/subscriptions/quantities) for this item that the customer should subscribe to through this flow.
+               * [Quantity](https://docs.stripe.com/subscriptions/quantities) for this item that the customer should subscribe to through this flow.
                */
               quantity?: number;
             }