Yesterday, I upgraded from 3.1.2 to 3.1.9. My payments are set-up to use AuthorizeNet AIM. Whenever I try to process a payment with 3.1.9, my user sees an error like: "AuthorizeNet Account name or password incorrect or account not active" I downgraded back to 3.1.2 and problem went away. Clearly something has changed in the way AuthorizeNet transactions are processed with 3.1.9.
After you upgraded to 3.1.9, did you go into your Authorize.NET configuration (setup / configuration -> Plugins -> Authorize.NET) and ensure all of the values are filled in and accurate?
I just reu a diff between plugin in 3.1.2 and 3.1.9 and there were only two minor modifications in plugin that can't generate such error. Can you contact us in helpdesk and attach payment debug info when error was generated I will check what can be wrong.
After installation of 3.1.9, I did confirm that all the AIM information was correct. The information was already in the db. As part of the debug work I did, I requested a new transaction key and entered it into amember. When I downgraded back to 3.1.2, the information already in the db (incl. new transaction key) worked correctly.
One potential cause of the problem is this. My merchant provider is call MerchantPlus (http://merchantplus.com). They offer their own gateway called Navigate which is "AuthorizeNet compatible". This mean that my server should speak to Navigate as if it was AuthorizeNet; I will send the same data in the same format and I will receive responses that are in the AuthorizeNet format. Somehow, we have lost that compatibility with 3.1.9. I suspect that the sending of credentials (AccountID and transaction key) is not working now.
John, So I guess you have modifications in your old plugin (possible gateway URL was changed to work with merchantplus.com ) check your old plugin files function run_transaction do you see auth.net gateway url here? In default plugin it should be: PHP: $ret = cc_core_get_url("https://secure.authorize.net/gateway/transact.dll", $vars1);