pub struct CheckoutCardPaymentMethodOptions {
pub installments: Option<CheckoutCardInstallmentsOptions>,
pub request_extended_authorization: Option<CheckoutCardPaymentMethodOptionsRequestExtendedAuthorization>,
pub request_incremental_authorization: Option<CheckoutCardPaymentMethodOptionsRequestIncrementalAuthorization>,
pub request_multicapture: Option<CheckoutCardPaymentMethodOptionsRequestMulticapture>,
pub request_overcapture: Option<CheckoutCardPaymentMethodOptionsRequestOvercapture>,
pub request_three_d_secure: CheckoutCardPaymentMethodOptionsRequestThreeDSecure,
pub restrictions: Option<PaymentPagesPrivateCardPaymentMethodOptionsResourceRestrictions>,
pub setup_future_usage: Option<CheckoutCardPaymentMethodOptionsSetupFutureUsage>,
pub statement_descriptor_suffix_kana: Option<String>,
pub statement_descriptor_suffix_kanji: Option<String>,
}
Fields§
§installments: Option<CheckoutCardInstallmentsOptions>
Request ability to capture beyond the standard authorization validity window for this CheckoutSession.
Request ability to increment the authorization for this CheckoutSession.
request_multicapture: Option<CheckoutCardPaymentMethodOptionsRequestMulticapture>
Request ability to make multiple captures for this CheckoutSession.
request_overcapture: Option<CheckoutCardPaymentMethodOptionsRequestOvercapture>
Request ability to overcapture for this CheckoutSession.
request_three_d_secure: CheckoutCardPaymentMethodOptionsRequestThreeDSecure
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.
If not provided, this value 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.
restrictions: Option<PaymentPagesPrivateCardPaymentMethodOptionsResourceRestrictions>
§setup_future_usage: Option<CheckoutCardPaymentMethodOptionsSetupFutureUsage>
Indicates that you intend to make future payments with this PaymentIntent’s payment method.
If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don’t provide a Customer, you can still attach the payment method to a Customer after the transaction completes.
If the payment method is card_present
and isn’t a digital wallet, Stripe creates and attaches a generated_card payment method representing the card to the Customer instead.
When processing card payments, Stripe uses setup_future_usage
to help you comply with regional legislation and network rules, such as SCA.
statement_descriptor_suffix_kana: Option<String>
Provides information about a card payment that customers see on their statements. Concatenated with the Kana prefix (shortened Kana descriptor) or Kana statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 22 characters. On card statements, the concatenation of both prefix and suffix (including separators) will appear truncated to 22 characters.
statement_descriptor_suffix_kanji: Option<String>
Provides information about a card payment that customers see on their statements. Concatenated with the Kanji prefix (shortened Kanji descriptor) or Kanji statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 17 characters. On card statements, the concatenation of both prefix and suffix (including separators) will appear truncated to 17 characters.
Trait Implementations§
Source§impl Clone for CheckoutCardPaymentMethodOptions
impl Clone for CheckoutCardPaymentMethodOptions
Source§fn clone(&self) -> CheckoutCardPaymentMethodOptions
fn clone(&self) -> CheckoutCardPaymentMethodOptions
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more