From f570962b6d8f848aaa8e6c10e1e6cd5375c8dabb Mon Sep 17 00:00:00 2001
From: "stripe-openapi[bot]"
 <105521251+stripe-openapi[bot]@users.noreply.github.com>
Date: Tue, 19 Dec 2023 18:14:34 +0000
Subject: [PATCH] OpenAPI Update (#580)

Update OpenAPI for e074b269a7fec4ec616fb2cc8d757f4e60478aea

Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com>
---
 embedded/openapi/spec3.beta.sdk.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/embedded/openapi/spec3.beta.sdk.json b/embedded/openapi/spec3.beta.sdk.json
index a34a41e8..73e605cd 100644
--- a/embedded/openapi/spec3.beta.sdk.json
+++ b/embedded/openapi/spec3.beta.sdk.json
@@ -9065,7 +9065,7 @@
         }
       },
       "confirmation_token": {
-        "description": "ConfirmationTokens help transport client side data collected by Stripe JS over\nto your server for confirming a PaymentIntent or SetupIntent. If the confirmation\nis successful, values present on the ConfirmationToken are written onto the Intent.",
+        "description": "ConfirmationTokens help transport client side data collected by Stripe JS over\nto your server for confirming a PaymentIntent or SetupIntent. If the confirmation\nis successful, values present on the ConfirmationToken are written onto the Intent.\n\nTo learn more or request access, visit the related guided: [Finalize payments on the server using Confirmation Tokens](https://stripe.com/docs/payments/finalize-payments-on-the-server-confirmation-tokens).",
         "properties": {
           "created": {
             "description": "Time at which the object was created. Measured in seconds since the Unix epoch.",