2
2 Comments

The unglamorous part of bootstrapping: waiting on payment processor review

Spent the last few weeks heads-down building CancelKit — a drop-in cancellation flow for Stripe-based SaaS founders that catches churn at the moment someone hits "cancel" and offers a discount or pause instead of just letting them walk.

Code is done. Security audit is done (found and fixed 2 critical issues before anyone but me ever saw the product — grateful I caught them early). Tests are green. Landing page is live.

And now... I'm just waiting on Lemon Squeezy's manual review to actually go live and take real payments. No code to write, no bug to fix, just watching an inbox.

Anyone else find this part weirdly harder than the actual building? Curious how long review took for other MoR users here.

on July 15, 2026
  1. 1

    That waiting period is frustrating because the product is basically at the one place where “done” still depends on someone else’s risk process.

    For CancelKit specifically, I’d use the review gap to build a go-live checklist around money-state edge cases, not more features: test-mode cancellation → discount applied, pause flow, webhook retry/idempotency, refund or failed-payment states, and what the founder sees if the MoR review or payment method is still pending.

    If those are boring and documented before the first live customer, the Lemon Squeezy delay at least turns into a safer launch instead of just inbox watching.

  2. 1

    Catching churn at the moment of cancellation is a strong angle. I'd keep validating whether founders are buying a better cancellation flow or confidence that they're retaining customers for the right reasons instead of just delaying inevitable churn.