Accepting Credit card problem..pls help !

[Fine Thai Decor]

First of all "Thank you very much " for your replies,

- I did put it on test mode, tried different cards ( 4 cards ) still not went thru every time I click confirm it kicked me back to stop 2 and got the same massage.

- Tried manual transection on Authorize.Net customer it' works.


What should I do ?

[darocket]

First of all "Thank you very much " for your replies,

- I did put it on test mode, tried different cards ( 4 cards ) still not went thru every time I click confirm it kicked me back to stop 2 and got the same massage.

- Tried manual transection on Authorize.Net customer it' works.


What should I do ?

Yes, I'm having the same problem. Im using the Authorize.Net_aim module though. But everytime I enter my card and want to go to step 3, it just goes back to step 2. Has anyone seen this and can offer a fix??

David

[darocket]

Yes, I'm having the same problem. Im using the Authorize.Net_aim module though. But everytime I enter my card and want to go to step 3, it just goes back to step 2. Has anyone seen this and can offer a fix??

David

I can process the transaction manually through authorize.net, but the website is not accepting it. I turned on logging but its not logging anything, or i cant find the log file, or i just don't know what I'm doing. When I look at the transaction using User Tracking, I can see a little bit of the error code as saying the cc is expired. I'm not sure if it means the timeout of the transaction or the credit card is expired. Can anyone help me??

[DrByte]

Yes, I'm having the same problem. Im using the Authorize.Net_aim module though. But everytime I enter my card and want to go to step 3, it just goes back to step 2. Has anyone seen this and can offer a fix??

David

I can process the transaction manually through authorize.net, but the website is not accepting it. I turned on logging but its not logging anything, or i cant find the log file, or i just don't know what I'm doing. When I look at the transaction using User Tracking, I can see a little bit of the error code as saying the cc is expired. I'm not sure if it means the timeout of the transaction or the credit card is expired. Can anyone help me??

darocket,
1. Is the customer's card being charged?
2. What version of Zen Cart are you using?
3. Is this a fresh install or an upgrade from a prior version?
4. What addons/mods/contributions have you installed?
5. What is the URL?

[darocket]

darocket,
1. Is the customer's card being charged?
2. What version of Zen Cart are you using?
3. Is this a fresh install or an upgrade from a prior version?
4. What addons/mods/contributions have you installed?
5. What is the URL?

1. No the customers card is not being charged. It seems as though authorize.net is not accepting it because it thinks the card is expired

2. I'm using 1.37

3. Its an upgrade from the prior version.

4. As far as payments modules is concern, I am using authorizenet_aim, moneyorder. I did have paypal and paypal express, but I uninstalled it to see if it will fix problem. I use SEO Urls, packager tracker, Return Authorization, Links manager, Google Analytics, As far as shipping, I use Free Shipper and ups. I have paypal instant payment notification, and I have the ability to add a tracking ID and customer in admin. I believe thats all the addons I have installed. I am currently using the future_zen theme.

5. www.your-lovely-home.com

[DrByte]

darocket,

1. Please install the updated module which I provided a link for (a couple posts above).

2. Then turn on debug logging in the module's settings.

3. Post the logs which will appear in the /cache folder. Hopefully we'll see more detailed error details there.

4. The error message *should* be displayed on the "checkout step 2" page, but if you didn't merge all the template adjustments while upgrading, you might have missed the part that does that display. Hence you're left wondering "why" you're back on that step-2 page without any details. Might be worth looking into separately.

[darocket]

darocket,

1. Please install the updated module which I provided a link for (a couple posts above).

2. Then turn on debug logging in the module's settings.

3. Post the logs which will appear in the /cache folder. Hopefully we'll see more detailed error details there.

4. The error message *should* be displayed on the "checkout step 2" page, but if you didn't merge all the template adjustments while upgrading, you might have missed the part that does that display. Hence you're left wondering "why" you're back on that step-2 page without any details. Might be worth looking into separately.

Well, I installed the module and it seems nothing has changed. The one thing I do notice is my address bar now says http://www.your-lovely-home.com/zsto...thorizenet_aim

I do have backups of my website...should I just go to a backup?? Also, I do not find any log files in my cache forlder, so maybe I really have something messed up from my upgrade?

David

[Fine Thai Decor]

hmmm I was thinking about change my Aut. to AIM ( after read suggestions on another thread )
http://www.zen-cart.com/forum/showth...dit+card+check
thought it might slove the problem.
I guess I better stay with SIM for now then [FONT="Arial"][/FONT]

[SophWise.com]

In my experience this is a classic error that happens when first setting up an Authorize.net account for use with the Authorize.net AIM Module. The problem occurs because of what is really a two-fold cause.


Incorrect Authorize.net Direct Response configuration

and/or

Incomplete Authorize.net (AIM) payment module


You either need to login to Authorize.net and make some changes to your Direct Response settings, or you need to modify your Authorize.net (AIM) payment module code. I have found that the best is to modify the payment module, as it is technically missing some lines of code that it should have when processing Authorize.net transactions.

in /includes/modules/payment/authorizenet_aim.php around line 320:

you'll find:

'x_relay_response' => 'FALSE', // AIM uses direct response, not relay response
'x_delim_data' => 'TRUE', // The default delimiter is a comma
'x_version' => '3.1',  // 3.1 is required to use CVV codes

change it to:

'x_relay_response' => 'FALSE', // AIM uses direct response, not relay response
'x_delim_data' => 'TRUE', // The default delimiter is a comma
'x_delim_char' => ',', // Force the delimiter to a comma
'x_encap_char' => '', // Force the encapsulation character to nothing
'x_version' => '3.1',  // 3.1 is required to use CVV codes

If you're only using Authorize.net with your ZenCart shop, I would also recommend you login to your Authorize.Net interface and do the following:

1. Login
2. Click on Account (top border)
3. Click on Settings (Left Border)
4. Click on "Direct Response" in the Transaction Format Settings group
5. Change Delimited Response to Yes
6. Change Default Field Separator to ",(comma)"
7. Change Field Encapsulation Character to blank/nothing (first in list)
8. Press the "Submit" button to save changes
9. You're all done!

This has to be by far the most common error my clients end up having when trying to switch to AIM on their own.

For the PHP-wise people, the error is happening because the default response that a new Authorize.Net account is returning is Quote Encapsulated, Comma Delimited

"1","1","1","This transaction has been approved.",...blahblahblah

but the Authorize.net AIM payment module is splitting it like so on line 411:

$response = split('\,', $authorize);

So on line 413 when we get the response code:

$response_code = explode(',', $response[0]);

$response_code doesn't contain just the number one, but rather 1 surrounded by the double quote encapsulation characters like so "1". So when we check for an approval on line ~427:

// DEBUG LOGGING
if ($x_response_code != '1' ||

We naturally get what looks like a decline, because "1" isn't equal to 1.

For the ZC crew, It seems like it would be best to incorporate the x_delim_char and x_encaps_char as a core change, since we don't want to rely on the default setup that Authorize.net implements.

For anyone having problems that the above info doesn't fix, well, post the debug information (obviously, with all sensitive data removed) and maybe we can figure out what's up.

HTH

[DrByte]

For the ZC crew, It seems like it would be best to incorporate the x_delim_char and x_encaps_char as a core change, since we don't want to rely on the default setup that Authorize.net implements.

This has been built-in to v1.3.8 dev code since January. You can find a pre-release version here:
http://www.zen-cart.com/forum/showpo...4&postcount=45