# Hiring freelancers to build Weweb+Supabase+Stripe flow to charge subscription payments from customers

**URL:** <https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670>\
**Category:** Jobs & collabs\
**Created:** [January 20, 2026, 4:34am UTC](https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670 "2026-01-20T04:34:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![LB7](https://avatars.discourse-cdn.com/v4/letter/l/5f9b8f/32.png) [@LB7](https://community.weweb.io/u/LB7)\
**Post date:** [January 20, 2026, 4:34am UTC](https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670/1 "2026-01-20T04:34:53Z")

</div>

Hi everyone,

As per heading, looking for a capable developer who’s successfully implemented a payment flow spanning weweb, supabase and stripe that can charge subscription payments from customers. My preferred route is customer initiating a checkout session from weweb by calling a supabase edge function, which interacts with Stripe, after which Stripe will return a URL of a payment page that the user is redirected to finish transaction. Post successful transaction, stripe uses webhook to notify backend to update customer subscription details etc.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [January 20, 2026, 9:11am UTC](https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670/2 "2026-01-20T09:11:25Z")

</div>

I think you don’t need Webhooks to sync with Supabase if you use the Database Wrapper. As for the rest, it’s fairly, simple (1 endpoint). I think with some help of the AI you could even manage it on your own. Good luck!

---

<div class="post-metadata">

**Author:** ![sushant18b](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@sushant18b](https://community.weweb.io/u/sushant18b)\
**Post date:** [January 22, 2026, 1:35pm UTC](https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670/3 "2026-01-22T13:35:34Z")

</div>

But remember when using database wrapper it’s harder to debug and customization is limited.

---

<div class="post-metadata">

**Author:** ![Shivam](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/shivam/32/14821_2.png) [@Shivam](https://community.weweb.io/u/Shivam)\
**Post date:** [January 29, 2026, 7:16am UTC](https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670/4 "2026-01-29T07:16:34Z")

</div>

Hi @LB7  
I’m a full-stack developer with experience building seamless WeWeb + Supabase + Stripe subscription flows exactly as you described—customer-initiated checkout via Supabase edge functions, Stripe session redirects, and webhook handling for post-payment updates (e.g., subscription status in Supabase).

I’ve successfully implemented this for multiple SaaS clients. Available to hop on a quick call to discuss your setup and timeline.

Best,  
Shivam  
[Shivam76tech@gmail.com](mailto:Shivam76tech@gmail.com)

---

<div class="post-metadata">

**Author:** ![AnnaR](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/annar/32/15860_2.png) [@AnnaR](https://community.weweb.io/u/AnnaR)\
**Post date:** [January 30, 2026, 12:05pm UTC](https://community.weweb.io/t/hiring-freelancers-to-build-weweb-supabase-stripe-flow-to-charge-subscription-payments-from-customers/20670/5 "2026-01-30T12:05:09Z")

</div>

> [@LB7](#):
>
> Hi everyone,
> 
> As per heading, looking for a capable developer who’s successfully implemented a payment flow spanning weweb, supabase and stripe that can charge subscription payments from customers. My preferred route is customer initiating a checkout session from weweb by calling a supabase edge function, which interacts with Stripe, after which Stripe will return a URL of a payment page that the user is redirected to finish transaction. Post successful transaction, stripe uses webhook to notify backend to update customer subscription details etc.

Hi @LB7  
I would be glad to assist you.  
To discuss further in detail kindly reach me at [annaradnor70@gmail.com](mailto:annaradnor70@gmail.com).

Thanks  
Anna
