- Enclosing class:
public static class PaymentIntentConfirmParams.PaymentMethodOptions.Bancontact extends Object
Nested Class SummaryModifier and TypeClassDescription
Method SummaryModifier and TypeMethodDescription
builder()Map of extra parameters for custom features not available in this client library.Preferred language of the Bancontact authorization page that the customer is redirected to.Indicates that you intend to make future payments with this PaymentIntent's payment method.
builderpublic static PaymentIntentConfirmParams.PaymentMethodOptions.Bancontact.Builder builder()
getExtraParamsMap of extra parameters for custom features not available in this client library. The content in this map is not serialized under this field's
@SerializedNamevalue. Instead, each key/value pair is serialized as if the key is a root-level field (serialized) name in this param object. Effectively, this map is flattened to its parent instance.
getPreferredLanguagepublic PaymentIntentConfirmParams.PaymentMethodOptions.Bancontact.PreferredLanguage getPreferredLanguage()Preferred language of the Bancontact authorization page that the customer is redirected to.
getSetupFutureUsagepublic ApiRequestParams.EnumParam getSetupFutureUsage()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_usageto dynamically optimize your payment flow and comply with regional legislation and network rules, such as SCA.
setup_future_usageis already set and you are performing a request using a publishable key, you may only update the value from