pub struct UpdatePaymentIntentPaymentMethodOptionsBancontact {
pub preferred_language: Option<UpdatePaymentIntentPaymentMethodOptionsBancontactPreferredLanguage>,
pub setup_future_usage: Option<UpdatePaymentIntentPaymentMethodOptionsBancontactSetupFutureUsage>,
}
Fields§
§preferred_language: Option<UpdatePaymentIntentPaymentMethodOptionsBancontactPreferredLanguage>
Preferred language of the Bancontact authorization page that the customer is redirected to.
setup_future_usage: Option<UpdatePaymentIntentPaymentMethodOptionsBancontactSetupFutureUsage>
Indicates that you intend to make future payments with this PaymentIntent’s payment method.
Providing this parameter will attach the payment method to the PaymentIntent’s Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete.
If no Customer was provided, the payment method can still be attached to a Customer after the transaction completes. When processing card payments, Stripe also uses setup_future_usage
to dynamically optimize your payment flow and comply with regional legislation and network rules, such as SCA. If setup_future_usage
is already set and you are performing a request using a publishable key, you may only update the value from on_session
to off_session
.
Trait Implementations§
source§impl Clone for UpdatePaymentIntentPaymentMethodOptionsBancontact
impl Clone for UpdatePaymentIntentPaymentMethodOptionsBancontact
source§fn clone(&self) -> UpdatePaymentIntentPaymentMethodOptionsBancontact
fn clone(&self) -> UpdatePaymentIntentPaymentMethodOptionsBancontact
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more