Update OpenAPI specification

Author: stripe-openapi[bot]

openapi/spec3.beta.sdk.json

@@ -19163,7 +19163,7 @@ components:
             However, if you wish to request 3D Secure based on logic from your
             own fraud engine, provide this option. Read our guide on [manually
             requesting 3D
-            Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+            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:
@@ -31742,7 +31742,7 @@ components:
             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#manual-three-ds)
+            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:
@@ -49329,7 +49329,7 @@ components:
             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#manual-three-ds)
+            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:
@@ -52413,7 +52413,7 @@ components:
             However, if you wish to request 3D Secure based on logic from your
             own fraud engine, provide this option. Read our guide on [manually
             requesting 3D
-            Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+            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:
@@ -91573,7 +91573,7 @@ paths:
                                     based on logic from your own fraud engine,
                                     provide this option. Read our guide on
                                     [manually requesting 3D
-                                    Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                                    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.
@@ -103002,7 +103002,7 @@ paths:
                                     based on logic from your own fraud engine,
                                     provide this option. Read our guide on
                                     [manually requesting 3D
-                                    Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                                    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.
@@ -121694,7 +121694,7 @@ paths:
                                 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#manual-three-ds)
+                                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:
@@ -126559,7 +126559,7 @@ paths:
                                 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#manual-three-ds)
+                                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:
@@ -132317,7 +132317,7 @@ paths:
                                 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#manual-three-ds)
+                                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:
@@ -154775,7 +154775,7 @@ paths:
                             option. If not provided, this value defaults to
                             `automatic`. Read our guide on [manually requesting
                             3D
-                            Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                            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:
@@ -156284,7 +156284,7 @@ paths:
                             option. If not provided, this value defaults to
                             `automatic`. Read our guide on [manually requesting
                             3D
-                            Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                            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:
@@ -157805,7 +157805,7 @@ paths:
                             option. If not provided, this value defaults to
                             `automatic`. Read our guide on [manually requesting
                             3D
-                            Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                            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:
@@ -166237,7 +166237,7 @@ paths:
                                     based on logic from your own fraud engine,
                                     provide this option. Read our guide on
                                     [manually requesting 3D
-                                    Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                                    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.
@@ -168005,7 +168005,7 @@ paths:
                                     based on logic from your own fraud engine,
                                     provide this option. Read our guide on
                                     [manually requesting 3D
-                                    Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds)
+                                    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.

openapi/spec3.beta.sdk.yaml

@@ -13441,7 +13441,7 @@
             "$ref": "#/components/schemas/invoice_installments_card"
           },
           "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. Read our guide on [manually requesting 3D Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+            "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. 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",
@@ -23155,7 +23155,7 @@
             "type": "string"
           },
           "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#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+            "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",
@@ -36300,7 +36300,7 @@
             "type": "string"
           },
           "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#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+            "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",
@@ -38981,7 +38981,7 @@
             "type": "string"
           },
           "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. Read our guide on [manually requesting 3D Secure](https://stripe.com/docs/payments/3d-secure#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.",
+            "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. 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",