stripe 15.1.0 → 15.2.0

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 15.2.0 - 2024-04-16
+* [#2064](https://github.com/stripe/stripe-node/pull/2064) Update generated code
+  * Add support for new resource `Entitlements.ActiveEntitlementSummary`
+  * Add support for `balances` and `payouts_list` on `AccountSession.components` and `AccountSessionCreateParams.components`
+  * Change `AccountSession.components.payment_details.features.destination_on_behalf_of_charge_management` and `AccountSession.components.payments.features.destination_on_behalf_of_charge_management` to be required
+  * Change `Billing.MeterEventCreateParams.timestamp` and `Dispute.payment_method_details.card` to be optional
+  * Change type of `Dispute.payment_method_details.card` from `DisputePaymentMethodDetailsCard | null` to `DisputePaymentMethodDetailsCard`
+  * Add support for new value `entitlements.active_entitlement_summary.updated` on enum `Event.type`
+  * Remove support for `config` on `Forwarding.RequestCreateParams` and `Forwarding.Request`. This field is no longer used by the Forwarding Request API.
+  * Add support for `capture_method` on `PaymentIntent.payment_method_options.revolut_pay`, `PaymentIntentConfirmParams.payment_method_options.revolut_pay`, `PaymentIntentCreateParams.payment_method_options.revolut_pay`, and `PaymentIntentUpdateParams.payment_method_options.revolut_pay`
+  * Add support for `swish` on `PaymentMethodConfigurationCreateParams`, `PaymentMethodConfigurationUpdateParams`, and `PaymentMethodConfiguration`
+  * Add support for new value `entitlements.active_entitlement_summary.updated` on enums `WebhookEndpointCreateParams.enabled_events[]` and `WebhookEndpointUpdateParams.enabled_events[]`
+
 ## 15.1.0 - 2024-04-11
 * [#2062](https://github.com/stripe/stripe-node/pull/2062) Update generated code
   * Add support for `account_management` and `notification_banner` on `AccountSession.components` and `AccountSessionCreateParams.components`

package/VERSION

@@ -1 +1 @@
-15.1.0
+15.2.0

package/cjs/stripe.core.js

@@ -34,7 +34,7 @@ const ALLOWED_CONFIG_PROPERTIES = [
 ];
 const defaultRequestSenderFactory = (stripe) => new RequestSender_js_1.RequestSender(stripe, StripeResource_js_1.StripeResource.MAX_BUFFERED_REQUEST_METRICS);
 function createStripe(platformFunctions, requestSender = defaultRequestSenderFactory) {
-    Stripe.PACKAGE_VERSION = '15.1.0';
+    Stripe.PACKAGE_VERSION = '15.2.0';
     Stripe.USER_AGENT = Object.assign({ bindings_version: Stripe.PACKAGE_VERSION, lang: 'node', publisher: 'stripe', uname: null, typescript: false }, (0, utils_js_1.determineProcessUserAgentProperties)());
     Stripe.StripeResource = StripeResource_js_1.StripeResource;
     Stripe.resources = resources;

package/esm/stripe.core.js

@@ -31,7 +31,7 @@ const ALLOWED_CONFIG_PROPERTIES = [
 ];
 const defaultRequestSenderFactory = (stripe) => new RequestSender(stripe, StripeResource.MAX_BUFFERED_REQUEST_METRICS);
 export function createStripe(platformFunctions, requestSender = defaultRequestSenderFactory) {
-    Stripe.PACKAGE_VERSION = '15.1.0';
+    Stripe.PACKAGE_VERSION = '15.2.0';
     Stripe.USER_AGENT = Object.assign({ bindings_version: Stripe.PACKAGE_VERSION, lang: 'node', publisher: 'stripe', uname: null, typescript: false }, determineProcessUserAgentProperties());
     Stripe.StripeResource = StripeResource;
     Stripe.resources = resources;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stripe",
-  "version": "15.1.0",
+  "version": "15.2.0",
   "description": "Stripe API wrapper",
   "keywords": [
     "stripe",

package/types/AccountSessions.d.ts

@@ -50,6 +50,8 @@ declare module 'stripe' {
 
         account_onboarding: Components.AccountOnboarding;
 
+        balances: Components.Balances;
+
         documents: Components.Documents;
 
         notification_banner: Components.NotificationBanner;
@@ -59,6 +61,8 @@ declare module 'stripe' {
         payments: Components.Payments;
 
         payouts: Components.Payouts;
+
+        payouts_list: Components.PayoutsList;
       }
 
       namespace Components {
@@ -98,6 +102,34 @@ declare module 'stripe' {
           }
         }
 
+        interface Balances {
+          /**
+           * Whether the embedded component is enabled.
+           */
+          enabled: boolean;
+
+          features: Balances.Features;
+        }
+
+        namespace Balances {
+          interface Features {
+            /**
+             * Whether to allow payout schedule to be changed. Default `true` when Stripe owns Loss Liability, default `false` otherwise.
+             */
+            edit_payout_schedule: boolean;
+
+            /**
+             * Whether to allow creation of instant payouts. Default `true` when Stripe owns Loss Liability, default `false` otherwise.
+             */
+            instant_payouts: boolean;
+
+            /**
+             * Whether to allow creation of standard payouts. Default `true` when Stripe owns Loss Liability, default `false` otherwise.
+             */
+            standard_payouts: boolean;
+          }
+        }
+
         interface Documents {
           /**
            * Whether the embedded component is enabled.
@@ -148,7 +180,7 @@ declare module 'stripe' {
             /**
              * Whether to allow connected accounts to manage destination charges that are created on behalf of them. This is `false` by default.
              */
-            destination_on_behalf_of_charge_management?: boolean;
+            destination_on_behalf_of_charge_management: boolean;
 
             /**
              * Whether to allow responding to disputes, including submitting evidence and accepting disputes. This is `true` by default.
@@ -181,7 +213,7 @@ declare module 'stripe' {
             /**
              * Whether to allow connected accounts to manage destination charges that are created on behalf of them. This is `false` by default.
              */
-            destination_on_behalf_of_charge_management?: boolean;
+            destination_on_behalf_of_charge_management: boolean;
 
             /**
              * Whether to allow responding to disputes, including submitting evidence and accepting disputes. This is `true` by default.
@@ -222,6 +254,19 @@ declare module 'stripe' {
             standard_payouts: boolean;
           }
         }
+
+        interface PayoutsList {
+          /**
+           * Whether the embedded component is enabled.
+           */
+          enabled: boolean;
+
+          features: PayoutsList.Features;
+        }
+
+        namespace PayoutsList {
+          interface Features {}
+        }
       }
     }
   }

package/types/AccountSessionsResource.d.ts

@@ -31,6 +31,11 @@ declare module 'stripe' {
          */
         account_onboarding?: Components.AccountOnboarding;
 
+        /**
+         * Configuration for the balances embedded component.
+         */
+        balances?: Components.Balances;
+
         /**
          * Configuration for the documents embedded component.
          */
@@ -55,6 +60,11 @@ declare module 'stripe' {
          * Configuration for the payouts embedded component.
          */
         payouts?: Components.Payouts;
+
+        /**
+         * Configuration for the payouts list embedded component.
+         */
+        payouts_list?: Components.PayoutsList;
       }
 
       namespace Components {
@@ -100,6 +110,37 @@ declare module 'stripe' {
           }
         }
 
+        interface Balances {
+          /**
+           * Whether the embedded component is enabled.
+           */
+          enabled: boolean;
+
+          /**
+           * The list of features enabled in the embedded component.
+           */
+          features?: Balances.Features;
+        }
+
+        namespace Balances {
+          interface Features {
+            /**
+             * Whether to allow payout schedule to be changed. Default `true` when Stripe owns Loss Liability, default `false` otherwise.
+             */
+            edit_payout_schedule?: boolean;
+
+            /**
+             * Whether to allow creation of instant payouts. Default `true` when Stripe owns Loss Liability, default `false` otherwise.
+             */
+            instant_payouts?: boolean;
+
+            /**
+             * Whether to allow creation of standard payouts. Default `true` when Stripe owns Loss Liability, default `false` otherwise.
+             */
+            standard_payouts?: boolean;
+          }
+        }
+
         interface Documents {
           /**
            * Whether the embedded component is enabled.
@@ -239,6 +280,22 @@ declare module 'stripe' {
             standard_payouts?: boolean;
           }
         }
+
+        interface PayoutsList {
+          /**
+           * Whether the embedded component is enabled.
+           */
+          enabled: boolean;
+
+          /**
+           * The list of features enabled in the embedded component.
+           */
+          features?: PayoutsList.Features;
+        }
+
+        namespace PayoutsList {
+          interface Features {}
+        }
       }
     }
 

package/types/Billing/MeterEventsResource.d.ts

@@ -16,11 +16,6 @@ declare module 'stripe' {
           [key: string]: string;
         };
 
-        /**
-         * The time of the event. Measured in seconds since the Unix epoch.
-         */
-        timestamp: number;
-
         /**
          * Specifies which fields in the response should be expanded.
          */
@@ -30,6 +25,11 @@ declare module 'stripe' {
          * A unique identifier for the event. If not provided, one will be generated. We recommend using a globally unique identifier for this. We'll enforce uniqueness within a rolling 24 hour period.
          */
         identifier?: string;
+
+        /**
+         * The time of the event. Measured in seconds since the Unix epoch. Defaults to current timestamp if not specified.
+         */
+        timestamp?: number;
       }
 
       class MeterEventsResource {

package/types/Disputes.d.ts

@@ -248,10 +248,7 @@ declare module 'stripe' {
       }
 
       interface PaymentMethodDetails {
-        /**
-         * Card specific dispute details.
-         */
-        card: PaymentMethodDetails.Card | null;
+        card?: PaymentMethodDetails.Card;
 
         /**
          * Payment method type.

package/types/Entitlements/ActiveEntitlementSummaries.d.ts

@@ -0,0 +1,32 @@
+// File generated from our OpenAPI spec
+
+declare module 'stripe' {
+  namespace Stripe {
+    namespace Entitlements {
+      /**
+       * A summary of a customer's active entitlements.
+       */
+      interface ActiveEntitlementSummary {
+        /**
+         * String representing the object's type. Objects of the same type share the same value.
+         */
+        object: 'entitlements.active_entitlement_summary';
+
+        /**
+         * The customer that is entitled to this feature.
+         */
+        customer: string;
+
+        /**
+         * The list of entitlements this customer has.
+         */
+        entitlements: ApiList<Stripe.Entitlements.ActiveEntitlement>;
+
+        /**
+         * Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode.
+         */
+        livemode: boolean;
+      }
+    }
+  }
+}

package/types/EventTypes.d.ts

@@ -70,6 +70,7 @@ declare module 'stripe' {
       | CustomerTaxIdUpdatedEvent
       | CustomerUpdatedEvent
       | CustomerCashBalanceTransactionCreatedEvent
+      | EntitlementsActiveEntitlementSummaryUpdatedEvent
       | FileCreatedEvent
       | FinancialConnectionsAccountCreatedEvent
       | FinancialConnectionsAccountDeactivatedEvent
@@ -1302,6 +1303,25 @@ declare module 'stripe' {
       }
     }
 
+    /**
+     * Occurs whenever a customer's entitlements change.
+     */
+    interface EntitlementsActiveEntitlementSummaryUpdatedEvent
+      extends EventBase {
+      type: 'entitlements.active_entitlement_summary.updated';
+      data: EntitlementsActiveEntitlementSummaryUpdatedEvent.Data;
+    }
+
+    namespace EntitlementsActiveEntitlementSummaryUpdatedEvent {
+      interface Data extends Stripe.Event.Data {
+        object: Stripe.Entitlements.ActiveEntitlementSummary;
+
+        previous_attributes?: Partial<
+          Stripe.Entitlements.ActiveEntitlementSummary
+        >;
+      }
+    }
+
     /**
      * Occurs whenever a new Stripe-generated file is available for your account.
      */

package/types/Events.d.ts

@@ -101,6 +101,7 @@ declare module 'stripe' {
         | 'customer.tax_id.updated'
         | 'customer.updated'
         | 'customer_cash_balance_transaction.created'
+        | 'entitlements.active_entitlement_summary.updated'
         | 'file.created'
         | 'financial_connections.account.created'
         | 'financial_connections.account.deactivated'

package/types/Forwarding/Requests.d.ts

@@ -4,9 +4,9 @@ declare module 'stripe' {
   namespace Stripe {
     namespace Forwarding {
       /**
-       * Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.
-       * A config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with
-       * your credentials in the config, and injects card details from the payment_method into the request.
+       * Instructs Stripe to make a request on your behalf using the destination URL. The destination URL
+       * is activated by Stripe at the time of onboarding. Stripe verifies requests with your credentials
+       * provided during onboarding, and injects card details from the payment_method into the request.
        *
        * Stripe redacts all sensitive fields and headers, including authentication credentials and card numbers,
        * before storing the request and response data in the forwarding Request object, which are subject to a
@@ -32,11 +32,6 @@ declare module 'stripe' {
          */
         object: 'forwarding.request';
 
-        /**
-         * The Forwarding Config used when making the forwarded request. The config specifes the HTTP method, merchant credentials, connection settings, and supported destination URLs.
-         */
-        config: string;
-
         /**
          * Time at which the object was created. Measured in seconds since the Unix epoch.
          */

package/types/Forwarding/RequestsResource.d.ts

@@ -4,11 +4,6 @@ declare module 'stripe' {
   namespace Stripe {
     namespace Forwarding {
       interface RequestCreateParams {
-        /**
-         * The Forwarding Config used when making the forwarded request. The config specifes the HTTP method, merchant credentials, connection settings, and supported destination URLs.
-         */
-        config: string;
-
         /**
          * The PaymentMethod to insert into the forwarded request. Forwarding previously consumed PaymentMethods is allowed.
          */

package/types/Invoices.d.ts

@@ -749,13 +749,13 @@ declare module 'stripe' {
          *
          * Create a SetupIntent when you're ready to collect your customer's payment credentials.
          * Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
-         * The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+         * The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides
          * you through the setup process.
          *
          * Successful SetupIntents result in payment credentials that are optimized for future payments.
          * For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
-         * [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
-         * to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+         * [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+         * to streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).
          * If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
          * it automatically attaches the resulting payment method to that Customer after successful setup.
          * We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
@@ -763,7 +763,7 @@ declare module 'stripe' {
          *
          * By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
          *
-         * Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
+         * Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
          */
         setup_intent?: Stripe.SetupIntent;
 

package/types/PaymentIntents.d.ts

@@ -347,13 +347,13 @@ declare module 'stripe' {
          *
          * Create a SetupIntent when you're ready to collect your customer's payment credentials.
          * Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
-         * The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+         * The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides
          * you through the setup process.
          *
          * Successful SetupIntents result in payment credentials that are optimized for future payments.
          * For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
-         * [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
-         * to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+         * [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+         * to streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).
          * If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
          * it automatically attaches the resulting payment method to that Customer after successful setup.
          * We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
@@ -361,7 +361,7 @@ declare module 'stripe' {
          *
          * By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
          *
-         * Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
+         * Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
          */
         setup_intent?: Stripe.SetupIntent;
 
@@ -2084,7 +2084,12 @@ declare module 'stripe' {
           setup_future_usage?: 'none';
         }
 
-        interface RevolutPay {}
+        interface RevolutPay {
+          /**
+           * Controls when the funds will be captured from the customer's account.
+           */
+          capture_method?: 'manual';
+        }
 
         interface SepaDebit {
           mandate_options?: SepaDebit.MandateOptions;

package/types/PaymentIntentsResource.d.ts

@@ -2069,6 +2069,15 @@ declare module 'stripe' {
         }
 
         interface RevolutPay {
+          /**
+           * Controls when the funds will be captured from the customer's account.
+           *
+           * If provided, this parameter will override the top level behavior of `capture_method` when finalizing the payment with this payment method type.
+           *
+           * If `capture_method` is already set on the PaymentIntent, providing an empty value for this parameter will unset the stored value for this payment method type.
+           */
+          capture_method?: Stripe.Emptyable<'manual'>;
+
           /**
            * Indicates that you intend to make future payments with this PaymentIntent's payment method.
            *
@@ -4295,6 +4304,15 @@ declare module 'stripe' {
         }
 
         interface RevolutPay {
+          /**
+           * Controls when the funds will be captured from the customer's account.
+           *
+           * If provided, this parameter will override the top level behavior of `capture_method` when finalizing the payment with this payment method type.
+           *
+           * If `capture_method` is already set on the PaymentIntent, providing an empty value for this parameter will unset the stored value for this payment method type.
+           */
+          capture_method?: Stripe.Emptyable<'manual'>;
+
           /**
            * Indicates that you intend to make future payments with this PaymentIntent's payment method.
            *
@@ -6666,6 +6684,15 @@ declare module 'stripe' {
         }
 
         interface RevolutPay {
+          /**
+           * Controls when the funds will be captured from the customer's account.
+           *
+           * If provided, this parameter will override the top level behavior of `capture_method` when finalizing the payment with this payment method type.
+           *
+           * If `capture_method` is already set on the PaymentIntent, providing an empty value for this parameter will unset the stored value for this payment method type.
+           */
+          capture_method?: Stripe.Emptyable<'manual'>;
+
           /**
            * Indicates that you intend to make future payments with this PaymentIntent's payment method.
            *

package/types/PaymentMethodConfigurations.d.ts

@@ -125,6 +125,8 @@ declare module 'stripe' {
 
       sofort?: PaymentMethodConfiguration.Sofort;
 
+      swish?: PaymentMethodConfiguration.Swish;
+
       us_bank_account?: PaymentMethodConfiguration.UsBankAccount;
 
       wechat_pay?: PaymentMethodConfiguration.WechatPay;
@@ -1255,6 +1257,40 @@ declare module 'stripe' {
         }
       }
 
+      interface Swish {
+        /**
+         * Whether this payment method may be offered at checkout. True if `display_preference` is `on` and the payment method's capability is active.
+         */
+        available: boolean;
+
+        display_preference: Swish.DisplayPreference;
+      }
+
+      namespace Swish {
+        interface DisplayPreference {
+          /**
+           * For child configs, whether or not the account's preference will be observed. If `false`, the parent configuration's default is used.
+           */
+          overridable: boolean | null;
+
+          /**
+           * The account's display preference.
+           */
+          preference: DisplayPreference.Preference;
+
+          /**
+           * The effective display preference value.
+           */
+          value: DisplayPreference.Value;
+        }
+
+        namespace DisplayPreference {
+          type Preference = 'none' | 'off' | 'on';
+
+          type Value = 'off' | 'on';
+        }
+      }
+
       interface UsBankAccount {
         /**
          * Whether this payment method may be offered at checkout. True if `display_preference` is `on` and the payment method's capability is active.

package/types/PaymentMethodConfigurationsResource.d.ts

@@ -188,6 +188,11 @@ declare module 'stripe' {
        */
       sofort?: PaymentMethodConfigurationCreateParams.Sofort;
 
+      /**
+       * Swish is a [real-time](https://stripe.com/docs/payments/real-time) payment method popular in Sweden. It allows customers to [authenticate and approve](https://stripe.com/docs/payments/payment-methods#customer-actions) payments using the Swish mobile app and the Swedish BankID mobile app. Check this [page](https://stripe.com/docs/payments/swish) for more details.
+       */
+      swish?: PaymentMethodConfigurationCreateParams.Swish;
+
       /**
        * Stripe users in the United States can accept ACH direct debit payments from customers with a US bank account using the Automated Clearing House (ACH) payments system operated by Nacha. Check this [page](https://stripe.com/docs/payments/ach-debit) for more details.
        */
@@ -885,6 +890,26 @@ declare module 'stripe' {
         }
       }
 
+      interface Swish {
+        /**
+         * Whether or not the payment method should be displayed.
+         */
+        display_preference?: Swish.DisplayPreference;
+      }
+
+      namespace Swish {
+        interface DisplayPreference {
+          /**
+           * The account's preference for whether or not to display this payment method.
+           */
+          preference?: DisplayPreference.Preference;
+        }
+
+        namespace DisplayPreference {
+          type Preference = 'none' | 'off' | 'on';
+        }
+      }
+
       interface UsBankAccount {
         /**
          * Whether or not the payment method should be displayed.
@@ -1139,6 +1164,11 @@ declare module 'stripe' {
        */
       sofort?: PaymentMethodConfigurationUpdateParams.Sofort;
 
+      /**
+       * Swish is a [real-time](https://stripe.com/docs/payments/real-time) payment method popular in Sweden. It allows customers to [authenticate and approve](https://stripe.com/docs/payments/payment-methods#customer-actions) payments using the Swish mobile app and the Swedish BankID mobile app. Check this [page](https://stripe.com/docs/payments/swish) for more details.
+       */
+      swish?: PaymentMethodConfigurationUpdateParams.Swish;
+
       /**
        * Stripe users in the United States can accept ACH direct debit payments from customers with a US bank account using the Automated Clearing House (ACH) payments system operated by Nacha. Check this [page](https://stripe.com/docs/payments/ach-debit) for more details.
        */
@@ -1836,6 +1866,26 @@ declare module 'stripe' {
         }
       }
 
+      interface Swish {
+        /**
+         * Whether or not the payment method should be displayed.
+         */
+        display_preference?: Swish.DisplayPreference;
+      }
+
+      namespace Swish {
+        interface DisplayPreference {
+          /**
+           * The account's preference for whether or not to display this payment method.
+           */
+          preference?: DisplayPreference.Preference;
+        }
+
+        namespace DisplayPreference {
+          type Preference = 'none' | 'off' | 'on';
+        }
+      }
+
       interface UsBankAccount {
         /**
          * Whether or not the payment method should be displayed.

package/types/SetupAttempts.d.ts

@@ -582,13 +582,13 @@ declare module 'stripe' {
          *
          * Create a SetupIntent when you're ready to collect your customer's payment credentials.
          * Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
-         * The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+         * The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides
          * you through the setup process.
          *
          * Successful SetupIntents result in payment credentials that are optimized for future payments.
          * For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
-         * [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
-         * to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+         * [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+         * to streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).
          * If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
          * it automatically attaches the resulting payment method to that Customer after successful setup.
          * We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
@@ -596,7 +596,7 @@ declare module 'stripe' {
          *
          * By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
          *
-         * Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
+         * Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
          */
         setup_intent?: Stripe.SetupIntent;
 

package/types/SetupIntents.d.ts

@@ -9,13 +9,13 @@ declare module 'stripe' {
      *
      * Create a SetupIntent when you're ready to collect your customer's payment credentials.
      * Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
-     * The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+     * The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides
      * you through the setup process.
      *
      * Successful SetupIntents result in payment credentials that are optimized for future payments.
      * For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
-     * [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
-     * to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+     * [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+     * to streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).
      * If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
      * it automatically attaches the resulting payment method to that Customer after successful setup.
      * We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
@@ -23,7 +23,7 @@ declare module 'stripe' {
      *
      * By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
      *
-     * Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
+     * Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
      */
     interface SetupIntent {
       /**
@@ -260,13 +260,13 @@ declare module 'stripe' {
          *
          * Create a SetupIntent when you're ready to collect your customer's payment credentials.
          * Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
-         * The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+         * The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides
          * you through the setup process.
          *
          * Successful SetupIntents result in payment credentials that are optimized for future payments.
          * For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
-         * [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
-         * to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+         * [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection
+         * to streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).
          * If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
          * it automatically attaches the resulting payment method to that Customer after successful setup.
          * We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
@@ -274,7 +274,7 @@ declare module 'stripe' {
          *
          * By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
          *
-         * Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
+         * Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)
          */
         setup_intent?: Stripe.SetupIntent;
 

package/types/WebhookEndpointsResource.d.ts

@@ -212,6 +212,7 @@ declare module 'stripe' {
         | 'customer.tax_id.updated'
         | 'customer.updated'
         | 'customer_cash_balance_transaction.created'
+        | 'entitlements.active_entitlement_summary.updated'
         | 'file.created'
         | 'financial_connections.account.created'
         | 'financial_connections.account.deactivated'
@@ -482,6 +483,7 @@ declare module 'stripe' {
         | 'customer.tax_id.updated'
         | 'customer.updated'
         | 'customer_cash_balance_transaction.created'
+        | 'entitlements.active_entitlement_summary.updated'
         | 'file.created'
         | 'financial_connections.account.created'
         | 'financial_connections.account.deactivated'

package/types/index.d.ts

@@ -161,6 +161,7 @@
 ///<reference path='./Customers.d.ts' />
 ///<reference path='./Discounts.d.ts' />
 ///<reference path='./Disputes.d.ts' />
+///<reference path='./Entitlements/ActiveEntitlementSummaries.d.ts' />
 ///<reference path='./Entitlements/ActiveEntitlements.d.ts' />
 ///<reference path='./Entitlements/Features.d.ts' />
 ///<reference path='./EphemeralKeys.d.ts' />