Update generated code

API_VERSION

@@ -1 +1 @@
-368be7755d15d02a1038325c7d159703b01662b0
+88aa59022b32620f4d66d6196e3b42d5a0f86bbb

OPENAPI_VERSION

@@ -1 +1 @@
-v2128
+v2140

stripe/_account_link.py

@@ -15,7 +15,7 @@ class AccountLink(CreateableAPIResource["AccountLink"]):
     Account Links are the means by which a Connect platform grants a connected account permission to access
     Stripe-hosted applications, such as Connect Onboarding.
 
-    Related guide: [Connect Onboarding](https://stripe.com/docs/connect/custom/hosted-onboarding)
+    Related guide: [Connect Onboarding](https://docs.stripe.com/connect/custom/hosted-onboarding)
     """
 
     OBJECT_NAME: ClassVar[Literal["account_link"]] = "account_link"

stripe/_account_session.py

@@ -19,7 +19,7 @@ class AccountSession(CreateableAPIResource["AccountSession"]):
     to your user. Do not save AccountSessions to your database as they expire relatively
     quickly, and cannot be used more than once.
 
-    Related guide: [Connect embedded components](https://stripe.com/docs/connect/get-started-connect-embedded-components)
+    Related guide: [Connect embedded components](https://docs.stripe.com/connect/get-started-connect-embedded-components)
     """
 
     OBJECT_NAME: ClassVar[Literal["account_session"]] = "account_session"
@@ -463,7 +463,7 @@ class Features(StripeObject):
 
     The client secret can be used to provide access to `account` from your frontend. It should not be stored, logged, or exposed to anyone other than the connected account. Make sure that you have TLS enabled on any page that includes the client secret.
 
-    Refer to our docs to [setup Connect embedded components](https://stripe.com/docs/connect/get-started-connect-embedded-components) and learn about how `client_secret` should be handled.
+    Refer to our docs to [setup Connect embedded components](https://docs.stripe.com/connect/get-started-connect-embedded-components) and learn about how `client_secret` should be handled.
     """
     components: Components
     expires_at: int

stripe/_api_version.py

@@ -1,5 +1,5 @@
 # -*- coding: utf-8 -*-
 # File generated from our OpenAPI spec
 class _ApiVersion:
-    CURRENT = "2025-11-17.clover"
+    CURRENT = "2025-12-15.clover"
     CURRENT_MAJOR = "clover"

stripe/_application_fee_refund.py

@@ -17,7 +17,7 @@ class ApplicationFeeRefund(UpdateableAPIResource["ApplicationFeeRefund"]):
     has previously been created but not yet refunded. Funds will be refunded to
     the Stripe account from which the fee was originally collected.
 
-    Related guide: [Refunding application fees](https://stripe.com/docs/connect/destination-charges#refunding-app-fee)
+    Related guide: [Refunding application fees](https://docs.stripe.com/connect/destination-charges#refunding-app-fee)
     """
 
     OBJECT_NAME: ClassVar[Literal["fee_refund"]] = "fee_refund"
@@ -47,7 +47,7 @@ class ApplicationFeeRefund(UpdateableAPIResource["ApplicationFeeRefund"]):
     """
     metadata: Optional[Dict[str, str]]
     """
-    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.
     """
     object: Literal["fee_refund"]
     """

stripe/_balance.py

@@ -16,7 +16,7 @@ class Balance(SingletonAPIResource["Balance"]):
 
     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)
     """
 
     OBJECT_NAME: ClassVar[Literal["balance"]] = "balance"
@@ -256,7 +256,7 @@ class SourceTypes(StripeObject):
 
     available: List[Available]
     """
-    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.
     """
     connect_reserved: Optional[List[ConnectReserved]]
     """

stripe/_balance_settings.py

@@ -59,7 +59,7 @@ class Schedule(StripeObject):
             """
             schedule: Optional[Schedule]
             """
-            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.
             """
             statement_descriptor: Optional[str]
             """

stripe/_balance_transaction.py

@@ -39,7 +39,7 @@ class BalanceTransaction(ListableAPIResource["BalanceTransaction"]):
     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)
     """
 
     OBJECT_NAME: ClassVar[Literal["balance_transaction"]] = (

stripe/_bank_account.py

@@ -151,19 +151,19 @@ class Error(StripeObject):
 
         currently_due: Optional[List[str]]
         """
-        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.
         """
         errors: Optional[List[Error]]
         """
-        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.
         """
         past_due: Optional[List[str]]
         """
-        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.
         """
         pending_verification: Optional[List[str]]
         """
-        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.
         """
         _inner_class_types = {"errors": Error}
 
@@ -282,19 +282,19 @@ class Error(StripeObject):
 
         currently_due: Optional[List[str]]
         """
-        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.
         """
         errors: Optional[List[Error]]
         """
-        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.
         """
         past_due: Optional[List[str]]
         """
-        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.
         """
         pending_verification: Optional[List[str]]
         """
-        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.
         """
         _inner_class_types = {"errors": Error}
 
@@ -348,7 +348,7 @@ class Error(StripeObject):
     """
     future_requirements: Optional[FutureRequirements]
     """
-    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.
     """
     id: str
     """
@@ -360,7 +360,7 @@ class Error(StripeObject):
     """
     metadata: Optional[Dict[str, str]]
     """
-    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.
     """
     object: Literal["bank_account"]
     """

stripe/_capability.py

@@ -13,7 +13,7 @@ class Capability(UpdateableAPIResource["Capability"]):
     """
     This is an object representing a capability for a Stripe account.
 
-    Related guide: [Account capabilities](https://stripe.com/docs/connect/account-capabilities)
+    Related guide: [Account capabilities](https://docs.stripe.com/connect/account-capabilities)
     """
 
     OBJECT_NAME: ClassVar[Literal["capability"]] = "capability"
@@ -22,11 +22,11 @@ class FutureRequirements(StripeObject):
         class Alternative(StripeObject):
             alternative_fields_due: List[str]
             """
-            Fields that can be provided to satisfy all fields in `original_fields_due`.
+            Fields that can be provided to resolve all fields in `original_fields_due`.
             """
             original_fields_due: List[str]
             """
-            Fields that are due and can be satisfied by providing all fields in `alternative_fields_due`.
+            Fields that are due and can be resolved by providing all fields in `alternative_fields_due`.
             """
 
         class Error(StripeObject):
@@ -143,15 +143,15 @@ class Error(StripeObject):
 
         alternatives: Optional[List[Alternative]]
         """
-        Fields that are due and can be satisfied by providing the corresponding alternative fields instead.
+        Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same `original_fields_due`. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing `original_fields_due` again also serves as a pathway for attempting to resolve the fields.
         """
         current_deadline: Optional[int]
         """
         Date on which `future_requirements` becomes the main `requirements` hash and `future_requirements` becomes empty. After the transition, `currently_due` requirements may immediately become `past_due`, but the account may also be given a grace period depending on the capability's enablement state prior to transitioning.
         """
         currently_due: List[str]
         """
-        Fields that need to be collected to keep the capability enabled. If not collected by `future_requirements[current_deadline]`, these fields will transition to the main `requirements` hash.
+        Fields that need to be resolved to keep the capability enabled. If not resolved by `future_requirements[current_deadline]`, these fields will transition to the main `requirements` hash.
         """
         disabled_reason: Optional[
             Literal[
@@ -172,31 +172,31 @@ class Error(StripeObject):
         """
         errors: List[Error]
         """
-        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.
         """
         eventually_due: List[str]
         """
         Fields you must collect when all thresholds are reached. As they become required, they appear in `currently_due` as well.
         """
         past_due: List[str]
         """
-        Fields that weren't collected by `requirements.current_deadline`. These fields need to be collected to enable the capability on the account. New fields will never appear here; `future_requirements.past_due` will always be a subset of `requirements.past_due`.
+        Fields that haven't been resolved by `requirements.current_deadline`. These fields need to be resolved to enable the capability on the account. `future_requirements.past_due` is a subset of `requirements.past_due`.
         """
         pending_verification: List[str]
         """
-        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` or `currently_due`. Fields might appear in `eventually_due` or `currently_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.
         """
         _inner_class_types = {"alternatives": Alternative, "errors": Error}
 
     class Requirements(StripeObject):
         class Alternative(StripeObject):
             alternative_fields_due: List[str]
             """
-            Fields that can be provided to satisfy all fields in `original_fields_due`.
+            Fields that can be provided to resolve all fields in `original_fields_due`.
             """
             original_fields_due: List[str]
             """
-            Fields that are due and can be satisfied by providing all fields in `alternative_fields_due`.
+            Fields that are due and can be resolved by providing all fields in `alternative_fields_due`.
             """
 
         class Error(StripeObject):
@@ -313,15 +313,15 @@ class Error(StripeObject):
 
         alternatives: Optional[List[Alternative]]
         """
-        Fields that are due and can be satisfied by providing the corresponding alternative fields instead.
+        Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same `original_fields_due`. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing `original_fields_due` again also serves as a pathway for attempting to resolve the fields.
         """
         current_deadline: Optional[int]
         """
         The date by which all required account information must be both submitted and verified. This includes fields listed in `currently_due` as well as those in `pending_verification`. If any required information is missing or unverified by this date, the account may be disabled. Note that `current_deadline` may change if additional `currently_due` requirements are requested.
         """
         currently_due: List[str]
         """
-        Fields that need to be collected to keep the capability enabled. If not collected by `current_deadline`, these fields appear in `past_due` as well, and the capability is disabled.
+        Fields that need to be resolved to keep the capability enabled. If not resolved by `current_deadline`, these fields will appear in `past_due` as well, and the capability is disabled.
         """
         disabled_reason: Optional[
             Literal[
@@ -338,23 +338,23 @@ class Error(StripeObject):
             ]
         ]
         """
-        Description of why the capability is disabled. [Learn more about handling verification issues](https://stripe.com/docs/connect/handling-api-verification).
+        Description of why the capability is disabled. [Learn more about handling verification issues](https://docs.stripe.com/connect/handling-api-verification).
         """
         errors: List[Error]
         """
-        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.
         """
         eventually_due: List[str]
         """
         Fields you must collect when all thresholds are reached. As they become required, they appear in `currently_due` as well, and `current_deadline` becomes set.
         """
         past_due: List[str]
         """
-        Fields that weren't collected by `current_deadline`. These fields need to be collected to enable the capability on the account.
+        Fields that haven't been resolved by `current_deadline`. These fields need to be resolved to enable the capability on the account.
         """
         pending_verification: List[str]
         """
-        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.
         """
         _inner_class_types = {"alternatives": Alternative, "errors": Error}