Authorize.net merchant login ID or password is invalid.

  • localcoverageva
    Asked on January 18, 2019 at 12:31 AM

    Hi there,

    Our customers are getting this error when running a transaction, even though our auth.net API and transaction keys are correct.  Is there something I may have incorrect on the jotform side of things?  thanks so much.

    stephanie1547789463Screen Shot 2019 01 17 at 9 Screenshot 10

  • Jed_C
    Replied on January 18, 2019 at 6:15 AM

    Are you using the correct Transaction Key in Authorize.net Integration? I would suggest you to please generate a new transaction key and use that in the integration to see if that solves your problem. The following guide should help you:  https://support.authorize.net/authkb/index?page=content&id=A682

    Hope this helps. Looking forward for your response. 

  • Stephanie
    Replied on January 18, 2019 at 3:19 PM

    Hi there.  I did generate a new transaction key and it still did not work.  I did this both for sandbox mode and live mode and they both generated the same error, the one above.  I talked with Auth.net support and they said without the Response String noting the specific error code it's impossible for them to help me.  They also said it's the third party's responsibility (in this case jot form)  to display that info, that it does not go through our Auth.net interface at all Can you access this on your end?  They also said to check the url where the transactions are being sent (it's indicated in the screenshots).  I've included screen shots of our conversation (sorry the window was small and would not let me expand it hence the left/right screenshots of the convo).  Does jot form not integrate well with Auth.net? honestly? What would you recommend, square? Anything you can do to look into this deeper would be greatly appreciated, not being able to take payments online is a problem.


    1547842661Screen Shot 2019 01 18 at 1 Screenshot 10


    1547842671Screen Shot 2019 01 18 at 1 Screenshot 21.

    1547842724Screen Shot 2019 01 18 at 1 Screenshot 32


    1547842752Screen Shot 2019 01 18 at 1 Screenshot 43


    1547842772Screen Shot 2019 01 18 at 1 Screenshot 54

  • Victoria_K
    Replied on January 18, 2019 at 5:23 PM

    I am sorry about inconvenience you are experiencing. I see that you have added Authorize.net credentials, but since it requires live payment, I was not able to submit your form to test the issue. 

    I would suggest you to please login to your Authorize.net account and see if there is any problem with the account. I suspect that either your password is changed / expired or your account is inactive.

    Also, are you testing with live Authorize.net account or sandbox one? Your form is currently in live mode, so you should use credentials of your live Authorize.net account.

    Let us know how it goes.

  • Stephanie
    Replied on January 18, 2019 at 7:23 PM

    It seems you did not read my previous response, please whoever is reading this, start there.  I DID log in to my auth.net account, I even spoke with tech support there.  Please refer me to a supervisor or someone with more experience as I am getting rather frustrated I've spent the amount of time I have on this form, and now it's not working.  It WAS working, at least in sandbox mode, but auth.net has seen nothing go through since 1/12.

    I am experiencing this error in BOTH sandbox and LIVE mode.  I have now put the account in sandbox mode, using my authorize.net sandbox account API and transaction keys so that you can test.

    In summary, auth.net is unable to tell me what the problem might be without the specific Response String that is generated each and every time a transaction is sent or attempted.  JotForm, according to auth.net as you are the third party go between from user to transaction, is responsible for supplying me with that response string information which will contain the specific error code.  Instead, Jotform just supples a very basic error message which is not informative enough to even try to fix the problem, assuming it is on auth.net's side.

    Is there any way you can access this response string information?  Is there any way you can see why no transactions are going through, even though I have the correct API keys for both sandbox and live, and I've generated new transaction keys for both as well?

    Does jot form not integrate well with auth.net?  Is square better to use?  What would you recommend?  Your quick response would be much appreciated. Thank you

  • stephanie
    Replied on January 18, 2019 at 7:42 PM

    UPDATE: It seems to be working.  I just kept trying new transaction codes for the live mode and it went through.


    Do you have any more information you can give me on the jot form error codes and what they mean so I know more clearly where the issue is coming from in the future?  And is there a way to see the Response String auth.net was talking about?  I want to make sure if there's a problem again in the future it can be dealt with better.  Thank you so much.

  • Jed_C
    Replied on January 18, 2019 at 9:08 PM

    Jotform only displays the error thrown back to the app by Authorize.ent. Kindly check their article here https://support.authorize.net/s/article/How-Do-I-Look-up-Authorize-Net-Api-Response-Codes on how you can search for the error codes.

    Normally you will see error codes in the console. To view browser console, please refer to our guide here https://www.jotform.com/help/453-How-to-get-a-console-report-from-most-common-browsers.

    Let us know if you have any questions or if you need further assistance.