Issue with Auth.net

  • Resolved tsunamiecig

    (@tsunamiecig)


    5 years, 5 months ago

    When I try to run a manual payment through Authorize.net, I receive an error: Sorry, the Login ID, Client Key, or both, are not valid. Please check your settings and try again.

    I am sure I have entered the correct details, as they are the same credentials as what is being used on the frontend for regular payments.

    Sandbox mode does not work either.

    Not sure as to why this is happening, would love any troubleshooting tips.

    Thanks

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author bfl

    (@bfl)

    Hey @tsunamiecig. There are three settings that are required: Login ID, Transaction Key, and Client Key. The Client Key is not used by all Authorize.Net plugins, so comparing the settings with another plugin’s settings may mislead you. You can find instructions for getting the Client Key here.

    Plugin Author bfl

    (@bfl)

    Hey @tsunamiecig. Have you resolved this issue?

    cmilleratlas

    (@cmilleratlas)

    I have this same problem and I don’t see the resolution. Woo/ Authnet plugin has no field for Client key. All of the the other 3 keys are in place and working with checkout.

    Plugin Author bfl

    (@bfl)

    Hey @cmilleratlas. Most Authorize.Net plugins do not require the Client Key field. You will need to follow the instructions in step 2 to find your Client Key.

    cmilleratlas

    (@cmilleratlas)

    The instructions specifically call for “Public Client Key” as noted below:
    “Go to WooCommerce > Settings > Manual Payment > Authorize.Net.
    Copy and paste your API Login ID (from step 1) into the Login ID field.
    Copy and paste your Transaction Key (from step 1) into the Transaction Key field.
    Copy and paste your Public Client Key (from step 2) into the Client Key field.
    Click Save changes. That’s it, you’re all set.”

    I have a Public Client Key, but there is no field for Client Key, so this is of NO help. You say “most Authorize.Net plugins do not require the Public Client Key”, so what is the solution?? Authorize.net requires a Signature Key which is different.

    Plugin Author bfl

    (@bfl)

    This plugin has its own settings. Here’s a screenshot of the relevant settings page. I’ve highlighted the important navigational elements and the Client Key field. Let me know how it goes.

    Plugin Author bfl

    (@bfl)

    Hey @cmilleratlas. Did you figure it out?

    cmilleratlas

    (@cmilleratlas)

    We did. The screen elements that you referenced on mine are far different than you displayed. We reinstalled the plug, don’t know if that changed the tabs on secondary screens, but had to drill down 2or 3 more layers to find the field.

    Have a further question. Is there a way to display a zip code field to override system address for clients using a CC with address different? Thanks

    Plugin Author bfl

    (@bfl)

    No, there is currently no way to override the ZIP Code on a per-card basis.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Issue with Auth.net’ is closed to new replies.