AShop V ユーザーガイド

Credit card fraud can be a nuisance and can indirectly damage your credit. Credit card issuing banks
and organizations have developed security devices to prevent unauthorized use of credit cards. Not all
banks support all security devices and not all payment processors or payment gateways support them.
This help topic is not intended to be a comprehensive coverage of credit card fraud prevention, only some
notes about what we have experienced and what works for us.

It seems that the security codes and address verfication (below) have inherent limitations. For instance,
once the security code is given out, it is likely to be pirated along with the credit card number and
expiration date. Address verification is not supported by all banks and fails often when PO boxes or ATM
Visas are submitted. A new and very effective solution is 

The 3-digit CVV2 security code can be found on the back of most US issued credit cards.

Requiring a security code match reduces exposure to fraud. The drawback is that most non-US issued
credit cards don't support it. Depending on your business location and where your customers are, this
may not be an option. For US merchants selling mostly to US customers, it is highly effective. An
alternative payment option, such as the offline credit card processing option can be used in conjunction
with the real time gateway in order to accommodate cards that do not support the security code.

Authorize.Net Security Code Settings
Login to the 

Under Security, click Card Code Verification
Check the boxes to activate code check conditions. Check all of them for the highest level of security. If
you find that cards are rejected too often, look at the rejection code to evaluate how it is working and
adjust accordingly for your customer base.