Class SetupIntentUpdateParams.PaymentMethodOptions.Card

java.lang.Object
com.stripe.param.SetupIntentUpdateParams.PaymentMethodOptions.Card
Enclosing class:
SetupIntentUpdateParams.PaymentMethodOptions

public static class SetupIntentUpdateParams.PaymentMethodOptions.Card extends Object
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 SetupIntentUpdateParams.PaymentMethodOptions.Blik.extraParams for the field documentation.
  • Method Details

    • builder

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

      Configuration options for setting up an eMandate for cards issued in India.
    • getMoto

      public Boolean getMoto()
      When specified, this parameter signals that a card has been collected as MOTO (Mail Order Telephone Order) and thus out of scope for SCA. This parameter can only be provided during confirmation.
    • 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.