diff --git a/embedded/openapi/spec3.beta.sdk.json b/embedded/openapi/spec3.beta.sdk.json
index e80d4a18..d4890a73 100644
--- a/embedded/openapi/spec3.beta.sdk.json
+++ b/embedded/openapi/spec3.beta.sdk.json
@@ -7624,6 +7624,16 @@
           "installments": {
             "$ref": "#/components/schemas/checkout_card_installments_options"
           },
+          "request_three_d_secure": {
+            "description": "We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and [other requirements](https://stripe.com/docs/strong-customer-authentication). However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. If not provided, this value defaults to `automatic`. Read our guide on [manually requesting 3D Secure](https://stripe.com/docs/payments/3d-secure/authentication-flow#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+            "enum": [
+              "any",
+              "automatic",
+              "challenge"
+            ],
+            "type": "string",
+            "x-stripeBypassValidation": true
+          },
           "setup_future_usage": {
             "description": "Indicates that you intend to make future payments with this PaymentIntent's payment method.\n\nProviding this parameter will [attach the payment method](https://stripe.com/docs/payments/save-during-payment) to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be [attached](https://stripe.com/docs/api/payment_methods/attach) to a Customer after the transaction completes.\n\nWhen processing card payments, Stripe also uses `setup_future_usage` to dynamically optimize your payment flow and comply with regional legislation and network rules, such as [SCA](https://stripe.com/docs/strong-customer-authentication).",
             "enum": [
@@ -7644,6 +7654,9 @@
             "type": "string"
           }
         },
+        "required": [
+          "request_three_d_secure"
+        ],
         "title": "CheckoutCardPaymentMethodOptions",
         "type": "object",
         "x-expandableFields": [
@@ -84620,6 +84633,16 @@
                             "title": "installments_param",
                             "type": "object"
                           },
+                          "request_three_d_secure": {
+                            "description": "We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and [other requirements](https://stripe.com/docs/strong-customer-authentication). However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. If not provided, this value defaults to `automatic`. Read our guide on [manually requesting 3D Secure](https://stripe.com/docs/payments/3d-secure/authentication-flow#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+                            "enum": [
+                              "any",
+                              "automatic",
+                              "challenge"
+                            ],
+                            "type": "string",
+                            "x-stripeBypassValidation": true
+                          },
                           "setup_future_usage": {
                             "description": "Indicates that you intend to make future payments with this PaymentIntent's payment method.\n\nProviding this parameter will [attach the payment method](https://stripe.com/docs/payments/save-during-payment) to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be [attached](https://stripe.com/docs/api/payment_methods/attach) to a Customer after the transaction completes.\n\nWhen processing card payments, Stripe also uses `setup_future_usage` to dynamically optimize your payment flow and comply with regional legislation and network rules, such as [SCA](https://stripe.com/docs/strong-customer-authentication).",
                             "enum": [
diff --git a/embedded/openapi/spec3.json b/embedded/openapi/spec3.json
index b6d304cb..d4675bae 100644
--- a/embedded/openapi/spec3.json
+++ b/embedded/openapi/spec3.json
@@ -5149,6 +5149,16 @@
           "installments": {
             "$ref": "#/components/schemas/checkout_card_installments_options"
           },
+          "request_three_d_secure": {
+            "description": "We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and [other requirements](https://stripe.com/docs/strong-customer-authentication). However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. If not provided, this value defaults to `automatic`. Read our guide on [manually requesting 3D Secure](https://stripe.com/docs/payments/3d-secure/authentication-flow#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+            "enum": [
+              "any",
+              "automatic",
+              "challenge"
+            ],
+            "type": "string",
+            "x-stripeBypassValidation": true
+          },
           "setup_future_usage": {
             "description": "Indicates that you intend to make future payments with this PaymentIntent's payment method.\n\nProviding this parameter will [attach the payment method](https://stripe.com/docs/payments/save-during-payment) to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be [attached](https://stripe.com/docs/api/payment_methods/attach) to a Customer after the transaction completes.\n\nWhen processing card payments, Stripe also uses `setup_future_usage` to dynamically optimize your payment flow and comply with regional legislation and network rules, such as [SCA](https://stripe.com/docs/strong-customer-authentication).",
             "enum": [
@@ -5169,6 +5179,9 @@
             "type": "string"
           }
         },
+        "required": [
+          "request_three_d_secure"
+        ],
         "title": "CheckoutCardPaymentMethodOptions",
         "type": "object",
         "x-expandableFields": [
@@ -61469,6 +61482,15 @@
                             "title": "installments_param",
                             "type": "object"
                           },
+                          "request_three_d_secure": {
+                            "enum": [
+                              "any",
+                              "automatic",
+                              "challenge"
+                            ],
+                            "type": "string",
+                            "x-stripeBypassValidation": true
+                          },
                           "setup_future_usage": {
                             "enum": [
                               "off_session",