Update generated code for v358

OPENAPI_VERSION

@@ -1 +1 @@
-v354
+v358

lib/Charge.php

@@ -5,11 +5,10 @@
 namespace Stripe;
 
 /**
- * To charge a credit or a debit card, you create a <code>Charge</code> object. You can
- * retrieve and refund individual charges as well as list all charges. Charges
- * are identified by a unique, random ID.
- *
- * Related guide: <a href="https://stripe.com/docs/payments/accept-a-payment-charges">Accept a payment with the Charges API</a>
+ * The <code>Charge</code> object represents a single attempt to move money into your Stripe account.
+ * PaymentIntent confirmation is the most common way to create Charges, but transferring
+ * money to a different Stripe account through Connect also creates Charges.
+ * Some legacy payment flows create Charges directly, which is not recommended for new integrations.
  *
  * @property string $id Unique identifier for the object.
  * @property string $object String representing the object's type. Objects of the same type share the same value.

lib/Service/ChargeService.php

@@ -23,14 +23,15 @@ public function all($params = null, $opts = null)
     }
 
     /**
-     * Capture the payment of an existing, uncaptured, charge. This is the second half
-     * of the two-step payment flow, where first you <a href="#create_charge">created a
-     * charge</a> with the capture option set to false.
+     * Capture the payment of an existing, uncaptured charge that was created with the
+     * <code>capture</code> option set to false.
      *
      * Uncaptured payments expire a set number of days after they are created (<a
-     * href="/docs/charges/placing-a-hold">7 by default</a>). If they are not captured
-     * by that point in time, they will be marked as refunded and will no longer be
-     * capturable.
+     * href="/docs/charges/placing-a-hold">7 by default</a>), after which they are
+     * marked as refunded and capture attempts will fail.
+     *
+     * Don’t use this method to capture a PaymentIntent-initiated charge. Use <a
+     * href="/docs/api/payment_intents/capture">Capture a PaymentIntent</a>.
      *
      * @param string $id
      * @param null|array $params
@@ -46,11 +47,10 @@ public function capture($id, $params = null, $opts = null)
     }
 
     /**
-     * To charge a credit card or other payment source, you create a
-     * <code>Charge</code> object. If your API key is in test mode, the supplied
-     * payment source (e.g., card) won’t actually be charged, although everything else
-     * will occur as if in live mode. (Stripe assumes that the charge would have
-     * completed successfully).
+     * Use the <a href="/docs/api/payment_intents">Payment Intents API</a> to initiate
+     * a new payment instead of using this method. Confirmation of the PaymentIntent
+     * creates the <code>Charge</code> object used to request payment, so this method
+     * is limited to legacy integrations.
      *
      * @param null|array $params
      * @param null|array|\Stripe\Util\RequestOptions $opts

lib/Token.php

@@ -26,8 +26,6 @@
  * <a href="https://stripe.com/docs/radar">Radar</a>, our integrated solution for automatic fraud protection,
  * performs best with integrations that use client-side tokenization.
  *
- * Related guide: <a href="https://stripe.com/docs/payments/accept-a-payment-charges#web-create-token">Accept a payment with Charges and Tokens</a>
- *
  * @property string $id Unique identifier for the object.
  * @property string $object String representing the object's type. Objects of the same type share the same value.
  * @property null|\Stripe\BankAccount $bank_account <p>These bank accounts are payment methods on <code>Customer</code> objects.</p><p>On the other hand <a href="https://stripe.com/docs/api#external_accounts">External Accounts</a> are transfer destinations on <code>Account</code> objects for <a href="https://stripe.com/docs/connect/custom-accounts">Custom accounts</a>. They can be bank accounts or debit cards as well, and are documented in the links above.</p><p>Related guide: <a href="https://stripe.com/docs/payments/bank-debits-transfers">Bank debits and transfers</a></p>