Address Verification User Guide

Transcription

1 Address Verification User Guide

2 Table of Contents Introduction Retail AVS MOTO AVS MOTO AVS at Point of Sale MOTO AVS Setup... 7 Page 2

3 Introduction Address Verification Service (AVS) is designed for businesses that process credit card sales where the customer, and the credit card, is not physically present when making a purchase. This includes sales such as Mail Order and Telephone Order (also known as MOTO) sales. Mail and telephone orders have a much higher risk of a chargeback due to fraud. AVS helps minimize fraud and reduce risk on card-not-present transactions but keep in mind that chargebacks can still occur. AVS requests additional customer address and card information for manually keyed card numbers and those values are passed on to the processor. An AVS response code is returned by the processor and allows the clerk to proceed or not proceed with the transaction accordingly. AVS validates that the customer is the legitimate and authorized card holder by verifying the billing address against the card information provided. A response code indicates if the AVS data is an exact match, a partial match, or not a match at all. AVS transactions request an AVS response code and a Card Verification (CV) response code. The CV code (the three-digit number printed on the back of a bank card) further ensures that the consumer actually has the credit card in their possession, because the CV code is not included in the embossed account number or in the magnetic stripe data. If the authorization request is approved, it is up to the merchant to evaluate the AVS and CV response codes and decide whether or not to proceed with the transaction. It is important to note that using AVS for a transaction does not provide protection for a chargeback; rather, it is a tool for assessing the risk of fraud, giving you a greater level of confidence when deciding whether or not to complete a card-not-present transaction. The topics in this guide cover two types of AVS: Retail AVS and MOTO AVS. Retail AVS Retail AVS is available to all Eagle for Windows users, and is helpful when a customer is in the store purchasing goods, but their bank card cannot be scanned. The clerk is required to enter zip code information before the transaction can proceed, and can optionally enter the CV code. This additional information is sent to the processor along with the transaction data; however, the zip and CV code are NOT verified with Retail AVS. The benefit of Retail AVS is a reduction in processing fees for non-scanned transactions. Page 3

4 MOTO AVS With MOTO AVS a manually keyed card must be tested prior to completing the transaction. When a card is tested and it comes back approved and if the AVS and CV responses are acceptable, the transaction can be completed. If the AVS/CV responses are not acceptable the clerk must enter another card or obtain a manager override to complete the transaction. MOTO AVS is a purchase option for some other bankcard gateways and providers but Epicor Payment Exchange users may utilize this feature for no additional cost. 1 Retail AVS Of the two types of address verification, Retail AVS is easier to use and requires much less setup and less field entry at point of sale. Setup is easy; simply make sure that option 8292 is set to R. Note that this option defaults as a System option, but the kept by field can be changed so that some terminals can use Retail AVS and others, that take phone orders, can use MOTO AVS. When a card is manually entered at Point of sale a zip code must be provided and optionally a CV (card value code) can be entered. The cashier will see no response at point of sale and the sale will not be prevented due to an invalid zip code or card value code. However, by using this feature the interchange charged on the transaction will be slightly lower. Retail AVS and a required zip code is used only for manually keyed card numbers. Swiped cards will not prompt for the zip code. An additional window, illustrated below, displays after entering the card number. You must provide the Expiration Month, Expiration Year and the Zip Code. Note: Leave the Authorization Code field blank! Any value entered in the authorization code field, other than a valid authorization code, may result in a chargeback. The Card Value Code field is optional, but we recommend that you enter the card value whenever possible. The card value is the 3 digit code on the back of a Visa, MasterCard or Discover Card and the 4 digit un-embossed number on the front of an American Express card. Page 4

5 After entering the required information click OK or enter to process the card. At POS there will be no response indicating whether the zip code and card value code matched. Even with incorrect entries, the card may be approved. Once again, with retail AVS, the transaction is not stopped or prevented if invalid entries are made for the zip code or card value code. However, lower transaction rates will apply by providing a zip code; whether or not the zip code matches. 2 MOTO AVS MOTO AVS requires a little more effort to set up and to use at Point of Sale. MOTO AVS can prevent a transaction from being processed if the address and card value information do not match, depending on how you construct the response table. Let s first take a look at how MOTO AVS works and then we ll discuss the setup steps. Eagle s MOTO/AVS runs a total of 4 validations or tests; 1. The card account is open and valid. 2. Proper CVV code 3. Address matches the customer account 4. Zip code matches the customer account 2.1 MOTO AVS at Point of Sale Like retail AVS, you begin with a manual entry of a credit card. After entering the card number on the totals screen, the Pay by Bankcard window displays just as it does with Retail AVS. You must provide the required information and while the card value code may not be required on this screen, it must be provided on the following AVS test window. When the required fields are completed, click OK to continue Clicking the OK button on the information window, shown at right, will initiate the test and display the Credit Card Test window. An AVS test may not be required each time a card is keyed, if a card has been successfully tested within the number of days indicated in option 8295 there will be no prompt for an AVS Test Page 5

6 The information keyed on the Pay By Bankcard window will carry over to the Credit Card Test window, but even if previously entered, the card value code will have to be re-entered. Make sure to record the card holder name, and address. After pressing Enter or clicking OK, the house number, zip code and card value code will be compared to the information on file at the issuing bank. Response codes from the processor are compared to 2 tables in the Eagle; the Address Verification Table and the Card Value table. The tables include action codes for each processor response and those action codes can prevent a transaction from being completed as shown here. The AVS Test Response displays. Card Account Test indicates only that the card account is open and valid. In the example shown at right, the Address Verification Response indicates a partial match. Click OK to continue. The response results for AVS, address verification, and Card Value or CV, are now at the bottom of the Credit Card Test window. Corrected values may be entered and then retested, or the cashier can select Cancel to attempt a different card number or obtain a Manager Override. A Manager Override can only be performed by a user with security bit 798 set to Yes. The Manager Override Required window displays. Select OK and another window displays in which a user with security bit 798 must enter their username and password to continue. Page 6

7 Following a successful AVS test, an information window displays. Selecting OK on this window will return the cashier to the totals screen in AVS Credit Card Tender Mode. Just press Enter to submit the transaction for bankcard processing. Normally the transaction will be approved and completed, but it is possible for a decline to occur for reasons other than invalid address and card value information. Once a card has successfully passed an AVS test, a new test will not be required for the number of days indicated in option MOTO AVS Setup As indicated earlier, setting up MOTO AVS requires a few additional steps compared to Retail AVS. An Epicor Advice Line or Training Team member must set Option 8291 to Yes. When that is accomplished you can set option 8292 to M, indicating you are using the MOTO or full address and card value checking ability of the Eagle. Options 8293 and 8294 require that tables that are constructed with processor responses and action codes that you specify. A combination of response and action codes is built in the table for each card type. You will see an example in the pages below. Option 8295 indicates the number of days for which an AVS test is valid. This is typically set to 3-7 days. And finally option 3355 allows you to record alerts for AVS overrides. Address verification or AVS response codes and Card Value response codes are set up in two independent tables. Response codes may differ by processor and indicate the validity of the data you submit. For each response code and each card type you can determine whether the transaction should be allowed to proceed. These actions are indicated in each of the 2 tables for each response code and card type. Page 7

8 Security bit 798 allows complete override of the AVS test, and security bit 797 is required for the ability to perform an AVS test. In the Address Verification table you will record response codes for the house number and zip code. Along with each response code and card type you will need to determine if invoicing is allowed by selecting A or if corrections are required by selecting C. You may wish to obtain a list of current AVS response codes from the web and compare to your table. Remember that codes may differ by card type. Here are a few helpful sites: Armed with the current response codes, you can access the Address Verification table by going to the Misc Menu on the Options Configuration screen. Select button X to access the table. The Address Verification Table may already be populated with existing values, but you should compare each of those to the AVS Response list. To change an existing code, card type, message or POS Response, just click on the line and then select F5- Change. After making the change in the Address Verification Code window, click OK. To add a new code, choose F4-Add, make the appropriate entries and then click OK. Response codes are required for all card types. Select POS Response code A if you want to allow the transaction based on the processor s response. Choose POS Response code C to stop the transaction based on the processor s response. When your table is complete, compare it to the processor s response codes. Page 8

9 When you complete your edits and additions make sure to select F6-Save at the top of the tool bar and when the Save View screen displays choose the Save button as shown on the slide. We recommend that you retain the default name of Address Verification for your table. Enter the table s name in Option 8293 and click Save. The Card Value response code table is built following similar steps as the Address Verification table. It requires card value codes from your processor and also allows you to specify a POS response code for each processor code. Card Value response codes are returned by the processor and interpreted by a table built on the Eagle. Each response code can be set as; A Invoicing Allowed C Corrective Action Required Obtain a list of Card Value response codes from your processor From the options configurations window, select button Y from the Misc Menu. Like the Address Verification table, the Card Value table may already be populated with existing values. You should compare each value to those on the CV Response list provided by your processor. To change an existing code, card type, message or POS Response, just click on the line and then select F5- Change. After making the change in the Card Verification window, click OK. To add a new code, choose F4-Add, make the appropriate entries and then click OK. Response codes are required for all card types. Select POS Response code A if you want to allow the transaction based on the processor s response. Choose POS Response code C to stop the transaction based on the processor s response. When your table is complete, compare it to the processor s response codes. Page 9

10 When you complete your edits and additions make sure to select F6-Save at the top of the tool bar and when the Save View screen displays choose the Save button as shown on the slide. We recommend that you retain the default name of Card Verification for your table. Make sure to enter the description of the Card Value table in option 8294 and click Save. Security must be provided to cashiers for access to the AVS test. Set security bit 797 to Yes for all individuals that should be granted access. Managers or key individuals should have bit 798 set to yes if they are allowed to override a failed AVS test. When users with bit 798 manually enter a card, they will find that the AVS test screen will not display. Instead the transaction will process immediately after entering the required information. Users with Security bit 798 may access the AVS Test from the Totals Menu, that s the Menu button on the toolbar at the top of the Totals window. Select Button U and enter the card information. Page 10