Package com.stripe.param

Class PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance

java.lang.Object
com.stripe.param.PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance
Enclosing class:
PaymentIntentUpdateParams.PaymentMethodOptions
public static class PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance extends Object
Request ability to increment this PaymentIntent if the combination of MCC and card brand is eligible. Check incremental_authorization_supported in the Confirm response to verify support.

  • Method Details

    • builder

      public static PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance.Builder builder()

    • getBankTransfer

      public PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance.BankTransfer getBankTransfer()
      Configuration for the bank transfer funding type, if the funding_type is set to bank_transfer.

    • getExtraParams

      public Map<String,Object> getExtraParams()
      Map of extra parameters for custom features not available in this client library. The content in this map is not serialized under this field's @SerializedName value. Instead, each key/value pair is serialized as if the key is a root-level field (serialized) name in this param object. Effectively, this map is flattened to its parent instance.

    • getFundingType

      public PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance.FundingType getFundingType()
      The funding method type to be used when there are not enough funds in the customer balance. Permitted values include: bank_transfer.

    • getSetupFutureUsage

      public PaymentIntentUpdateParams.PaymentMethodOptions.CustomerBalance.SetupFutureUsage getSetupFutureUsage()
      Indicates that you intend to make future payments with this PaymentIntent's payment method.

      Providing this parameter will attach the payment method to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be attached to a Customer after the transaction completes.

      When processing card payments, Stripe also uses setup_future_usage to dynamically optimize your payment flow and comply with regional legislation and network rules, such as SCA.

      If setup_future_usage is already set and you are performing a request using a publishable key, you may only update the value from on_session to off_session.