Your account
HOL-D107Story implementation: Planned

Manage my saved payment methods

commerce · Proposed launch phase 4

Start from Home

Review as Registered user · Full workflow planned

User story

As a registered member, I want to view and manage my own saved payment-method summaries so I can choose how to pay when a supported checkout is connected.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Provide a Payment methods page under Payments & purchases with honest empty/unavailable states until a supported payment service and records exist.
  • When implemented, show only safe provider summaries such as card brand, last four digits and expiry; use provider-mediated add/replace/default/remove flows with clear outcomes.
  • Do not collect or persist full card numbers/security codes in app profiles, seed data, logs or browser product state. Only approved synthetic summaries are suitable for a later explicit demo preview.
  • Personal saved methods are independent of paid content entitlement and organization manager/owner status. Default/removal constraints and the selected checkout provider must be agreed before connected actions.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on this account’s permitted Home. For a local review use Sign in → Try a demo account → Alex Morgan → Free Member Home. Settings belong to this same personal account; keep Professional/organization/staff authority separate.

Navigation from sign-in

  1. 01Open the fictional Registered user account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Begin at this role’s Home, open its account/workspace menu, then Profile & settings when that navigation is delivered. Follow the section named in the checks; stop if a planned destination is unavailable.

Feature checks start here

Manage my saved payment methods · Full workflow planned

Planned follow-up. Requirements are recorded; the dedicated settings page and backend workflow are not implemented. Current navigation/editor work does not implement this outcome.

  1. 03From the role Home open Profile & settings → Payments & purchases → Payment methods when delivered; this is currently planned.
  2. 04Review empty/unavailable states first. Later use the approved provider test flow and compare the owned safe summary; never use a real card for dev review.
  3. 05Check default/removal failures and another account’s exclusion when the provider-backed workflow is authorized.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Future model needs an owner-to-provider-customer mapping and provider payment-method references with safe display metadata, current/default status and auditable outcomes.
  • Provider authority, webhook/replay handling and any recent-auth requirement must be defined with the selected integration before implementation. A client-selected method or default never grants membership.
  • No payment provider, credentials, live charge, raw-card storage, hosted migration or financial schema implementation is authorized by the navigation/editor slice.

How to verify when implementation is approved

  1. Test owner isolation, unavailable provider, expired/removed references and retry/idempotence once connected.
  2. Inspect payloads/logs for raw card/security-code exclusion; verify no payment-method change alters entitlement.

Before this can work

  • Use an existing fictional account; keep its current role/entitlement and selected Home. No profile/preference reset is required to review requirements.
  • Dev only. No real card/address/recipient data, provider setup, outbound delivery or publication is part of this review.

Connected stories