TOPIC: [SOLVED] Can't process credit cards

I'm trying to test credit card authorization using Authorize.net, but can't get it to work. Every time I submit the CC information, I get a screen with "Event Registration: Payment" and a button that says "Try Again." No error message or other indication of what happened. I have my Authorize.net account in Test mode, and have tried DT Register in both Test and Live modes. Same thing every time. I'm supposed to go live on Monday. Can someone help?

DT Register 2.7.3
Joomla 1.5.22
RocketTheme Maelstrom template

Thanks,
Andy

I set my Authorize.net account to Live mode, and it still doesn't work. And yes, I double-checked my API Login ID and Transaction Key values, and the card type I'm using is enabled in my Authorize.net account. We can't ALL be doing something wrong...I'm going to open a trouble ticket. This is a MAJOR problem. Can't use DT Register if it doesn't process credit cards!

***SOLVED***
Since this was an urgent problem, I decided to dig around in the DT Register code myself. After about 3 hours, I figured out the problem! There were actually 2 problems:
1. The GoDaddy Hosting setting was causing the main problem. I set it to NO, even though I am on GoDaddy. It was trying to go through a proxy server for the cURL request to Authorize.net. This may have been necessary in the past, but not anymore. My advice is to NEVER set the GoDaddy Hosting option to Yes.
2. DT Register uses the Authorize.net Transaction Version 3.1. The default for my Authorize.net account was version 3.0, so I changed it. Make sure you have that set properly on your account.

I wasted a lot of time on this, which could have been avoided by the developer either adding a little documentation. DT Register should remove that GoDaddy Hosting setting so other people don't have the same problem. And information should be added to the documentation for the required settings on the Authorize.net account.

Now that I've vented, I should say that I like this product very much. It has a lot of functionality and even allows for custom code with the MyScript plugin.

Andy, glad you got this figured out. I do apologize that we weren't able to assist sooner. We've been short-handed the last couple of days, and now you're into the weekend where we often are unable to handle any support issues anyway. Just bad timing. We work hard to provide the best support possible.

To address what you found...

1) The GoDaddy setting is needed for many. GoDaddy handles CURL differently than the rest of the world, which is why this setting is there. Most GoDaddy users need this. It's only been in more recent times that we've heard of a GoDaddy user NOT needing that parameter. It seems they have some newer servers and the smaller number of users that are on these particular servers have CURL handled properly. The setting should most definitely NOT be removed, but probably needs updated as far as how it is labeled.

2) The difference in 3.0 to 3.1 versions you mentioned has never actually come up before with any other DT Register user... which is why that is not documented. We'll look to add a note about that if anyone else would happen to encounter that in the future.

Thanks Andy If you run into anything else, let us know.