Struct stripe::UpdateSetupIntent

pub struct UpdateSetupIntent<'a> {
    pub attach_to_self: Option<bool>,
    pub customer: Option<CustomerId>,
    pub description: Option<&'a str>,
    pub expand: &'a [&'a str],
    pub flow_directions: Option<Vec<UpdateSetupIntentFlowDirections>>,
    pub metadata: Option<Metadata>,
    pub payment_method: Option<PaymentMethodId>,
    pub payment_method_configuration: Option<PaymentMethodConfigurationId>,
    pub payment_method_data: Option<UpdateSetupIntentPaymentMethodData>,
    pub payment_method_options: Option<UpdateSetupIntentPaymentMethodOptions>,
    pub payment_method_types: Option<Vec<String>>,
}

The parameters for SetupIntent::update.

Fields

attach_to_self: Option<bool>

If present, the SetupIntent’s payment method will be attached to the in-context Stripe Account.

It can only be used for this Stripe Account’s own money movement flows like InboundTransfer and OutboundTransfers.

It cannot be set to true when setting up a PaymentMethod for a Customer, and defaults to false when attaching a PaymentMethod to a Customer.

customer: Option<CustomerId>

ID of the Customer this SetupIntent belongs to, if one exists.

If present, the SetupIntent’s payment method will be attached to the Customer on successful setup.

Payment methods attached to other Customers cannot be used with this SetupIntent.

description: Option<&'a str>

An arbitrary string attached to the object.

Often useful for displaying to users.

expand: &'a [&'a str]

Specifies which fields in the response should be expanded.

flow_directions: Option<Vec<UpdateSetupIntentFlowDirections>>

Indicates the directions of money movement for which this payment method is intended to be used.

Include inbound if you intend to use the payment method as the origin to pull funds from.

Include outbound if you intend to use the payment method as the destination to send funds to. You can include both if you intend to use the payment method for both purposes.

metadata: Option<Metadata>

Set of key-value pairs that you can attach to an object.

This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to metadata.

payment_method: Option<PaymentMethodId>

ID of the payment method (a PaymentMethod, Card, or saved Source object) to attach to this SetupIntent.

payment_method_configuration: Option<PaymentMethodConfigurationId>

The ID of the payment method configuration to use with this SetupIntent.

payment_method_data: Option<UpdateSetupIntentPaymentMethodData>

When included, this hash creates a PaymentMethod that is set as the payment_method value in the SetupIntent.

payment_method_options: Option<UpdateSetupIntentPaymentMethodOptions>

Payment method-specific configuration for this SetupIntent.

payment_method_types: Option<Vec<String>>

The list of payment method types (for example, card) that this SetupIntent can set up.

If you don’t provide this array, it defaults to [“card”].

Implementations

impl<'a> UpdateSetupIntent<'a>

pub fn new() -> Self

Trait Implementations

impl<'a> Clone for UpdateSetupIntent<'a>

fn clone(&self) -> UpdateSetupIntent<'a>

Returns a copy of the value.

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

Performs copy-assignment from source.

impl<'a> Debug for UpdateSetupIntent<'a>

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

Formats the value using the given formatter.

impl<'a> Default for UpdateSetupIntent<'a>

fn default() -> UpdateSetupIntent<'a>

Returns the “default value” for a type.

impl<'a> Serialize for UpdateSetupIntent<'a>

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

where __S: Serializer,

Serialize this value into the given Serde serializer.