Answers.Body: <p>Test this patch to see if it fixes your problem? <a href="https://github.com/civicrm/civicrm-core/pull/14407" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/14407</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-03T20:41:14.073Z
Answers.Text: Thanks for your reply. But I am a bit confused while applying this patch!! I am on 5.13.5 and the PHP content of the patch is very different to the file of 5.13.5. For example, ContributionRecur.php code lines of  5.13.5 are very different from the latest patch file. And other 3 files also I found similar things. So, do I replace the entire content of the latest patch file? or apply only the differences, but my fear something might break!! Any thoughts? Thanks again!
Answers.UserDisplayName: Tapash
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-06T11:21:23.703Z
Answers.Text: There should be a fix for this in 5.14.0 - dropping today
Answers.UserDisplayName: eileen
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-03T19:44:05.400Z
Answers.LastActivityDate: 2019-06-03T19:44:05.400Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>Some of our donors have reported that they were not able to update the amount or cancel their recurring subscription payment using the standard email receipt that gets sent from CiviCRM. I am using Paypal pro with CiviCRM 5.13.5. When I have tried it myself, I get the following error. </p>
  
  <p>However, if a link is served with checksum for that user then I was able to use UPDATE, CANCEL links!
  How can I fix this problem, please? Thanks.</p>
  
  <p><a href="https://i.sstatic.net/PAcgs.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/PAcgs.png" alt="enter image description here"></a></p>
  
  <p>UPDATE: this is the url I get when I click the link</p>
  
  <p><a href="https://example.com/index.php?q=civicrm/contribute/unsubscribe&amp;reset=1&amp;crid=173&amp;cs=631e63d2b52b3596e18b1f3fe144afc3_1559485259_inf" rel="nofollow noreferrer">https://example.com/index.php?q=civicrm/contribute/unsubscribe&amp;reset=1&amp;crid=173&amp;cs=631e63d2b52b3596e18b1f3fe144afc3_1559485259_inf</a></p>
  
  <p>does it seem all parameters present in the URL?</p>
  
Tags: <paypal><recurring-contributions><receipts>
Title: What is stopping to update recurring payment or billing details!
ThreadText: # What is stopping to update recurring payment or billing details!
  
  (Asked by: username_0 on 2019-06-02)
  
  Some of our donors have reported that they were not able to update the amount or cancel their recurring subscription payment using the standard email receipt that gets sent from CiviCRM. I am using Paypal pro with CiviCRM 5.13.5. When I have tried it myself, I get the following error.
  
  However, if a link is served with checksum for that user then I was able to use UPDATE, CANCEL links!
  How can I fix this problem, please? Thanks.
  
  [![enter image description here](https://i.sstatic.net/PAcgs.png)](https://i.sstatic.net/PAcgs.png)
  
  UPDATE: this is the url I get when I click the link
  
  <https://example.com/index.php?q=civicrm/contribute/unsubscribe&reset=1&crid=173&cs=631e63d2b52b3596e18b1f3fe144afc3_1559485259_inf>
  
  does it seem all parameters present in the URL?
  
  **Tags:** paypal, recurring-contributions, receipts
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-06-03. Score: 2
  
  Test this patch to see if it fixes your problem? <https://github.com/civicrm/civicrm-core/pull/14407>
  
  > **Comments:**
  > **username_0**: Thanks for your reply. But I am a bit confused while applying this patch!! I am on 5.13.5 and the PHP content of the patch is very different to the file of 5.13.5. For example, ContributionRecur.php code lines of  5.13.5 are very different from the latest patch file. And other 3 files also I found similar things. So, do I replace the entire content of the latest patch file? or apply only the differences, but my fear something might break!! Any thoughts? Thanks again!  
  > **username_2**: There should be a fix for this in 5.14.0 - dropping today  
  
  ---
  
  