Anyone experiencing issues with brand new Stripe accounts and the Bubble plugin?
When using the official Bubble Stripe plugin to update an existing user subscription, we’re receiving a Stripe error related to billing_mode.type = flexible.
The Stripe account is configured with Billing Type: Classic but every new subscription is still being created with billing_mode = flexible, which is not supported by the plugin’s update subscription action.
This behaviour only occurs on the Stripe account using API version 2025-11-17.clover. On other apps, which use API version 2025-06-30.basil, new subscriptions are created as classic and the Bubble plugin works as expected.
Creating a new subscription works, but subsequently updating that existing subscription action fails with the above error.
Anyone experienced this? I’ve opened a Bubble support ticket but it’s taking a while to get a reply from the devs and it’s holding up a project.
It is possible that with the new version of Stripe, there may be some error in the Bubble plugin…
I don’t know what requests you make to Stripe and how many, but I would recommend that you migrate them, or part of them, to the API connector, making calls directly to Stripe in the API connector.
That way, there is no chance of something being wrong or out of date.
Hi Reece,
I aso had a similar chalenge. I realized that with API version 2025-09-30.clover or newer, Stripe defaults all new subscriptions to “flexible” billing mode. If the request API version is older than 2025-09-30.clover, the default is classic billing mode.
The problem is that the Bubble plugin’s “Update Subscription” action sends deprecated parameters (plan, quantity) that are not supported when billing_mode.type=flexible is set on a subscription. Even though you’ve configured your Stripe account billing settings to “Classic,” new Stripe accounts on API version 2025-11-17.clover automatically create subscriptions in flexible mode by default.
Solution:
Change Default Billing Mode in Stripe Dashboard (Quickest Fix)
Go to Settings → Billing → Subscriptions and emails and change the billing mode default setting:
Select “Classic” to ensure both flexible and classic billing modes are displayed, with classic selected by default
This option is recommended if your integration depends on classic billing mode and you cannot migrate to flexible billing yet.
Then delete the test subscriptions created with flexible mode and recreate them—they should now be created as classic.
Any response from the Bubble team?
I also reached out to them regarding the plugin issue but what they are suggesting is to delete existing subscription and create new one or to use API calls. Both of these solutions are a workaround but they didn’t mentioned anything about updating the official plugin.
It’s being investigated apparently but I’m surprised it’s not top of the priority list as so many new apps with new stripe accounts with the incompatible api version from December are likely affected
this is concerning. is stripe still the main the go-to for most “Google Pay/Apple Pay” billing in the US? e.g Quick Checkout. I don’t love them having a monopoly but asking for credit card details in 2026 is not the move.
I don’t know if bubble even has reasonable stripe alternatives in the USA. I don’t think I’ve ever even seen a braintree checkout in the wild.