Class PaymentIntentConfirmParams.PaymentMethodOptions.AfterpayClearpay

Enclosing class:

public static class PaymentIntentConfirmParams.PaymentMethodOptions.AfterpayClearpay extends Object
  • Method Details

    • builder

    • getCaptureMethod

      public ApiRequestParams.EnumParam getCaptureMethod()
      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.

    • 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.
    • getReference

      public String getReference()
      Order identifier shown to the customer in Afterpay’s online portal. We recommend using a value that helps you answer any questions a customer might have about the payment. The identifier is limited to 128 characters and may contain only letters, digits, underscores, backslashes and dashes.
    • 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.