Authorize.net - One card works.. another doesn't?

Hello.

I've been trying to get a site up and running using Authorize.net for card processing. I had initially run into the difficulty outlined in another post (who's link I can't find right now) - wherein all attempts to charge something resulted in a 'transaction declined' error.

After grabbing the latest version of the aim payment module, and sending my CC through it without issue (on the live server no less), I thought my problem had been fixed.

Alas, it has been reported that my client's credit card is not being accepted. Nor is another of my CC...

So... any idea why Authorize.net would accept 1 credit card, but not all credit cards (all are Mastercards) ???

Any help would be very much appreciated.

Make sure your AuthorizeNet account is configured to for the right Credit Cards ...

Also make sure that Zen Cart is configured for the right Credit Cards in the Tools ... Credit Cards ...

If all the cards are the same type and one went through but the other didn't you may have to readjust your security settings on Authorize. I actually talked with a representative that talked me through it.
I was having problems with all international cards being declined on the first day. I found that I had to loosen the "security grip" so to speak. There are some address and identity verification procedures that American banks have in place that a lot of international banks don't. So even if their address actually matches, if their bank doesn't participate in that particular verification procedure then it may be declined on your end if your settings are set to "deny if.....". There are A LOT of different settings that I didn't know about until I talked to the rep at Authorize.net. He even walked me through the basics of my account. I learned a lot, I HIGHLY recommend taking the time to call Authorize.net if you have any questions.
I still have sporadic problems (seems mostly canadians now) but 99% of the time I'm fine. AND now I know what I'm looking at and how to find certain info on my Authorize.net account; like why the card was declined, there are different codes for different reasons, you can pinpoint your problem better that way.

Thanks for the replies.

I'll check on the authorize.net security settings. I don't know if that's the cause however, because the declined transactions aren't even showing up in the ZC database log... which I'm assuming they would if the response from Authorize.net was parsed correctly?

Or does this error message occur when an unknown error type is sent in the reply? Or perhaps if the communication with AN fails in the first place?

You will see no record of an order in zencart unless it was processed successfully (either successful credit card, or successful paypal, or by checking check/moneyorder option if you're offering that).
Only when zencart gets confirmation of a payment (or pending payment if moneyorder) will it record as a successfully placed order.

You need to find out why exactly it was declined. You can find a letter code next to the specific transaction in your authorize.net account that will tell you for what reason it was declined. If you don't know how to look that up you should definitely call them!

The problem is... the transaction isn't showing up on authorize.net at all.

Let me be more specific.

1st card (mastercard): Enter info, processes correctly.

2nd card (mastercard): Enter info, get 'transaction declined' but it does not show up on authorize.net and is not in the authorize.net transaction log table in ZC

3rd card (discover): Enter info, get different 'transaction declined' error message, this time from authorize.net (is in the log and on an's admin panel). This is correct because account is not set up to accept Discover

So.. its almost like that second card is not even being sent to authorize.net, but is being declined by ZC. I had another person test a 4th card, and they also had the same thing happen.

The question is, why?

Again, I appreciate your help thus far.

What are the first 6 digits of these cards, and how many digits long is the whole number?

If you turn on the basic "Credit Card" payment module and try these cards through that, are they accepted or rejected?

Dr. Byte,

They're all 16 digits.. Running the card through the basic CC module works fine..
I see there are a few posts about this error and AN.. i was trying to avoid diving into the code to try to find some sort of answer (or at least eliminate some things).. but i guess i won't be so lucky :)

i'll let you know if i discover anything.

Revisiting the logging, I found that the transactions were getting to AN, and were being given decline error #2, which according to their documentation and their support is a 'general decline' (with no description of what the heck happened).

Support suggested through e-mail that the problem was that my credit card provider had declined the transaction (due to insufficient funds)... I've written AN back to tell them how ridiculous that is.

So.. could be the security settings. Unfortunately my client doesn't feel comfortable giving me their AN login (because AN told them not to give it to anybody).. so, I have to somehow get them to check their settings.. :)

Will report back to assist others should they suffer the same fate.

The codes I get on transaction declines are letters not numbers and will signify specifically things like Address not matching, or zip not matching....etc.

aerodynamic_elephant:

Revisiting the logging, I found that the transactions were getting to AN, and were being given decline error #2, which according to their documentation and their support is a 'general decline' (with no description of what the heck happened).

Support suggested through e-mail that the problem was that my credit card provider had declined the transaction (due to insufficient funds)... I've written AN back to tell them how ridiculous that is.

So.. could be the security settings. Unfortunately my client doesn't feel comfortable giving me their AN login (because AN told them not to give it to anybody).. so, I have to somehow get them to check their settings.. :)

Will report back to assist others should they suffer the same fate.

At least you're headed in the right direction. The key is that the decline is coming from the gateway somehow. That means it's at least getting out there. And, as you said, it's likely the bank that's doing the decline, or it could be security settings too tight in the account.

Stormshade:

The codes I get on transaction declines are letters not numbers and will signify specifically things like Address not matching, or zip not matching....etc.

Those would be AVS feedback details. Useful when checking for fraudulent activity. AVS failures don't always trigger a decline upon failure ... that depends on the bank and your gateway settings. It would be good to check the AVS results in the failed transactions mentioned in the earlier post.

So.. its a little embarassing.. but it turns out my bank had LOCKED my credit card due to a prior online transaction i had made (without bothering to tell me about it). I didn't find this out until I called them to ask about the declines (just in case) and they asked me to verify that purchase.

End result - it was working in the first place, but thanks to my bank not communicating with me, i spent hours troubleshooting a non-issue.

:oops:

Thanks for your help regardless - its good to know there are people out there ready and able to assist.

Silly ol' banks ... :smartalec:

Lots of fun when testing and you hit limits that do not autoexpire based on number of transactions ...

That's why we pay banks the big bucks to handle our money ... :rolleyes: