Equal to {@code deferred}. + */ + @SerializedName("type") + String type; } @Getter diff --git a/src/main/java/com/stripe/model/ConfirmationToken.java b/src/main/java/com/stripe/model/ConfirmationToken.java index f24dc4c68a0..a08839bf349 100644 --- a/src/main/java/com/stripe/model/ConfirmationToken.java +++ b/src/main/java/com/stripe/model/ConfirmationToken.java @@ -883,6 +883,14 @@ public static class Offline extends StripeObject { /** Time at which the payment was collected while offline. */ @SerializedName("stored_at") Long storedAt; + + /** + * The method used to process this payment method offline. Only deferred is allowed. + * + *
Equal to {@code deferred}.
+ */
+ @SerializedName("type")
+ String type;
}
@Getter
@@ -1194,6 +1202,10 @@ public static class CardPresent extends StripeObject {
@SerializedName("networks")
Networks networks;
+ /** Details about payment methods collected offline. */
+ @SerializedName("offline")
+ Offline offline;
+
/** EMV tag 5F2D. Preferred languages specified by the integrated circuit chip. */
@SerializedName("preferred_locales")
List Equal to {@code deferred}.
+ */
+ @SerializedName("type")
+ String type;
+ }
}
@Getter
diff --git a/src/main/java/com/stripe/model/CustomerSession.java b/src/main/java/com/stripe/model/CustomerSession.java
index 5fe077f89ad..b9f64b5433a 100644
--- a/src/main/java/com/stripe/model/CustomerSession.java
+++ b/src/main/java/com/stripe/model/CustomerSession.java
@@ -205,7 +205,7 @@ public static class Features extends StripeObject {
/**
* Determines the max number of saved payment methods for the Payment Element to display.
- * This parameter defaults to {@code 10}.
+ * This parameter defaults to {@code 3}.
*/
@SerializedName("payment_method_redisplay_limit")
Long paymentMethodRedisplayLimit;
diff --git a/src/main/java/com/stripe/model/PaymentIntent.java b/src/main/java/com/stripe/model/PaymentIntent.java
index 43fe711554c..121b35983b3 100644
--- a/src/main/java/com/stripe/model/PaymentIntent.java
+++ b/src/main/java/com/stripe/model/PaymentIntent.java
@@ -285,20 +285,21 @@ public class PaymentIntent extends ApiResource implements HasId, MetadataStore Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required
- * actions from the user are complete. If no Customer was provided, the payment method can still
- * be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required actions.
+ * If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates and
+ * attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code off_session}, or {@code on_session}.
*/
@@ -319,18 +320,21 @@ public class PaymentIntent extends ApiResource implements HasId, MetadataStore source;
/**
- * For card charges, use statement_descriptor_suffix.
- * Otherwise, you can use this value as the complete description of a charge on your customers'
- * statements. It must contain at least one letter and be 1–22 characters long.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the statement_descriptor_suffix
+ * instead.
*/
@SerializedName("statement_descriptor")
String statementDescriptor;
/**
- * Provides information about a card payment that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that’s set on the account to
- * form the complete statement descriptor. Maximum 22 characters for the concatenated descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the customer's
+ * statement.
*/
@SerializedName("statement_descriptor_suffix")
String statementDescriptorSuffix;
@@ -2443,21 +2447,21 @@ public static class AcssDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -2524,21 +2528,21 @@ public static class Affirm extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2569,21 +2573,21 @@ public static class AfterpayClearpay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2598,21 +2602,21 @@ public static class Alipay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -2635,21 +2639,21 @@ public static class AmazonPay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -2664,21 +2668,21 @@ public static class AuBecsDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -2693,21 +2697,21 @@ public static class BacsDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -2730,21 +2734,21 @@ public static class Bancontact extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -2759,21 +2763,21 @@ public static class Blik extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2796,21 +2800,21 @@ public static class Boleto extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -2914,21 +2918,21 @@ public static class Card extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -3136,21 +3140,21 @@ public static class Cashapp extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -3177,21 +3181,21 @@ public static class CustomerBalance extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3249,21 +3253,21 @@ public static class Eps extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3278,21 +3282,21 @@ public static class Fpx extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3307,21 +3311,21 @@ public static class Giropay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3336,21 +3340,21 @@ public static class Grabpay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3365,21 +3369,21 @@ public static class Ideal extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -3411,21 +3415,21 @@ public static class Klarna extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3470,21 +3474,21 @@ public static class Konbini extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3512,21 +3516,21 @@ public static class Link extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -3549,21 +3553,21 @@ public static class Mobilepay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3578,21 +3582,21 @@ public static class Multibanco extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3615,21 +3619,21 @@ public static class Oxxo extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3644,21 +3648,21 @@ public static class P24 extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3673,21 +3677,21 @@ public static class Paynow extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3722,21 +3726,21 @@ public static class Paypal extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -3759,21 +3763,21 @@ public static class Pix extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3788,21 +3792,21 @@ public static class Promptpay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3825,21 +3829,21 @@ public static class RevolutPay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -3857,21 +3861,21 @@ public static class SepaDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -3900,21 +3904,21 @@ public static class Sofort extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -3933,21 +3937,21 @@ public static class Swish extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -3962,21 +3966,21 @@ public static class Twint extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -4005,21 +4009,21 @@ public static class UsBankAccount extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -4105,21 +4109,21 @@ public static class WechatPay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -4134,21 +4138,21 @@ public static class Zip extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
- *
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
- *
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
+ *
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
+ *
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
diff --git a/src/main/java/com/stripe/model/PaymentLink.java b/src/main/java/com/stripe/model/PaymentLink.java
index 34f3114275e..fa181a99991 100644
--- a/src/main/java/com/stripe/model/PaymentLink.java
+++ b/src/main/java/com/stripe/model/PaymentLink.java
@@ -973,17 +973,16 @@ public static class PaymentIntentData extends StripeObject {
String setupFutureUsage;
/**
- * Extra information about the payment. This will appear on your customer's statement when this
- * payment succeeds in creating a charge.
+ * For a non-card payment, information about the charge that appears on the customer's statement
+ * when this payment succeeds in creating a charge.
*/
@SerializedName("statement_descriptor")
String statementDescriptor;
/**
- * Provides information about the charge that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that's set on the account to
- * form the complete statement descriptor. Maximum 22 characters for the concatenated
- * descriptor.
+ * For a card payment, information about the charge that appears on the customer's statement
+ * when this payment succeeds in creating a charge. Concatenated with the account's statement
+ * descriptor prefix to form the complete statement descriptor.
*/
@SerializedName("statement_descriptor_suffix")
String statementDescriptorSuffix;
diff --git a/src/main/java/com/stripe/model/PaymentMethod.java b/src/main/java/com/stripe/model/PaymentMethod.java
index a08fc373fda..0feb377abd7 100644
--- a/src/main/java/com/stripe/model/PaymentMethod.java
+++ b/src/main/java/com/stripe/model/PaymentMethod.java
@@ -1125,6 +1125,14 @@ public static class Offline extends StripeObject {
/** Time at which the payment was collected while offline. */
@SerializedName("stored_at")
Long storedAt;
+
+ /**
+ * The method used to process this payment method offline. Only deferred is allowed.
+ *
+ * Equal to {@code deferred}.
+ */
+ @SerializedName("type")
+ String type;
}
@Getter
@@ -1430,6 +1438,10 @@ public static class CardPresent extends StripeObject {
@SerializedName("networks")
Networks networks;
+ /** Details about payment methods collected offline. */
+ @SerializedName("offline")
+ Offline offline;
+
/** EMV tag 5F2D. Preferred languages specified by the integrated circuit chip. */
@SerializedName("preferred_locales")
List Equal to {@code deferred}.
+ */
+ @SerializedName("type")
+ String type;
+ }
}
@Getter
diff --git a/src/main/java/com/stripe/model/Person.java b/src/main/java/com/stripe/model/Person.java
index 2eb63c56979..cf6263a0bc0 100644
--- a/src/main/java/com/stripe/model/Person.java
+++ b/src/main/java/com/stripe/model/Person.java
@@ -285,6 +285,7 @@ public Person update(PersonUpdateParams params, RequestOptions options) throws S
@Setter
@EqualsAndHashCode(callSuper = false)
public static class AdditionalTosAcceptances extends StripeObject {
+ /** Details on the legal guardian's acceptance of the main Stripe service agreement. */
@SerializedName("account")
Account account;
diff --git a/src/main/java/com/stripe/model/SetupAttempt.java b/src/main/java/com/stripe/model/SetupAttempt.java
index 0fc0a7a8f24..8ef8993ea5f 100644
--- a/src/main/java/com/stripe/model/SetupAttempt.java
+++ b/src/main/java/com/stripe/model/SetupAttempt.java
@@ -687,6 +687,14 @@ public static class Offline extends StripeObject {
/** Time at which the payment was collected while offline. */
@SerializedName("stored_at")
Long storedAt;
+
+ /**
+ * The method used to process this payment method offline. Only deferred is allowed.
+ *
+ * Equal to {@code deferred}.
+ */
+ @SerializedName("type")
+ String type;
}
}
diff --git a/src/main/java/com/stripe/model/StripeError.java b/src/main/java/com/stripe/model/StripeError.java
index 61a7c6b7e4c..51b85143d9d 100644
--- a/src/main/java/com/stripe/model/StripeError.java
+++ b/src/main/java/com/stripe/model/StripeError.java
@@ -47,12 +47,13 @@ public class StripeError extends StripeObject {
* insufficient_funds}, {@code intent_invalid_state}, {@code intent_verification_method_missing},
* {@code invalid_card_type}, {@code invalid_characters}, {@code invalid_charge_amount}, {@code
* invalid_cvc}, {@code invalid_expiry_month}, {@code invalid_expiry_year}, {@code
- * invalid_number}, {@code invalid_source_usage}, {@code invalid_tax_location}, {@code
- * invoice_no_customer_line_items}, {@code invoice_no_payment_method_types}, {@code
- * invoice_no_subscription_line_items}, {@code invoice_not_editable}, {@code
- * invoice_on_behalf_of_not_editable}, {@code invoice_payment_intent_requires_action}, {@code
- * invoice_upcoming_none}, {@code livemode_mismatch}, {@code lock_timeout}, {@code missing},
- * {@code no_account}, {@code not_allowed_on_standard_account}, {@code out_of_inventory}, {@code
+ * invalid_mandate_reference_prefix_format}, {@code invalid_number}, {@code invalid_source_usage},
+ * {@code invalid_tax_location}, {@code invoice_no_customer_line_items}, {@code
+ * invoice_no_payment_method_types}, {@code invoice_no_subscription_line_items}, {@code
+ * invoice_not_editable}, {@code invoice_on_behalf_of_not_editable}, {@code
+ * invoice_payment_intent_requires_action}, {@code invoice_upcoming_none}, {@code
+ * livemode_mismatch}, {@code lock_timeout}, {@code missing}, {@code no_account}, {@code
+ * not_allowed_on_standard_account}, {@code out_of_inventory}, {@code
* ownership_declaration_not_allowed}, {@code parameter_invalid_empty}, {@code
* parameter_invalid_integer}, {@code parameter_invalid_string_blank}, {@code
* parameter_invalid_string_empty}, {@code parameter_missing}, {@code parameter_unknown}, {@code
diff --git a/src/main/java/com/stripe/model/Subscription.java b/src/main/java/com/stripe/model/Subscription.java
index 7eafc515afc..30415ab55ca 100644
--- a/src/main/java/com/stripe/model/Subscription.java
+++ b/src/main/java/com/stripe/model/Subscription.java
@@ -78,10 +78,8 @@ public class Subscription extends ApiResource implements HasId, MetadataStore Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
- *
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
- *
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
+ *
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
+ *
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -1631,21 +1631,21 @@ public static class Affirm extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -1660,21 +1660,21 @@ public static class AfterpayClearpay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -1689,21 +1689,21 @@ public static class Alipay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -1718,21 +1718,21 @@ public static class AmazonPay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -1747,21 +1747,21 @@ public static class AuBecsDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -1776,21 +1776,21 @@ public static class BacsDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -1805,21 +1805,21 @@ public static class Bancontact extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -1842,21 +1842,21 @@ public static class Boleto extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -1890,21 +1890,21 @@ public static class Card extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -1948,21 +1948,21 @@ public static class Cashapp extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -1989,21 +1989,21 @@ public static class CustomerBalance extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2061,21 +2061,21 @@ public static class Eps extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2090,21 +2090,21 @@ public static class Fpx extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2119,21 +2119,21 @@ public static class Giropay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2148,21 +2148,21 @@ public static class Grabpay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2177,21 +2177,21 @@ public static class Ideal extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2206,21 +2206,21 @@ public static class Klarna extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -2244,21 +2244,21 @@ public static class Konbini extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2273,21 +2273,21 @@ public static class Link extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -2302,21 +2302,21 @@ public static class Mobilepay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2331,21 +2331,21 @@ public static class Multibanco extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2368,21 +2368,21 @@ public static class Oxxo extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2397,21 +2397,21 @@ public static class P24 extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2426,21 +2426,21 @@ public static class Paynow extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2475,21 +2475,21 @@ public static class Paypal extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -2513,21 +2513,21 @@ public static class RevolutPay extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, or {@code off_session}.
*/
@@ -2542,21 +2542,21 @@ public static class SepaDebit extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
@@ -2571,21 +2571,21 @@ public static class Sofort extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* Equal to {@code none}.
*/
@@ -2615,21 +2615,21 @@ public static class UsBankAccount extends StripeObject {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
- *
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
- *
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
+ *
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
+ *
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
* One of {@code none}, {@code off_session}, or {@code on_session}.
*/
diff --git a/src/main/java/com/stripe/model/identity/VerificationSession.java b/src/main/java/com/stripe/model/identity/VerificationSession.java
index 6353fcdf956..38db0863067 100644
--- a/src/main/java/com/stripe/model/identity/VerificationSession.java
+++ b/src/main/java/com/stripe/model/identity/VerificationSession.java
@@ -130,6 +130,10 @@ public class VerificationSession extends ApiResource
@SerializedName("redaction")
Redaction redaction;
+ /** Token referencing a Customer resource. */
+ @SerializedName("related_customer")
+ String relatedCustomer;
+
/**
* Status of this VerificationSession. Learn more about the lifecycle of
diff --git a/src/main/java/com/stripe/model/tax/Calculation.java b/src/main/java/com/stripe/model/tax/Calculation.java
index cc51e6981cf..da69ddf7ed6 100644
--- a/src/main/java/com/stripe/model/tax/Calculation.java
+++ b/src/main/java/com/stripe/model/tax/Calculation.java
@@ -14,6 +14,7 @@
import com.stripe.net.StripeResponseGetter;
import com.stripe.param.tax.CalculationCreateParams;
import com.stripe.param.tax.CalculationListLineItemsParams;
+import com.stripe.param.tax.CalculationRetrieveParams;
import java.util.List;
import java.util.Map;
import lombok.EqualsAndHashCode;
@@ -202,6 +203,45 @@ public CalculationLineItemCollection listLineItems(
return getResponseGetter().request(request, CalculationLineItemCollection.class);
}
+ /** Retrieves a Tax {@code Calculation} object, if the calculation hasn’t expired. */
+ public static Calculation retrieve(String calculation) throws StripeException {
+ return retrieve(calculation, (Map One of {@code offline}, or {@code online}.
*/
diff --git a/src/main/java/com/stripe/param/AccountCreateParams.java b/src/main/java/com/stripe/param/AccountCreateParams.java
index f82049e9658..a61d565d848 100644
--- a/src/main/java/com/stripe/param/AccountCreateParams.java
+++ b/src/main/java/com/stripe/param/AccountCreateParams.java
@@ -10896,22 +10896,32 @@ public static class Payments {
Map Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required
- * actions from the user are complete. If no Customer was provided, the payment method can still
- * be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required actions.
+ * If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates and
+ * attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code off_session}.
*/
@SerializedName("setup_future_usage")
@@ -473,22 +474,23 @@ public Builder setReturnUrl(String returnUrl) {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment method
- * can still be attached to a
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
* Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -501,22 +503,23 @@ public Builder setSetupFutureUsage(
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment method
- * can still be attached to a
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
* Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -6572,23 +6575,23 @@ public static class AcssDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -6672,24 +6675,24 @@ public Builder setMandateOptions(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -6703,24 +6706,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -6993,23 +6996,23 @@ public static class Affirm {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7117,24 +7120,24 @@ public Builder setPreferredLocale(String preferredLocale) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7205,23 +7208,23 @@ public static class AfterpayClearpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7334,24 +7337,24 @@ public Builder setReference(String reference) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7401,23 +7404,23 @@ public static class Alipay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7476,24 +7479,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7507,24 +7510,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -7576,21 +7579,21 @@ public static class AmazonPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
ApiRequestParams.EnumParam setupFutureUsage;
@@ -7684,21 +7687,21 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentConfirmParams.PaymentMethodOptions.AmazonPay.SetupFutureUsage
@@ -7711,21 +7714,21 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
this.setupFutureUsage = setupFutureUsage;
@@ -7775,23 +7778,23 @@ public static class AuBecsDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7851,24 +7854,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7882,24 +7885,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -7941,23 +7944,23 @@ public static class BacsDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8017,24 +8020,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8048,24 +8051,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8113,23 +8116,23 @@ public static class Bancontact {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8205,24 +8208,24 @@ public Builder setPreferredLanguage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8236,24 +8239,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8320,23 +8323,23 @@ public static class Blik {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8410,24 +8413,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8441,24 +8444,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8502,23 +8505,23 @@ public static class Boleto {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8593,24 +8596,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8624,24 +8627,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8783,23 +8786,23 @@ public static class Card {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -9116,24 +9119,24 @@ public Builder setRequireCvcRecollection(Boolean requireCvcRecollection) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -9147,24 +9150,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -9345,8 +9348,8 @@ public Builder setPlan(EmptyParam plan) {
@Getter
public static class Plan {
/**
- * Required. For {@code fixed_count} installment plans, this is the
- * number of installment payments your customer will make to their credit card.
+ * For {@code fixed_count} installment plans, this is required. It represents the number
+ * of installment payments your customer will make to their credit card.
*/
@SerializedName("count")
Long count;
@@ -9362,9 +9365,9 @@ public static class Plan {
Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -10881,24 +10887,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -10912,24 +10918,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -10997,23 +11003,23 @@ public static class CustomerBalance {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11106,24 +11112,24 @@ public Builder setFundingType(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11477,23 +11483,23 @@ public static class Eps {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11552,24 +11558,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11606,23 +11612,23 @@ public static class Fpx {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11681,24 +11687,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11735,23 +11741,23 @@ public static class Giropay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11810,24 +11816,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11865,23 +11871,23 @@ public static class Grabpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11940,24 +11946,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11995,23 +12001,23 @@ public static class Ideal {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12070,24 +12076,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12101,24 +12107,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -12234,23 +12240,23 @@ public static class Klarna {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12360,24 +12366,24 @@ public Builder setPreferredLocale(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12605,23 +12611,23 @@ public static class Konbini {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12781,24 +12787,24 @@ public Builder setProductDescription(EmptyParam productDescription) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12854,23 +12860,23 @@ public static class Link {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12977,24 +12983,24 @@ public Builder setPersistentToken(String persistentToken) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13008,24 +13014,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -13089,23 +13095,23 @@ public static class Mobilepay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13201,24 +13207,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13268,23 +13274,23 @@ public static class Multibanco {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13343,24 +13349,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13406,23 +13412,23 @@ public static class Oxxo {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13497,24 +13503,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13552,23 +13558,23 @@ public static class P24 {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13637,24 +13643,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13697,23 +13703,23 @@ public static class Paynow {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13772,24 +13778,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13850,23 +13856,23 @@ public static class Paypal {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13990,24 +13996,24 @@ public Builder setRiskCorrelationId(String riskCorrelationId) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14021,24 +14027,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -14175,23 +14181,23 @@ public static class Pix {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14278,24 +14284,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14332,23 +14338,23 @@ public static class Promptpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14407,24 +14413,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14475,21 +14481,21 @@ public static class RevolutPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
ApiRequestParams.EnumParam setupFutureUsage;
@@ -14584,21 +14590,21 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentConfirmParams.PaymentMethodOptions.RevolutPay.SetupFutureUsage
@@ -14611,21 +14617,21 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
this.setupFutureUsage = setupFutureUsage;
@@ -14679,23 +14685,23 @@ public static class SepaDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14768,24 +14774,24 @@ public Builder setMandateOptions(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14799,24 +14805,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -14923,23 +14929,23 @@ public static class Sofort {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15018,24 +15024,24 @@ public Builder setPreferredLanguage(EmptyParam preferredLanguage) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15049,24 +15055,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -15139,23 +15145,23 @@ public static class Swish {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15230,24 +15236,24 @@ public Builder setReference(EmptyParam reference) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15285,23 +15291,23 @@ public static class Twint {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15360,24 +15366,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15431,23 +15437,23 @@ public static class UsBankAccount {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15577,24 +15583,24 @@ public Builder setPreferredSettlementSpeed(EmptyParam preferredSettlementSpeed)
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15608,24 +15614,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -16325,23 +16331,23 @@ public static class WechatPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -16423,24 +16429,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -16496,23 +16502,23 @@ public static class Zip {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -16571,24 +16577,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
diff --git a/src/main/java/com/stripe/param/PaymentIntentCreateParams.java b/src/main/java/com/stripe/param/PaymentIntentCreateParams.java
index 43d3bcc1efc..46b4614f519 100644
--- a/src/main/java/com/stripe/param/PaymentIntentCreateParams.java
+++ b/src/main/java/com/stripe/param/PaymentIntentCreateParams.java
@@ -236,20 +236,21 @@ public class PaymentIntentCreateParams extends ApiRequestParams {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required
- * actions from the user are complete. If no Customer was provided, the payment method can still
- * be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required actions.
+ * If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates and
+ * attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
SetupFutureUsage setupFutureUsage;
@@ -259,19 +260,21 @@ public class PaymentIntentCreateParams extends ApiRequestParams {
Shipping shipping;
/**
- * For card charges, use statement_descriptor_suffix.
- * Otherwise, you can use this value as the complete description of a charge on your customers'
- * statements. It must contain at least one letter and be 1–22 characters long.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the statement_descriptor_suffix
+ * instead.
*/
@SerializedName("statement_descriptor")
String statementDescriptor;
/**
- * Provides information about a card payment that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that’s set on the account to
- * form the complete statement descriptor. The concatenated descriptor must contain 1-22
- * characters.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the customer's
+ * statement.
*/
@SerializedName("statement_descriptor_suffix")
String statementDescriptorSuffix;
@@ -848,20 +851,21 @@ public Builder setReturnUrl(String returnUrl) {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment method
- * can still be attached to a
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
* Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentCreateParams.SetupFutureUsage setupFutureUsage) {
@@ -876,10 +880,13 @@ public Builder setShipping(PaymentIntentCreateParams.Shipping shipping) {
}
/**
- * For card charges, use statement_descriptor_suffix.
- * Otherwise, you can use this value as the complete description of a charge on your customers'
- * statements. It must contain at least one letter and be 1–22 characters long.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the
+ * statement_descriptor_suffix
+ * instead.
*/
public Builder setStatementDescriptor(String statementDescriptor) {
this.statementDescriptor = statementDescriptor;
@@ -887,10 +894,10 @@ public Builder setStatementDescriptor(String statementDescriptor) {
}
/**
- * Provides information about a card payment that customers see on their statements.
- * Concatenated with the prefix (shortened descriptor) or statement descriptor that’s set on the
- * account to form the complete statement descriptor. The concatenated descriptor must contain
- * 1-22 characters.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the
+ * customer's statement.
*/
public Builder setStatementDescriptorSuffix(String statementDescriptorSuffix) {
this.statementDescriptorSuffix = statementDescriptorSuffix;
@@ -7072,23 +7079,23 @@ public static class AcssDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7172,24 +7179,24 @@ public Builder setMandateOptions(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7203,24 +7210,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -7493,23 +7500,23 @@ public static class Affirm {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7617,24 +7624,24 @@ public Builder setPreferredLocale(String preferredLocale) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7705,23 +7712,23 @@ public static class AfterpayClearpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7834,24 +7841,24 @@ public Builder setReference(String reference) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7901,23 +7908,23 @@ public static class Alipay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7976,24 +7983,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8007,24 +8014,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8076,21 +8083,21 @@ public static class AmazonPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
ApiRequestParams.EnumParam setupFutureUsage;
@@ -8184,21 +8191,21 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentCreateParams.PaymentMethodOptions.AmazonPay.SetupFutureUsage
@@ -8211,21 +8218,21 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
this.setupFutureUsage = setupFutureUsage;
@@ -8275,23 +8282,23 @@ public static class AuBecsDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8351,24 +8358,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8382,24 +8389,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8441,23 +8448,23 @@ public static class BacsDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8517,24 +8524,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8548,24 +8555,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8613,23 +8620,23 @@ public static class Bancontact {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8705,24 +8712,24 @@ public Builder setPreferredLanguage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8736,24 +8743,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8820,23 +8827,23 @@ public static class Blik {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8910,24 +8917,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8940,24 +8947,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -9001,23 +9008,23 @@ public static class Boleto {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -9092,24 +9099,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -9123,24 +9130,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -9282,23 +9289,23 @@ public static class Card {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -9615,24 +9622,24 @@ public Builder setRequireCvcRecollection(Boolean requireCvcRecollection) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -9645,24 +9652,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -9843,8 +9850,8 @@ public Builder setPlan(EmptyParam plan) {
@Getter
public static class Plan {
/**
- * Required. For {@code fixed_count} installment plans, this is the
- * number of installment payments your customer will make to their credit card.
+ * For {@code fixed_count} installment plans, this is required. It represents the number
+ * of installment payments your customer will make to their credit card.
*/
@SerializedName("count")
Long count;
@@ -9860,9 +9867,9 @@ public static class Plan {
Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11377,24 +11387,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11408,24 +11418,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -11493,23 +11503,23 @@ public static class CustomerBalance {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11602,24 +11612,24 @@ public Builder setFundingType(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11973,23 +11983,23 @@ public static class Eps {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12048,24 +12058,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12102,23 +12112,23 @@ public static class Fpx {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12177,24 +12187,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12231,23 +12241,23 @@ public static class Giropay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12306,24 +12316,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12361,23 +12371,23 @@ public static class Grabpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12436,24 +12446,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12491,23 +12501,23 @@ public static class Ideal {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12566,24 +12576,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12597,24 +12607,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -12730,23 +12740,23 @@ public static class Klarna {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12855,24 +12865,24 @@ public Builder setPreferredLocale(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13100,23 +13110,23 @@ public static class Konbini {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13276,24 +13286,24 @@ public Builder setProductDescription(EmptyParam productDescription) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13349,23 +13359,23 @@ public static class Link {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13472,24 +13482,24 @@ public Builder setPersistentToken(String persistentToken) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13502,24 +13512,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -13583,23 +13593,23 @@ public static class Mobilepay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13695,24 +13705,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13762,23 +13772,23 @@ public static class Multibanco {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13837,24 +13847,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13900,23 +13910,23 @@ public static class Oxxo {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13991,24 +14001,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14045,23 +14055,23 @@ public static class P24 {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14130,24 +14140,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14190,23 +14200,23 @@ public static class Paynow {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14265,24 +14275,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14343,23 +14353,23 @@ public static class Paypal {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14482,24 +14492,24 @@ public Builder setRiskCorrelationId(String riskCorrelationId) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14513,24 +14523,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -14667,23 +14677,23 @@ public static class Pix {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14770,24 +14780,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14824,23 +14834,23 @@ public static class Promptpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14899,24 +14909,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14967,21 +14977,21 @@ public static class RevolutPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
ApiRequestParams.EnumParam setupFutureUsage;
@@ -15075,21 +15085,21 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentCreateParams.PaymentMethodOptions.RevolutPay.SetupFutureUsage
@@ -15102,21 +15112,21 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
this.setupFutureUsage = setupFutureUsage;
@@ -15170,23 +15180,23 @@ public static class SepaDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15259,24 +15269,24 @@ public Builder setMandateOptions(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15290,24 +15300,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -15414,23 +15424,23 @@ public static class Sofort {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15509,24 +15519,24 @@ public Builder setPreferredLanguage(EmptyParam preferredLanguage) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15540,24 +15550,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -15630,23 +15640,23 @@ public static class Swish {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15721,24 +15731,24 @@ public Builder setReference(EmptyParam reference) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15776,23 +15786,23 @@ public static class Twint {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15851,24 +15861,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15922,23 +15932,23 @@ public static class UsBankAccount {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -16066,24 +16076,24 @@ public Builder setPreferredSettlementSpeed(EmptyParam preferredSettlementSpeed)
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -16097,24 +16107,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -16814,23 +16824,23 @@ public static class WechatPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -16912,24 +16922,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -16985,23 +16995,23 @@ public static class Zip {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -17060,24 +17070,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
diff --git a/src/main/java/com/stripe/param/PaymentIntentIncrementAuthorizationParams.java b/src/main/java/com/stripe/param/PaymentIntentIncrementAuthorizationParams.java
index 449fd14698d..0a7ed7ef162 100644
--- a/src/main/java/com/stripe/param/PaymentIntentIncrementAuthorizationParams.java
+++ b/src/main/java/com/stripe/param/PaymentIntentIncrementAuthorizationParams.java
@@ -55,10 +55,12 @@ public class PaymentIntentIncrementAuthorizationParams extends ApiRequestParams
Map Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required
- * actions from the user are complete. If no Customer was provided, the payment method can still
- * be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required actions.
+ * If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates and
+ * attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code off_session}.
*/
@SerializedName("setup_future_usage")
@@ -159,18 +160,21 @@ public class PaymentIntentUpdateParams extends ApiRequestParams {
Object shipping;
/**
- * For card charges, use statement_descriptor_suffix.
- * Otherwise, you can use this value as the complete description of a charge on your customers'
- * statements. It must contain at least one letter and be 1–22 characters long.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the statement_descriptor_suffix
+ * instead.
*/
@SerializedName("statement_descriptor")
Object statementDescriptor;
/**
- * Provides information about a card payment that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that’s set on the account to
- * form the complete statement descriptor. Maximum 22 characters for the concatenated descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the customer's
+ * statement.
*/
@SerializedName("statement_descriptor_suffix")
Object statementDescriptorSuffix;
@@ -627,22 +631,23 @@ public Builder setReceiptEmail(EmptyParam receiptEmail) {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment method
- * can still be attached to a
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
* Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -655,22 +660,23 @@ public Builder setSetupFutureUsage(
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method to
- * the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment method
- * can still be attached to a
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
* Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to dynamically
- * optimize your payment flow and comply with regional legislation and network rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -692,10 +698,13 @@ public Builder setShipping(EmptyParam shipping) {
}
/**
- * For card charges, use statement_descriptor_suffix.
- * Otherwise, you can use this value as the complete description of a charge on your customers'
- * statements. It must contain at least one letter and be 1–22 characters long.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the
+ * statement_descriptor_suffix
+ * instead.
*/
public Builder setStatementDescriptor(String statementDescriptor) {
this.statementDescriptor = statementDescriptor;
@@ -703,10 +712,13 @@ public Builder setStatementDescriptor(String statementDescriptor) {
}
/**
- * For card charges, use statement_descriptor_suffix.
- * Otherwise, you can use this value as the complete description of a charge on your customers'
- * statements. It must contain at least one letter and be 1–22 characters long.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the
+ * statement_descriptor_suffix
+ * instead.
*/
public Builder setStatementDescriptor(EmptyParam statementDescriptor) {
this.statementDescriptor = statementDescriptor;
@@ -714,10 +726,10 @@ public Builder setStatementDescriptor(EmptyParam statementDescriptor) {
}
/**
- * Provides information about a card payment that customers see on their statements.
- * Concatenated with the prefix (shortened descriptor) or statement descriptor that’s set on the
- * account to form the complete statement descriptor. Maximum 22 characters for the concatenated
- * descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the
+ * customer's statement.
*/
public Builder setStatementDescriptorSuffix(String statementDescriptorSuffix) {
this.statementDescriptorSuffix = statementDescriptorSuffix;
@@ -725,10 +737,10 @@ public Builder setStatementDescriptorSuffix(String statementDescriptorSuffix) {
}
/**
- * Provides information about a card payment that customers see on their statements.
- * Concatenated with the prefix (shortened descriptor) or statement descriptor that’s set on the
- * account to form the complete statement descriptor. Maximum 22 characters for the concatenated
- * descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the
+ * customer's statement.
*/
public Builder setStatementDescriptorSuffix(EmptyParam statementDescriptorSuffix) {
this.statementDescriptorSuffix = statementDescriptorSuffix;
@@ -6536,23 +6548,23 @@ public static class AcssDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -6636,24 +6648,24 @@ public Builder setMandateOptions(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -6667,24 +6679,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -6966,23 +6978,23 @@ public static class Affirm {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7098,24 +7110,24 @@ public Builder setPreferredLocale(EmptyParam preferredLocale) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7186,23 +7198,23 @@ public static class AfterpayClearpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7325,24 +7337,24 @@ public Builder setReference(EmptyParam reference) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7392,23 +7404,23 @@ public static class Alipay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7467,24 +7479,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7498,24 +7510,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -7567,21 +7579,21 @@ public static class AmazonPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
ApiRequestParams.EnumParam setupFutureUsage;
@@ -7675,21 +7687,21 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentUpdateParams.PaymentMethodOptions.AmazonPay.SetupFutureUsage
@@ -7702,21 +7714,21 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
this.setupFutureUsage = setupFutureUsage;
@@ -7766,23 +7778,23 @@ public static class AuBecsDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -7842,24 +7854,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -7873,24 +7885,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -7932,23 +7944,23 @@ public static class BacsDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8008,24 +8020,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8039,24 +8051,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8104,23 +8116,23 @@ public static class Bancontact {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8196,24 +8208,24 @@ public Builder setPreferredLanguage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8227,24 +8239,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8311,23 +8323,23 @@ public static class Blik {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8410,24 +8422,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8440,24 +8452,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8501,23 +8513,23 @@ public static class Boleto {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -8592,24 +8604,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -8623,24 +8635,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -8782,23 +8794,23 @@ public static class Card {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -9125,24 +9137,24 @@ public Builder setRequireCvcRecollection(Boolean requireCvcRecollection) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -9155,24 +9167,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -9353,8 +9365,8 @@ public Builder setPlan(EmptyParam plan) {
@Getter
public static class Plan {
/**
- * Required. For {@code fixed_count} installment plans, this is the
- * number of installment payments your customer will make to their credit card.
+ * For {@code fixed_count} installment plans, this is required. It represents the number
+ * of installment payments your customer will make to their credit card.
*/
@SerializedName("count")
Long count;
@@ -9370,9 +9382,9 @@ public static class Plan {
Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -10941,24 +10956,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -10972,24 +10987,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -11057,23 +11072,23 @@ public static class CustomerBalance {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11166,24 +11181,24 @@ public Builder setFundingType(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11547,23 +11562,23 @@ public static class Eps {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11622,24 +11637,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11676,23 +11691,23 @@ public static class Fpx {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11751,24 +11766,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11805,23 +11820,23 @@ public static class Giropay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -11880,24 +11895,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -11935,23 +11950,23 @@ public static class Grabpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12010,24 +12025,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12065,23 +12080,23 @@ public static class Ideal {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12140,24 +12155,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12171,24 +12186,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -12304,23 +12319,23 @@ public static class Klarna {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12429,24 +12444,24 @@ public Builder setPreferredLocale(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12674,23 +12689,23 @@ public static class Konbini {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -12850,24 +12865,24 @@ public Builder setProductDescription(EmptyParam productDescription) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -12923,23 +12938,23 @@ public static class Link {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13053,24 +13068,24 @@ public Builder setPersistentToken(EmptyParam persistentToken) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13083,24 +13098,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -13164,23 +13179,23 @@ public static class Mobilepay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13276,24 +13291,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13343,23 +13358,23 @@ public static class Multibanco {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13418,24 +13433,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13481,23 +13496,23 @@ public static class Oxxo {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13572,24 +13587,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13626,23 +13641,23 @@ public static class P24 {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13711,24 +13726,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13771,23 +13786,23 @@ public static class Paynow {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -13846,24 +13861,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -13924,23 +13939,23 @@ public static class Paypal {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14081,24 +14096,24 @@ public Builder setRiskCorrelationId(EmptyParam riskCorrelationId) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14112,24 +14127,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -14266,23 +14281,23 @@ public static class Pix {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14369,24 +14384,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14423,23 +14438,23 @@ public static class Promptpay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14498,24 +14513,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14566,21 +14581,21 @@ public static class RevolutPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*/
@SerializedName("setup_future_usage")
ApiRequestParams.EnumParam setupFutureUsage;
@@ -14674,21 +14689,21 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(
PaymentIntentUpdateParams.PaymentMethodOptions.RevolutPay.SetupFutureUsage
@@ -14701,21 +14716,21 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
this.setupFutureUsage = setupFutureUsage;
@@ -14769,23 +14784,23 @@ public static class SepaDebit {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -14858,24 +14873,24 @@ public Builder setMandateOptions(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -14889,24 +14904,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -15013,23 +15028,23 @@ public static class Sofort {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15108,24 +15123,24 @@ public Builder setPreferredLanguage(EmptyParam preferredLanguage) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15139,24 +15154,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -15229,23 +15244,23 @@ public static class Swish {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15320,24 +15335,24 @@ public Builder setReference(EmptyParam reference) {
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15375,23 +15390,23 @@ public static class Twint {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15450,24 +15465,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15521,23 +15536,23 @@ public static class UsBankAccount {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -15665,24 +15680,24 @@ public Builder setPreferredSettlementSpeed(EmptyParam preferredSettlementSpeed)
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -15696,24 +15711,24 @@ public Builder setSetupFutureUsage(
* Indicates that you intend to make future payments with this PaymentIntent's payment
* method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(EmptyParam setupFutureUsage) {
@@ -16422,23 +16437,23 @@ public static class WechatPay {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -16526,24 +16541,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
@@ -16599,23 +16614,23 @@ public static class Zip {
/**
* Indicates that you intend to make future payments with this PaymentIntent's payment method.
*
- * Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer after
- * the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the
+ * Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe creates
+ * and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you comply
+ * with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
+ * If you've already set {@code setup_future_usage} and you're performing a request using a
* publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
@@ -16674,24 +16689,24 @@ public Builder putAllExtraParam(Map Providing this parameter will attach the payment method
- * to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any
- * required actions from the user are complete. If no Customer was provided, the payment
- * method can still be attached to a Customer
- * after the transaction completes.
+ * If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to
+ * the Customer after the PaymentIntent is confirmed and the customer completes any required
+ * actions. If you don't provide a Customer, you can still attach the payment method to a
+ * Customer after the transaction completes.
*
- * If the payment method is {@code card_present} and isn't a digital wallet, then a generated_card
- * payment method representing the card is created and attached to the Customer instead.
+ * If the payment method is {@code card_present} and isn't a digital wallet, Stripe
+ * creates and attaches a generated_card
+ * payment method representing the card to the Customer instead.
*
- * When processing card payments, Stripe also uses {@code setup_future_usage} to
- * dynamically optimize your payment flow and comply with regional legislation and network
- * rules, such as SCA.
+ * When processing card payments, Stripe uses {@code setup_future_usage} to help you
+ * comply with regional legislation and network rules, such as SCA.
*
- * If {@code setup_future_usage} is already set and you are performing a request using a
- * publishable key, you can only update the value from {@code on_session} to {@code
+ * If you've already set {@code setup_future_usage} and you're performing a request using
+ * a publishable key, you can only update the value from {@code on_session} to {@code
* off_session}.
*/
public Builder setSetupFutureUsage(
diff --git a/src/main/java/com/stripe/param/PaymentLinkCreateParams.java b/src/main/java/com/stripe/param/PaymentLinkCreateParams.java
index 65e0b180d28..2c73f60736a 100644
--- a/src/main/java/com/stripe/param/PaymentLinkCreateParams.java
+++ b/src/main/java/com/stripe/param/PaymentLinkCreateParams.java
@@ -3542,17 +3542,22 @@ public static class PaymentIntentData {
SetupFutureUsage setupFutureUsage;
/**
- * Extra information about the payment. This will appear on your customer's statement when this
- * payment succeeds in creating a charge.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the
+ * statement_descriptor_suffix
+ * instead.
*/
@SerializedName("statement_descriptor")
String statementDescriptor;
/**
- * Provides information about the charge that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that's set on the account to
- * form the complete statement descriptor. Maximum 22 characters for the concatenated
- * descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the
+ * customer's statement.
*/
@SerializedName("statement_descriptor_suffix")
String statementDescriptorSuffix;
@@ -3713,8 +3718,13 @@ public Builder setSetupFutureUsage(
}
/**
- * Extra information about the payment. This will appear on your customer's statement when
- * this payment succeeds in creating a charge.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set
+ * the statement_descriptor_suffix
+ * instead.
*/
public Builder setStatementDescriptor(String statementDescriptor) {
this.statementDescriptor = statementDescriptor;
@@ -3722,10 +3732,10 @@ public Builder setStatementDescriptor(String statementDescriptor) {
}
/**
- * Provides information about the charge that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that's set on the account to
- * form the complete statement descriptor. Maximum 22 characters for the concatenated
- * descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the
+ * customer's statement.
*/
public Builder setStatementDescriptorSuffix(String statementDescriptorSuffix) {
this.statementDescriptorSuffix = statementDescriptorSuffix;
diff --git a/src/main/java/com/stripe/param/PaymentLinkUpdateParams.java b/src/main/java/com/stripe/param/PaymentLinkUpdateParams.java
index 0d4ab6ce16e..a0fdc578406 100644
--- a/src/main/java/com/stripe/param/PaymentLinkUpdateParams.java
+++ b/src/main/java/com/stripe/param/PaymentLinkUpdateParams.java
@@ -3240,17 +3240,22 @@ public static class PaymentIntentData {
Object metadata;
/**
- * Extra information about the payment. This will appear on your customer's statement when this
- * payment succeeds in creating a charge.
+ * Text that appears on the customer's statement as the statement
+ * descriptor for a non-card charge. This value overrides the account's default statement
+ * descriptor. Setting this value for a card charge returns an error. For card charges, set the
+ * statement_descriptor_suffix
+ * instead.
*/
@SerializedName("statement_descriptor")
Object statementDescriptor;
/**
- * Provides information about the charge that customers see on their statements. Concatenated
- * with the prefix (shortened descriptor) or statement descriptor that's set on the account to
- * form the complete statement descriptor. Maximum 22 characters for the concatenated
- * descriptor.
+ * Provides information about a card charge. Concatenated to the account's statement
+ * descriptor prefix to form the complete statement descriptor that appears on the
+ * customer's statement.
*/
@SerializedName("statement_descriptor_suffix")
Object statementDescriptorSuffix;
@@ -3396,8 +3401,13 @@ public Builder setMetadata(Map Providing this parameter will