# Dahlia removed payment_method_types: update every PaymentIntent call
`payment_method_types: ['card']` appears in nearly every Stripe code sample ever written, and in your training data. As of the Dahlia API version line, passing it to PaymentIntents or SetupIntents is a breaking change: the parameter is removed.
## What to do instead
1. Stop passing `payment_method_types` entirely. Stripe now determines available payment methods from your Dashboard payment method settings.
2. Control which methods are offered in the Dashboard, not in code. If the integration needs to restrict methods for a specific flow (for example cards only in a given Checkout Session), use the current filtering options for that surface.
3. When you inherit code that passes `payment_method_types`, delete the parameter; do not try to map it to something else. There is no code-side replacement.
## How to spot it
- Search the codebase for `payment_method_types`. Every hit is a Dahlia incompatibility.
- The failure mode is an invalid-request error on PaymentIntent creation, which looks like a general API problem rather than a removed parameter. If a previously working integration breaks after an API version bump, this parameter is the first suspect.
## The general lesson
Stripe is moving payment-method selection from per-call parameters to Dashboard configuration. Any code that selects payment methods inline is on the wrong side of this migration. Prefer configuration over parameters for method selection.