gregoconnor VIP
Total posts: 34
04 Март 2015 23:52

Hi I am trying to use authorize.net on my site and need to get the gatway to shake hands. My site is rainbowrv.com I have been using your product for many years and now want to use Auth net and dump LinkPoint I get a error (14) AUthorize . net describe this error here .........................................................
Response Reason Code: 14

Response Reason Text: The Referrer or Relay Response URL is invalid.

Integration Team Suggestions: The Invalid Referrer or Relay Response URL message can be the result of a few different situations that could impact SIM and Weblink users.

SIM Integration Suggestions Error 14 occurs for SIM users when one or more URLs are specified in your Default Response/Receipt URL settings, but we receive a URL with your transaction that does not match any listed here. In this case the transaction would include the field x_receipt_link_url if you prefer to view our receipt page but provide a link for the customer to use to return to your site. Alternately, the transaction would include the field x_relay_url to specify which web page on your server should be used as the receipt page your customers see.

By designating a Default Response/Receipt URL, you are telling our system to only return results to one of the listed URLs. If the value of either x_receipt_link_url or x_relay_url does not match one of these designated Default Response/Receipt URLs, Error 14 will occur.

While x_receipt_link_url and x_relay_url will work without specifying a Default Response/Receipt URL, it is strongly suggested that you set Default Response/Receipt URLs if you are sending either of these fields, to ensure that only these URLs can be used.

To add a valid Response/Receipt URL, please follow these steps:

Login to your Merchant Interface at  https://account.authorize.net/ 
Click Settings in the main left side menu
Click Response/Receipt URLs
Click Add URL
Enter your Response URL
Click Submit

Weblink Integration Suggestions Note: Weblink is no longer actively supported and is subject to be discontinued in the near future. We strongly recommend that Weblink merchants upgrade to SIM or AIM. For details about upgrading to AIM or SIM, please read the Weblink Conversion Guide at http://www.authorize.net/files/conversionguide.pdf.

For Weblink users, Error 14 could indicate that the referrer URL, from which you are submitting transactions, is not listed as a Valid Referrer URL in your Authorize.Net account (this is only applicable to Weblink users).

The referrer URL is the very last page viewed by your customer before being sent to our payment form, or, if using your own payment form, it is the last page before transaction information is submitted to Authorize.Net.

The easiest way to determine what your referrer URL is, is to run a test transaction through your website. When you get to the page where your customer enters their credit card number, look at the web address in your browser bar ( http://mysite.com/etc.. ).

Check the web address of this page. If it is https://secure.authorize.net/gateway/transact.dll , click Back on your browser bar, then look at the web address again. This url is the one you will need to enter as a Valid Browser Referrer URL.

If the web address of your payment form is not https://secure.authorize.net/gateway/transact.dll , please continue with the test by submitting your credit card information. Once you have submitted your credit card information and received an approval or decline, look at the web address again. If it says https://secure.authorize.net/gateway/transact.dll in the address bar, you will need to add Valid Browser Referrer URL's for your website. Click the Back button on your browser and look at the web address again. This is the url you will need to enter as a Valid Browser Referrer URL.

If you do not see https://secure.authorize.net/gateway/transact.dll as a web address on either the payment form or receipt page, you are using AIM and do not need referrer URL's. In this case, please remove all referrer URL's from your Settings menu.

To designate a Valid Referrer URL:

Login to your Merchant Interface at  https://account.authorize.net 
Click Settings in the main left side menu
Click WebLink
Click Referrer URLs
Click on Add URL
Add the URL designating the page that should be a valid referrer URL
Click Submit

Note: More than one URL may be designated as a Valid Referrer URL.

Also, we recommend adding versions of your URL--both with and without the initial "www"--as many search engines will refer searches to your site without the "www" in front of your domain name.

Another possible cause of this error is that your customer's web browser may not support the ability to pass the Referrer URL to us. In this case, the customer can use a different browser to place the order. The long-term solution for this is to upgrade your connection method to SIM or AIM, as these methods do not rely on customer browser compatibility for authentication.

Other Suggestions: Applicable only to SIM and WebLink APIs. The Relay Response or Referrer URL does not match the merchant’s configured value(s) or is absent.

Последние изменения: 26 Авг 2022


gregoconnor VIP
Total posts: 34
05 Март 2015 00:04

Here are the url's I tried to list with no luck http://rainbowrv.com/component/emerald/?task=payment.back
http://rainbowrv.com/component/emerald/?task=plans.create& ;processor=authorize.net
http://www.rainbowrv.com/component/emerald/?task=payment.back
http://www.rainbowrv.com/component/emerald/?task=plans.create& ;processor=authorize.net

here is the url with the error message https://secure.authorize.net/gateway/transact.dll?x_fp_sequence=13362& ;x_invoice_num=5-13362&x_fp_timestamp=1425513375&x_amount=39.95&x_login=7GKQ8zq75&x_currency_code=USD&x_test_request=0&x_show_form=PAYMENT_FORM&x_method=CC&x_email=greg%40rainbowrv.com&x_cust_id=67&x_description=Our+1+Year+Plan+%5BrainbowRV+Subscription%5D&x_version=3.1&x_relay_url=http%3A%2F%2Frainbowrv.com%2Findex.php%3Foption%3Dcom_emerald%26task%3Dplans.create%26Itemid%3D1%26processor%3Dauthorize%26em_id%3D13362&x_relay_response=TRUE&x_relay_always=TRUE&x_receipt_link_method=LINK&x_receipt_link_text=Return+to+website&x_receipt_link_url=http%3A%2F%2Frainbowrv.com%2Findex.php%3Foption%3Dcom_emerald%26task%3Dpayment.back%26Itemid%3D1%26processor%3Dauthorize%26em_id%3D13362&x_cancel_url=http%3A%2F%2Frainbowrv.com%2Findex.php%3Foption%3Dcom_emerald%26task%3Dpayment.back%26Itemid%3D1%26processor%3Dauthorize%26em_id%3D13362&x_fp_hash=02961b14e625aa7e872ccc688cbcd09a

Thanks in advance


Sergey
Total posts: 13,748
05 Март 2015 03:39

In your transaction URL you can see that x_relay_url and x_receipt_link_url have different format.

http%3A%2F%2Frainbowrv.com%2Findex.php%3Foption%3Dcom_emerald%26task%3Dplans.create%26Itemid%3D1%26processor%3Dauthorize%26em_id%3D13362
http%3A%2F%2Frainbowrv.com%2Findex.php%3Foption%3Dcom_emerald%26task%3Dpayment.back%26Itemid%3D1%26processor%3Dauthorize%26em_id%3D13362

which decodes into

 http://rainbowrv.com/index.php?option=com_emerald& ;task=plans.create&Itemid=1&processor=authorize&em_id=13362
 http://rainbowrv.com/index.php?option=com_emerald& ;task=payment.back&Itemid=1&processor=authorize&em_id=13362

Try to add these but delete &em_id=13362. This is specific for each transaction. But start with just adding http://rainbowrv.com . This should be enough already.


gregoconnor VIP
Total posts: 34
05 Март 2015 17:47

OK cool that did the trick but now I cant get the authorize.net link to accept the handshake but an error code of 99 comes up from their url. I went thru all the fields with authorize.net tec support and everything checks out correct but they are stumped? they asked me if this shopping cart uses AIM or SIM or if it requires a ssl to be used. they also asked if there was a way to send or not send the curancy code. thanks in advance for your help.
Gregory OConnor


Sergey
Total posts: 13,748
06 Март 2015 03:56
  • We are using SIM
  • Those URLs without &em_id=13362 produce an errors. Yes handshake might be a problem.
  • No SSL is required unless you create your site based on HTTPS.

gregoconnor they also asked if there was a way to send or not send the curancy code.

Do you mean currency? Yes it sends x_currency_code parameter.


gregoconnor VIP
Total posts: 34
25 Март 2015 03:27

I dont know where to go from here with trying to get authorize.net to wok on my site. The gateway works in another area of the site and the authorize.net tech support caim it should work here also. do you have some info I can send to them to have this worked out. Does the payment gate way work on other sites with Emerald users?


gregoconnor VIP
Total posts: 34
25 Март 2015 22:52

I need to move on and find another payment gateway. 3 hours on the phone with Authorize.net and nothing is resolved. they claim there is an issue with the syntax but cant point to it s,the same syntax shows in my other gateway. Is anyone else using authorize.net in the USA .


Sergey
Total posts: 13,748
30 Март 2015 09:19

gregoconnor Does the payment gate way work on other sites with Emerald users?

We did not have any problem reports so far.

gregoconnor I need to move on and find another payment gateway. 3 hours on the phone with Authorize.net and nothing is resolved. they claim there is an issue with the syntax but cant point to it s,the same syntax shows in my other gateway. Is anyone else using authorize.net in the USA .

Give me full access to your site I'll try to have a look. I might also need you online to assist with Authorize parameters.


killersmile
Total posts: 121
26 Авг 2022 12:39

Interesting site i love it keep posting more! custom shed builders

Работает на Cobalt