Bubble <> Stripe integration breaking workflow

Need help
1

A new issue arose today. I’ve always been using the standard Stripe plugin, which redirects users to the Stripe checkout and then back to the dashboard upon successful payment.

I have a single workflow that calls to the Stripe plugin and then makes a change to the user’s DB information. It’s always worked, but starting today, the workflow doesn’t continue after the Stripe plugin/redirect, thus the user’s information in Bubble is not being updates, resulting in them getting charged, but their account not being updated to ‘paid’.

Anyone else experiencing this issue?

Screenshot 2025-08-19 at 10.34.09 AM
Screenshot 2025-08-19 at 10.34.09 AM972×466 53.1 KB

1 Like
2

Is this bubble stripe plugin you are using?

3

Yes, it is. Has never been an issue until today.

4

Hey @datasetmatchllc :waving_hand:

This isn’t the most reliable way to track a persons subscription status when using the Bubble Stripe Plugin. Bubble has those fields built into the User. You can access it by saying Current User’s Stripe Subscription Status. If it is ‘active’ that means they have an up to date subscription.

Hope that helps. :blush:

5

Thanks, so how are you passing the information into Bubble? Is it the same workflow? Backend workflow / webhook?

6

Bubble does it automatically. No need to pass it to Bubble.

7

Oh, I see. Much simpler, but will need to change a lot of dynamic content on my end. I’ll explore. Thanks!

2 Likes
8

checking with the team and will pick up your bug report from the queue to expedite a resolution @datasetmatchllc !

9

also having this issue and submitted a bug report.

10

@founder6 are you still experiencing this issue? I think the engineering team reverted some changes that should’ve addressed this

11

I reported the same issue a couple of months back, nothing was done about it as the team could not replicate the issue.

12

This is the main reason we built two different Stripe plugins.

Link: Stripe Marketplace API Payments Plugin | Bubble

Link: Stripe Payment Element 3DS Plugin | Bubble

There’s a few steps here to follow to get it working right.

  1. Create a customer and store the customer ID in your database
  2. Create a webhook in the backend to watch for subscriptions from Customers using the Customer ID
  3. Create a webhook to watch for subscription cancelled events.
  4. Optionally use our payment element plugin on the front end to avoid redirecting to Stripe.
13

Just about to submit a bug report, but it looks like this functionality has broken over the past few days. Bubble isn’t correctly storing those default Stripe fields like Customer ID etc, since around the 18th

14

Awe man. :man_facepalming: So either way it won’t work then. I hope they can go back and fix things somehow since I’m sure people have lost money because of that.

15

hey @macklpgr I’m going to flag this to success so they can take a look. Mind sending me a DM with the ticket # you got when submitting the report?

16

I’ve submitted under the bug report flow in live chat, but doesn’t look to have given me a ticket number (yet). It was submitted under macklpgr@gmail.com.

Issuing refunds/credit notes as we speak due to this, so very high priority for me and I suspect lots of others that monetise bubble apps via Stripe.

2 Likes
17

Strange. Also having Stripe issues yesterday-today, seems like the API-calls/structure has changed somehow; getting both 400 errors from Stripe and Google. Using Stripe via direct API-calls (api plugin) and the Google oauth plugin.

18

For me, when I change to Version 3 in plugin settings, it started working. Version 3 is also recommended.

19

Is there any update on this? We’re still having to piece together data in the backend and contact customers to ask for missing data we need to fulfil purchases. I have rebuilt quite a few workflows to compensate.

20

it’s been a while since this was flagged so at this point I would recommend you submit a bug report to support so they can take a look at what’s going on with the app