# Payment Source Name Does Not Match Payment Link Name

**URL:** <https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060>\
**Category:** Commerce Tools\
**Tags:** payments-links\
**Created:** [November 1, 2023, 2:59pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060 "2023-11-01T14:59:22Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![KellenRogers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kellenrogers/32/12467_2.png) [@KellenRogers](https://community.hubspot.com/u/KellenRogers)\
**Post date:** [November 1, 2023, 2:59pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/1 "2023-11-01T14:59:22Z")

</div>

Hello, has anyone had an issue where the “Payment Source Name” on a Payment record doesn’t match the name of the payment link? (See Below).

 ![KellenRogers_0-1698850459758.jpg](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/9/c96de1de6b83beca3e24ed5d47b5a1a412517acc.jpeg)

The issue appears whenever a payment link’s name is updated after a payment has been recorded. See steps below:

1. The payment link was created with name **"**** Customer #10061787037"**
2. Payment link was used to complete payment
3. A Payment record was created by the system
4. Payment link name was updated to **"**** Customer #5369525"**
5. Payment record still shows original name

It doesn’t appear that the updated payment link name is being reflected on the payment record.

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [November 2, 2023, 8:41am UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/2 "2023-11-02T08:41:57Z")

</div>

Hi @KellenRogers, I hope that you are well!  
Thanks for asking about this to the Community!  
Just to clarify, regarding the point number 4, how is the payment link name updated, please?  
Is that via an API? If yes, which one? Is that manually? Is this via a workflow that you set up?

I also wanted to invite a couple of subject matter experts to this conversation @danmoyle, [@Alex\_Elborn](https://community.hubspot.com/t5/user/viewprofilepage/user-id/73663) and @Jnix284 do you have suggestions to help @KellenRogers, please?  
**If anybody else has anything to add and/or share, please feel free to join in the conversation 🙂**  
Thank you for your help and have a fantastic day!  
Bérangère

---

<div class="post-metadata">

**Author:** ![KellenRogers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kellenrogers/32/12467_2.png) [@KellenRogers](https://community.hubspot.com/u/KellenRogers)\
**Post date:** [November 2, 2023, 3:51pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/3 "2023-11-02T15:51:27Z")

</div>

Hello Bérangère,  
The Payment Link’s name was updated manually via the HubSpot UI.  
(I updated the original post to show the customer # changing. For some reason the actual numbers got remove when I originally posted them.)

Thanks!

---

<div class="post-metadata">

**Author:** ![danmoyle](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmoyle/32/91166_2.png) [@danmoyle](https://community.hubspot.com/u/danmoyle)\
**Post date:** [November 2, 2023, 12:44pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/4 "2023-11-02T12:44:26Z")

</div>

Hey there @KellenRogers and welcome to the community.

That does seem odd. In our portal we have payment links and the payment source name stays the same. For example, we have consulting blocks and we have a product called HubLMS. Both of these have payment links we use again and again, and the payments that result from them simply pull in that payment link name into “payment source name.” That’s what I’d expect. I’m not sure why yours would change numbers.

Have you asked Support? That’s where I start, so maybe you have. But I don’t see how or why that would change without getting a live look at your process and what your settings are, since that hasn’t been my experience. Sorry I didn’t have a better answer!

---

<div class="post-metadata">

**Author:** ![KellenRogers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kellenrogers/32/12467_2.png) [@KellenRogers](https://community.hubspot.com/u/KellenRogers)\
**Post date:** [November 2, 2023, 3:53pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/5 "2023-11-02T15:53:01Z")

</div>

Hello Dan,

I appologize for the confusion cause by leaving off the actual customer # on steps 1 and 4 in the original post.  
The issue is that we manually updated the payment link’s name and it wasn’t updated on the payment record.

---

<div class="post-metadata">

**Author:** ![danmoyle](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmoyle/32/91166_2.png) [@danmoyle](https://community.hubspot.com/u/danmoyle)\
**Post date:** [November 3, 2023, 7:31pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/6 "2023-11-03T19:31:26Z")

</div>

@KellenRogers you update the payment link name after it’s been sent to the customer to pay? I guess I’m not understanding your use case fully. If it helps, I’d be open to a chat (link in my signature) to try and talk through it rather than forum posts. I may or may not be able to help, but I’ll sure try!

---

<div class="post-metadata">

**Author:** ![KellenRogers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kellenrogers/32/12467_2.png) [@KellenRogers](https://community.hubspot.com/u/KellenRogers)\
**Post date:** [November 9, 2023, 7:32pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/7 "2023-11-09T19:32:29Z")

</div>

Hello Dan,  
You’re a busy man! I just booked a meeting for November 16, 2023 @7:45 AM.  
If anything pops up before let me know and I’d be happy to hop on. I’m on Pacific timezone.

---

<div class="post-metadata">

**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\
**Post date:** [November 10, 2023, 1:26am UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/8 "2023-11-10T01:26:07Z")

</div>

@KellenRogers

The payment source will reflect the name of the payment link at the time it was made, it won’t dynamically update when you change the payment link name.

This creates a historic snapshot of the payment name at the time the payment was made so it can’t be altered unintentionally.

Are you changing the name of the payment link afterward to correct a mistake or to reuse the link for another purpose?

---

<div class="post-metadata">

**Author:** ![KellenRogers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kellenrogers/32/12467_2.png) [@KellenRogers](https://community.hubspot.com/u/KellenRogers)\
**Post date:** [November 10, 2023, 5:46am UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/9 "2023-11-10T05:46:14Z")

</div>

Hello Jennifer,

Thank you for the clear explanation!  
We are changing it to update a mistake. Occasionally, the custom no is put in wrong by our sales team and it needs to be corrected so that our accounting team is not confused when they review payments.

---

<div class="post-metadata">

**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\
**Post date:** [November 10, 2023, 1:27pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/10 "2023-11-10T13:27:13Z")

</div>

You’re welcome @KellenRogers, happy this was helpful!

---

<div class="post-metadata">

**Author:** ![danmoyle](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmoyle/32/91166_2.png) [@danmoyle](https://community.hubspot.com/u/danmoyle)\
**Post date:** [November 16, 2023, 3:56pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/11 "2023-11-16T15:56:05Z")

</div>

Hey @KellenRogers - thanks for scheduling. It’s been busy with some PTO and moving training clients around to get them all in 😊

Sorry we didn’t connect on today’s scheduled meeting. Maybe you didn’t need it thanks to @Jnix284 (she’s awesome) but since it wasn’t canceled I waited for the duration.

If I can help in the future, please let me know!

---

<div class="post-metadata">

**Author:** ![KellenRogers](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kellenrogers/32/12467_2.png) [@KellenRogers](https://community.hubspot.com/u/KellenRogers)\
**Post date:** [November 16, 2023, 5:17pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/12 "2023-11-16T17:17:29Z")

</div>

@danmoyle I appologize. I completely forgot to cancel the meeting this morning.  
After @Jnix284 gave the great explanation, I moved along to other items.  
I appreciate your help and follow up. Hopefully we can connect at another time.

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [November 17, 2023, 1:09pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/13 "2023-11-17T13:09:18Z")

</div>

Hi @danmoyle, I hope that you are well!  
Thank you so much for all the amazing contributions/help on the Community, and also for going the extra mile and suggesting to Members to schedule a call ❤  
We really appreciate you and thank you for that! 🌟  
Also, thanks for the **reminder to the Community Members to cancel appointments if they are no longer needed**. Time is precious for all.  
Have a great Friday and an excellent weekend!  
Best,  
Bérangère

---

<div class="post-metadata">

**Author:** ![Berangere](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/berangere/32/220784_2.png) [@Berangere](https://community.hubspot.com/u/Berangere)\
**Post date:** [November 10, 2023, 12:19pm UTC](https://community.hubspot.com/t/payment-source-name-does-not-match-payment-link-name/93060/14 "2023-11-10T12:19:25Z")

</div>

Hi @KellenRogers, I hope that you are doing well!  
Thanks a lot for your help and contributions @danmoyle and @Jnix284 🌟  
Just to confirm, I checked for you and if a payment link name was updated after someone transacted, it wouldn’t change in the contact record.  
If data about the payment link is changed after it was used to collect payment, the payment record will have the details stored **as of** the time of payment.  
However, just a thought: it seems like making the quote payable or using an invoice would help facilitate customer tracking more accurately maybe in your case? (since it could be handled via associations).  
I hope this clarifies your question and that it helps!  
Have a fantastic day!  
Best,  
Bérangère
