Answers.Body: <p>Not so much an answer as a possible approach to debugging:</p>
  
  <p>1) find out the URL that this command visits and see if you get the same result. If so it's a bug with authorize.net</p>
  
  <p>2) if that URL works then it's a bug with civi. In this case get it to spit out what the api key is and check that against the vale you've entered, checking they're the same. </p>
  
  <p>The error should lie in one of those two places.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-18T06:23:30.467Z
Answers.LastActivityDate: 2016-03-18T06:23:30.467Z
Answers.UserDisplayName: JohnFF
Answers.Body: <p>We had this issue and we solved it by uninstalling the stripe extension.
  Somehow it was interfering with Authorize.net processing. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-01T06:22:58.820Z
Answers.Text: Thanks for this tip. It solved the problem for me too. I [opened an issue](https://github.com/drastik/com.drastikbydesign.stripe/issues/155) on the Stripe project for this.
Answers.UserDisplayName: universalhandle
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-13T18:53:50.563Z
Answers.LastActivityDate: 2016-07-13T18:53:50.563Z
Answers.UserDisplayName: Yossi
Body: <p>System Details</p>
  
  <p><strong>Versions</strong>
  <strong>CiviCRM:</strong> 4.7.4<br>
  <strong>WordPress:</strong> 4.4.2</p>
  
  <p>When I attempt to renew an expired membership via the Renew-Credit Card option I am presented with the following error.</p>
  
  <p><code>
  Payment Error Response:
  Error: Invalid API Key provided: ************W4kG
  </code></p>
  
  <p>We know the API keys are valid because we have other functions of CiviCRM that are authorizing succesfully with Authorize.net. Any help would be welcomed with open arms. XD.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-13T18:32:50.427Z
Comments.Text: I don't believe we did. We actually ended up redoing our CiviCRM installation because of other problems we ran into.
Comments.UserDisplayName: bitmvr
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-30T18:58:00.680Z
Comments.Text: Did you make any progress with this issue. We seem to have the same problem on our site.
Comments.UserDisplayName: Yossi
Tags: <api><authorize.net>
Title: Invalid API Key provided
ThreadText: # Invalid API Key provided
  
  (Asked by: username_0 on 2016-03-18)
  
  System Details
  
  **Versions**
  **CiviCRM:** 4.7.4  
  **WordPress:** 4.4.2
  
  When I attempt to renew an expired membership via the Renew-Credit Card option I am presented with the following error.
  
  `Payment Error Response:
  Error: Invalid API Key provided: ************W4kG`
  
  We know the API keys are valid because we have other functions of CiviCRM that are authorizing succesfully with Authorize.net. Any help would be welcomed with open arms. XD.
  
  **Tags:** api, authorize.net
  
  > **Comments:**
  > **username_1**: Did you make any progress with this issue. We seem to have the same problem on our site.  
  > **username_0**: I don't believe we did. We actually ended up redoing our CiviCRM installation because of other problems we ran into.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-03-18. Score: 2
  
  Not so much an answer as a possible approach to debugging:
  
  1) find out the URL that this command visits and see if you get the same result. If so it's a bug with authorize.net
  
  2) if that URL works then it's a bug with civi. In this case get it to spit out what the api key is and check that against the vale you've entered, checking they're the same.
  
  The error should lie in one of those two places.
  
  
  ---
  
  ### Answer by username_1 on 2016-07-13. Score: 1
  
  We had this issue and we solved it by uninstalling the stripe extension.
  Somehow it was interfering with Authorize.net processing.
  
  > **Comments:**
  > **username_3**: Thanks for this tip. It solved the problem for me too. I [opened an issue](https://github.com/drastik/com.drastikbydesign.stripe/issues/155) on the Stripe project for this.  
  
  ---
  
  