mirror of
https://github.com/stripe/stripe-ruby.git
synced 2025-12-07 00:00:35 -05:00
Update generated code (#1430)
* Update generated code for v1121 * Update generated code for v1126 --------- Co-authored-by: Stripe OpenAPI <105521251+stripe-openapi[bot]@users.noreply.github.com> Co-authored-by: helenye-stripe <111009531+helenye-stripe@users.noreply.github.com>
This commit is contained in:
parent
aa49a46b82
commit
5424da3fff
@ -1 +1 @@
|
||||
v1111
|
||||
v1126
|
||||
@ -16,7 +16,7 @@ module Stripe
|
||||
# Create sessions on-demand when customers intend to manage their subscriptions
|
||||
# and billing details.
|
||||
#
|
||||
# Learn more in the [integration guide](https://stripe.com/docs/billing/subscriptions/integrating-customer-portal).
|
||||
# Related guide: [Customer management](https://stripe.com/customer-management)
|
||||
class Session < APIResource
|
||||
extend Stripe::APIOperations::Create
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ module Stripe
|
||||
# API. To configure and create VerificationReports, use the
|
||||
# [VerificationSession](https://stripe.com/docs/api/identity/verification_sessions) API.
|
||||
#
|
||||
# Related guides: [Accessing verification results](https://stripe.com/docs/identity/verification-sessions#results).
|
||||
# Related guide: [Accessing verification results](https://stripe.com/docs/identity/verification-sessions#results).
|
||||
class VerificationReport < APIResource
|
||||
extend Stripe::APIOperations::List
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ module Stripe
|
||||
# A payment method domain represents a web domain that you have registered with Stripe.
|
||||
# Stripe Elements use registered payment method domains to control where certain payment methods are shown.
|
||||
#
|
||||
# Related guides: [Payment method domains](https://stripe.com/docs/payments/payment-methods/pmd-registration).
|
||||
# Related guide: [Payment method domains](https://stripe.com/docs/payments/payment-methods/pmd-registration).
|
||||
class PaymentMethodDomain < APIResource
|
||||
extend Stripe::APIOperations::Create
|
||||
extend Stripe::APIOperations::List
|
||||
|
||||
@ -115,7 +115,7 @@ module Stripe
|
||||
|
||||
# Updates an existing subscription to match the specified parameters.
|
||||
# When changing prices or quantities, we optionally prorate the price we charge next month to make up for any price changes.
|
||||
# To preview how the proration is calculated, use the [upcoming invoice](https://stripe.com/docs/api/invoices/upcoming) endpoint.
|
||||
# To preview how the proration is calculated, use the [create preview](https://stripe.com/docs/api/invoices/create_preview) endpoint.
|
||||
#
|
||||
# By default, we prorate subscription changes. For example, if a customer signs up on May 1 for a 100 price, they'll be billed 100 immediately. If on May 15 they switch to a 200 price, then on June 1 they'll be billed 250 (200 for a renewal of her subscription, plus a 50 prorating adjustment for half of the previous month's 100 difference). Similarly, a downgrade generates a credit that is applied to the next invoice. We also prorate when you make quantity changes.
|
||||
#
|
||||
@ -123,11 +123,11 @@ module Stripe
|
||||
#
|
||||
#
|
||||
# The billing interval is changed (for example, from monthly to yearly).
|
||||
# The subscription moves from free to paid, or paid to free.
|
||||
# The subscription moves from free to paid.
|
||||
# A trial starts or ends.
|
||||
#
|
||||
#
|
||||
# In these cases, we apply a credit for the unused time on the previous price, immediately charge the customer using the new price, and reset the billing date.
|
||||
# In these cases, we apply a credit for the unused time on the previous price, immediately charge the customer using the new price, and reset the billing date. Learn about how [Stripe immediately attempts payment for subscription changes](https://stripe.com/billing/subscriptions/upgrade-downgrade#immediate-payment).
|
||||
#
|
||||
# If you want to charge for an upgrade immediately, pass proration_behavior as always_invoice to create prorations, automatically invoice the customer for those proration adjustments, and attempt to collect payment. If you pass create_prorations, the prorations are created but not automatically invoiced. If you want to bill the customer for the prorations before the subscription's renewal date, you need to manually [invoice the customer](https://stripe.com/docs/api/invoices/create).
|
||||
#
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user