How do you stack payments and authentication?

I’m interested in learning how developers are managing payments and authentication for web apps.
For payments, I personally use Stripe and Next-auth.
I haven’t developed anything for supabase auth yet, but I hear it’s rather popular.

Stripe with Laravel (Laravel Cashier). Basically plug and play, requiring very little work.

I work mostly with JS and React, but I also know PHP. With just a few lines of code, I can have a PHP backend and React frontend functioning together thanks to Inertia.

+1 Stripe connection using Laravel and Cashier. Very easy to setup!

Hello, I’m going to move from nextjs plus lambda to complete lambda due to its robustness. Is it difficult to practice reacting with inertia? I want to know if everything works perfectly with navigation, SSR, suspense, etc., or if some things take longer to complete?

For our authentication and payments stack, we’ve developed a robust solution that prioritizes security, flexibility, and seamless payment operations:
Authentication: We rely on Auth0 for secure and scalable authentication. It supports a variety of login methods, including social logins, SSO, and multi-factor authentication, making it a versatile choice as our user base expands.
Payments: We use OpenPay as our payment orchestration platform. It simplifies the management of multiple payment gateways and methods, providing flexibility for different markets, currencies, and user preferences. OpenPay handles subscription management, one-time payments, and complex workflows, ensuring smooth transactions without needing to integrate each payment provider individually.
User Management: For specific projects requiring an integrated back-end with authentication, we’ve explored options like Supabase Auth and Firebase. However, for larger-scale applications, the combination of Auth0’s flexibility and OpenPay’s advanced payment orchestration has proven to be the best fit for us.

Let me know if this helps clarify things!

Don’t I feel foolish, though? I’ve just been using JWT for a week and a half to build out my own auth. I should probably look into firebase next time.

I make payments using Lemonsqueezy and Next Auth. Every time I start a new project, I use boilergen.com.

It has email setup, database, and auth.

Has anyone developed a system that allows users to withdraw money to their bank accounts? I’ve worked out how to use Stripe to collect payments, but I’m not sure how to pay a customer afterwards.

My Ruby on Rails setup uses pay gems to handle transactions and omniauth-google-oauth2 for authentication. So far, it’s been fantastic! I’m curious if anyone else has any suggestions for how to make it better or comparable setups.