For my semester project in the 2nd semester of the Master Class Mobile, I built a club dashboard: a web application that ski clubs use to manage their trips, while members can book and pay for them directly online. The goal was a working MVP with a complete end-to-end payment integration, from creating an event to a successful payment on the website.
Tech stack
- Next.js (App Router): server-side rendering, API routes and a clean split between server and client components
- Convex: a reactive backend-as-a-service with data and server logic written in TypeScript, so I didn’t need a separate REST or GraphQL layer
- Tailwind CSS & shadcn/ui for a consistent, accessible UI
- Clerk for authentication and user management
- Stripe Checkout for payments, including webhook handling
The payment flow
- A member picks a trip and clicks “Book”
- Stripe Checkout opens and the payment goes through
- Stripe sends a webhook, and the booking is confirmed and stored in Convex
Both Stripe and Clerk talk to the system through webhooks, which arrive in Next.js API routes and are then processed in Convex.
Challenges & learnings
Validating webhook signatures was error-prone at first and needed a clean separation between security and business logic. I also had to learn Convex’s own schema system and get used to the Next.js rendering model with server and client components. Above all, the project taught me a lot about payment flows, security and API communication.
Read the full post on the MFG Blog of USTP → (in German)