Update OpenAPI specification

openapi/spec3.beta.sdk.json

@@ -55122,7 +55122,7 @@
         }
       },
       "setup_intent": {
-        "description": "A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.\nFor example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.\nLater, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.\n\nCreate a SetupIntent when you're ready to collect your customer's payment credentials.\nDon't maintain long-lived, unconfirmed SetupIntents because they might not be valid.\nThe SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides\nyou through the setup process.\n\nSuccessful SetupIntents result in payment credentials that are optimized for future payments.\nFor example, cardholders in [certain regions](/guides/strong-customer-authentication) might need to be run through\n[Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection\nto streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).\nIf you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),\nit automatically attaches the resulting payment method to that Customer after successful setup.\nWe recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on\nPaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.\n\nBy using SetupIntents, you can reduce friction for your customers, even as regulations change over time.\n\nRelated guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)",
+        "description": "A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.\nFor example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.\nLater, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.\n\nCreate a SetupIntent when you're ready to collect your customer's payment credentials.\nDon't maintain long-lived, unconfirmed SetupIntents because they might not be valid.\nThe SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides\nyou through the setup process.\n\nSuccessful SetupIntents result in payment credentials that are optimized for future payments.\nFor example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through\n[Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection\nto streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).\nIf you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),\nit automatically attaches the resulting payment method to that Customer after successful setup.\nWe recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on\nPaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.\n\nBy using SetupIntents, you can reduce friction for your customers, even as regulations change over time.\n\nRelated guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)",
         "properties": {
           "application": {
             "anyOf": [

openapi/spec3.beta.sdk.yaml

@@ -50166,7 +50166,7 @@ components:
         not be valid.
 
         The SetupIntent transitions through multiple
-        [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as
+        [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as
         it guides
 
         you through the setup process.
@@ -50176,15 +50176,15 @@ components:
         for future payments.
 
         For example, cardholders in [certain
-        regions](/guides/strong-customer-authentication) might need to be run
-        through
+        regions](https://stripe.com/guides/strong-customer-authentication) might
+        need to be run through
 
         [Strong Customer
-        Authentication](https://stripe.com/docs/strong-customer-authentication)
+        Authentication](https://docs.stripe.com/strong-customer-authentication)
         during payment method collection
 
         to streamline later [off-session
-        payments](https://stripe.com/docs/payments/setup-intents).
+        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),
@@ -50205,7 +50205,7 @@ components:
 
 
         Related guide: [Setup Intents
-        API](https://stripe.com/docs/payments/setup-intents)
+        API](https://docs.stripe.com/payments/setup-intents)
       properties:
         application:
           anyOf:

openapi/spec3.json

@@ -38078,7 +38078,7 @@
         "x-expandableFields": []
       },
       "setup_intent": {
-        "description": "A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.\nFor example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.\nLater, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.\n\nCreate a SetupIntent when you're ready to collect your customer's payment credentials.\nDon't maintain long-lived, unconfirmed SetupIntents because they might not be valid.\nThe SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides\nyou through the setup process.\n\nSuccessful SetupIntents result in payment credentials that are optimized for future payments.\nFor example, cardholders in [certain regions](/guides/strong-customer-authentication) might need to be run through\n[Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection\nto streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).\nIf you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),\nit automatically attaches the resulting payment method to that Customer after successful setup.\nWe recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on\nPaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.\n\nBy using SetupIntents, you can reduce friction for your customers, even as regulations change over time.\n\nRelated guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)",
+        "description": "A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.\nFor example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.\nLater, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.\n\nCreate a SetupIntent when you're ready to collect your customer's payment credentials.\nDon't maintain long-lived, unconfirmed SetupIntents because they might not be valid.\nThe SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides\nyou through the setup process.\n\nSuccessful SetupIntents result in payment credentials that are optimized for future payments.\nFor example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through\n[Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection\nto streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).\nIf you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),\nit automatically attaches the resulting payment method to that Customer after successful setup.\nWe recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on\nPaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.\n\nBy using SetupIntents, you can reduce friction for your customers, even as regulations change over time.\n\nRelated guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)",
         "properties": {
           "application": {
             "anyOf": [

openapi/spec3.sdk.json

@@ -46429,7 +46429,7 @@
         }
       },
       "setup_intent": {
-        "description": "A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.\nFor example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.\nLater, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.\n\nCreate a SetupIntent when you're ready to collect your customer's payment credentials.\nDon't maintain long-lived, unconfirmed SetupIntents because they might not be valid.\nThe SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides\nyou through the setup process.\n\nSuccessful SetupIntents result in payment credentials that are optimized for future payments.\nFor example, cardholders in [certain regions](/guides/strong-customer-authentication) might need to be run through\n[Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection\nto streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).\nIf you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),\nit automatically attaches the resulting payment method to that Customer after successful setup.\nWe recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on\nPaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.\n\nBy using SetupIntents, you can reduce friction for your customers, even as regulations change over time.\n\nRelated guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)",
+        "description": "A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.\nFor example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.\nLater, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.\n\nCreate a SetupIntent when you're ready to collect your customer's payment credentials.\nDon't maintain long-lived, unconfirmed SetupIntents because they might not be valid.\nThe SetupIntent transitions through multiple [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as it guides\nyou through the setup process.\n\nSuccessful SetupIntents result in payment credentials that are optimized for future payments.\nFor example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through\n[Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection\nto streamline later [off-session payments](https://docs.stripe.com/payments/setup-intents).\nIf you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),\nit automatically attaches the resulting payment method to that Customer after successful setup.\nWe recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on\nPaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.\n\nBy using SetupIntents, you can reduce friction for your customers, even as regulations change over time.\n\nRelated guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents)",
         "properties": {
           "application": {
             "anyOf": [

openapi/spec3.sdk.yaml

@@ -42452,7 +42452,7 @@ components:
         not be valid.
 
         The SetupIntent transitions through multiple
-        [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as
+        [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as
         it guides
 
         you through the setup process.
@@ -42462,15 +42462,15 @@ components:
         for future payments.
 
         For example, cardholders in [certain
-        regions](/guides/strong-customer-authentication) might need to be run
-        through
+        regions](https://stripe.com/guides/strong-customer-authentication) might
+        need to be run through
 
         [Strong Customer
-        Authentication](https://stripe.com/docs/strong-customer-authentication)
+        Authentication](https://docs.stripe.com/strong-customer-authentication)
         during payment method collection
 
         to streamline later [off-session
-        payments](https://stripe.com/docs/payments/setup-intents).
+        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),
@@ -42491,7 +42491,7 @@ components:
 
 
         Related guide: [Setup Intents
-        API](https://stripe.com/docs/payments/setup-intents)
+        API](https://docs.stripe.com/payments/setup-intents)
       properties:
         application:
           anyOf:

openapi/spec3.yaml

@@ -35853,7 +35853,7 @@ components:
         not be valid.
 
         The SetupIntent transitions through multiple
-        [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as
+        [statuses](https://docs.stripe.com/payments/intents#intent-statuses) as
         it guides
 
         you through the setup process.
@@ -35863,15 +35863,15 @@ components:
         for future payments.
 
         For example, cardholders in [certain
-        regions](/guides/strong-customer-authentication) might need to be run
-        through
+        regions](https://stripe.com/guides/strong-customer-authentication) might
+        need to be run through
 
         [Strong Customer
-        Authentication](https://stripe.com/docs/strong-customer-authentication)
+        Authentication](https://docs.stripe.com/strong-customer-authentication)
         during payment method collection
 
         to streamline later [off-session
-        payments](https://stripe.com/docs/payments/setup-intents).
+        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),
@@ -35892,7 +35892,7 @@ components:
 
 
         Related guide: [Setup Intents
-        API](https://stripe.com/docs/payments/setup-intents)
+        API](https://docs.stripe.com/payments/setup-intents)
       properties:
         application:
           anyOf: