authorizenet_aim problems using v1.3.5

[silvito]

it happens when i switch the modle from one to the other. and it appears on the site. specifically on the page that you enter you credit card information. after clicking submit a red box with that error message comes up all the time.

[DrByte]

You still haven't said *exactly* what the error message is.

[silvito]

It's really not a syntax error but more of a processing error.
its the generic error message that you get when you have enter in the wrong information for processing the credit card, but the information entered is correct.

[DrByte]

Well ... I'm having a hard time guessing exactly what the error says ... and thus I can't tell you what specifically might be wrong.

I would figure that if the things' truly broken it would be very quick and easy for you to go and simulate the problem and quote the exact actual error message if you really wanted support. It's very possible you have a setting set incorrectly somewhere.

Upgrading to the latest officially supported software version will probably resolve the matter (unless it's just a settings issue), since the authorize.net modules received a significant overhaul in v1.3.8. I just figured getting the real error message might be a little easier and faster than doing an upgrade.

[silvito]

He is the exact message that appears on the page

- Your credit card could not be authorized for this reason. Please correct any information and try again or contact us for further assistance.


Like i have mention before it's you typical message you receive when the information on the credit card was entered in wrong

[DrByte]

Okay, in 1.3.5 there was no debugging support available in the module, so there's no "simple" way to diagnose exactly what's causing the problem.

1. If you intend to use AIM, you need to have an SSL certificate set up so you can accept secure transactions on your site. Otherwise if you collect CC numbers without SSL protection you subject you and your customers to fraud and theft problems.
But not having SSL isn't going to give that particular error.

2. In your Authorize.net account, there is a page which allows you to set a transaction "delimiter" and maybe even an "encapsulation" character. What do you have those set to presently? I think v1.3.5 expects the Delimiter to be a comma, and the encapsulation to be blank.

3. Do you have an "authorizenet" table in your database? If you do, then it's possible you might be able to get some debug response data from the records in it. If not, things get more complicated. Upgrading would be advisable.

[silvito]

1. If you intend to use AIM, you need to have an SSL certificate set up so you can accept secure transactions on your site. Otherwise if you collect CC numbers without SSL protection you subject you and your customers to fraud and theft problems.
But not having SSL isn't going to give that particular error.

Yes i do have a SSL install to the cart

2. In your Authorize.net account, there is a page which allows you to set a transaction "delimiter" and maybe even an "encapsulation" character. What do you have those set to presently? I think v1.3.5 expects the Delimiter to be a comma, and the encapsulation to be blank.

I really am not sure where it is in my authorize.net net account this is at, but i did find a Direct Response Delimiter and it's set to no. i set it to yesusing the character set you specified above and it still did work

3. Do you have an "authorizenet" table in your database? If you do, then it's possible you might be able to get some debug response data from the records in it. If not, things get more complicated. Upgrading would be advisable.

Yes i do have an authorize.net table in my database, but it appears to be empty.



What else can i do. i would love to upgrade but it does work for me. i have tries in the past and it messed up other page on the website. Our current host only supports php4 and MySQL4. So upgrade would be an even more headache.