Discussion on "Set Up Subscription Payments With Stripe using Firebase and Next.JS"

Jarrod Watts · 2021-07-13T07:00:38.160Z

Introduction Accepting payments online can seem like a daunting task, with considerations such as security, conversion rates and tax, there is a lot to consider. In this blog post, we'll explore how we can simplify the process of taking subscription ...

Hi! This article seems great! I have a client side rendered react site att the moment and would like to add auth and subscriptions like this. Do I need to upgrade my project to Next.js? If so, why? Thank you.

"Plans" seems deprecated now (2022) -in Stripe's Restricted API Key ressources- and you should use "Prices" instead (see docs).

Thanks a lot for this article. Spot-on! 😀

Awesome post, gr8 job.

but as I am going through it need to use these imports in firebaseClient.tsx to be more compatible with v9

import firebase from 'firebase/compat/app';
import 'firebase/compat/auth';
import 'firebase/compat/firestore';

Hi Jarrod,

thanks for your post, it was very useful :)

Hi,

Congrats, your work is great!

If you have some time, I have a question : how is managed the unsubscribing of the premium user? For example, if its credit card expires, next payment will be rejected. How your application will be notified and the role attribute "premium" will be removed for the user?

Thanks

To be completely honest I am not 100% sure how this is handled.

I am hoping that this is handled by Stripe behind the scenes - I will let you know if I find out!

The cloud functions that add the claim also remove it using the customer.subscription.updated event. I just did some experimenting to make sure I understood everything correctly, and that is what I found. Also, if you do a refund make sure to cancel the subscription also, that way it doesn't charge again and they do not keep access (unless you want that of course).

Thanks for the tutorial! I am trying to build a simple SaaS product with NextJs as well. I wasn't sure how to structure my data using firebase as it is different compare to traditional table db. Can I pick your mind on this?

It is a restaurant menu app, paid user can create merchant, merchant has many categories, categories have many items. The key is to allow paid user to easily manage their shop inventory.

Normal user able to leave a review for the restaurant or fav a dish and show in their profile page.

How should I go with that? Thanks!

Hey there!

Sounds like an interesting project, for this kind of structure I'd probably recommend having a database for users, and a database for items.

Items could have a category field and a merchant field, then you could filter items by merchant and by category when you want to query them.

I'd also recommend watching some of Firebase's videos about structuring the database as they really helped me.

youtube.com/watch

Jarrod Watts And by "database" i mean top-level collections.

Thanks Paul! Glad you enjoyed it :)

Discussion

Set Up Subscription Payments With Stripe using Firebase and Next.JS

Responses(7)

Recent in Forum

Search Hashnode

Set Up Subscription Payments With Stripe using Firebase and Next.JS

Responses(7)

Recent in Forum