AbleCommerce Shopping Cart Software

We're getting some orders where the auth failed.

For all of these, the CVV and AVS codes come back as n/a.

Everything else looks fine as far as billing and shipping address goes.

Our next step is to contact the customer to try and work out the problem.

Can anyone tell me what "n/a" for CVV and AVS means? Or is the best thing just to tell them their card was rejected?

Thanks.

I'm not sure if this is the same problem, but we're using Skipjack and apparently after some system upgrade, they now require a phone number (like some of the other gateways that are in AC by default). So, if the customer doesn't provide one, the authorization fails.

I did talk to support about this and they said the checkout page has been fixed for the next release (whenever that is) or you could just edit the checkout page to require the phone number, whichever is easier ...

Hopefully that helps!

Mike

We ended up making the phone required. We need it anyways to help when there's an order problem.

That's what we're doing, as well. You go live and then find plenty of things to spend your time with.

N/A is used differently based on the gateway.

With PayPal login-style payments, it means not-applicable as in there is no CVV or AVS possible since it's a PayPal-authenticated payment.

For my Authorize.Net, I'm seeing it most often with AmEx payments. I'm having a real pain getting certain AmEx cards to pass AVS even when the customer swears the information matches their card statement. Especially happens when the AmEx card is partner-issued (local bank) instead of issued from AmEx themselves. Or when the customer has alternate addresses configured for their AmEx card.

AC7 needs an AVS override switch on payment Auth/Capture so I don't have to keep logging into the gateway website to temporarily turn off AVS when I want to ignore AVS for a particular payment.

Why do you have to turn off AVS to do the capture? If we get a partial AVS match, we're still getting an authorization. We then call the customer to work it out, then capture the funds. The AVS partial match hasn't prevented us from doing the capture.

Is there something we're missing there?

A partial AVS will authorize/capture.

But some of these AmEx cards won't even get a partial AVS - system responds like there was no match at all and my Authorize.net setup is configured to decline a full AVS failure.

With Authorize.net, you can configure the exact rules you want applied to the AVS accept or decline policy.

I do get some legitimate international charge card orders, but many international charge card issuers do not support AVS at all and will fail an AVS check every time.