Skip to content

feat(TBF-162): ship Paddle billing frontend - #181

Merged
Human-Glitch merged 15 commits into
mainfrom
feat/paddle-frontend
Jul 24, 2026
Merged

feat(TBF-162): ship Paddle billing frontend#181
Human-Glitch merged 15 commits into
mainfrom
feat/paddle-frontend

Conversation

@Human-Glitch

@Human-Glitch Human-Glitch commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR ships the Paddle billing frontend end-to-end: pricing checkout, entitlement-aware app routing, paid-access recovery, settings plan management (including scheduled cancel visibility and in-app cancellation), and production billing docs.

Without this, users could authenticate and use the product without a clear upgrade path, and paid members had no in-app way to see plan status or cancel. That left billing as a backend-only concern and made demo-to-paid conversion and entitlement recovery inconsistent.

Root cause of the gap was missing frontend runtime contract and workflow orchestration around Paddle: no pricing screen, no shared billing workflow/state, incomplete settings plan UX, and incomplete wiring from onboarding/demo upgrade into checkout.

What changed

  • Checkout & pricing: Paddle pricing screen, plan cards, trial form, and client boundary for opening checkout.
  • Access control: App routes onboarding and gated surfaces through pricing; paid-access recovery and upgrade-required modal when entitlements block use.
  • Settings plan: Plan section with cancel membership modal, scheduled-cancel visibility, and billing action wiring.
  • Demo/pricing unification: Demo upgrade and pricing flows share one path so conversion is consistent.
  • Backend support for frontend contract: scheduled cancel fields, billing handler/service/provider updates, OpenAPI/docs, migrations, and tests.
  • Docs: docs/PRODUCTION_BILLING.md and the paddle billing frontend MPRD.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 008857fd0b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread frontend/src/App.tsx
Comment thread frontend/src/App.tsx
@TwoBitFoundry TwoBitFoundry deleted a comment from cursor Bot Jul 24, 2026
Co-authored-by: Cursor <cursoragent@cursor.com>
@TwoBitFoundry TwoBitFoundry deleted a comment from cursor Bot Jul 24, 2026
@Human-Glitch
Human-Glitch merged commit 55fce58 into main Jul 24, 2026
4 checks passed
@Human-Glitch
Human-Glitch deleted the feat/paddle-frontend branch July 24, 2026 06:24
Human-Glitch pushed a commit that referenced this pull request Jul 24, 2026
## [7.2.0](v7.1.1...v7.2.0) (2026-07-24)

### Features

* ship Paddle billing frontend ([#181](#181)) ([55fce58](55fce58))
@Human-Glitch

Copy link
Copy Markdown
Contributor Author

🎉 This PR is included in version 7.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@Human-Glitch Human-Glitch changed the title feat: ship Paddle billing frontend feat(TBF-162): ship Paddle billing frontend Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant