Struct CreatePaymentIntentPaymentMethodOptionsUsBankAccount

pub struct CreatePaymentIntentPaymentMethodOptionsUsBankAccount {
    pub financial_connections: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountFinancialConnections>,
    pub mandate_options: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountMandateOptions>,
    pub networks: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountNetworks>,
    pub preferred_settlement_speed: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountPreferredSettlementSpeed>,
    pub setup_future_usage: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountSetupFutureUsage>,
    pub target_date: Option<String>,
    pub verification_method: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountVerificationMethod>,
}

If this is a us_bank_account PaymentMethod, this sub-hash contains details about the US bank account payment method options.

Fields

financial_connections: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountFinancialConnections>

Additional fields for Financial Connections Session creation

mandate_options: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountMandateOptions>

Additional fields for Mandate creation

networks: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountNetworks>

Additional fields for network related functions

preferred_settlement_speed: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountPreferredSettlementSpeed>

Preferred transaction settlement speed

setup_future_usage: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountSetupFutureUsage>

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.

If you’ve already set setup_future_usage and you’re performing a request using a publishable key, you can only update the value from on_session to off_session.

target_date: Option<String>

Controls when Stripe will attempt to debit the funds from the customer’s account. The date must be a string in YYYY-MM-DD format. The date must be in the future and between 3 and 15 calendar days from now.

verification_method: Option<CreatePaymentIntentPaymentMethodOptionsUsBankAccountVerificationMethod>

Bank account verification method.

Implementations

impl CreatePaymentIntentPaymentMethodOptionsUsBankAccount

pub fn new() -> Self

Trait Implementations

impl Clone for CreatePaymentIntentPaymentMethodOptionsUsBankAccount

fn clone(&self) -> CreatePaymentIntentPaymentMethodOptionsUsBankAccount

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreatePaymentIntentPaymentMethodOptionsUsBankAccount

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for CreatePaymentIntentPaymentMethodOptionsUsBankAccount

fn default() -> Self

Returns the “default value” for a type.

impl Serialize for CreatePaymentIntentPaymentMethodOptionsUsBankAccount

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.