Removes the payment method types parameter from Checkout SessionsBreaking changes

What’s new

Removes the payment_method_types parameter from the create Checkout Session method. You can no longer pass payment_method_types when you create a Checkout Session. Use dynamic payment methods to manage payment methods from the Dashboard without writing code.

You can also use excluded_payment_method_types to exclude specific payment methods from the dynamic payment methods results or the new allowed_payment_method_types parameter to specify a set of payment methods.

The allowed_payment_method_types parameter accepts an array of payment method type and filters the list to only compatible payment methods based on other parameters such as currency, amount, and customer. The compatible subset is shown in the payment_method_types property of the response.

Previously, payment_method_types returned an error when you specified an incompatible payment method. allowed_payment_method_types silently filters out incompatible methods and returns only those that work with the current configuration.

Why is this a breaking change?

Passing payment_method_types as a parameter when you create a Checkout Session now returns a 400 error. If your integration sets this parameter, you must remove it and migrate to dynamic payment methods or allowed_payment_method_types.

Impact

This migration requires careful attention if your integration passes payment_method_types when creating a Checkout Session. You must update your integration to use dynamic payment methods or switch to allowed_payment_method_types to get automatic compatibility filtering instead of errors. Requests that include payment_method_types on this now return a 400 error.

Changes

Upgrade