Problem Statement
During a subscription change, the system currently charges the same card linked to the active subscription, without giving users a chance to choose a different one.
If that card has insufficient funds, the upgrade still proceeds, often resulting in a past-due subscription and poor customer experience.
User Story
As a subscriber changing my plan, I want to select an existing saved payment method or add a new one before confirming the change, so that my payment succeeds and I can control which card is charged.
Definition of Done (DoD)
Modify Change Subscription API (reference) to accept an optional payment_method_id parameter.
Validate that:
If payment_method_id is provided, charge that method instead of the default subscription card.
If none is provided, fallback to the current default.
UI / SDK
Within Change Plan flow, display the Payment Method modal:
Similar to normal checkout flow,
Allow selection from existing saved cards.
“Add new card” should be available.
If user adds a new card, set it as the payment_method_id for the API request.
Unit tests to verify:
Successful charge using alternate saved card
Successful charge using new card
Graceful fallback to default card
Include proper error handling for declined payments before plan activation.
Affected Components
API / SDK / Integrations
Please authenticate to join the conversation.
Done
Pelcro Product
3 months ago

Rana Haleem
Get notified by email when there are changes.
Done
Pelcro Product
3 months ago

Rana Haleem
Get notified by email when there are changes.