Adds the allowed payment method types parameter to Payment Intents and Setup Intents
What’s new
Adds the allowed_payment_method_types parameter to Payment Intents and Setup Intents. This parameter accepts an array of payment method types and filters the list to only compatible payment methods based on other parameters such as currency, amount, and customer. We reflect the resulting compatible subset in the payment_method_types property of the response.
Unlike the payment_method_types parameter, which returns an error when you specify an incompatible payment method, allowed_payment_method_types silently filters out incompatible methods and returns only those that work with the current configuration.
This parameter is mutually exclusive with payment_method_types, excluded_payment_method_types, automatic_payment_methods, and payment_method_configuration.
Impact
If your integration currently uses payment_method_types to manually specify which methods to accept, you can switch to allowed_payment_method_types to get automatic compatibility filtering instead of errors. To migrate:
- Replace payment _ method _ types with allowed _ payment _ method _ types on your create, update, or confirm calls, passing the same array of payment method types you support.
- Remove any error-handling logic that catches incompatible payment method errors, since incompatible types are filtered out automatically.
- Read the payment _ method _ types property on the response to see which of your allowed types we determined to be compatible with the current configuration.
Changes
| Parameter | Change | Resources or endpoints |
|---|---|---|
| allowed_payment_method_types | Added | PaymentIntent PaymentIntent#confirm PaymentIntent#create + 5 more PaymentIntent#update SetupIntent SetupIntent#confirm 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-07-29. dahlia
- 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.
Related changes
- Adds the ability to update shipping options, consent collection, and future usage support on Payment Links
- Adds the ability to indicate that you don’t intend to reuse Samsung Pay and the related setting payment method types
- Adds customer and payment method details to the Refunds API
- Adds support for new banks to FPX payments
- Adds the related setting as a supported network for funding instructions
- Adds MB WAY support to the hosted invoice page
- Adds card network details to the Dispute object
- Adds the ability to list Payment Records