Dynamic payment methods is part of the default Stripe integration and enables you to configure payment methods settings from the Dashboard—no code required. When you use dynamic payment methods in an Element, Checkout, Payment Links, or hosted invoice page integration, Stripe handles the logic for dynamically displaying the most relevant eligible payment methods to each customer to maximize conversion. Dynamic payment methods also unlocks customization features to help you customize and experiment with payment methods.

Use dynamic payment methods to:

• Turn on and manage most payment methods in the Dashboard
• Eliminate the need to specify eligibility requirements for individual payment methods
• Apply Stripe’s AI models based on more than 100 signals to dynamically determine which payment methods are eligible and how to display them in order for every checkout session
• Set rules when payment methods are shown to customers
• Exclude payment methods for specific transactions
• Run A/B Tests for new payment methods before rolling them out to customers

Integration options

Use Checkout or Payment Element with dynamic payment methods to have Stripe handle the logic for displaying eligible payment methods in your frontend for each transaction. If you have a platform account, follow our Connect integration.

Dashboard-based customization features

Access the following features with dynamic payment methods to control how and when payment methods render.

How dynamic payment methods work

Review this section to understand the criteria that Stripe uses to eligible payment methods, decide whether to hide or show them, and in what order. If a specific payment method isn’t appearing in your payment flow, one or more of these criteria might not be met.

Dashboard settings

View the available payment methods in your Stripe Dashboard. Only payment methods that you enabled can be shown to your customers.

If a payment method isn’t listed in your Dashboard settings, it’s either not supported by Stripe or not supported in the country where your account is registered. For example, PayNow is only available to Stripe accounts in Singapore.

Learn more about country support.

Exclude payment methods

While dynamic payment methods allows you to manage payment methods through the Dashboard, you can also exclude specific payment methods on a per-transaction basis using the excluded_payment_method_types parameter when creating a PaymentIntent. This gives you control over which payment methods are available for each transaction, even if they’re enabled in your Dashboard settings.

Today, excluded_payment_method_types is available using PaymentIntents, SetupIntents, Checkout, and Payment Element. To exclude payment methods for a specific PaymentIntent:

curl https://api.stripe.com/v1/payment_intents \
  -u "sk_test_...:" \
  -d amount=1000 \
  -d currency=usd \
  -d "automatic_payment_methods[enabled]=true" \
  -d "excluded_payment_method_types[]=affirm" \
  -d "excluded_payment_method_types[]=acss_debit"

Product support

Several Stripe products allow you to charge customers, such as Checkout Sessions and Payment Element. Not all payment methods are available in all products. For example, Bacs Direct Debit isn’t available in the Mobile Payment Element. Some payment methods, such as Swish, don’t support recurring payments.

Learn more about product support.

Presentment currency

Stripe supports over 135 presentment currencies, but most payment methods only support a subset of these. For example, ACH Direct Debit is only available for payments in USD currency.

Learn more about currency support.

Charge amount

On top of the general minimum and maximum amount Stripe supports, some payment methods have their own minimum and maximum. For example, SEPA Direct Debit is only available for payments below 10,000 EUR.

To learn more, go to that payment method’s overview page.

API support

Some payment methods, such as TWINT, can’t be set up for future usage. When you set setup_future_usage, some payment methods are automatically filtered out.

Similarly, some payment methods, such as iDEAL, don’t support manual capture. When you set capture_method: manual, some payment methods are automatically filtered out.

Learn more about API support.

Customer’s country

A customer’s country impacts which payment methods are available on the payment page, because most payment methods are available in a predefined number of countries. For example, BLIK is only available for customers in Poland.

Learn more about country support.

Other considerations

The following features can also impact the availability of some payment methods:

• Payment method configuration, to customize the payment method shown.
• Payment method rules, to show or hide a payment method based on conditions, such as the amount and currencies.
• A/B testing, to temporarily show or hide a payment method to see its impact on conversion rates.

AI models

For every checkout session, the AI models in the Optimized Checkout Suite dynamically determine how eligible payment methods are displayed, including their order. These models incorporate more than 100 on-session signals—such as real-time payment method uptime and popularity among similar customers—as well as broader network signals, such as preferred payment methods used by similar businesses. The AI models work alongside any payment method logic you add in code or any rules you set up in the Dashboard.

Our AI models use an exploration-exploitation framework, delivering proven strategies while continuously testing new approaches. As a result, payment method ordering quickly adapts to changing customer expectations and systematically improves over time.