Problem with international credit cards

[la_stella_celeste]

We are using authorize.net for credit card capture and process. We are having international customers who are getting their card rejected with an address mismatch at the rate of at least one a day. Sometimes they contact us to work out an alternate way to pay, and sometimes they don't and we lose the sale. We also use ProPay and the transactions almost always go through ok on Propay.

Is there a module available that could collect and encrypt credit card info to pass through to us so that we could process by an alternate method (via a link that says something like 'click here if you are getting an address mismatch and you have confirmed that your address is correct)?

I know that Miva has an option to just capture the credit card number to be processed offline, so couldn't it work the same way? It seems like it could be encrypted and passed through to us and I could use a key that's only stored on my local computer to decrypt it or something.

thanks!

[CybrHost]

Re: Problem with international credit cards

The problem is there is I don't think there is any easy way for you to dynamically turn on "Credit Card with Simple Validation" if Authorize.net returns an AVS error.

Have you considered turing AVS off for all orders?

--
Thank you,
Gary Hodder
Support
--
CybrHost Corp. - http://www.cybrhost.com/ - [email protected]
+1-866-300-MIVA - Professional Miva & E-Commerce web hosting services.

[la_stella_celeste]

Re: Problem with international credit cards

Well I don't know. Does everyone else use AVS validation or not?

[CybrHost]

Re: Problem with international credit cards

I don't think there is a *perfect* AVS system and I'll bet your ProPay doesn't do any address verification. Unless you get a lot of fraudulent orders you may not need the additional security AVS provides.

--
Thank you,
Gary Hodder
Support
--
CybrHost Corp. - http://www.cybrhost.com/ - [email protected]
+1-866-300-MIVA - Professional Miva & E-Commerce web hosting services.

[d_host]

Re: Problem with international credit cards

Turning off AVS is probably not a good idea... at least for domestic orders. But, what you can do JUST for international orders is enable the Simple CC Validation option and rename all credit cards from just the card name to something that would indicate to visitors to use that option instead of the default Authorize.net options. For example, rename "Visa" to "Visa - International Orders ONLY", etc. While not bulletproof - people can still select the standard "Visa" (which would be Authorize.net), I'd guess this will solve 99% of your problems. You'll need to manually enter these transactions in Authorize.net terminal, but at least you won't lose all those sales.

[Pete McNamara]

Re: Problem with international credit cards

I am located in Australia and use an Australian credit card. I buy stuff almost daily from US stores and rarely have problems. I have found that AVS problems are generally caused when the billing address entered is not identical to the credit card billing address (i.e. the address to which the credit card statements are sent). I overcome this in stores that I build by adding notes to this effect in the ACAD, ACED and OPAY templates.

Any difference whatsover between the billing and credit card addresses generally cause problems.

FWIW.

[d_host]

Re: Problem with international credit cards

Pete,

That is just part of the problem. The bigger issue is that very few banks across country lines have agreements to share and exchange their cardholders' address info (for privacy reasons), which means most international orders do fail the AVS response. This doesn't mean the card is declined - just that the AVS response will be "XX" (no match on street address and ZIP/Postal code). It's up to the merchant to figure out if they want to take the risk of shipping the order at that point - and any potential chargebacks associated with it, or not. If the AVS doesn't match, chances are high that a dispute will result in a chargeback to the merchant, whereas if the AVS did match, the merchant would have a much higher chance of winning such a dispute.

The accept/decline is very much different from verifying the AVS or CVV2 codes. Most payment gateways also have the option to reject orders not only when the card gets declined, but also when the AVS or CVV2 doesn't match. If you place an order on sites which use this option, ie: if the merchant chooses to decline transactions where the AVS code doesn't match and your bank will not share the info with the US banks, the order will get declined - even though your card is fine and the "transaction" per se could have been 100% legitimate. It's all up to the merchant and how they have configured their payment gateway.

[ocpxc02]

Re: Problem with international credit cards

We use Authorize.net and usually find that international cards return a G or S code, which indicates the card issuer doesn't support AVS or it is an international card. We have Authorize.net set up to not decline these transactions. Instead, we accept them and manually review before shipping. Some countries and cards actually do pass AVS information, but when not supported, we usually get the G or S code vs. one of the codes indicating an actual address mismatch.


Paul