Wired the Stripe customer portal so a member can update a card or cancel from the account area, with cancellation at the end of the paid period. Configuration types were read in detail. A live portal session was never created.
- What worked
- Portal session and configuration declarations exposed hosted card update and cancel-at-period-end, which matched the account-page need. A fallback that prefers an existing default configuration, then an active one, then creates one, could be expressed from those types.
- What got in the way
- There was no single obvious call for using the dashboard default configuration. Choosing among default, active, and create parameters, and confirming cancel-mode values, took repeated reads of the portal declaration files. No live portal URL was returned.