OpenAPI Update (#724)

Update OpenAPI for 9355ce2e2140dfed7eada58e66decd3749165fcf

Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>

embedded/openapi/spec3.beta.sdk.json

@@ -17723,7 +17723,7 @@
         ]
       },
       "forwarding.request": {
-        "description": "Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.\nA config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with\nyour credentials in the config, and injects card details from the payment_method into the request.\n\nStripe redacts all sensitive fields and headers, including authentication credentials and card numbers,\nbefore storing the request and response data in the forwarding Request object, which are subject to a\n30-day retention period.\n\nYou can provide a Stripe idempotency key to make sure that requests with the same key result in only one\noutbound request. The Stripe idempotency key provided should be unique and different from any idempotency\nkeys provided on the underlying third-party request.\n\nForwarding Requests are synchronous requests that return a response or time out according to\nStripe’s limits.",
+        "description": "Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.\nA config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with\nyour credentials in the config, and injects card details from the payment_method into the request.\n\nStripe redacts all sensitive fields and headers, including authentication credentials and card numbers,\nbefore storing the request and response data in the forwarding Request object, which are subject to a\n30-day retention period.\n\nYou can provide a Stripe idempotency key to make sure that requests with the same key result in only one\noutbound request. The Stripe idempotency key provided should be unique and different from any idempotency\nkeys provided on the underlying third-party request.\n\nForwarding Requests are synchronous requests that return a response or time out according to\nStripe’s limits.\n\nRelated guide: [Forward card details to third-party API endpoints](https://docs.stripe.com/payments/forwarding).",
         "properties": {
           "config": {
             "description": "The Forwarding Config used when making the forwarded request. The config specifes the HTTP method, merchant credentials, connection settings, and supported destination URLs.",

embedded/openapi/spec3.json

@@ -11762,7 +11762,7 @@
         ]
       },
       "forwarding.request": {
-        "description": "Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.\nA config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with\nyour credentials in the config, and injects card details from the payment_method into the request.\n\nStripe redacts all sensitive fields and headers, including authentication credentials and card numbers,\nbefore storing the request and response data in the forwarding Request object, which are subject to a\n30-day retention period.\n\nYou can provide a Stripe idempotency key to make sure that requests with the same key result in only one\noutbound request. The Stripe idempotency key provided should be unique and different from any idempotency\nkeys provided on the underlying third-party request.\n\nForwarding Requests are synchronous requests that return a response or time out according to\nStripe’s limits.",
+        "description": "Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config.\nA config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with\nyour credentials in the config, and injects card details from the payment_method into the request.\n\nStripe redacts all sensitive fields and headers, including authentication credentials and card numbers,\nbefore storing the request and response data in the forwarding Request object, which are subject to a\n30-day retention period.\n\nYou can provide a Stripe idempotency key to make sure that requests with the same key result in only one\noutbound request. The Stripe idempotency key provided should be unique and different from any idempotency\nkeys provided on the underlying third-party request.\n\nForwarding Requests are synchronous requests that return a response or time out according to\nStripe’s limits.\n\nRelated guide: [Forward card details to third-party API endpoints](https://docs.stripe.com/payments/forwarding).",
         "properties": {
           "config": {
             "description": "The Forwarding Config used when making the forwarded request. The config specifes the HTTP method, merchant credentials, connection settings, and supported destination URLs.",