# Securing Stripe webhooks without authentication

**URL:** <https://forum.bubble.io/t/securing-stripe-webhooks-without-authentication/281120>\
**Category:** Tips\
**Created:** [September 2, 2023, 2:36pm UTC](https://forum.bubble.io/t/securing-stripe-webhooks-without-authentication/281120 "2023-09-02T14:36:07Z")\
**Posts on this page:** 1\
**Showing post:** 33

<div class="post-metadata">

**Author:** ![sudsy](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sudsy/32/114637_2.png) [@sudsy](https://forum.bubble.io/u/sudsy)\
**Post date:** [June 5, 2024, 6:11pm UTC](https://forum.bubble.io/t/securing-stripe-webhooks-without-authentication/281120/33 "2024-06-05T18:11:35Z")

</div>

Just stumbled upon this thread. Nice summary, @georgecollier . It seems to reiterate [the basic strategy I outlined](https://forum.bubble.io/t/stripe-webhook-in-bubble-big-vulnerability-to-all-apps-that-use-them/134030/25) several years ago (and which I still use).

Having said that, I’ll be implementing a “relay” approach (not unlike [this Cloudflare example](https://github.com/cloudflare/cf-webhook-relay/tree/main)) in an upcoming project. I made that decision based on the anticipated higher volume, higher dollar amounts, and higher risk profile of the transactions.

Anyway, it’s a shame Bubble doesn’t provide access to the raw request data (similar to the `raw body text` feature of API calls). It would make things simpler and easier. I like simple. 🙂

---

_[View the full topic](https://forum.bubble.io/t/securing-stripe-webhooks-without-authentication/281120)._