Answers.Body: <p>There was an issue that sounds very much like what you are describing (<a href="https://issues.civicrm.org/jira/browse/CRM-18277" rel="nofollow">https://issues.civicrm.org/jira/browse/CRM-18277</a> that is marked as having been fixed as of 4.7.8), but I think you are saying that beyond the source of the first installment, there were actual recurring contribution records created and listed at the bottom of the contributions tab of a given contact that you then are not able to cancel? If that is the case, I would suggest opening a ticket on JIRA - I haven't seen any tickets in this regards. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-28T01:09:33.640Z
Answers.LastActivityDate: 2016-06-28T01:37:51.023Z
Answers.LastEditDate: 2016-06-28T01:37:51.023Z
Answers.UserDisplayName: Tamar Meir - Cividesk
Body: <p>We've had a really high number of recurring contributions this month. I started becoming worried because some of the amounts are quite high. Doing some digging, it appears that everyone who used paypal to register in the past month has a recurring contribution set. I tried to run a test, but the payment wouldn't go through (for some reason civi is deleting the "sandbox" portion of the URL when I click save. Any idea what's happening there?) In any case, the test appears to have recurrence turned on even though I didn't opt for a recurring payment.</p>
  
  <p>Could this be an issue with our payment settings? Or is there a bug in civi? This bug runs a serious risk of breaking our trust with our members.</p>
  
  <p>We changed over to paypal pro at the beginning of the month, so it really seems that this issue is tied to that change. Credit cards entered on the back-end aren't coming up as recurring, but it appears every single transaction entered on the front end includes recurrence. There's no way 100% of users selected this option. As mentioned, my test appears to confirm this, even though I couldn't complete the payment.</p>
  
  <p>We are running Wordpress 4.5.1 and CiviCrm 4.7.6. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-04-27T19:47:32.183Z
Comments.Text: I've done more digging. First off, it appears that every payment processed since upgrading to CiviCRM 4.7.3 has been recurring, if made from the user front end. This precedes our shift to PayPal pro.
  It appears that the contributions aren't actually recurring - they are simply appearing to recur. This is still a serious issue as we have a different process for recurring contributions than for regular contributions.
Comments.UserDisplayName: Ben
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-04-27T20:47:16.737Z
Comments.Text: Attempting to cancel them (per comment 1) does not work. "The recurring contribution could not be cancelled." Presumably this occurs because the contribution doesn't exist.
Comments.UserDisplayName: Ben
Tags: <civicontribute><paypal>
Title: Is civi automatically adding recurrence to contributions?
ThreadText: # Is civi automatically adding recurrence to contributions?
  
  (Asked by: username_0 on 2016-04-27)
  
  We've had a really high number of recurring contributions this month. I started becoming worried because some of the amounts are quite high. Doing some digging, it appears that everyone who used paypal to register in the past month has a recurring contribution set. I tried to run a test, but the payment wouldn't go through (for some reason civi is deleting the "sandbox" portion of the URL when I click save. Any idea what's happening there?) In any case, the test appears to have recurrence turned on even though I didn't opt for a recurring payment.
  
  Could this be an issue with our payment settings? Or is there a bug in civi? This bug runs a serious risk of breaking our trust with our members.
  
  We changed over to paypal pro at the beginning of the month, so it really seems that this issue is tied to that change. Credit cards entered on the back-end aren't coming up as recurring, but it appears every single transaction entered on the front end includes recurrence. There's no way 100% of users selected this option. As mentioned, my test appears to confirm this, even though I couldn't complete the payment.
  
  We are running Wordpress 4.5.1 and CiviCrm 4.7.6.
  
  **Tags:** civicontribute, paypal
  
  > **Comments:**
  > **username_0**: I've done more digging. First off, it appears that every payment processed since upgrading to CiviCRM 4.7.3 has been recurring, if made from the user front end. This precedes our shift to PayPal pro. It appears that the contributions aren't actually recurring - they are simply appearing to recur. This is still a serious issue as we have a different process for recurring contributions than for regular contributions.  
  > **username_0**: Attempting to cancel them (per comment 1) does not work. "The recurring contribution could not be cancelled." Presumably this occurs because the contribution doesn't exist.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-06-28. Score: 1 | Accepted answer
  
  There was an issue that sounds very much like what you are describing (<https://issues.civicrm.org/jira/browse/CRM-18277> that is marked as having been fixed as of 4.7.8), but I think you are saying that beyond the source of the first installment, there were actual recurring contribution records created and listed at the bottom of the contributions tab of a given contact that you then are not able to cancel? If that is the case, I would suggest opening a ticket on JIRA - I haven't seen any tickets in this regards.
  
  
  ---
  
  