Class PaymentIntentUpdateParams.PaymentMethodOptions.Card

    • Method Detail

      • getCvcToken

        public java.lang.Object getCvcToken()
        A single-use cvc_update Token that represents a card CVC value. When provided, the CVC value will be verified during the card payment attempt. This parameter can only be provided during confirmation.
      • getExtraParams

        public java.util.Map<java.lang.String,​java.lang.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.
      • getMoto

        public java.lang.Boolean getMoto()
        When specified, this parameter indicates that a transaction will be marked as MOTO (Mail Order Telephone Order) and thus out of scope for SCA. This parameter can only be provided during confirmation.
      • getRequestThreeDSecure

        public PaymentIntentUpdateParams.PaymentMethodOptions.Card.RequestThreeDSecure getRequestThreeDSecure()
        We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and other requirements. However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. Permitted values include: automatic or any. If not provided, defaults to automatic. Read our guide on manually requesting 3D Secure for more information on how this configuration interacts with Radar and our SCA Engine.
      • getSetupFutureUsage

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