From 428797638445adb458f567587464b2192f479c06 Mon Sep 17 00:00:00 2001 From: "stripe-openapi[bot]" <105521251+stripe-openapi[bot]@users.noreply.github.com> Date: Mon, 15 Apr 2024 23:25:27 -0700 Subject: [PATCH] Update generated code (#1379) * Update generated code for v940 * Update generated code for v945 * Update generated code for v947 * Update generated code for v961 --------- Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com> Co-authored-by: Ramya Rao <100975018+ramya-stripe@users.noreply.github.com> --- OPENAPI_VERSION | 2 +- lib/stripe/resources/billing/meter.rb | 2 +- lib/stripe/resources/billing/meter_event_adjustment.rb | 2 +- lib/stripe/resources/forwarding/request.rb | 6 +++--- lib/stripe/resources/reversal.rb | 2 +- lib/stripe/resources/setup_intent.rb | 8 ++++---- lib/stripe/resources/usage_record.rb | 2 ++ 7 files changed, 13 insertions(+), 11 deletions(-) diff --git a/OPENAPI_VERSION b/OPENAPI_VERSION index d91517e1..ea2fb0ba 100644 --- a/OPENAPI_VERSION +++ b/OPENAPI_VERSION @@ -1 +1 @@ -v938 +v961 \ No newline at end of file diff --git a/lib/stripe/resources/billing/meter.rb b/lib/stripe/resources/billing/meter.rb index 49bcf2e0..e8a0c9a0 100644 --- a/lib/stripe/resources/billing/meter.rb +++ b/lib/stripe/resources/billing/meter.rb @@ -3,7 +3,7 @@ module Stripe module Billing - # A billing meter is a resource that allows you to track usage of a particular event. For example, you might create a billing meter to track the number of API calls made by a particular user. You can then use the billing meter to charge the user for the number of API calls they make. + # A billing meter is a resource that allows you to track usage of a particular event. For example, you might create a billing meter to track the number of API calls made by a particular user. You can then attach the billing meter to a price and attach the price to a subscription to charge the user for the number of API calls they make. class Meter < APIResource extend Stripe::APIOperations::Create extend Stripe::APIOperations::List diff --git a/lib/stripe/resources/billing/meter_event_adjustment.rb b/lib/stripe/resources/billing/meter_event_adjustment.rb index 1da80385..8cd34585 100644 --- a/lib/stripe/resources/billing/meter_event_adjustment.rb +++ b/lib/stripe/resources/billing/meter_event_adjustment.rb @@ -3,7 +3,7 @@ module Stripe module Billing - # A billing meter event adjustment represents the status of a meter event adjustment. + # A billing meter event adjustment is a resource that allows you to cancel a meter event. For example, you might create a billing meter event adjustment to cancel a meter event that was created in error or attached to the wrong customer. class MeterEventAdjustment < APIResource extend Stripe::APIOperations::Create diff --git a/lib/stripe/resources/forwarding/request.rb b/lib/stripe/resources/forwarding/request.rb index d9201e59..4a59ed86 100644 --- a/lib/stripe/resources/forwarding/request.rb +++ b/lib/stripe/resources/forwarding/request.rb @@ -3,9 +3,9 @@ module Stripe module Forwarding - # Instructs Stripe to make a request on your behalf using the destination URL and HTTP method in the config. - # A config is set up for each destination URL by Stripe at the time of onboarding. Stripe verifies requests with - # your credentials in the config, and injects card details from the payment_method into the request. + # Instructs Stripe to make a request on your behalf using the destination URL. The destination URL + # is activated by Stripe at the time of onboarding. Stripe verifies requests with your credentials + # provided during onboarding, and injects card details from the payment_method into the request. # # Stripe redacts all sensitive fields and headers, including authentication credentials and card numbers, # before storing the request and response data in the forwarding Request object, which are subject to a diff --git a/lib/stripe/resources/reversal.rb b/lib/stripe/resources/reversal.rb index af746556..5dd78311 100644 --- a/lib/stripe/resources/reversal.rb +++ b/lib/stripe/resources/reversal.rb @@ -14,7 +14,7 @@ module Stripe # transfer only if the destination account has enough balance to cover the # reversal. # - # Related guide: [Reversing transfers](https://stripe.com/docs/connect/separate-charges-and-transfers#reversing-transfers) + # Related guide: [Reverse transfers](https://stripe.com/docs/connect/separate-charges-and-transfers#reverse-transfers) class Reversal < APIResource include Stripe::APIOperations::Save diff --git a/lib/stripe/resources/setup_intent.rb b/lib/stripe/resources/setup_intent.rb index 3fb300ca..3a6980f1 100644 --- a/lib/stripe/resources/setup_intent.rb +++ b/lib/stripe/resources/setup_intent.rb @@ -8,13 +8,13 @@ module Stripe # # 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 + # The SetupIntent transitions through multiple [statuses](https://docs.stripe.com/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) 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). + # [Strong Customer Authentication](https://docs.stripe.com/strong-customer-authentication) during payment method collection + # to streamline later [off-session payments](https://docs.stripe.com/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 @@ -22,7 +22,7 @@ module Stripe # # 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) + # Related guide: [Setup Intents API](https://docs.stripe.com/payments/setup-intents) class SetupIntent < APIResource extend Stripe::APIOperations::Create extend Stripe::APIOperations::List diff --git a/lib/stripe/resources/usage_record.rb b/lib/stripe/resources/usage_record.rb index c863c562..3444824f 100644 --- a/lib/stripe/resources/usage_record.rb +++ b/lib/stripe/resources/usage_record.rb @@ -6,6 +6,8 @@ module Stripe # metered billing of subscription prices. # # Related guide: [Metered billing](https://stripe.com/docs/billing/subscriptions/metered-billing) + # + # This is our legacy usage-based billing API. See the [updated usage-based billing docs](https://docs.stripe.com/billing/subscriptions/usage-based). class UsageRecord < APIResource OBJECT_NAME = "usage_record" def self.object_name