Woocommerce Error at Checkout using Authorize.net Payment Gateway plugin

[imawake]

Hi All,

I'm using woocommerce and the Authorize.net Payment Gateway plugin on a site in staging. I'm getting the following error message at checkout, before entering cc info when running in test mode: 

----

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.

---

My woocommerce is up to date along with the plugin.

Any help is appreciated.

[RaynorC1emen7]

Not sure how your plugin work but read this Relay Response Basics and Troubleshooting

http://community.developer.authorize.net/t5/The-Authorize-Net-Developer-Blog/Relay-Response-Basics-a...

[jasonjudge]

This happens if the callback fails (the "relay response").

Authorize.Net will try to contact your shop to tell it what the result of the transaction is. It does this through the callback (aka "relay") URL. Failures can have many causes, and here are a few:

• You have not pre-registered the URL with the Authorize.Net account.
• Your site does not respond with a HTTP 200 (usually an error in your code).
• You have used a https URL and a self-signed certificate. Authorize.Net can use http or https, but if it's https, then the certificate needs to be 100% valid and trusted.

If you know the relay URL, try it manually and see what happens. If you don't know it, then you probably haven't registered it with Authorize.Net.

Either your application sends the relay URL it wants to use with the original authorization request, or you set up a default relay  URL in the Authorize.Net admin panel. Both ways should work. Authorize.Net will use the one it is given, or fall back to the default if it is not givem a URL. If there is no default and none is provided by your application, then that is another source of error.

-- Jason

[jasonjudge]

Forgot to ask - which plugin is this?