View source

==Overview==
This article explains how to set up your CV3 website to authorize credit cards online.  This allows you to catch many declined credit cards before the order is placed, reducing the burden on your customer service team to individually contact the purchasers for alternate payment information.  You will still need to capture funds within CMS.


==Configuring your site to authorize cards online==
# To begin, log into your CV3 admin.
# Expand '''Settings->Options->Payment Options->Credit Card Options'''.
# You should already have selected the credit cards you will accept.
# Click the drop-down box labeled '''Choose the type of payment gateway you would like to use''' and select your payment gateway.

This will bring up some new fields, slightly different depending on your selection:

===Authorize.net===
* '''Username (API Login ID)
* '''Transaction key'''
* '''Auth Type: ''' Select Auth only (see the section below for the reason we recommend this)
* '''Auth Full Amount? ''' Recommend selecting "Yes" here to ensure the card has enough remaining balance for the order amount.  Selecting No does a simple $1 authorization, which ensures the card is not frozen or disabled, but doesn't guarantee the funds are available.
* '''Service Location: ''' Select Authorize.net from the drop-down.

===TransFirst ePay===
* '''Account number'''
* '''Password'''
* '''Auth Type: ''' Select Auth only (see the section below for the reason we recommend this)
* '''Auth Full Amount? ''' Recommend selecting "Yes" here to ensure the card has enough remaining balance for the order amount.  Selecting No does a simple $1 authorization, which ensures the card is not frozen or disabled, but doesn't guarantee the funds are available.
* '''Accept AVS Response ''' This determines what level of AVS match you want your website to accept - full, partial, or all ("all" means you will accept any order regardless of the AVS status).  We strongly recommend you select Partial Matches or All Matches, since Exact Matches will exclude many valid results that use a different abbreviation than expected (St. vs. Street, etc.)
* '''Service Location: ''' Select "<nowiki>https://epaysecure.transfirst.com/elink/authms.asp</nowiki>" from the drop-down (the first option of the two, it may be pre-selected).

===Mercury Payment Systems===
* '''MerchantID'''
* '''Password'''
* '''Auth Type: ''' Select Auth only (see the section below for the reason we recommend this)
* '''Auth Full Amount? ''' Recommend selecting "Yes" here to ensure the card has enough remaining balance for the order amount.  Selecting No does a simple $1 authorization, which ensures the card is not frozen or disabled, but doesn't guarantee the funds are available.
* '''Environment: ''' Select "Production" (unless you are in fact still testing your site's integration with MPS, in which case you should select "Testing").

When finished, scroll to the bottom of the page and click submit.  From that point on any orders being placed on your live website will try to authorize credit cards with your processor as soon as the order is submitted.  If an error occurs, the user will redirect back to the billing page with an error message displayed at the top (this will be the error returned by your credit card processor).

==Auth Only vs. Auth/Capture==
We generally recommend that authorize on the web and capture within CMS, rather than having the website do both.  Capturing the funds within CMS allows you to issue refunds directly to the card from within CMS; if you have captured the funds on your website and just downloaded the order with the completed transaction, any refunds will need to be issued from your processor's website.