diff --git a/embedded/openapi/spec3.beta.sdk.json b/embedded/openapi/spec3.beta.sdk.json
index dc689ce6..a253acc3 100644
--- a/embedded/openapi/spec3.beta.sdk.json
+++ b/embedded/openapi/spec3.beta.sdk.json
@@ -8880,6 +8880,15 @@
               ]
             }
           },
+          "payment_method_options": {
+            "anyOf": [
+              {
+                "$ref": "#/components/schemas/confirmation_tokens_resource_payment_method_options"
+              }
+            ],
+            "description": "Payment-method-specific configuration for this ConfirmationToken.",
+            "nullable": true
+          },
           "payment_method_preview": {
             "anyOf": [
               {
@@ -8929,6 +8938,7 @@
           "object",
           "payment_intent",
           "payment_method",
+          "payment_method_options",
           "payment_method_preview",
           "return_url",
           "setup_future_usage",
@@ -8940,6 +8950,7 @@
         "x-expandableFields": [
           "mandate_data",
           "payment_method",
+          "payment_method_options",
           "payment_method_preview",
           "shipping"
         ],
@@ -9026,6 +9037,45 @@
         "type": "object",
         "x-expandableFields": []
       },
+      "confirmation_tokens_resource_payment_method_options": {
+        "description": "Payment-method-specific configuration",
+        "properties": {
+          "card": {
+            "anyOf": [
+              {
+                "$ref": "#/components/schemas/confirmation_tokens_resource_payment_method_options_resource_card"
+              }
+            ],
+            "description": "This hash contains the card payment method options.",
+            "nullable": true
+          }
+        },
+        "required": [
+          "card"
+        ],
+        "title": "ConfirmationTokensResourcePaymentMethodOptions",
+        "type": "object",
+        "x-expandableFields": [
+          "card"
+        ]
+      },
+      "confirmation_tokens_resource_payment_method_options_resource_card": {
+        "description": "This hash contains the card payment method options.",
+        "properties": {
+          "cvc_token": {
+            "description": "The `cvc_update` Token collected from the Payment Element.",
+            "maxLength": 5000,
+            "nullable": true,
+            "type": "string"
+          }
+        },
+        "required": [
+          "cvc_token"
+        ],
+        "title": "ConfirmationTokensResourcePaymentMethodOptionsResourceCard",
+        "type": "object",
+        "x-expandableFields": []
+      },
       "confirmation_tokens_resource_payment_method_preview": {
         "description": "Details of the PaymentMethod collected by Payment Element",
         "properties": {
@@ -35047,6 +35097,10 @@
             "type": "string",
             "x-stripeBypassValidation": true
           },
+          "require_cvc_recollection": {
+            "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+            "type": "boolean"
+          },
           "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": [
@@ -35336,6 +35390,10 @@
           "installments": {
             "$ref": "#/components/schemas/payment_flows_installment_options"
           },
+          "require_cvc_recollection": {
+            "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+            "type": "boolean"
+          },
           "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": [
@@ -131095,6 +131153,10 @@
                                 "type": "string",
                                 "x-stripeBypassValidation": true
                               },
+                              "require_cvc_recollection": {
+                                "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+                                "type": "boolean"
+                              },
                               "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).\n\nIf `setup_future_usage` is already set and you are performing a request using a publishable key, you may only update the value from `on_session` to `off_session`.",
                                 "enum": [
@@ -134952,6 +135014,10 @@
                                 "type": "string",
                                 "x-stripeBypassValidation": true
                               },
+                              "require_cvc_recollection": {
+                                "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+                                "type": "boolean"
+                              },
                               "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).\n\nIf `setup_future_usage` is already set and you are performing a request using a publishable key, you may only update the value from `on_session` to `off_session`.",
                                 "enum": [
@@ -139745,6 +139811,10 @@
                                 "type": "string",
                                 "x-stripeBypassValidation": true
                               },
+                              "require_cvc_recollection": {
+                                "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+                                "type": "boolean"
+                              },
                               "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).\n\nIf `setup_future_usage` is already set and you are performing a request using a publishable key, you may only update the value from `on_session` to `off_session`.",
                                 "enum": [
diff --git a/embedded/openapi/spec3.json b/embedded/openapi/spec3.json
index 815ca6e3..7b2952b7 100644
--- a/embedded/openapi/spec3.json
+++ b/embedded/openapi/spec3.json
@@ -23150,6 +23150,10 @@
             "type": "string",
             "x-stripeBypassValidation": true
           },
+          "require_cvc_recollection": {
+            "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+            "type": "boolean"
+          },
           "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": [
@@ -23403,6 +23407,10 @@
           "installments": {
             "$ref": "#/components/schemas/payment_flows_installment_options"
           },
+          "require_cvc_recollection": {
+            "description": "When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter).",
+            "type": "boolean"
+          },
           "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": [
@@ -94671,6 +94679,9 @@
                                 "type": "string",
                                 "x-stripeBypassValidation": true
                               },
+                              "require_cvc_recollection": {
+                                "type": "boolean"
+                              },
                               "setup_future_usage": {
                                 "enum": [
                                   "",
@@ -97285,6 +97296,9 @@
                                 "type": "string",
                                 "x-stripeBypassValidation": true
                               },
+                              "require_cvc_recollection": {
+                                "type": "boolean"
+                              },
                               "setup_future_usage": {
                                 "enum": [
                                   "",
@@ -100038,6 +100052,9 @@
                                 "type": "string",
                                 "x-stripeBypassValidation": true
                               },
+                              "require_cvc_recollection": {
+                                "type": "boolean"
+                              },
                               "setup_future_usage": {
                                 "enum": [
                                   "",