Actions
Task #36
openEpic #13: Patient Portal
Feature #16: Stripe and checkout pages
Subscribe to a Health Plan
Status:
New
Priority:
Normal
Assignee:
-
Start date:
11/06/2025
Due date:
% Done:
0%
Estimated time:
Description
User Story:
As a patient, I want to subscribe to a selected health plan so that I can access its benefits and services.
Acceptance Criteria :
- From the Plans page, user can click Subscribe on a chosen plan.
- System shows a confirmation step summarizing plan name, price, duration and any trial/intro offers.
- If payment is required, user can provide payment details and confirm the charge.
After successful confirmation/payment :
- Plan status becomes Active for the user.
- Subscription start and end dates are recorded.
- The user is shown an onscreen confirmation and returned to the Plans or Dashboard.
- System stores the subscription record in the backend with start/end dates and plan id.
- A notification (in-app) is created informing user of successful subscription.
Notes for QA :
- Subscribe to a paid plan and verify active status, start/end dates saved.
- Test subscription flow with and without payment required.
- Confirm confirmation UI and redirection behavior.
- Check subscription record in backend (if accessible).
Updated by Redmine Admin about 1 month ago
Redmine Admin wrote:
User Story:
As a patient, I want to subscribe to a selected health plan so that I can access its benefits and services.Acceptance Criteria :
- From the Plans page, user can click Subscribe on a chosen plan.
- System shows a confirmation step summarizing plan name, price, duration and any trial/intro offers.
- If payment is required, user can provide payment details and confirm the charge.
After successful confirmation/payment :
- Plan status becomes Active for the user.
- Subscription start and end dates are recorded.
- The user is shown an onscreen confirmation and returned to the Plans or Dashboard.
- System stores the subscription record in the backend with start/end dates and plan id.
- A notification (in-app) is created informing user of successful subscription.
Notes for QA :
- Subscribe to a paid plan and verify active status, start/end dates saved.
- Test subscription flow with and without payment required.
- Confirm confirmation UI and redirection behavior.
Actions