Stripe Payments not being recorded (0.025% of the time...)

[benlenzo]

Hiya,

I’m seeking input from others that have implemented Stripe and have processed hundreds if not thousands of transactions via Stripe/Bubble.

We have a build that has processed almost 1,200 transactions since Jan 1, 2025. 3 of those transactions - with no distinguishing elements to them i.e. they are bog standard, just like the other 1197 - have failed to send data back to Bubble.

The transactions are successful, Stripe marks them as such, but this data doesn’t hit Bubble. So, no logs either… And then of course, because the Bubble has not detected that payment has been made (even though Stripe and the customer are told it is, and… it has been), there are internal processes that do not get kicked off as a result.

1 time? Ok, not ideal.
Twice? Curious.
Three times? Man, this is not ok.

We can blame webhooks, outages, workflows etc, but financial transactions cannot be allowed to fail!

I’m curious if anyone else has experienced this, and how/if they were able to track down an internal to Bubble/Stripe solution.

We can implement external checks, but this seems a (hopefully) unnecessary complication.

Cheers,
Ben

[mitchbaylis]

Did you check the stripe webhook history to see if:

a) webhook was sent
b) if it retried on failure (or if it was success)
c) if fault is stripe sending or bubble receiving

I haven’t encountered this issue and I’ve used bubble stripe integration for hundreds of transactions personally and a few thousand across bubble apps I manage.

Having said that, I also haven’t done a cross check to see if there is an issue. The webhooks have always been successful so I’ve never doubted that it was working.

[georgecollier]

@mitchbaylis

Did you check the stripe webhook history to see if:

a) webhook was sent
b) if it retried on failure (or if it was success)
c) if fault is stripe sending or bubble receiving

^^^

Find out if the webhook ever left Stripe. If Stripe sent it but Bubble didn’t receive it, then the webhook URL or public backend workflow that receives it is probably misconfigured. If Stripe didn’t send it, you’re probably listening to the wrong trigger event.