Update generated code (#1277)

* Update generated code for v570

* Update generated code for v573

* Update generated code for v576

* Update generated code for v580

---------

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

OPENAPI_VERSION

@@ -1 +1 @@
-v563
+v580

lib/stripe/object_types.rb

@@ -59,6 +59,7 @@ def self.object_names_to_classes
         Issuing::Card::OBJECT_NAME => Issuing::Card,
         Issuing::Cardholder::OBJECT_NAME => Issuing::Cardholder,
         Issuing::Dispute::OBJECT_NAME => Issuing::Dispute,
+        Issuing::Token::OBJECT_NAME => Issuing::Token,
         Issuing::Transaction::OBJECT_NAME => Issuing::Transaction,
         LineItem::OBJECT_NAME => LineItem,
         LoginLink::OBJECT_NAME => LoginLink,

lib/stripe/resources.rb

@@ -46,6 +46,7 @@
 require "stripe/resources/issuing/card"
 require "stripe/resources/issuing/cardholder"
 require "stripe/resources/issuing/dispute"
+require "stripe/resources/issuing/token"
 require "stripe/resources/issuing/transaction"
 require "stripe/resources/line_item"
 require "stripe/resources/login_link"

lib/stripe/resources/issuing/token.rb

@@ -0,0 +1,14 @@
+# File generated from our OpenAPI spec
+# frozen_string_literal: true
+
+module Stripe
+  module Issuing
+    # An issuing token object is created when an issued card is added to a digital wallet. As a [card issuer](https://stripe.com/docs/issuing), you can view and manage these tokens through Stripe.
+    class Token < APIResource
+      extend Stripe::APIOperations::List
+      include Stripe::APIOperations::Save
+
+      OBJECT_NAME = "issuing.token"
+    end
+  end
+end

lib/stripe/resources/payment_method_configuration.rb

@@ -2,7 +2,20 @@
 # frozen_string_literal: true
 
 module Stripe
-  # An object detailing payment method configurations.
+  # PaymentMethodConfigurations control which payment methods are displayed to your customers when you don't explicitly specify payment method types. You can have multiple configurations with different sets of payment methods for different scenarios.
+  #
+  # There are two types of PaymentMethodConfigurations. Which is used depends on the [charge type](https://stripe.com/docs/connect/charges):
+  #
+  # **Direct** configurations apply to payments created on your account, including Connect destination charges, Connect separate charges and transfers, and payments not involving Connect.
+  #
+  # **Child** configurations apply to payments created on your connected accounts using direct charges, and charges with the on_behalf_of parameter.
+  #
+  # Child configurations have a `parent` that sets default values and controls which settings connected accounts may override. You can specify a parent ID at payment time, and Stripe will automatically resolve the connected account's associated child configuration. Parent configurations are [managed in the dashboard](https://dashboard.stripe.com/settings/payment_methods/connected_accounts) and are not available in this API.
+  #
+  # Related guides:
+  # - [Payment Method Configurations API](https://stripe.com/docs/connect/payment-method-configurations)
+  # - [Multiple payment method configurations on dynamic payment methods](https://stripe.com/docs/payments/multiple-payment-method-configs)
+  # - [Multiple configurations for your Connect accounts](https://stripe.com/docs/connect/multiple-payment-method-configurations)
   class PaymentMethodConfiguration < APIResource
     extend Stripe::APIOperations::Create
     extend Stripe::APIOperations::List

lib/stripe/resources/setup_intent.rb

@@ -3,25 +3,24 @@
 
 module Stripe
   # A SetupIntent guides you through the process of setting up and saving a customer's payment credentials for future payments.
-  # For example, you could use a SetupIntent to set up and save your customer's card without immediately collecting a payment.
+  # For example, you can use a SetupIntent to set up and save your customer's card without immediately collecting a payment.
   # Later, you can use [PaymentIntents](https://stripe.com/docs/api#payment_intents) to drive the payment flow.
   #
-  # Create a SetupIntent as soon as you're ready to collect your customer's payment credentials.
-  # Do not maintain long-lived, unconfirmed SetupIntents as they may no longer be valid.
-  # The SetupIntent then transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
+  # Create a SetupIntent when you're ready to collect your customer's payment credentials.
+  # Don't maintain long-lived, unconfirmed SetupIntents because they might not be valid.
+  # The SetupIntent transitions through multiple [statuses](https://stripe.com/docs/payments/intents#intent-statuses) as it guides
   # you through the setup process.
   #
   # Successful SetupIntents result in payment credentials that are optimized for future payments.
-  # For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) may need to be run through
-  # [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) at the time of payment method collection
-  # in order to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
-  # If the SetupIntent is used with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer), upon success,
-  # it will automatically attach the resulting payment method to that Customer.
+  # For example, cardholders in [certain regions](https://stripe.com/guides/strong-customer-authentication) might need to be run through
+  # [Strong Customer Authentication](https://stripe.com/docs/strong-customer-authentication) during payment method collection
+  # to streamline later [off-session payments](https://stripe.com/docs/payments/setup-intents).
+  # If you use the SetupIntent with a [Customer](https://stripe.com/docs/api#setup_intent_object-customer),
+  # it automatically attaches the resulting payment method to that Customer after successful setup.
   # We recommend using SetupIntents or [setup_future_usage](https://stripe.com/docs/api#payment_intent_object-setup_future_usage) on
-  # PaymentIntents to save payment methods in order to prevent saving invalid or unoptimized payment methods.
+  # PaymentIntents to save payment methods to prevent saving invalid or unoptimized payment methods.
   #
-  # By using SetupIntents, you ensure that your customers experience the minimum set of required friction,
-  # even as regulations change over time.
+  # By using SetupIntents, you can reduce friction for your customers, even as regulations change over time.
   #
   # Related guide: [Setup Intents API](https://stripe.com/docs/payments/setup-intents)
   class SetupIntent < APIResource

lib/stripe/resources/token.rb

@@ -5,21 +5,21 @@ module Stripe
   # Tokenization is the process Stripe uses to collect sensitive card or bank
   # account details, or personally identifiable information (PII), directly from
   # your customers in a secure manner. A token representing this information is
-  # returned to your server to use. You should use our
+  # returned to your server to use. Use our
   # [recommended payments integrations](https://stripe.com/docs/payments) to perform this process
-  # client-side. This ensures that no sensitive card data touches your server,
+  # on the client-side. This guarantees that no sensitive card data touches your server,
   # and allows your integration to operate in a PCI-compliant way.
   #
-  # If you cannot use client-side tokenization, you can also create tokens using
-  # the API with either your publishable or secret API key. Keep in mind that if
-  # your integration uses this method, you are responsible for any PCI compliance
-  # that may be required, and you must keep your secret API key safe. Unlike with
-  # client-side tokenization, your customer's information is not sent directly to
-  # Stripe, so we cannot determine how it is handled or stored.
+  # If you can't use client-side tokenization, you can also create tokens using
+  # the API with either your publishable or secret API key. If
+  # your integration uses this method, you're responsible for any PCI compliance
+  # that it might require, and you must keep your secret API key safe. Unlike with
+  # client-side tokenization, your customer's information isn't sent directly to
+  # Stripe, so we can't determine how it's handled or stored.
   #
-  # Tokens cannot be stored or used more than once. To store card or bank account
-  # information for later use, you can create [Customer](https://stripe.com/docs/api#customers)
-  # objects or [Custom accounts](https://stripe.com/docs/api#external_accounts). Note that
+  # You can't store or use tokens more than once. To store card or bank account
+  # information for later use, create [Customer](https://stripe.com/docs/api#customers)
+  # objects or [Custom accounts](https://stripe.com/docs/api#external_accounts).
   # [Radar](https://stripe.com/docs/radar), our integrated solution for automatic fraud protection,
   # performs best with integrations that use client-side tokenization.
   class Token < APIResource