[FEEDBACK NEEDED 👀] Stripe/PayPal + Auth0

I have been doing research on the demand for content around the integration of Auth0 with payment platforms like Stripe and PayPal. @donovan provided an interesting use case to explore on a blog post:

Customer makes a Gold subscription and can access all pages, but a Bronze subscription can only access some pages.

Source: Securing Gatsby with Auth0

I’d like to hear/read more from y’all on what would you like to read about this type of integration? What should we cover in such blog post? Thank you!

2 Likes

This would be really helpful. I think the tutorials around implementing auth0 to protect certain pages are well written, I adapted this tutorial for my own application.

What is a bit trickier to implement, and what I am struggling with currently, is a “paywall” as @donovan describes.

Ideally a blog post/tutorial would assume you have already successfully implemented authentication using auth0. Selfishly, I would like that to be in React as a natural follow on to the article linked above. The closest tutorial I have found to being helpful so far is this

I think a useful structure would be;

  1. Authenticated user clicks Buy Button (unauthenticated user asked to SignUp)
  2. Stripe Modal/PopUp/Redirect
  3. User purchases
  4. Stripe webhook updates Auth0 profile with “paid: yes” (or similar)
  5. “Paid up” Authenticated User is redirected back to Application
  6. “Paid Up” user can now access premium content
  7. Reversion to “normal” membership if user unsubscribes/doesnt pay

The above logic might be quite accurate- I am not sure how stripe and auth0 best communicate.

Also useful, rather than having 3 “tiers” (causual visitor, member, paid subscriber), inclusion of stripe/paypal in the user onboarding process would be useful in alot of cases whereby you are either a casual visitor or a paid subscriber.

IndieHackers have a lot of discussion around Auth0 and how it integrates with stripe if you wanted to do some extra research on use cases.

1 Like

Thank you for this amazing feedback and welcome to the Auth0 community. Your reply helps me a lot to put things in perspective.

Recently, I was shopping for some things for a home improvement project at Home Depot and I noticed that they have two types of checkout: “As Guest” and as “Registered Customer”. The Guest Checkout lets you use Paypal Checkout which is super fast and uses your PayPal information to populate the order information. What was cool is that as a Guest, you are given the option to enter a password if you want to create an account (sign up) and it uses your PayPal info to populate the Home Depot account. I felt the checkout process was very smooth and I liked the many “paths” to registration.

So if we were looking at providing you, our readers and customers, a sample application of integrating Auth0 with paywalls, I think that an experience like that one from Home Depot would be useful, I think that applies to your point of “rather than having tiers”. Adding PayPal is optional during the on-boarding process of anyone.

What’s very challenging of coming with guidance like this is that we have to use a sample app that is as generic as possible but also focused :sweat_smile: “it has to be hot but also cold” -> creating it feels like that. I think that we could be safe with a retail demo app as it fits the use case and flow of paywalls (checkout) universally. What do you think?

Thanks for the quick response!

That sounds great - I appreciate maintaining simplicity while still having all the functionality you mentioned is probably the biggest challenge but look forward to reading in he future!

1 Like

Thanks a lot for those words @df4r4m7!