Answers.Body: <p>Found it! The contact_id in civicrm_iats_customer_codes was linked to the wrong contact. Previously the records were merged and one was soft-deleted, so in our import process that was confused. Should be a simple fix!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-15T11:59:15.557Z
Answers.Text: Correct process would have been to export the exisiting recurring series in progress -> the contact id-s in that file would have been the only contact id-s associated with any recurring series. If you ran a dedupe match process instead there very likely are more issues.
Answers.UserDisplayName: KarinG - Semper IT
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-15T00:02:21.560Z
Answers.LastActivityDate: 2019-06-15T00:02:21.560Z
Answers.UserDisplayName: Zachary
Answers.Body: <p>This tells me there are issues with the way in which you have migrated your recurring series from PayPal to iATS Payments and into CiviCRM. </p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-06-14T19:12:20.840Z
Answers.LastActivityDate: 2019-06-14T19:12:20.840Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>What happened:
  1: Went to recurring series. Clicked "Process" on Card on File
  2: Put in the amount, left defaults
  3: Charge went to iATS and posted successfully.
  4. The charge linked to a formerly merged/deleted record of the same name as the record it was supposed to be processed on, unlinked to the recurring contribution.</p>
  
  <p>What could have caused this?</p>
  
Tags: <iats>
Title: iATS Charge to Card on File attributed to merged/deleted record
ThreadText: # iATS Charge to Card on File attributed to merged/deleted record
  
  (Asked by: username_0 on 2019-06-14)
  
  What happened:
  1: Went to recurring series. Clicked "Process" on Card on File
  2: Put in the amount, left defaults
  3: Charge went to iATS and posted successfully.
  4. The charge linked to a formerly merged/deleted record of the same name as the record it was supposed to be processed on, unlinked to the recurring contribution.
  
  What could have caused this?
  
  **Tags:** iats
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2019-06-15. Score: 1 | Accepted answer
  
  Found it! The contact\_id in civicrm\_iats\_customer\_codes was linked to the wrong contact. Previously the records were merged and one was soft-deleted, so in our import process that was confused. Should be a simple fix!
  
  > **Comments:**
  > **username_1**: Correct process would have been to export the exisiting recurring series in progress -> the contact id-s in that file would have been the only contact id-s associated with any recurring series. If you ran a dedupe match process instead there very likely are more issues.  
  
  ---
  
  ### Answer by username_1 on 2019-06-14. Score: 1
  
  This tells me there are issues with the way in which you have migrated your recurring series from PayPal to iATS Payments and into CiviCRM.
  
  
  ---
  
  