05 Nov Stripe’s Endive API Release: What eCommerce Teams Should Check Before Peak Season
Most eCommerce teams only think about their Stripe API version when something breaks. That habit is risky this autumn. On 30 September 2026 Stripe released 2026-09-30.endive, the first version of a new major release called Endive, and on 28 October it followed with 2026-10-28.endive. According to Stripe’s Endive changelog, the September version introduces breaking changes, while later Endive versions include only additive changes.
Nothing changes for your store until you move your integration to the new version. But the gap between what your checkout code expects and what new SDKs, plugins and documentation assume grows every month, and the worst time to discover that gap is the week of Black Friday. This guide covers what Endive changes for online retailers, what is genuinely useful in the October update, and a practical way to plan the upgrade around peak season.
Key takeaways
- Endive starts with
2026-09-30.endive, which contains breaking changes. Later Endive versions, including2026-10-28.endive, are additive only. - The biggest checkout change is the removal of the
payment_method_typesparameter from Checkout Sessions, Payment Intents and Setup Intents, in favour of dynamic payment methods orallowed_payment_method_types. - Stripe has deprecated the payment request button in Stripe.js, so stores still using it for Apple Pay or Google Pay should plan a move.
- The October update adds useful retail features: evidence submission for dispute appeals, refund reference tracking for Klarna, PayPal and Afterpay Clearpay, and card-on-file usage when saving or charging cards.
- If you cannot test properly before your code freeze, upgrade after the holidays. A rushed API upgrade is a bigger risk than an old one.
What Endive is and why the version matters
Stripe pins every account and every request to an API version. Your integration keeps getting the response shapes and behaviour of the version it was built against until you choose to upgrade, which is why an old integration can keep working for years. Stripe names its major releases after plants. Endive is the fifth, after Acacia, Basil, Clover and Dahlia, and Stripe says it moves to a new release name every time it introduces a breaking change version.
That gives you a simple rule. Moving from a Dahlia version to 2026-09-30.endive needs a proper review, because response fields and accepted parameters change. Moving between Endive versions later should be routine. Stripe’s upgrade guide covers how to test a new version on individual requests before you change your account default, and that is the approach we recommend.
The Endive changes most likely to affect an online store
The full changelog runs across Billing, Connect, Treasury, Tax and more. For a typical retailer on Stripe Checkout or Elements, these are the items worth checking first.
Payment method configuration in Checkout and Elements
This is the change most stores will feel. Stripe removed the payment_method_types parameter from Checkout Sessions and removed the writable version from Payment Intents and Setup Intents. In Stripe.js, the paymentMethodTypes option for Elements is gone. Stripe’s guidance is to use dynamic payment methods, managed from the Dashboard, or to filter explicitly with allowed_payment_method_types or excluded_payment_method_types on Checkout, and allowedPaymentMethodTypes in Elements.
If your code hard-codes a list such as card and Klarna, that list has to move. Many teams will find this is a good moment to switch to dynamic payment methods, so merchandising or finance can turn methods on and off in the Dashboard without a deployment.
The payment request button is deprecated
Endive marks the payment request button in Stripe.js as deprecated. Older storefronts often use it to show Apple Pay and Google Pay. Stripe’s payment request button documentation points to the Express Checkout Element as the way forward. This is not an emergency, but it is the kind of change to schedule now rather than discover later.
Radar, 3D Secure and fraud signals
- Payment Evaluation signal scores in Radar are now nullable. Code that treats a missing score as a number, or that expects a placeholder value, needs a guard.
- Stripe added support for Data Share Only for 3D Secure authentication, listed as a breaking change, plus a new Standalone 3D Secure API.
- Payment Evaluations gain early fraud warnings and fraudulent dispute signals, which fraud teams may want to feed into their own review rules.
Elements with Checkout Sessions and dispute evidence
Three smaller Stripe.js changes affect stores that pair Elements with Checkout Sessions: canConfirm is now false while updates are pending, empty optional address fields are allowed, and billing details are required when collection is turned off in the Payment Element. Separately, Endive adds page limit validation for dispute evidence, so any tool that uploads large evidence bundles automatically should be tested.
What the October update adds for retailers
The 2026-10-28.endive version is additive, so it brings new capabilities without breaking anything that already works on Endive. Several are directly useful for online retail.
Dispute appeals and Smart Disputes
You can now stage or submit evidence when appealing an eligible dispute decision through the API. A new submission method property lets you say whether evidence will be submitted manually or by Smart Disputes, and shows how evidence was actually submitted. With chargebacks from the holiday season arriving in December and January, this is worth wiring into your support or finance workflow.
Refund tracking and card-on-file
- Refund reference tracking for Klarna, PayPal and Afterpay Clearpay, which makes reconciliation and customer service conversations easier.
- Card-on-file usage can now be specified when saving or charging cards, relevant to subscriptions, saved wallets and one-click reorders.
- Payment intent data can be configured when updating Checkout Sessions, and invoice settings can be set for Checkout Sessions and Payment Links subscriptions.
New payment methods and billing options
The October update adds Scalapay on Payment Links and SeQura for invoices and subscriptions. In the customer portal, subscribers can now pause subscriptions, and an expired portal session can be recovered by verifying an email address. Stripe also lists the Wero bank redirect method for EU customers in its public preview channel, which is not yet general availability.
Endive changes at a glance
Use this table to decide which items need code changes, which are optional, and who should own them.
| Change | Type | Who is affected | What to do |
|---|---|---|---|
payment_method_types removed from Checkout Sessions, Payment Intents and Setup Intents | Breaking (2026-09-30) | Stores that hard-code payment methods | Move to dynamic payment methods or allowed_payment_method_types |
paymentMethodTypes removed from Elements | Breaking (2026-09-30) | Custom Elements checkouts | Use allowedPaymentMethodTypes or the Dashboard |
| Payment request button deprecated | Breaking (2026-09-30) | Older Apple Pay and Google Pay buttons | Plan a move to the Express Checkout Element |
| Radar signal scores nullable | Breaking (2026-09-30) | Custom fraud rules and reports | Handle null values in code and dashboards |
| Dispute evidence page limit validation | Breaking (2026-09-30) | Automated dispute tools | Test evidence uploads |
| Dispute appeal evidence and submission method | Additive (2026-10-28) | Finance and support teams | Add to the chargeback workflow |
| Refund references for Klarna, PayPal and Afterpay Clearpay | Additive (2026-10-28) | Finance and customer service | Store references for reconciliation |
| Card-on-file usage when saving or charging cards | Additive (2026-10-28) | Subscriptions and saved cards | Review with your payments lead |

How to plan the upgrade around peak season
Take an inventory first
Before anyone changes code, list every place your business calls Stripe. For many retailers that is more than one system: the storefront or platform plugin, an order management system, a subscriptions app, a returns tool, finance reporting and sometimes a marketplace connector. Note the API version and SDK version each one uses, and which webhooks each one listens to.
- Search your code for
payment_method_types,paymentMethodTypesand the payment request button. - Check whether your platform plugin, for example on Adobe Commerce, WooCommerce or a headless build, has released an Endive-compatible version.
- Confirm which webhook endpoints exist and which API version their events are rendered in.
Test in a sandbox, request by request
Stripe lets you send individual requests with a newer API version, so you can test new code paths in a sandbox before you change the account default. Run real scenarios: a card payment with 3D Secure, a wallet payment, a buy now pay later order, a refund, a partial refund and a dispute in test mode. Check that your order states, emails and accounting exports still match.

Decide before your code freeze
Black Friday is on 27 November 2026 and Cyber Monday on 30 November. Most stores freeze code at least a week before. If your team can finish inventory and testing by mid November, upgrading now gives you a cleaner base for the season. If not, keep your current version, which Stripe continues to honour, and schedule the upgrade for January. The one thing to avoid is a half-finished upgrade going live in Thanksgiving week.

How WeVerve helps
WeVerve Systems builds and supports payment integrations for eCommerce brands on Adobe Commerce, Shopify, BigCommerce, WooCommerce and headless stacks, including Stripe, PayPal and Authorize.net. We can audit your Stripe integration against the Endive changelog, list exactly what needs to change, test it in a sandbox and help you choose a safe upgrade window around peak season. Our 24/7 support team can also watch payments and webhooks through Black Friday and Cyber Monday.
If you want a second pair of eyes on your Stripe setup before the holidays, talk to our team.
No Comments