- Breaking changes
- Public preview
Removes support for specifying payment method types in Payment Intents and Setup Intents Breaking changes Public preview
What’s new
Removes payment_method_types as a writable parameter from the create, update, and confirm methods on Payment Intents, and from the create and update methods on Setup Intents. Passing payment_method_types now returns a 400 error with the code payment_method_types_no_longer_supported.
The PaymentIntent and SetupIntent objects still return payment_method_types as a read-only property, reflecting the computed list of available payment methods.
Why is this a breaking change?
Previously, payment_method_types accepted a list of payment method types to explicitly set which methods to present on a Payment Intent or Setup Intent. This change disables writing to this parameter and returns a 400 error on requests that pass payment_method_types on the affected endpoints.
Impact
If your integration passes payment_method_types when creating, updating, or confirming a PaymentIntent or SetupIntent, you must remove it before upgrading to API version 2026-08-26.preview or later.
You can replace it with dynamic payment methods to automatically determine available payment methods based on other parameters such as currency, amount, and customer. If you need more control:
- Use excluded_payment_method_types to exclude specific types from the set determined by dynamic payment methods.
- Use allowed_payment_method_types to specify a list of types you want to accept. Stripe filters out incompatible types instead of returning an error.
You can continue to read payment_method_types to retrieve the computed list of available payment methods.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| payment_method_types | Removed | PaymentIntent#confirm PaymentIntent#create PaymentIntent#update + 2 more SetupIntent#create SetupIntent#update |
Upgrade
- View your current API version in Workbench.
- If you use an SDK, upgrade to the corresponding SDK version for this API version.
- If you don’t use an SDK, update your API requests to include Stripe-Version: 2026-08-26. preview
- Upgrade the API version used for webhook endpoints .
- Test your integration against the new version.
- If you use Connect, test your Connect integration .
- In Workbench, perform the upgrade . You can roll back the version for 72 hours.
Learn more about Stripe API upgrades.