feat(TBF-162): ship Paddle billing frontend - #181
Merged
Conversation
There was a problem hiding this comment.
💡 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".
Co-authored-by: Cursor <cursoragent@cursor.com>
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))
Contributor
Author
|
🎉 This PR is included in version 7.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
docs/PRODUCTION_BILLING.mdand the paddle billing frontend MPRD.