The developer account was working when I first setup a test server but after playing around with the relay response urls it no longer works. I am getting some sort of redirect (not a full redirect because the browser still shows https://test.authorize.net/gateway/transact.dll in the address bar) back to my relay response url instead of showing the payment form. I get no error messages. Any idea how to debug this? I posted to https://developer.authorize.net/tools/paramdump/index.php and all the data is the same as before. I created a new TransactionID and tried that with the same result. How to debug when you get no errors? Any help would be greatly appreciated.
If I enter an invalid relay response url (but one that is listed in the allowed urls) then I get an email error below. It appears that it is trying to process the transaction instead of giving me the payment form so I can enter the credit card information. Why would it think that I am using SIM instead of AIM?
Authorize.Net Developer Center Merchant, Your script timed out while we were trying to post transaction results to it. Transaction ID: 0 Transaction Result: %s cannot be left blank. 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. Credit card number is required. Expiration date is required. ------------------------------
Solved! Go to Solution.
03-12-2014
07:57 AM
- last edited on
03-12-2014
08:45 AM
by
RichardH
SIM required
<INPUT TYPE=HIDDEN NAME="x_show_form" VALUE="PAYMENT_FORM">
03-12-2014 08:25 AM - edited 03-12-2014 08:25 AM
You mean SIM, AIM don't use relay response.
So the payment form doesn't show and go straight to the relay response page when you put the payment form url on the browser?
If you are running AIM, it should leave your website at all, the post is in your server code, and not a form post
03-12-2014 08:08 AM - edited 03-12-2014 08:10 AM
Reposting this correctly. I mean SIM. Sorry.
03-12-2014 08:19 AM
SIM required
<INPUT TYPE=HIDDEN NAME="x_show_form" VALUE="PAYMENT_FORM">
03-12-2014 08:25 AM - edited 03-12-2014 08:25 AM
Regarding x_show_form ... You might be onto something. That line has always been there, but I wanted to dynamically change x_relay_URL in ASP code so i added runat="server" to both of those lines. I don't know how or why that would cause this problem but I am going to check it now.
Thanks.
03-12-2014 08:32 AM - edited 03-12-2014 08:44 AM
Ok. Not sure what is going on with the ASP server, but removing the runat="server" from the x_show_form tag fixed the problem. Maybe any field tagged as runat="server" must actually be touched by the server in order to get passed to the client. Regardless, your post led to the fix.
If you will add a note to your post about not using runat="server" in ASP then I will mark this solved. I really appreciate your timely help. I hope you are getting paid for this.
03-12-2014 08:40 AM
when you add runat="server" it would change the ID and Name attribute values, https://developer.authorize.net/tools/paramdump/index.php should have should you it was different.
03-12-2014 08:58 AM
You are right. It changed the names to ctl01 and ctl02 (control 1 and control 2). So I had the clue I needed in that report and didn't see the significance of those strangely named tags. Thanks again.
03-12-2014 09:33 AM