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.

Problem with form communicating with Authorize.net

  1. graphical_force
    Member

    Hello, I have my form setup to work with Authorize.net and had a test account set up. When using the test account, it worked. I then switched to a live production account and switched the gravity forms mode to Production from test and it does not seem to work. I am not getting an error on the Wordpress site but nothing is showing up in the transaction history in Authorize.net. When chatting with their support they were wondering if the Wordpress site was even communicating with Authorize.net. It should be since I have a check mark by the api login id and transaction key fields.

    No error codes are being shown in the html. Any suggestions?

    Posted 12 years ago on Wednesday August 8, 2012 | Permalink
  2. What error are you getting on the WordPress site?

    Posted 12 years ago on Thursday August 9, 2012 | Permalink
  3. graphical_force
    Member

    I'm getting no errors.

    Posted 12 years ago on Thursday August 9, 2012 | Permalink
  4. Shoot me an email to rob@rocketgenius.com and I'll send you a logging plugin that could help us out here. Just reference this post in your email.

    Posted 12 years ago on Thursday August 9, 2012 | Permalink
  5. graphical_force
    Member

    @Rob email sent.

    Posted 12 years ago on Thursday August 9, 2012 | Permalink
  6. graphical_force
    Member

    Hello, I've got the logging plugin installed and I've set it for Log all messages. I then filled out the form in question and tried to check the logs but I don't see any logs there. It appears nothing has changed.

    Posted 12 years ago on Friday August 10, 2012 | Permalink
  7. Resolved via email.

    Posted 12 years ago on Monday August 13, 2012 | Permalink

This topic has been resolved and has been closed to new replies.