Discovering the problem problem.

[AaronHildebrand]

Okay folks;

This one's a bit strange, no I'm not asking for help with my implementation directly, but I am wondering if there is a way to see the FULL RESPONSE that the RECEIVING SERVER is sending to AUTHORIZE.NET on transaction to generate the beloved phrase:

"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."

Silent Post URL doesn't do what I'm looking for either, just a heads up on that.

Again, I am not looking for Authorize.Net's lovely statement above, what I am looking for is what the page is sending (preferrably verbatim) to ANET that's generating the lovely statement above.

Also, is there a way to produce some dummy data to send to the receiving point to test this directly? I know you can inject it into the head, but I need a dummy sample to do a header injection (effectively a fake POST right in the browser).

[RaynorC1emen7]

is the test account set with weblink enable?

http://developer.authorize.net/tools/responsereasoncode/

said to remove all Referrer URLs too.

[AaronHildebrand]

I thought weblink was being discontinued?

Sorry Raynor, but your response really isn't making a lot of sense.

I have removed the URLs from the three places I stated already, unless you mean remove it from the code, which if I do that how do I tell the API where to go?

[RaynorC1emen7]

on the http://developer.authorize.net/tools/responsereasoncode/

and put in the error 14.

it said

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

[AaronHildebrand]

Okay,

Error 14 is gone, but I am verry off-put by how it happened, you see, I had made sure that the data was cleared from all locations, and yet it would give that error.

I checked again this morning, and lo and behold, something had added the test url automatically to the Response / Receipt URL area.

It wasn't the default, but it was there, and I hope we don't see more of it.

[AaronHildebrand]

Okay, here's where it's at now, I'm sitting with this particular line drawing no data:

response = new AuthorizeNet.GatewayResponse(Request.Headers.AllKeys);

Request is pulling data from System.Web.HttpBase.

Yet this data is pulling nothing,.

[RaynorC1emen7 · Accepted solution]

The response is in the Request.Form

[AaronHildebrand]

Well, Raynor, you have gotten me through this, thank you very much for your time and patience!