# Update Payment Method for Subscriptions (without creating a new one)

**URL:** <https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720>\
**Category:** Commerce Tools\
**Tags:** recurring-payments\
**Created:** [September 19, 2024, 10:02pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720 "2024-09-19T22:02:51Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![GLePage](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@GLePage](https://community.hubspot.com/u/GLePage)\
**Post date:** [September 19, 2024, 10:02pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/1 "2024-09-19T22:02:51Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kennedyp](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kennedyp](https://community.hubspot.com/u/kennedyp)\
**Post date:** [September 20, 2024, 4:36pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/2 "2024-09-20T16:36:54Z")

</div>

Hey @GLePage! Thanks for your post.

~~From what I understand with Payment Subscriptions, the existing Subscription~~~~ _should_ ~~~~continue 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](https://community.hubspot.com/t5/HubSpot-Ideas/Add-quot-Update-payment-method-quot-link-as-a-token-in-emails-in/idi-p/714254)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

---

<div class="post-metadata">

**Author:** ![Humashankar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/humashankar/32/30856_2.png) [@Humashankar](https://community.hubspot.com/u/Humashankar)\
**Post date:** [September 20, 2024, 10:00pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/3 "2024-09-20T22:00:48Z")

</div>

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**

---

<div class="post-metadata">

**Author:** ![kennedyp](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kennedyp](https://community.hubspot.com/u/kennedyp)\
**Post date:** [September 23, 2024, 9:39pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/4 "2024-09-23T21:39:14Z")

</div>

Thanks for the correction @Humashankar!

---

<div class="post-metadata">

**Author:** ![GLePage](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@GLePage](https://community.hubspot.com/u/GLePage)\
**Post date:** [September 23, 2024, 10:04pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/5 "2024-09-23T22:04:50Z")

</div>

Correction? That would be “confirmation” of the issue.

---

<div class="post-metadata">

**Author:** ![kennedyp](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kennedyp](https://community.hubspot.com/u/kennedyp)\
**Post date:** [September 24, 2024, 5:45pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/6 "2024-09-24T17:45:58Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![GLePage](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@GLePage](https://community.hubspot.com/u/GLePage)\
**Post date:** [September 23, 2024, 10:03pm UTC](https://community.hubspot.com/t/update-payment-method-for-subscriptions-without-creating-a-new-one/116720/7 "2024-09-23T22:03:00Z")

</div>

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.
