API Updates

OPENAPI_VERSION

@@ -1 +1 @@
-v173
+v174

lib/Checkout/Session.php

@@ -54,10 +54,10 @@
  * @property \Stripe\StripeObject $phone_number_collection
  * @property null|string $recovered_from The ID of the original expired Checkout Session that triggered the recovery flow.
  * @property null|string|\Stripe\SetupIntent $setup_intent The ID of the SetupIntent for Checkout Sessions in <code>setup</code> mode.
- * @property null|\Stripe\StripeObject $shipping Shipping information for this Checkout Session.
  * @property null|\Stripe\StripeObject $shipping_address_collection When set, provides configuration for Checkout to collect a shipping address from a customer.
+ * @property null|\Stripe\StripeObject $shipping_cost The details of the customer cost of shipping, including the customer chosen ShippingRate.
+ * @property null|\Stripe\StripeObject $shipping_details Shipping information for this Checkout Session.
  * @property \Stripe\StripeObject[] $shipping_options The shipping rate options applied to this Session.
- * @property null|string|\Stripe\ShippingRate $shipping_rate The ID of the ShippingRate for Checkout Sessions in <code>payment</code> mode.
  * @property null|string $status The status of the Checkout Session, one of <code>open</code>, <code>complete</code>, or <code>expired</code>.
  * @property null|string $submit_type Describes the type of transaction being performed by Checkout in order to customize relevant text on the page, such as the submit button. <code>submit_type</code> can only be specified on Checkout Sessions in <code>payment</code> mode, but not Checkout Sessions in <code>subscription</code> or <code>setup</code> mode.
  * @property null|string|\Stripe\Subscription $subscription The ID of the subscription for Checkout Sessions in <code>subscription</code> mode.

lib/Customer.php

@@ -19,7 +19,6 @@
  * @property null|\Stripe\CashBalance $cash_balance The current funds being held by Stripe on behalf of the customer. These funds can be applied towards payment intents with source "cash_balance".The settings[reconciliation_mode] field describes whether these funds are applied to such payment intents manually or automatically.
  * @property int $created Time at which the object was created. Measured in seconds since the Unix epoch.
  * @property null|string $currency Three-letter <a href="https://stripe.com/docs/currencies">ISO code for the currency</a> the customer can be charged in for recurring billing purposes.
- * @property null|string $default_currency The default three-letter <a href="https://stripe.com/docs/currencies">ISO code for the currency</a> that the customer will be charged in for billing purposes.
  * @property null|string|\Stripe\Account|\Stripe\BankAccount|\Stripe\Card|\Stripe\Source $default_source <p>ID of the default payment source for the customer.</p><p>If you are using payment methods created via the PaymentMethods API, see the <a href="https://stripe.com/docs/api/customers/object#customer_object-invoice_settings-default_payment_method">invoice_settings.default_payment_method</a> field instead.</p>
  * @property null|bool $delinquent <p>When the customer's latest invoice is billed by charging automatically, <code>delinquent</code> is <code>true</code> if the invoice's latest charge failed. When the customer's latest invoice is billed by sending an invoice, <code>delinquent</code> is <code>true</code> if the invoice isn't paid by its due date.</p><p>If an invoice is marked uncollectible by <a href="https://stripe.com/docs/billing/automatic-collection">dunning</a>, <code>delinquent</code> doesn't get reset to <code>false</code>.</p>
  * @property null|string $description An arbitrary string attached to the object. Often useful for displaying to users.

lib/Service/PaymentMethodService.php

@@ -31,10 +31,11 @@ public function all($params = null, $opts = null)
      * you use a <a href="/docs/api/setup_intents">SetupIntent</a> or a PaymentIntent
      * with <a
      * href="/docs/api/payment_intents/create#create_payment_intent-setup_future_usage">setup_future_usage</a>.
-     * These approaches will perform any necessary steps to ensure that the
-     * PaymentMethod can be used in a future payment. Using the
-     * <code>/v1/payment_methods/:id/attach</code> endpoint does not ensure that future
-     * payments can be made with the attached PaymentMethod. See <a
+     * These approaches will perform any necessary steps to set up the PaymentMethod
+     * for future payments. Using the <code>/v1/payment_methods/:id/attach</code>
+     * endpoint without first using a SetupIntent or PaymentIntent with
+     * <code>setup_future_usage</code> does not optimize the PaymentMethod for future
+     * use, which makes later declines and payment friction more likely. See <a
      * href="/docs/payments/payment-intents#future-usage">Optimizing cards for future
      * payments</a> for more information about setting up future payments.
      *

lib/Util/ApiVersion.php

@@ -6,5 +6,5 @@
 
 class ApiVersion
 {
-    const CURRENT = '2020-08-27';
+    const CURRENT = '2022-08-01';
 }