Struct PaymentMethodOptionsWechatPay

pub struct PaymentMethodOptionsWechatPay {
    pub app_id: Option<String>,
    pub client: Option<PaymentMethodOptionsWechatPayClient>,
    pub setup_future_usage: Option<PaymentMethodOptionsWechatPaySetupFutureUsage>,
}

Fields

app_id: Option<String>

The app ID registered with WeChat Pay. Only required when client is ios or android.

client: Option<PaymentMethodOptionsWechatPayClient>

The client type that the end customer will pay from

setup_future_usage: Option<PaymentMethodOptionsWechatPaySetupFutureUsage>

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.

Trait Implementations

impl Clone for PaymentMethodOptionsWechatPay

fn clone(&self) -> PaymentMethodOptionsWechatPay

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for PaymentMethodOptionsWechatPay

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

Formats the value using the given formatter.

impl Deserialize for PaymentMethodOptionsWechatPay

fn begin(out: &mut Option<Self>) -> &mut dyn Visitor

The only correct implementation of this method is:

impl FromValueOpt for PaymentMethodOptionsWechatPay

fn from_value(v: Value) -> Option<Self>

impl ObjectDeser for PaymentMethodOptionsWechatPay

type Builder = PaymentMethodOptionsWechatPayBuilder