Hi lrunnells,
it is a really strange issue; you can set your relay_url in your authorize.net account, indeed, but it shouldn’t be necessary, as plugin send it to authorize when customer pay an order
Can you please share with a us a link where we can do some test?
Let us know
Have a nice day 🙂
Not such a strange issue. I have the same problem. And there is also another new, unanswered post about this issue.
Is this plugin designed to work with API AIM?
This is the error message me and the customer get (mine via email) after every credit card transaction
>>>>>>>>>>>>>>
**Please DO NOT REPLY to this message. E-mail support@authorize.net if you have any questions.
Authorize.Net Merchant,
Your script timed out while we were trying to post transaction results to it.
Transaction ID: 721655xxxx <<< (I modified for post purposes)
Transaction Result: This transaction has been approved.
The following message was displayed to the customer:
——————————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.
Hi JimCoz516,
we’re here to help, but as I have already told, I *do* need a link to check your installation, without it, there is nothing I can do.
Every time the plugin redirects you to authorize.net payment page, it also send an url where authorize will redirect you after payment is complete; it seems there are some issues with this url, and I need to check this data to understand why.
“Is this plugin designed to work with API AIM?”
No, sorry; free version of the plugin uses SIM integration.
In our premium version, we implemented AIM integration, letting users to pay without leaving your site.
Let me know 🙂
Thank you @webmicroz. I actually discovered that plugin too late… after I already purchased an AIM plugin from CodeCanyon.
Unfortunately neither one, CodeCanyon or free AIM version, properly connects to Authorize.Net, so there is obviously some other site and/or server issue I need to figure out.
Yep. I just double checked. It’s called Authorize.Net WooCommerce Addon 1.0.2, by Syed Nazrul Hassan. I can not get it to connect either. It must be a code or server issue on my end.
I get code 14
I see that this in not API but AIM, right?
so they send me this,,
>>>>>>
Note: If you are integrating your website with Advanced Integration Method (AIM) using PHP, please be aware that the gateway URL is listed twice–once in the cURL configuration, and once again in the main body of the code. Using the test gateway URL in the cURL section of the code will create an Error 13 as cURL would connect to the incorrect server.>>>>
using woo commerce – what should be there?
sorry – no, I see – not AIM – Sim…
The Relay Response or Referrer URL does not match the merchant’s configured value(s) or is absent. Applies only to SIM and webLink APIs.
so what should it be for woocommerce?
I have tried leaving it empty – putting in the my-accoount link and the transaction link
and get the same response – any help?
I Jan,
as stated in this article,
“Error 14 occurs for SIM and DPM users when a transaction request is submitted that includes values for x_receipt_link_url or x_relay_url that are not specified in your Default Response/Receipt URL settings in the Merchant Interface.”
Can you please dobule check that you leave empty your rely url in merchat account? Plugin sends to authorize a rely url different for avery transaction, so that payment can be correctly registered, when confirmed; so you don’t need to specify a default realy url
Let me know
Have a nice day 🙂
Thank you for your response. The client this is installed in will check it today.
this is what the client tells me
“All the URL fields have been empty.”
Authorize net sends this in response to our receiving a message that they don’t know where to send the visitor back to…
2. Check to see if you have a properly formatted value for x_amount.
Verify that there is no dollar sign. The value should be strictly
numeric. Additionally, our sample scripts require a numeral with two
decimal places. Fingerprints created with an invalid amount value may
result in Response Code 99.
3. Compare the case of x_amount that is being posted to your script
with the case of x_amount in the fingerprint generating script. Some
scripting languages (such as Perl and PHP) are case sensitive. If you
post x_Amount to your SIM script and the script is programmed for
x_amount, the uppercase version may be ignored by the script and result
in an incorrect fingerprint. Correct the case of either your post
variable or the variable in the script to fix the error. Note: The
sample Perl script is written to accept the amount field as x_amount.
The sample PHP script is designed to accept this field as x_Amount.
Hi again Jan,
We recently published 1.0.5 version of the plugin; can you please try updating, and check results?
Otherwise, can you share with us a link where to check your installation and data passed to authorize.net?
Thank you!
