Plan auth and payments before the fun part
Built in a weekend, then 3 weeks on auth and payments · Reddit r/VibeCodingSaaS · u/Background-Gur-8289 · Mar 2026
The product took two days with Cursor, but auth, Stripe and webhook problems took weeks. The poster ends by recommending a boilerplate.
The honest numbers
- Says 2 days to build
- Says 3 more weeks to make it launchable
As stated by the source. Not independently verified.
Lesson
Plan the boring parts first: sign-in, payments and webhooks are where launch time actually goes.
Fix prompt
Copy this into your own AI tool (Cursor, Lovable, Claude Code, Bolt…). It's general guidance written by us. Review what the AI suggests before applying it.
I'm a beginner with a Cursor app that takes payments with Stripe (or a similar provider). Please audit the payment flow. 1) Find the webhook endpoint and check that it verifies the provider's signature using the raw request body, and isn't blocked by my own auth (e.g. Supabase verify_jwt on the function). 2) Check that it handles failed payments, refunds, cancellations and the same event arriving twice (idempotency). 3) Make sure only the server/webhook can change a user's plan or credits, never the browser. 4) List problems with file names and fixes, then give me a test checklist using test-mode events and one small real payment. Don't change anything until I've approved your plan. Never ask me to paste API keys, passwords or .env contents; tell me where to check them myself.
Source: Reddit r/VibeCodingSaaS ↗