pub struct CreateSetupIntentPaymentMethodOptionsCard {
pub mandate_options: Option<CreateSetupIntentPaymentMethodOptionsCardMandateOptions>,
pub moto: Option<bool>,
pub network: Option<CreateSetupIntentPaymentMethodOptionsCardNetwork>,
pub request_three_d_secure: Option<CreateSetupIntentPaymentMethodOptionsCardRequestThreeDSecure>,
}
Fields§
§mandate_options: Option<CreateSetupIntentPaymentMethodOptionsCardMandateOptions>
Configuration options for setting up an eMandate for cards issued in India.
moto: Option<bool>
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.
network: Option<CreateSetupIntentPaymentMethodOptionsCardNetwork>
Selected network to process this SetupIntent on.
Depends on the available networks of the card attached to the SetupIntent. Can be only set confirm-time.
request_three_d_secure: Option<CreateSetupIntentPaymentMethodOptionsCardRequestThreeDSecure>
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.
Trait Implementations§
source§impl Clone for CreateSetupIntentPaymentMethodOptionsCard
impl Clone for CreateSetupIntentPaymentMethodOptionsCard
source§fn clone(&self) -> CreateSetupIntentPaymentMethodOptionsCard
fn clone(&self) -> CreateSetupIntentPaymentMethodOptionsCard
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more