Trouble setting up SIM that makes no sense

[AaronHildebrand]

Good day;

Alright, here's the issue I have, I'm currently trying to set up a SIM system, and I keep getting an error response code 14: http://support.authorize.net/authkb/index?page=content&id=A601

Anyways, I've gone over the support, searched the forums, and agonized over this for almost a week now and I'm no closer to solving this than when I started.

The big problem I'm getting is, my logs are empty, it's as if I send the request out to Authorize.Net and nothing comes back at all to my server and it instantly spits out the above error.

This is also in C# to those who are interested, so I'll try to throw snippets in here that are non-specific.

_response.Write("<form action = '" + formAction + "' method = 'post'>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_fp_hash' value = '" + fingerPrint + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_fp_sequence' value = '" + seq + "'\\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_fp_timestamp' value = '" + stamp + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_login' value = '" + _apiLogin + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_tran_key' value = '" + _transactionkey + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_amount' value = '" + _order.TotalPayable.Amount + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_relay_url' value = '" + _returnUrl + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_po_num' value = '" + _order.OrderNumber + "' \\>\n");
            _response.Write("\t\t<input type = 'hidden' name = 'x_relay_response' value = 'TRUE' \\>\n");

That's my SIM form generation script that produces the following HTML

		<input type = 'hidden' name = 'x_fp_hash' value = 'a5796de3cf172f254247c18ec7765969' \>
		<input type = 'hidden' name = 'x_fp_sequence' value = '679'\>
		<input type = 'hidden' name = 'x_fp_timestamp' value = '1354822639' \>
		<input type = 'hidden' name = 'x_login' value = '00000000' \>
		<input type = 'hidden' name = 'x_tran_key' value = '00000000' \>
		<input type = 'hidden' name = 'x_amount' value = '30.00' \>
		<input type = 'hidden' name = 'x_relay_url' value = 'http://somewhere.something.net/responsenotification/anet' \>
		<input type = 'hidden' name = 'x_po_num' value = '221' \>
		<input type = 'hidden' name = 'x_relay_response' value = 'TRUE' \>

Now that link in reality passes no data, but also passes an HTTP Response of 200, so it should be working fine for the condition of 'needing a response' that I read about in one post

Again, I'm having difficulty debugging this because I can't see any of my logging lines tripping in my error log code, and the only errors that map are the 'no data errors' when I manually go to that page it references, is ANET not even going to where the relay_url is telling them to go?

Also, is there a way to send this data to one place, and send the user to a different location? A design decision for the current project was to separate the threading to send the payments to a background worker in the site and the users elsewhere and I have to accomodate that functionality unfortunately.

[RaynorC1emen7]

error 14 mean the relay url settings on your merchant accounts is set to an url other than http://somewhere.something.net/responsenotification/anet . login to your merchant account to check that. if it ishttps it need to be https.

not sure about a different thread, since the the CC info are entery in authorize.net, you can't really have any control of what it doing. unless you want to do a popup before you submit to authorize.net SIM form.

[AaronHildebrand]

Okay, well here's problem number two, that URL can't be default then, because the response receiving page url is dynamically generated using URL Rewriting to include the order ID.

Should I just leave that field blank for it to take from the SIM form or am I up the creek without a paddle on this one?

[RaynorC1emen7 · Accepted solution]

I think you can remove relay url from the merchant account settings.

Once you do that the x_relay_url will works, it just won't validate againist someone temper with it.

[AaronHildebrand]

Now why couldn't support have just told me that when I was chatting with them?

Thank you kindly RaynorC1emen7, I've still got more development to go but this gets me past the silent barricade I've had to deal with thusfar.

Take care!

[ayla]

Hi, thanks for sharing all the details. It sounds like the error 14 might be related to how the relay response URL is set up or how Authorize.Net is handling the relay request. Since your logs aren’t showing any hits, it could be that Authorize.Net isn’t reaching your relay_url properly or there's a mismatch in the configuration.

A couple of things to check:

Make sure your relay_url endpoint is publicly accessible and can handle POST requests correctly.

Verify that there are no firewall or security settings blocking Authorize.Net’s requests.

Check if your server responds quickly enough — sometimes slow responses cause Authorize.Net to timeout.

Also, review that your API Login and Transaction Key are correct and active.

Regarding sending data to one place but redirecting users elsewhere, you might want to implement server-side processing where the payment data is handled asynchronously, and the user is redirected after confirmation. This can be done using webhook listeners or background jobs depending on your platform.

Hope this helps! Let me know if you want me to share some examples or guides that helped me with similar setups.