Mock-Safe by Default: I Built a Payments Flow With No Stripe Key

When you build something that touches Stripe, a calendar, a video provider, and a database, there's a temptation to go get all the accounts first. Sign up, mint keys, paste them in, and only then start building. It feels responsible. It's actually the slow way.

I built the entire paid-sessions flow for Home Studio Mastery, checkout, scheduling, Zoom meetings, calendar invites, saved bookings, before wiring a single real credential. The trick was a rule I now apply to everything: mock-safe by default.

---

The rule is small. Every integration checks whether its credentials exist. If they do, it does the real thing. If they don't, it returns a clearly-labelled fake, and the app keeps working.

No Stripe key? Checkout "succeeds" and sends you to the booking step with a banner that says payment was skipped. No Zoom key? The booking gets a placeholder join link. No database? The booking is logged instead of saved. Nothing throws. Nothing dead-ends.

---

Why this matters more than it sounds: you get to see the product on day one. Not a diagram, not a test that prints "OK", the actual screens. The real confirmation page. The real error state when someone picks a slot that's gone. You click through the whole thing on your laptop with zero accounts, and the gaps in the experience show up immediately, while they're cheap to fix.

It also means anyone can run the project. A teammate clones it and the whole flow works out of the box, no "here are the twelve secrets you need before anything renders." Credentials become the last step, not the first.

---

There's a discipline cost: every external call needs that two-path shape, and every fake needs to be obviously fake so it never gets mistaken for the real thing in production. I label them loudly, "dev preview," placeholder URLs that clearly aren't real, log lines that say "not configured, skipping." The goal is that mock mode is impossible to ship by accident.

The payoff is that "going live" stops being a scary big-bang. You flip in the real keys one at a time and watch each part switch from fake to real, with the surrounding experience already proven. The day I added the real credentials, there were no surprises, because I'd already watched every screen work a hundred times.

---

If you take one thing from this: make the absence of a credential a supported state, not a crash. Build against the fake, prove the experience, and let the real keys be a config detail you add at the end. It's faster, calmer, and it makes your project something other people can actually run.

This is how the booking system on Home Studio Mastery came together, and you can try the booking flow that came out of it.