Title: Create subscription upgrade flow

[temma02]

Description
Implement the UI flow for upgrading from one subscription tier to another.

Requirements and context

• Must be secure, tested, and documented where applicable
• Should stay reviewable and fit the current monorepo structure

Suggested execution

• Create branch: create-subscription-upgrade-flow
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Create upgrade confirmation screen
• Handle proration and billing cycle changes
• Redirect to Stripe checkout for payment

Test and commit

• Run the most relevant tests for the touched service or UI surface
• Include screenshots or request/response examples when the change is user-facing
• Call out edge cases, assumptions, and any follow-up work

Example commit message
feat: add subscription upgrade flow

Guidelines

• Prefer small, reviewable PRs
• Keep naming and data contracts consistent with the spec docs
• Preserve responsive and accessible behavior for frontend work

[idrisososanwo]

@idrisososanwo has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’m a good fit for this task because I focus on building smooth, secure, and user-friendly subscription flows.

My approach would be to implement the UI for upgrading between tiers, including an upgrade confirmation screen, handling proration and billing cycle adjustments, and redirecting users to Stripe checkout for payment. I’ll ensure edge cases like overlapping billing cycles or failed payments are gracefully handled. The flow will be fully responsive, accessible, and testable, with clear documentation and examples for reviewers. My goal is to provide a seamless upgrade experience that aligns with the existing monorepo structure and keeps the code clean and maintainable.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @idrisososanwo to this issue.

[drips-wave]

Congratulations, @vicajohn! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @vicajohn: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[GoSTEAN]

@GoSTEAN has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Can i work on this?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GoSTEAN to this issue.