RetryFix - Building OAuth in Public
See Building In Public steps below in my replies
———————————————————
A few weeks ago I posted my Show IH here:
→ https://www.indiehackers.com/post/show-ih-retryfix-get-your-failed-stripe-payments-back-on-autopilot-10-fee-85c8132498
Since then I’ve been quietly shipping:
Full Account page live (Stripe Customer Portal for updating payment methods, subscription details, email & password changes)
First few PRs of the Stripe Connect OAuth series (onboarding is about to get a lot smoother)
Various stability, UX, and reliability improvements across the dashboard and onboarding flow
Still very early and pre-revenue, but the core engine (auto-retry + smart dunning) is working solidly in testing.
If you’re running a subscription business on Stripe and want to try it, I’m still offering the first month completely free on the Performance plan (10% of recovered revenue only).
Would love any feedback or thoughts.
👉 https://retryfix.com
#BuildInPublic #SaaS #IndieHackers
Love the focused execution here. Failed payment recovery is one of those painful problems every subscription business knows about, but most founders postpone fixing properly until churn starts hurting.
A few things that stand out positively:
• Stripe Customer Portal integration → reduces support friction immediately
• Smart dunning + retry automation → direct measurable ROI feature
• Stripe Connect onboarding work → smart move for scaling partnerships/agencies later
• Focusing on reliability early before aggressive growth → very underrated
The pricing model also feels aligned:
“10% only on recovered revenue” is easy for founders to understand because the value is directly measurable.
One thing that could become a strong differentiator long term:
transparent recovery analytics.
Not just “payment recovered,” but:
• why it originally failed
• which retry sequence succeeded
• issuer/network patterns
• churn risk prediction before failure
That kind of insight layer could make RetryFix more than just a recovery tool.
Excited to see where this goes, Emmanuel here 👋
If you ever need help with product engineering, dashboard UX, AI-assisted workflows, Stripe integrations, or scaling the platform, I’d be interested in collaborating or contributing.
Hey Emmanuel,
Thank you so much for the thoughtful comment — I really appreciate the kind words and the detailed feedback.
The transparent recovery analytics idea is excellent and something I definitely want to build toward.
If you have a few minutes, I’d love your eyes on the current onboarding flow. You can sign up completely free (no credit card required) and you’ll immediately get a full 30-day lookback showing your failed payments + the real monetary value + estimated recovery.
Would be super valuable to hear your take as a founder.
Happy to send you the direct link if you’re up for it.
Cheers,
Paul
Quick Update (4 weeks in): OAuth Ticket 5 + Subscription Management Improvements
Hey everyone,
Just wanted to give a quick follow-up on progress since my last post.
What shipped recently:
OAuth Ticket 5 is now merged: Added ENABLE_STRIPE_OAUTH feature flag (default off) with a special preview for paul@retryfix.com. Normal users see a disabled "OAuth coming soon" button, while I can test the full "Connect with Stripe" flow. The manual secret key + webhook onboarding path remains completely unchanged.
Customer Portal Toggle: Added STRIPE_USE_CUSTOMER_PORTAL (default false). When enabled it opens Stripe’s full Customer Portal (including cancel option). For now it stays off, so "Manage Subscription" still goes to the narrow payment method update flow. Easy to flip later.
Cleaned up several onboarding edge cases after fresh DB wipes (support user ownership, cross-device login redirects, etc.).
The app is feeling much more solid. I can now safely test OAuth pieces in a feature environment while keeping production stable.
Still a long way to go on the full OAuth epic (token exchange, re-connect logic, webhook mode, etc.), but the foundation is in place and shipping incrementally.
Would love any thoughts or brutal feedback — especially from folks who have built Stripe Connect / OAuth flows before.
Thanks for following along! 🚀
What I’m Working On — Starting the OAuth Series
I’ve begun the big Stripe Connect OAuth project (roughly 5–15 tickets total).
The backend work is now underway: permissions, secure token exchange, webhook management, and safe feature flagging so we can roll this out without breaking anything for current users.
This is the biggest UX improvement we’ve tackled so far. Excited (and a bit nervous) about the next few weeks.
#buildinpublic #saas #churn #retention
Day 2 of OAuth work — deep dive into token lifecycle and error states.
Learned (again) that assuming “Stripe will always behave nicely” is dangerous. Building proper resilience now.
#buildinpublic #saas #churn #retention
Onboarding Redesign Wave 1 shipped
Finished the new signup choice screen today. It finally positions the upcoming OAuth flow as the main path while keeping the current manual setup as a supported option.
Feels good to start guiding users toward the better long-term experience.
#buildinpublic #saas #churn #retention
Wave 2: Building the OAuth explainer page.
The tone here is tricky — you’re asking people to give your app fairly broad access to their Stripe account. Getting the wording right is taking longer than expected, but it’s important.
#buildinpublic #saas #churn #retention
Wave 3 Complete
Just finished the third wave of the onboarding redesign. The signup choice page and explainer are now much stronger.
It’s starting to feel like a real product experience instead of a technical hurdle. Still a lot of polish left, but the direction feels right.
#buildinpublic #saas #churn #retention
What I’m Working On — Wave 4 of Onboarding Redesign Now Live
Just deployed Wave 4.
This round focused on polishing the entire signup choice and explainer experience. The new flow better positions Stripe Connect OAuth as the recommended path while keeping the manual setup clearly available and supported.
It’s still not perfect, but it feels like a big step toward making onboarding actually pleasant instead of a chore.
Next up: more visual polish and final testing before we open the OAuth path wider.
#buildinpublic #saas #churn #retention