Currently, a person cannot update their payment details without creating a new subscription. The link to update the card details cannot be sent through a workflow; it can only be done automatically (once) or manually.
If a card expires or declines, there will be only one automatic reminder with the update link (not editable). If the person uses this link, a new subscription is created, rather than an update to the old subscription. That means there will be a new subscription start date, new deal and the old subscription is left sitting with the old payment status (unpaid, past due etc). This is totally unworkable for the following reasons:
1. If a member updates their subscription, it only creates a new one, and the reminder workflow continues. (I have a reminder workflow for subscriptions that is triggered where the payment was missed or the card expired -based on the subscription status)
2. I can only refer people back to the original, automatic email to update their cards anyway
Solution Requested:
1. Provide an “Update Payment Method Link” for each subscription type so I can add this to a workflow.
2. Allow this update the payment method for existing subscription, not create a new one
Hey @GLePage! Thanks for your post.
From what I understand with Payment Subscriptions, the existing Subscriptionshouldcontinue when the payment method is updated. Do you have any examples of new subscriptions created by just updating a payment method? I’d love to see these for more context.
As for the update payment method link, I agree that sending that manually or through automation would be super convenient. It appears we aren’t the only ones hoping for this either-- check out this existing Idea on our forum. I upvoted it! Be sure to upvote and add your use case to keep the momentum 
Let’s invite some of our experts to confirm that update payment behavior: @danmoyle, @Humashankar, @louischausse can any of you confirm the behavior described here? When a payment method is updated for a Subscription, a net new subscription is created, and the original one is not continued.
Best,
Kennedy
Hi @GLePage -
Yes, based on current behavior - when a payment method is updated for a subscription, it results in the creation of a new subscription rather than continuing the original one.
Best Regards
Thanks for the correction @Humashankar!
Correction? That would be “confirmation” of the issue.
Yes, @GLePage! I was incorrect in my initial reply. Thanks for clarifying
Additionally, I can understand the impact this has on business. I will be sure to submit some feedback internally along with following the Idea linked above. The ability to continue a subscription and have manual control of the payment method update are highly requested features. Thank you again for your contribution here!
Thanks @Humashankar - I know. The issue with this particular thread, is that you confirming what I already posted has now been marked as a “solution”. It’s not though, it’s a massive and obvious deficiency with the Commerce product. I must say, these features that get half thought out and then made live for user testing is a real issue. It impacts my business.