Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 933
    • Issues 933
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1249

Closed
Open
Opened Sep 11, 2019 by andrewcormickdockery@andrewcormickdockery

Paypal IPN fails when contact is merged

Some contacts, when they sign up to a Paypal recurring contribution on our online forms, use details which which do not exactly match what we already have for them in Civi, so a new contact is created at that time. We have volunteers which search for such duplicates and merge them back into the original contact.

But the IPN details do not change. The IPN still sends back the information with the contact ID set to the duplicated ID, so then Civi refuses to process it and gives the message "Could not find contact record: 123456 in IPN request". So these contacts end up never having their transactions recorded in Civi as a result.

The Paypal IPN details cannot be altered. But people's contact ID do sometimes change, so Civi must take this into account. One of the details in the IPN, the Contribution Recur ID, is actually correct (as is the Contribution ID of the original contribution). So a possible solution might be for Civi to look at those details instead and infer the correct contact ID to record the new transaction.

Edited Sep 12, 2019 by andrewcormickdockery
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1249