I have the same issue that this person did, though I'm updated to 4.6.10 The issue is that when submitting payments, I get the 9003 error code, which says "MD5 Verification failed." I've reset the MD5 code from both sides, and am confident that they match. It's possible that my issue could be solved with the answer that I linked, but I don't know enough to apply it. It's also possible that Authorize.net tech support could help me, but they won't do anything without the log and I'm unsure where it lives. So...

1) Do you know how to fix this error?

Or failing that,

2) Where are CiviCRM's payment processor logs?

  • 1
    Can you please edit your question and correct the version number (4.10) which you've reported? There isn't (yet) such a CiviCRM version, and an accurate answer will be more likely with an accurate question. Jun 16, 2016 at 20:52
  • Good catch! Edited.
    – naomisl
    Jun 16, 2016 at 20:55

1 Answer 1


Answering (2) only here.

CiviCRM's payment processor logs vary in their location based on the CMS in use. These logfiles include a unique string per site, as the logfiles are located within the webroot and a hard to guess filename offers some defense against attackers viewing debug output.

This is documented @ -


4.6 and below: wp-content/plugins/files/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log 4.7 and above: wp-content/uploads/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log


media/com_civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log (1) or media/civicrm/ConfigAndLog/CiviCRM.HARDTOGUESS.log (2)



  • I don't think the web-accessible logfiles are great even with the current protections applied, and I'm working to provide better options in CRM-13639. Jun 16, 2016 at 21:18
  • Thank you! Follow up question: If this log shows only email related errors and nothing about the payment processor that is acting up, what would you take from that information?
    – naomisl
    Jun 16, 2016 at 22:20
  • I'd check if the Authorize.NET payment processor logs to a separate file; next I'd track down the location of that error message (capitalisation of Verification may make the location distinctive?) and debug what specific inputs aren't matching, leading to a validation failure. Jun 17, 2016 at 0:12
  • Correction for Joomla: ~/media/civicrm/ConfigAndLog/
    – BruceW
    Aug 10, 2016 at 5:13
  • Thanks BruceW! Looks like Debugging for Developers and CMS Standard directories differ re Joomla! locations, hope someone who uses Joomla can check and correct the wiki docs. Updated the above to mention both for now, let me know if I should trim it down again. Aug 10, 2016 at 11:00

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.