DoHBoY-subscriptions

[sleek scarab]

hi! well you don't need Connect I would think, no.

Connect is for creating Stripe account for entities that will either charge end-customers, or receive funds directly from you like partners/service providers.

end-customers themselves don't need Stripe accounts or to be managed with Connect

overall I would say you can build authentication for your end-customers using something like Firebase yes, and then when you have a reliable way to map end-user to a Stripe Customer object (cus_xxx), you can redirect them to the Stripe Customer Portal for managing their subscriptions. https://stripe.com/docs/billing/subscriptions/integrating-customer-portal

[clear hawk]

Ahh gotcha, makes sense! So I would still need something to service authentication.. which as I dig into this more, it seems like they may have used firebase for a reason, seems to be supported for stripe authentication specifically https://github.com/stripe-samples/firebase-subscription-payments

So, my understanding of this entire process is that I would need these pieces:

Website/domain to host content
System to service user creation/Authentication (firebase)
Checkout/payment process for users once authenticated (Stripe)

User accesses our website, logs in with firebase (I think I know how to push discord info into firebase), then based on their firebase login, they can purchase/manage subscriptions in Stripe?

[umbral galleon]

Hi there 👋 jumping in as @sleek scarab needs to step away. Yup, as long as you have a way to map your Firebase logins to the appropriate Stripe customers, then that sounds possible.

[clear hawk]

Perfect! Thank you both; I am a tech by trade but user auth/payment processing is brand new to me, so it's nice to be able to ask these silly questions as I learn all the lingo and systems 😄 I'll start running with this and will surely pop back in whenever I have new questions