Update OpenAPI specification

openapi/spec3.beta.sdk.json

@@ -5967,7 +5967,7 @@
                 "$ref": "#/components/schemas/deleted_customer"
               }
             ],
-            "description": "The ID of the customer for this Session.\nFor Checkout Sessions in `payment` or `subscription` mode, Checkout\nwill create a new customer object based on information provided\nduring the payment flow unless an existing customer was provided when\nthe Session was created.",
+            "description": "The ID of the customer for this Session.\nFor Checkout Sessions in `subscription` mode or Checkout Sessions with `customer_creation` set as `always` in `payment` mode, Checkout\nwill create a new customer object based on information provided\nduring the payment flow unless an existing customer was provided when\nthe Session was created.",
             "nullable": true,
             "x-expansionResources": {
               "oneOf": [
@@ -72430,7 +72430,7 @@
                     "type": "object"
                   },
                   "customer": {
-                    "description": "ID of an existing Customer, if one exists. In `payment` mode, the customer’s most recent card\npayment method will be used to prefill the email, name, card details, and billing address\non the Checkout page. In `subscription` mode, the customer’s [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)\nwill be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.\n\nIf the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.\nIf the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.\n\nIf blank for Checkout Sessions in `payment` or `subscription` mode, Checkout will create a new Customer object based on information provided during the payment flow.\n\nYou can set [`payment_intent_data.setup_future_usage`](https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage) to have Checkout automatically attach the payment method to the Customer you pass in for future reuse.",
+                    "description": "ID of an existing Customer, if one exists. In `payment` mode, the customer’s most recent card\npayment method will be used to prefill the email, name, card details, and billing address\non the Checkout page. In `subscription` mode, the customer’s [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)\nwill be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.\n\nIf the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.\nIf the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.\n\nIf blank for Checkout Sessions in `subscription` mode or with `customer_creation` set as `always` in `payment` mode, Checkout will create a new Customer object based on information provided during the payment flow.\n\nYou can set [`payment_intent_data.setup_future_usage`](https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage) to have Checkout automatically attach the payment method to the Customer you pass in for future reuse.",
                     "maxLength": 5000,
                     "type": "string"
                   },

openapi/spec3.beta.sdk.yaml

@@ -5659,7 +5659,8 @@ components:
           description: >-
             The ID of the customer for this Session.
 
-            For Checkout Sessions in `payment` or `subscription` mode, Checkout
+            For Checkout Sessions in `subscription` mode or Checkout Sessions
+            with `customer_creation` set as `always` in `payment` mode, Checkout
 
             will create a new customer object based on information provided
 
@@ -65805,10 +65806,10 @@ paths:
                     set the email entered during the session on the Customer.
 
 
-                    If blank for Checkout Sessions in `payment` or
-                    `subscription` mode, Checkout will create a new Customer
-                    object based on information provided during the payment
-                    flow.
+                    If blank for Checkout Sessions in `subscription` mode or
+                    with `customer_creation` set as `always` in `payment` mode,
+                    Checkout will create a new Customer object based on
+                    information provided during the payment flow.
 
 
                     You can set

openapi/spec3.json

@@ -4145,7 +4145,7 @@
                 "$ref": "#/components/schemas/deleted_customer"
               }
             ],
-            "description": "The ID of the customer for this Session.\nFor Checkout Sessions in `payment` or `subscription` mode, Checkout\nwill create a new customer object based on information provided\nduring the payment flow unless an existing customer was provided when\nthe Session was created.",
+            "description": "The ID of the customer for this Session.\nFor Checkout Sessions in `subscription` mode or Checkout Sessions with `customer_creation` set as `always` in `payment` mode, Checkout\nwill create a new customer object based on information provided\nduring the payment flow unless an existing customer was provided when\nthe Session was created.",
             "nullable": true,
             "x-expansionResources": {
               "oneOf": [
@@ -55784,7 +55784,7 @@
                     "type": "object"
                   },
                   "customer": {
-                    "description": "ID of an existing Customer, if one exists. In `payment` mode, the customer’s most recent card\npayment method will be used to prefill the email, name, card details, and billing address\non the Checkout page. In `subscription` mode, the customer’s [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)\nwill be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.\n\nIf the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.\nIf the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.\n\nIf blank for Checkout Sessions in `payment` or `subscription` mode, Checkout will create a new Customer object based on information provided during the payment flow.\n\nYou can set [`payment_intent_data.setup_future_usage`](https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage) to have Checkout automatically attach the payment method to the Customer you pass in for future reuse.",
+                    "description": "ID of an existing Customer, if one exists. In `payment` mode, the customer’s most recent card\npayment method will be used to prefill the email, name, card details, and billing address\non the Checkout page. In `subscription` mode, the customer’s [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)\nwill be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.\n\nIf the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.\nIf the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.\n\nIf blank for Checkout Sessions in `subscription` mode or with `customer_creation` set as `always` in `payment` mode, Checkout will create a new Customer object based on information provided during the payment flow.\n\nYou can set [`payment_intent_data.setup_future_usage`](https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage) to have Checkout automatically attach the payment method to the Customer you pass in for future reuse.",
                     "maxLength": 5000,
                     "type": "string"
                   },

openapi/spec3.sdk.json

@@ -5068,7 +5068,7 @@
                 "$ref": "#/components/schemas/deleted_customer"
               }
             ],
-            "description": "The ID of the customer for this Session.\nFor Checkout Sessions in `payment` or `subscription` mode, Checkout\nwill create a new customer object based on information provided\nduring the payment flow unless an existing customer was provided when\nthe Session was created.",
+            "description": "The ID of the customer for this Session.\nFor Checkout Sessions in `subscription` mode or Checkout Sessions with `customer_creation` set as `always` in `payment` mode, Checkout\nwill create a new customer object based on information provided\nduring the payment flow unless an existing customer was provided when\nthe Session was created.",
             "nullable": true,
             "x-expansionResources": {
               "oneOf": [
@@ -62171,7 +62171,7 @@
                     "type": "object"
                   },
                   "customer": {
-                    "description": "ID of an existing Customer, if one exists. In `payment` mode, the customer’s most recent card\npayment method will be used to prefill the email, name, card details, and billing address\non the Checkout page. In `subscription` mode, the customer’s [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)\nwill be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.\n\nIf the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.\nIf the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.\n\nIf blank for Checkout Sessions in `payment` or `subscription` mode, Checkout will create a new Customer object based on information provided during the payment flow.\n\nYou can set [`payment_intent_data.setup_future_usage`](https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage) to have Checkout automatically attach the payment method to the Customer you pass in for future reuse.",
+                    "description": "ID of an existing Customer, if one exists. In `payment` mode, the customer’s most recent card\npayment method will be used to prefill the email, name, card details, and billing address\non the Checkout page. In `subscription` mode, the customer’s [default payment method](https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method)\nwill be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer's card details.\n\nIf the Customer already has a valid [email](https://stripe.com/docs/api/customers/object#customer_object-email) set, the email will be prefilled and not editable in Checkout.\nIf the Customer does not have a valid `email`, Checkout will set the email entered during the session on the Customer.\n\nIf blank for Checkout Sessions in `subscription` mode or with `customer_creation` set as `always` in `payment` mode, Checkout will create a new Customer object based on information provided during the payment flow.\n\nYou can set [`payment_intent_data.setup_future_usage`](https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage) to have Checkout automatically attach the payment method to the Customer you pass in for future reuse.",
                     "maxLength": 5000,
                     "type": "string"
                   },

openapi/spec3.sdk.yaml

@@ -4798,7 +4798,8 @@ components:
           description: >-
             The ID of the customer for this Session.
 
-            For Checkout Sessions in `payment` or `subscription` mode, Checkout
+            For Checkout Sessions in `subscription` mode or Checkout Sessions
+            with `customer_creation` set as `always` in `payment` mode, Checkout
 
             will create a new customer object based on information provided
 
@@ -56845,10 +56846,10 @@ paths:
                     set the email entered during the session on the Customer.
 
 
-                    If blank for Checkout Sessions in `payment` or
-                    `subscription` mode, Checkout will create a new Customer
-                    object based on information provided during the payment
-                    flow.
+                    If blank for Checkout Sessions in `subscription` mode or
+                    with `customer_creation` set as `always` in `payment` mode,
+                    Checkout will create a new Customer object based on
+                    information provided during the payment flow.
 
 
                     You can set

openapi/spec3.yaml

@@ -4028,7 +4028,8 @@ components:
           description: >-
             The ID of the customer for this Session.
 
-            For Checkout Sessions in `payment` or `subscription` mode, Checkout
+            For Checkout Sessions in `subscription` mode or Checkout Sessions
+            with `customer_creation` set as `always` in `payment` mode, Checkout
 
             will create a new customer object based on information provided
 
@@ -50082,10 +50083,10 @@ paths:
                     set the email entered during the session on the Customer.
 
 
-                    If blank for Checkout Sessions in `payment` or
-                    `subscription` mode, Checkout will create a new Customer
-                    object based on information provided during the payment
-                    flow.
+                    If blank for Checkout Sessions in `subscription` mode or
+                    with `customer_creation` set as `always` in `payment` mode,
+                    Checkout will create a new Customer object based on
+                    information provided during the payment flow.
 
 
                     You can set