Package com.stripe.param

Class PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder

java.lang.Object
com.stripe.param.PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder
Enclosing class:
PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp
public static class PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder extends Object

  • Constructor Details

    • Builder

      public Builder()

  • Method Details

    • build

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp build()
      Finalize and obtain parameter instance from this builder.

    • setCaptureMethod

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder setCaptureMethod(PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.CaptureMethod captureMethod)
      Controls when the funds will be captured from the customer's account.

      If provided, this parameter will override the top-level capture_method when finalizing the payment with this payment method type.

      If capture_method is already set on the PaymentIntent, providing an empty value for this parameter will unset the stored value for this payment method type.

    • setCaptureMethod

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder setCaptureMethod(EmptyParam captureMethod)
      Controls when the funds will be captured from the customer's account.

      If provided, this parameter will override the top-level capture_method when finalizing the payment with this payment method type.

      If capture_method is already set on the PaymentIntent, providing an empty value for this parameter will unset the stored value for this payment method type.

    • putExtraParam

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder putExtraParam(String key, Object value)
      Add a key/value pair to `extraParams` map. A map is initialized for the first `put/putAll` call, and subsequent calls add additional key/value pairs to the original map. See PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.extraParams for the field documentation.

    • putAllExtraParam

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder putAllExtraParam(Map<String,Object> map)
      Add all map key/value pairs to `extraParams` map. A map is initialized for the first `put/putAll` call, and subsequent calls add additional key/value pairs to the original map. See PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.extraParams for the field documentation.

    • setSetupFutureUsage

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder setSetupFutureUsage(PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.SetupFutureUsage setupFutureUsage)
      Indicates that you intend to make future payments with this PaymentIntent's payment method.

      Providing this parameter will attach the payment method to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions 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.

    • setSetupFutureUsage

      public PaymentIntentConfirmParams.PaymentMethodOptions.Cashapp.Builder setSetupFutureUsage(EmptyParam setupFutureUsage)
      Indicates that you intend to make future payments with this PaymentIntent's payment method.

      Providing this parameter will attach the payment method to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions 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.