topic Re: Discovering the problem problem. in Integration and Testing

Discovering the problem problem.

AaronHildebrand — Thu, 13 Dec 2012 20:41:08 GMT

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

Re: Discovering the problem problem.

RaynorC1emen7 — Thu, 13 Dec 2012 20:49:25 GMT

Not sure what you asking for at all.

But you get that error when the relay response is not working correctly.

See if the following help

Relay Response Basics and Troubleshooting

And you can use this as the relay response URL to see what was return from authorize.net

Post Data Validation URL

To get some dummy data, use the above post data validation url result and use those fields to post(post it in code-use the AIM example) to your relay response page.

Re: Discovering the problem problem.

AaronHildebrand — Thu, 13 Dec 2012 21:02:20 GMT

The problem I have is that I can't get any loggging in this particular area (a point of acute frustration for me at this point) and all the API passes back as an error is "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." on the page and "Your script timed out while we were trying to post transaction results to it."

These two things could mean anything really, and without knowing exactly what error's being triggered I'm simply going around in circles chasing my tail, it's driving me to distraction.

The dummy data idea is another means of trying to extract what is wrong, because if I manually post a false post header that has all the fixings of a proper ANET response it should show me where the errors lie. (The reason for this is that error reporting will give a 'Bad Request' response if it's cold-called)

Re: Discovering the problem problem.

AaronHildebrand — Thu, 13 Dec 2012 21:04:13 GMT

Additional:

This is not the request that's faulty, it's the response reciever, so unfortunately pre-checking on the way in is going fine, but the response receiver is failling somehow and I have no means of finding out how at this point if the API doesn't pass anything back.

Re: Discovering the problem problem.

RaynorC1emen7 — Thu, 13 Dec 2012 21:12:39 GMT

It not getting log because authorize.net can't access it for some reason. You might able to see it trying to get access at the your web server http log.

Did you do all the thing it said to check?

Relay Response Basics and Troubleshooting

Are you using asp.net? add this EnableViewStateMac="false" to both the form post to SIM and the relay response page

And what is on the relay response page?

Re: Discovering the problem problem.

AaronHildebrand — Thu, 13 Dec 2012 21:20:57 GMT

I understand that it can't access it, I also know that it's timing out in less than a second so it's not hitting the ten second problem, so that means it's not sending a response code 2XX back.

What I don't understand is why, and that's not really something I can ask about here, so what I am asking about is if there's a way to see what the API is seeing when it attempts to pass the postdata to the site.

Okay, let's go through the checklist:

Check that the Relay URL:

Relay is dynamically generated and enters into the form correctly

Confirm that you can load the Relay URL in a Web browser:

Loads, this is what I need the dummy data for because the page it loads fires off a 'Bad Request' if it's cold called by design.

If the merchant’s Web server is not available on the public Internet, has authentication enabled, or if the Relay URL uses a non-standard port for HTTP or HTTPS:

Server is on the internet, It's got a self-signed certificate at this time (it's a test server) and the relay URL uses standard HTTPS.

If the relay response page is using an SSL connection, ensure that the SSL certificate is valid and is from a trusted issuer. If Authorize.Net’s server cannot validate the certificate, it will abandon the connection.

Again, it's a self-signed cert, if this is the issue I don't know how to fix it on our testing area and it cannot at this time be tested live (due to the live system being in use)

Log into the Merchant Interface at https://account.authorize.net/, click Account from the top navigation, click Response/Receipt URLs, and review the settings to ensure that the correct Relay Response URL is configured.

As per prior discussions, this is shut down intentionally so that it goes to the correct location.

Re: Discovering the problem problem.

RaynorC1emen7 — Thu, 13 Dec 2012 21:34:54 GMT

it is a self signed cert. that would be the problem as authorize.net probably getting a 403 error.

can you change that to just http for testing?

Re: Discovering the problem problem.

AaronHildebrand — Thu, 13 Dec 2012 22:02:03 GMT

Now I'm getting an error 14, at least it's something, but this brings us back to the problem of "this is a dynamic URL so I can't predefine it in Authorize.Net's settings"

Re: Discovering the problem problem.

RaynorC1emen7 — Thu, 13 Dec 2012 22:19:18 GMT

remove the relay response URL setting on your merchant account.

Re: Discovering the problem problem.

AaronHildebrand — Thu, 13 Dec 2012 22:21:48 GMT

Okay, it says that relay can be used without setting a default, but I'm still getting a 14 error...

There's nothing in the following locations:

Account -> Response/Receipt URLs

Account -> Relay Response

Account -> Silent Post URL

So where is it catching?

Re: Discovering the problem problem.

RaynorC1emen7 — Fri, 14 Dec 2012 00:05:44 GMT

is the test account set with weblink enable?

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

said to remove all Referrer URLs too.

Re: Discovering the problem problem.

AaronHildebrand — Fri, 14 Dec 2012 15:09:30 GMT

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?

Re: Discovering the problem problem.

RaynorC1emen7 — Fri, 14 Dec 2012 15:57:47 GMT

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

Re: Discovering the problem problem.

AaronHildebrand — Fri, 14 Dec 2012 16:11:14 GMT

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.

Re: Discovering the problem problem.

AaronHildebrand — Fri, 14 Dec 2012 17:01:20 GMT

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

Re: Discovering the problem problem.

RaynorC1emen7 — Fri, 14 Dec 2012 17:21:10 GMT

The response is in the Request.Form

Re: Discovering the problem problem.

AaronHildebrand — Fri, 14 Dec 2012 19:23:06 GMT

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