When posting a recurring transaction with PayPal (offline and online), we're getting a 'Transaction ID not set' Payment Processor error. The payment is created in Paypal.

Checking Civi log file, on offline transactions, getting:

[info] Could not find payment processor for contribution record: #######

For the online transaction, the log file has:

[info] contributionRecur could not be loaded
[info] Contribution record updated successfully
[info] Receipt sent
[info] Success: Database updated

This problem seems to have started with the 4.7 upgrade.

Even recurring transactions coming from Paypal are giving the same '[info] Could not find payment processor for contribution record:' error.

Site profile settings

  • I have exactly the same issue with CiviCRM 4.7.2 on the latest WordPress stable with non-recurring transactions. I suspect that civicrm.stackexchange.com/questions/9730/… is related. Feb 23, 2016 at 17:33
  • I found the problem and if I knew how to make a patch I would. The issue is found in the PayPalProIPN.php file. It attempts to find the Paypal payment processor, but doesn't limit the search to active processors. I had an old PayPal account. I added the parameter 'is_active = 1' and the problem was fixed.
    – Logan Bear
    Feb 23, 2016 at 21:08
  • Thanks for the info Logan, I'll see what I can do. I have a two Paypal processors, one for testing one for live - perhaps I'm seeing the same thing as you. Feb 23, 2016 at 22:27
  • 2
    @ChristianWach, yes I added a line 'is_active=1,' to the api3 call on PaymentProcessor 'getvalue'. In my situation, I have two PayPal processors - one enabled one disabled. Since the disabled was first, the system failed. By adding one line, Civi selected the only active Paypal processor and it worked. What's odd is the payment processor being used in already in the contribution_recur table. But since the IPN sets this variable before checking the recur table, the value in the recur table is ignored. If Civi would take the value from the recur table, this whole problem would disappear.
    – Logan Bear
    Feb 24, 2016 at 15:04
  • 1
    I posted a slightly different approach to the issue - but I'm not sure if it'll fix your situation. Essentially I can't figure out why finding the payment processor should trigger a fatal error. the following fixes things for me: civicrm.stackexchange.com/questions/9730/… Feb 25, 2016 at 12:16

1 Answer 1


You don't say which version of CiviCRM you're using. There were some fixes related to PayPal in 4.7.13, in particular look at CRM-18483 If you're not up on at least 4.7.13, it would be worth upgrading.

(Edited to correct a typo)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.