From 389442faa07cff64983edc891922504d1c29718f Mon Sep 17 00:00:00 2001 From: "stripe-openapi[bot]" <105521251+stripe-openapi[bot]@users.noreply.github.com> Date: Mon, 15 Apr 2024 23:16:37 -0700 Subject: [PATCH] Update generated code (#2064) * Update generated code for v951 * Update generated code for v954 * Update generated code for v955 * Update generated code for v956 * Update generated code for v957 * Update generated code for v958 * Update generated code for v960 * Update generated code for v961 --------- Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com> --- OPENAPI_VERSION | 2 +- types/AccountSessions.d.ts | 49 +++++++++++++++- types/AccountSessionsResource.d.ts | 57 +++++++++++++++++++ types/Billing/MeterEventsResource.d.ts | 10 ++-- types/Disputes.d.ts | 5 +- .../ActiveEntitlementSummaries.d.ts | 32 +++++++++++ types/EventTypes.d.ts | 20 +++++++ types/Events.d.ts | 1 + types/Forwarding/Requests.d.ts | 11 +--- types/Forwarding/RequestsResource.d.ts | 5 -- types/Invoices.d.ts | 8 +-- types/PaymentIntents.d.ts | 15 +++-- types/PaymentIntentsResource.d.ts | 27 +++++++++ types/PaymentMethodConfigurations.d.ts | 36 ++++++++++++ .../PaymentMethodConfigurationsResource.d.ts | 50 ++++++++++++++++ types/SetupAttempts.d.ts | 8 +-- types/SetupIntents.d.ts | 16 +++--- types/WebhookEndpointsResource.d.ts | 2 + types/index.d.ts | 1 + 19 files changed, 309 insertions(+), 46 deletions(-) create mode 100644 types/Entitlements/ActiveEntitlementSummaries.d.ts diff --git a/OPENAPI_VERSION b/OPENAPI_VERSION index b18a87edcc..ea2fb0ba15 100644 --- a/OPENAPI_VERSION +++ b/OPENAPI_VERSION @@ -1 +1 @@ -v950 \ No newline at end of file +v961 \ No newline at end of file diff --git a/types/AccountSessions.d.ts b/types/AccountSessions.d.ts index e5d34a40e4..fb0fb07c92 100644 --- a/types/AccountSessions.d.ts +++ b/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 {} + } } } } diff --git a/types/AccountSessionsResource.d.ts b/types/AccountSessionsResource.d.ts index 2257106179..abee3d1b56 100644 --- a/types/AccountSessionsResource.d.ts +++ b/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 {} + } } } diff --git a/types/Billing/MeterEventsResource.d.ts b/types/Billing/MeterEventsResource.d.ts index 4ecc71e281..29f53b9ad1 100644 --- a/types/Billing/MeterEventsResource.d.ts +++ b/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 { diff --git a/types/Disputes.d.ts b/types/Disputes.d.ts index 63f25ca60c..68512b56b2 100644 --- a/types/Disputes.d.ts +++ b/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. diff --git a/types/Entitlements/ActiveEntitlementSummaries.d.ts b/types/Entitlements/ActiveEntitlementSummaries.d.ts new file mode 100644 index 0000000000..b0b5d7649b --- /dev/null +++ b/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; + + /** + * Has the value `true` if the object exists in live mode or the value `false` if the object exists in test mode. + */ + livemode: boolean; + } + } + } +} diff --git a/types/EventTypes.d.ts b/types/EventTypes.d.ts index 3e4965b10b..320e03419b 100644 --- a/types/EventTypes.d.ts +++ b/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. */ diff --git a/types/Events.d.ts b/types/Events.d.ts index d495f49926..7db871b91f 100644 --- a/types/Events.d.ts +++ b/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' diff --git a/types/Forwarding/Requests.d.ts b/types/Forwarding/Requests.d.ts index 2bccf50d3b..278f206228 100644 --- a/types/Forwarding/Requests.d.ts +++ b/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. */ diff --git a/types/Forwarding/RequestsResource.d.ts b/types/Forwarding/RequestsResource.d.ts index bb0042df5e..7ab588437a 100644 --- a/types/Forwarding/RequestsResource.d.ts +++ b/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. */ diff --git a/types/Invoices.d.ts b/types/Invoices.d.ts index 8a7ce25936..0736569370 100644 --- a/types/Invoices.d.ts +++ b/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; diff --git a/types/PaymentIntents.d.ts b/types/PaymentIntents.d.ts index 2521782f4b..537d66ed45 100644 --- a/types/PaymentIntents.d.ts +++ b/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; diff --git a/types/PaymentIntentsResource.d.ts b/types/PaymentIntentsResource.d.ts index 4371c9e428..bff040a7fa 100644 --- a/types/PaymentIntentsResource.d.ts +++ b/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. * diff --git a/types/PaymentMethodConfigurations.d.ts b/types/PaymentMethodConfigurations.d.ts index 110e884e93..74f14b6277 100644 --- a/types/PaymentMethodConfigurations.d.ts +++ b/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. diff --git a/types/PaymentMethodConfigurationsResource.d.ts b/types/PaymentMethodConfigurationsResource.d.ts index 076b944e7d..8a573f5dbc 100644 --- a/types/PaymentMethodConfigurationsResource.d.ts +++ b/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. diff --git a/types/SetupAttempts.d.ts b/types/SetupAttempts.d.ts index 96669d3e70..39cb5bc7de 100644 --- a/types/SetupAttempts.d.ts +++ b/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; diff --git a/types/SetupIntents.d.ts b/types/SetupIntents.d.ts index bbd8273f47..b24edb5e54 100644 --- a/types/SetupIntents.d.ts +++ b/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; diff --git a/types/WebhookEndpointsResource.d.ts b/types/WebhookEndpointsResource.d.ts index 5040e9a0f9..719fe0fd96 100644 --- a/types/WebhookEndpointsResource.d.ts +++ b/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' diff --git a/types/index.d.ts b/types/index.d.ts index 051a8e6b12..020588e5e8 100644 --- a/types/index.d.ts +++ b/types/index.d.ts @@ -161,6 +161,7 @@ /// /// /// +/// /// /// ///