Auth and Payments for Full Stack Developers
Auth and payments cover identifying users and charging them. Authentication proves who someone is using sessions, JWTs or OAuth; authorisation decides what they may do through roles and permissions; payments use a provider such as Stripe with checkout sessions, subscriptions and webhooks to confirm results.
Stage: Backend and Data · Part of the Full Stack Developer roadmap · Last reviewed 19 November 2026
What to learn in Auth and Payments
- Hash passwords with bcrypt or Argon2 and never store plain text
- Implement session cookies and explain how they differ from JWTs
- Add role-based checks that run on the server for each request
- Start a Stripe Checkout session and handle the payment webhook
- Update a user's plan when a subscription event arrives
Auth and Payments interview questions
Where in a full stack app do you enforce authorisation after authentication?
Authentication verifies identity, for example by password or OAuth login. Authorisation determines what that verified user can access or do, such as viewing only their own records or admin pages. A request can be authenticated yet still forbidden. Enforce it on the server for every request.
Why trust a payment webhook rather than the browser redirect?
The redirect after checkout can be skipped, faked or interrupted, so reaching a success page proves nothing. A signed webhook comes directly from the provider's server and is the reliable signal to mark an order paid.
Where Auth and Payments fits in the Full Stack Developer roadmap
Auth and Payments belongs to the Backend and Data stage (beginner level), which takes about 9 hours. Services, APIs and storage.
Other units in this stage
Back to the full Full Stack Developer roadmap