Answers.Body: <p>Civi will not record contributions for PayPal recurring contributions that aren't set up through CiviCRM.</p>
  
  <p>Broadly speaking, there are two types of payment processors when it comes to recurring contributions - those that rely on webhooks and those that rely on tokens.  Most webhook-based processors call the webhook the IPN ("Instant Payment Notification") address.</p>
  
  <p>With IPN processors (like Stripe/PayPal), when you create a recurring donation, CiviCRM sends some info to the processor (amount, how often to charge, the CiviCRM contact ID, the recurring payment ID, etc.).  </p>
  
  <p>When the payments are processed on PayPal's end, the <em>processor</em> will push some data to a URL that Civi has set up explicitly for the purpose (the "IPN URL").  So Civi won't create payments until PayPal says, "Hey, we processed this and it succeeded or failed".  PayPal relies on the info that Civi sent to PayPal when the payment was created to send data back to Civi - so non-Civi recurring donations won't work, because, e.g., PayPal doesn't know the contact ID to send in its IPN.</p>
  
  <p>So one option is to record the payments manually each month.  The other is to investigate whether you can shoehorn the <a href="https://civicrm.org/blog/andyw/offline-recurring-payment-extension" rel="nofollow noreferrer">Offline Recurring Payment extension</a> to fit your needs.  Note, however, that the extension isn't tested on modern versions of Civi and is for a slightly different use case - so unless you are (or have access to) a coder, this might not be a good choice.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-27T20:18:42.870Z
Answers.Text: very clearly explained Jon. nice job.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-27T18:01:37.497Z
Answers.LastActivityDate: 2017-07-27T18:01:37.497Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>I'm in the process of moving our legacy memberships over to our new Civi install. We needed to get our membership drive going so we just used vanilla PayPal recurring donation buttons. I've set up Stripe on this new install since they offer $15k of free transactions.</p>
  
  <p>I created membership types to correspond to what we had set up on PayPal. For example, </p>
  
  <h3>Foo Membership</h3>
  
  <ul>
  <li>Financial Type: Member Dues</li>
  <li>Minimum Fee: $5</li>
  <li>Auto-renew Option: Auto-renew Required</li>
  <li>Membership Type Duration Unit: 1 Month</li>
  <li>Membership Type Plan: Rolling</li>
  </ul>
  
  <p>I've entered all the dues paying members with accurate start dates and even imported their dues history as a contribution import.</p>
  
  <p>Will Civi keep recording contributions for these individuals even though the payments are all being done offsite? Or will I need to import/record them each month or get all the legacy members switched over to Stripe?</p>
  
Tags: <civicontribute><civimember>
Title: Will recurring contributions be recorded for memberships not hosted by CiviCRM?
ThreadText: # Will recurring contributions be recorded for memberships not hosted by CiviCRM?
  
  (Asked by: username_0 on 2017-07-25)
  
  I'm in the process of moving our legacy memberships over to our new Civi install. We needed to get our membership drive going so we just used vanilla PayPal recurring donation buttons. I've set up Stripe on this new install since they offer $15k of free transactions.
  
  I created membership types to correspond to what we had set up on PayPal. For example,
  
  ### Foo Membership
  
  * Financial Type: Member Dues
  * Minimum Fee: $5
  * Auto-renew Option: Auto-renew Required
  * Membership Type Duration Unit: 1 Month
  * Membership Type Plan: Rolling
  
  I've entered all the dues paying members with accurate start dates and even imported their dues history as a contribution import.
  
  Will Civi keep recording contributions for these individuals even though the payments are all being done offsite? Or will I need to import/record them each month or get all the legacy members switched over to Stripe?
  
  **Tags:** civicontribute, civimember
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-07-27. Score: 4 | Accepted answer
  
  Civi will not record contributions for PayPal recurring contributions that aren't set up through CiviCRM.
  
  Broadly speaking, there are two types of payment processors when it comes to recurring contributions - those that rely on webhooks and those that rely on tokens. Most webhook-based processors call the webhook the IPN ("Instant Payment Notification") address.
  
  With IPN processors (like Stripe/PayPal), when you create a recurring donation, CiviCRM sends some info to the processor (amount, how often to charge, the CiviCRM contact ID, the recurring payment ID, etc.).
  
  When the payments are processed on PayPal's end, the *processor* will push some data to a URL that Civi has set up explicitly for the purpose (the "IPN URL"). So Civi won't create payments until PayPal says, "Hey, we processed this and it succeeded or failed". PayPal relies on the info that Civi sent to PayPal when the payment was created to send data back to Civi - so non-Civi recurring donations won't work, because, e.g., PayPal doesn't know the contact ID to send in its IPN.
  
  So one option is to record the payments manually each month. The other is to investigate whether you can shoehorn the [Offline Recurring Payment extension](https://civicrm.org/blog/andyw/offline-recurring-payment-extension) to fit your needs. Note, however, that the extension isn't tested on modern versions of Civi and is for a slightly different use case - so unless you are (or have access to) a coder, this might not be a good choice.
  
  > **Comments:**
  > **username_2**: very clearly explained Jon. nice job.  
  
  ---
  
  