PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

API Login and Transaction ID

  1. chill986
    Member

    The Authorize.net setup will not validate my API Login and Transaction ID. Says Invalid API Login ID and/or Transaction ID, please try again. It will not validate. Please help - we are DAYS from launching.

    Thanks!

    Posted 5 years ago on Monday November 5, 2012 | Permalink
  2. Please try typing the values in rather than pasting them to ensure no extra characters are coming along for the ride. Also be sure the check test or production as appropriate. You should have a green check mark by both values when this information is correct.

    Posted 5 years ago on Tuesday November 6, 2012 | Permalink
  3. chill986
    Member

    I actually did type them in - and we tried creating a new transaction id as well. I will be working on this later today. Is there someone that I can speak to on the phone or by skype if I'm unable to get this to work?

    Posted 5 years ago on Wednesday November 7, 2012 | Permalink
  4. David Peralty
    Administrator

    We only provide support via the forums currently, but we have multiple people on during business hours.

    Posted 5 years ago on Wednesday November 7, 2012 | Permalink
  5. chill986
    Member

    Ok, just retried by typing in API Login ID - and had been given a new transaction key, which I also typed in. It is still giving me an error. I don't know what to do.

    I have the API Login and Transaction id. Help? :/

    Posted 5 years ago on Wednesday November 7, 2012 | Permalink
  6. chill986
    Member

    Could use some help on this please?

    Posted 5 years ago on Wednesday November 7, 2012 | Permalink
  7. chill986
    Member

    It seems in order to get the api login and transaction key validated, the plugin needs to be set to production instead of test.

    Posted 5 years ago on Wednesday November 7, 2012 | Permalink
  8. That has not been my experience. I have mine set to test and have my API Login ID and Transaction ID validated with the green checkmark. When you request those bits of information from Authorize.net, is there a choice to select production or test? (it's been a while since I set mine up...)

    Posted 5 years ago on Thursday November 8, 2012 | Permalink
  9. Note: I am running the latest version of GF (1.7.2) and the add-ons [Authorize.net v1.3.4 | User Registration v1.5]

    I can confirm that the same thing happens for me. Just setup a brand new Authorize.net account and entered in my API Login ID and Transaction ID. It will only give green checkmarks when the GF add-on is set to Production. In "Test" mode I get the red stop sign.

    Authorize.net is currently set to "Test Mode" and I recreated my transaction ID just to confirm it is not an issue on their side.

    In addition, because of this issue, when in "Test" mode (GF) the Authorize.Net Forms that are created do not show up in the Authorize.Net Forms list. They do show up if I switch to Production mode.

    Regardless of either mode I am in I do not see a way to setup my User Registration add-on to only create a user account if the subscription is successful. Which on the add-on page for the Authorize.net add-on says it can do (http://www.gravityforms.com/add-ons/authorize-net/) but is not noted in the documentation (http://www.gravityhelp.com/documentation/page/Authorize.Net_Add-On).

    Posted 5 years ago on Monday May 13, 2013 | Permalink
  10. Bump - Still seeing this issue with GF 1.7.3, Authorize.net 1.3.4, and User Registration v1.5

    Can we please get an update to this as it is a critical component to our e-commerce solution for multiple customers.

    Posted 5 years ago on Tuesday May 21, 2013 | Permalink
  11. I will bring this to the attention of the development team for their feedback.

    Posted 5 years ago on Wednesday May 22, 2013 | Permalink
  12. I heard back from the development team:

    For Authorize.net and PayPal Pro, the form will fail validation when subscriptions are not successfully created, so that option is not necessary. If the form was submitted, the payment and subscription were created.

    We will update the documentation to reflect this information.

    Posted 5 years ago on Sunday May 26, 2013 | Permalink