restaurant enterprise series army/air force exchange ... · configuring the driver 5. select the...

Restaurant Enterprise Series

Army/Air Force Exchange System (AAFES) Driver for 3700 POSVersion 4.9

May 2, 2011

Copyright 2004-2011by MICROS Systems, Inc.Columbia, MD USAAll Rights Reserved

MD0003-073

AAFES Credit Card Driver for 3700 POS ii

Declarations

WarrantiesAlthough the best efforts are made to ensure that the information in this document is complete and correct, MICROS Systems, Inc. makes no warranty of any kind with regard to this material, including but not limited to the implied warranties of marketability and fitness for a particular purpose.

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information recording and retrieval systems, for any purpose other than for personal use, without the express written permission of MICROS Systems, Inc.

MICROS Systems, Inc. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this document.

Trademarks FrameMaker is a registered trademark of Adobe Corporation.

Microsoft, Microsoft Excel, Win32, Windows, Windows95, Windows 2000 (Win2K), and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S. and/or other countries.

Visio is a registered trademark of Visio Corporation.

All other trademarks are the property of their respective owners.

Installation and Setup

AAFES Credit Car

This section contains installation and setup instructions for the Version 4.9.21.2310 release of the Army/Air Force Exchange System (AAFES) Credit Card Driver. The release version is available on the MICROS web site Product Support page.

Before installing this driver, please familiarize yourself with the changes by reviewing the ReadMe First Section of this document.

This version of the AAFES may be used on RES systems running Version 4.3 Hotfix 1 or higher.

In This Section...

• Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4• Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 4• Files Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4• Installation Instructions . . . . . . . . . . . . . . . . . . . . . 5• Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . 5

• Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7• Configuring the Driver . . . . . . . . . . . . . . . . . . . . . 7• Configuration for the Co-branded Feature . . . . . . 13

• Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18• OpenSSL License . . . . . . . . . . . . . . . . . . . . . . . . . 18• SSLeay License . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

d Driver for 3700 POS 3

AAFES Credit

InstallationSite Requirements

Installation

Site Requirements

Before installing the AAFES Credit Card Driver on the RES system, the following configuration items should be considered:

• The installed version of RES Version 4.3 HF1 or higher. If using co-branded credit cards, RES Version 4.3 HF1 is required.

• If using co-branded, the Settle-to-File (STF) Driver Version 4.9.21.2310 or higher.

Files Included

The AAFES driver contains both an authorization driver and a settlement driver. The AAFES driver is installed by running the CaAAFA(4.9.21.2310).exe file. This executable will install the following files:

On the RES Server:

• \Micros\RES\POS\Bin\CaAAFA.dll

• \Micros\RES\POS\etc\CaAAFA.cfg

• \Micros\RES\POS\Bin\CaAAFA.hlp

• \Micros\RES\POS\Bin\CaAAFA.cnt

• \Micros\Res\Common\Bin\libeay32.dll

• \Micros\Res\Common\Bin\ssleay32.dll

On Win32 Clients:

• \CAL\Win32\Files\Micros\Res\Pos\Bin\CaAAFA.dll

• \CAL\Win32\Files\Micros\Res\Pos\Bin\CaAAFA.hlp

• \CAL\Win32\Files\Micros\Res\Pos\Bin\CaAAFA.cnt

• \CAL\Win32\Files\Micros\Res\Pos\Bin\libeay32.dll

• \CAL\Win32\Files\Micros\Res\Pos\Bin\ssleay32.dll

• \CAL\Win32\Files\Micros\Res\Pos\Etc\CaAAFA.cfg

All logging is recorded to the MicrosCaAAFAInstall.log file located on the root Micros Windows directory.

Card Driver for 3700 POS 4

AAFES Credit

InstallationBefore You Begin

Before You Begin

Before you begin installation make sure that you have the following information available. This information can be obtained by contacting your credit card processor:

• Facility Number.

• Host IP Address. The IP address and port of the primary host connection to be used for authorization requests If using

Installation Instructions

The installation of the credit card driver is now separate from the RES software. After each installation of RES software — whether it is a general release, service pack, or hotfix — you MUST re-install the site’s requisite credit card drivers.

1. Make sure all current batches have been settled. MICROS recommends installing a new driver before the site opens for the day. This will ensure that all CA/EDC transactions have been settled to their current version.

2. Shutdown all MICROS applications from the MICROS Control Panel.

3. Download the AAFA(4.9.21.2310).exe file from the MICROS Member Services web site. Copy this file to your RES Server’s temp folder.

4. Double-click the AAFA(4.9.21.2310).exe file. This will install the following files:

• AAFES Driver Dynamic Link Library (CaAAFA.dll)

• AAFES Driver Site Configuration File (CaAAFA.cfg)

• AAFES Driver POS Configurator Help Files (CaAAFA.hlp, CaAAFA.cnt)

• Support files for SSL Communications (ssleay32.dll, libeay32.dll)


AAFES Credit

InstallationInstallation Instructions

4.9.21.2310These files will be installed in the following locations:

On the RES Server:

• \Micros\RES\POS\Bin\CaAAFA.dll

• \Micros\RES\POS\etc\CaAAFA.cfg

• \Micros\RES\POS\Bin\CaAAFA.hlp

• \Micros\RES\POS\Bin\CaAAFA.cnt

• \Micros\Res\Common\Bin\libeay32.dll

• \Micros\Res\Common\Bin\ssleay32.dll

On Win32 Clients:

• \CAL\Win32\Files\Micros\Res\Pos\Bin\CaAAFA.dll

• \CAL\Win32\Files\Micros\Res\Pos\Bin\CaAAFA.hlp

• \CAL\Win32\Files\Micros\Res\Pos\Bin\CaAAFA.cnt

• \CAL\Win32\Files\Micros\Res\Pos\Bin\libeay32.dll

• \CAL\Win32\Files\Micros\Res\Pos\Bin\ssleay32.dll

• \CAL\Win32\Files\Micros\Res\Pos\Etc\CaAAFA.cfg

5. Install the Settle-to-File (STF) Driver:

• Download the CaSTF(4.9.21.2310).zip file from the MICROS Member Services web site.

• Unzip the CaSTF(4.9.21.2310).zip file to a Temp folder on the RES Server.

• Copy the files to the following locations:

Copy the CaSTF.dll file to the \MICROS\RES\POS\BIN folder.

Copy the CaSTF.hlp file to the \MICROS\RES\POS\BIN folder.

Copy the CaSTF.cnt file to the \MICROS\RES\POS\BIN folder.

Copy the CaSTF.cfg file to the \MICROS\RES\POS\ETC folder.

6. Turn on the RES system from the MICROS Control Panel. The AAFES driver is now installed on your system.


AAFES Credit

SetupConfiguring the Driver

Setup

Configuring the Driver

Follow the steps below to configure the CaAAFES Credit Card Driver:

1. Go to the POS Configurator | Devices | Ca/EDC Drivers form.

2. Select the blue plus sign to add a record.

3. Enter a descriptor for this new record in the Name field.

4. Enter the appropriate code associated with this driver in the Driver Code field (e.g., AAFA).


AAFES Credit


5. Select the System tab and configure the following fields:

• Authorization Device – Complete this step if you are using a modem for primary or fallback authorizations. If you are unsure of the device number, go to the command prompt in the \3700\bin directory and enter settle –m. The following sample message will display:

Device [1]: Boca 28.8 Kbps V.34 MV.34EDevice [2]: Standard 1200bps ModemDevice [3]: Standard 2400 bps ModemSelect the appropriate device number.

• Use SSL – To enable the encrypted SSL connection, enter a value of 1. If a TCP/IP connection type is used, enter a value of 0. This field will default to 0.

• Port Arbitration Enabled– Enabling this field will prevent communication errors by testing port availability before attempting an authorization request. Select 1 to enable this feature.


AAFES Credit


• Local Credit/STAR Floor Limit – Enter the maximum credit card amount that may be authorized on-site without requiring approval from the credit card service.

This is a non-decimal numeric field (the decimal point is implied). For example, a $25.00 limit would be entered as 2500. The default setting is 2500.

• Local Personal Check Floor Limit – Enter the maximum amount that may be authorized on-site for a personal check without requiring approval from the bank service.

This is a non-decimal numeric field (the decimal point is implied). For example, a $25.00 limit would be entered as 2500. The default setting is 2500.

• Military Star Tender. Use this field to determine the object number/ record number associated with the Military Star tender. Refer to the object number associated with the Military Star Tender found on the POS Configurator | Sales | Tender/Media tab. This option is required if the co-branded feature is used.

• Host IP Address: Port – Enter the IP address and port of the primary host connection to be used for authorization requests.

Note Local authorization is used when there is a failure to achieve a connection or proper processing by an online host. In local authorizations, if the request amount is below or equal to the floor limit, then the driver will automatically approve the authorization. If the amount is above the limit, an error will be reposted and the authorization will not be processed.


AAFES Credit


6. Go to the Merchant | Authorization tab and complete the following field:

• Facility Number – Enter the numeric identifier associated with the location. This number will be assigned by the credit card processor. If multiple merchants are entered, a separate Facility Number must be identified for each.


AAFES Credit


7. Go to the Merchant | RVC tab and verify that all Revenue Centers appear under the first merchant. If more than one merchant is needed (e.g., the multi-merchant feature), click the blue plus sign and enter the second Merchant Name. Delete any RVCs that need to be assigned to the second merchant from the first merchant’s record.

Once this is complete, click on the blue plus sign to add all of the revenue centers needed for the second merchant.:

8. Save all changes.


AAFES Credit


9. Go to the POS Configurator | Sales | Tender/Media | Credit Auth tab.

Go to the following fields and select AAFA from the drop down box:

• CA Driver

• EDC Driver

10. Save the record and bring the MICROS Control panel back to Front-of-House status. CA/EDC should be operational. A few test transactions should be done to ensure all is working correctly. Test connections option is located on the Micros Applications | POS | Credit Card Batch | Diagnostics tab.


AAFES Credit

SetupConfiguration for the Co-branded Feature

Configuration for the Co-branded Feature

If the co-branded feature is used, the user must configure the following options in POS Configurator:

• Co-branded Credit Card (Sales | Tender/Media | CC Tender). Enable this option if the selected tender is a co-branded credit card. This option is required to used a co-branded credit card.


AAFES Credit


• The Allow Partial Authorization (Sales | Tender/Media | Credit Auth | Authorization) option must be enabled for the Master Card tender.


AAFES Credit


Optionally, the following additional features may be turned on but are not required:

• Always Prompt for Co-branded (Revenue Center | RVC Credit Cards | General). When enabled, POS Operations will always circumvent the standard co-branded credit card sequence by prompting the operator for the co-branded Master Card and will bypass the Military Star Card.


AAFES Credit


• Override Co-branded Credit Card (Employees | Employee Classes | Transactions | Transaction Control). By default, the credit card driver will charge one account first (e.g., Military Star account), until the available balance is exhausted. This option allows a privileged employee class to override this default, and to apply the total to a second account before the first account is exhausted.

If this option is enabled, a separate Master Card Tender Key must be configured on the Payment screen. This key is needed to allow a privileged user to force the authorization onto the Master Card.

Follow these steps to add this key:

1. Open POS Configurator | Devices | Touchscreen Designer and select the Payment screen.

2. Add a new Master Card Tender key (e.g., Override Co-branded).

3. Use the Category drop-down to select Tender/Media Number.


AAFES Credit


4. Use the Tender Media drop-down to select Master Card.

5. Save all changes.

Refer to page 22 for additional information as well as use cases for using Co-branded credit cards.


AAFES Credit

LicensesConfiguration for the Co-branded Feature

Licenses

This driver is subject to the following license agreements:

• OpenSSL License

• SSLeay license

The terms of both licenses are listed below:

OpenSSL License

Open Source licenses. In case of any license issues related to OpenSSL please contact [email protected].

Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/).”

4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

“This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)”


AAFES Credit


THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT “AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected]).

SSLeay License

Copyright (C) 1995-1998 Eric Young ([email protected]). All rights reserved.

This package is an SSL implementation written by Eric Young ([email protected]). The implementation was written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson ([email protected]).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of condi-tions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.


AAFES Credit


3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes cryptographic software written by Eric Young ([email protected]).” The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-).

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:

“This product includes software written by Tim Hudson ([email protected]).”

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The licence and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]


ReadMe First – V 4.9.21.2310

AAFES Credit Car

This section contains a comprehensive guide to the new features, enhancements, and revisions included in the Version 4.9.21.2310 release of the Army/Air Force Exchange System (AAFES) Credit Card Driver.

In This Section...

• What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22• Detailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

• What’s Enhanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

• What’s Revised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24


AAFES Credit

What’s NewNew Features Summarized

What’s New

A new feature is defined as one that provides capabilities that were not available in previous versions of the application.

New Features Summarized

There table below lists the new features present in this release.

New Features Detailed

Support For Multiple Authorization Requests Added

The AAFES driver now supports multiple authorization requests simultaneously.

Feature PageSupport For Multiple Authorization Requests Added 22


AAFES Credit

What’s EnhancedEnhancements Summarized

What’s Enhanced

An enhancement is defined as a change made to improve or extend the current functionality. To qualify as an enhancement, the change must satisfy the following criteria:

• The basic feature or functionality already exists in the previous release of the software.

• The change adds to or extends the current process. This differs from a revision (i.e., a bug fix) which corrects a problem not caught in previous versions.

Enhancements Summarized

There are no enhancements in this release.


AAFES Credit

What’s RevisedRevisions Summarized

What’s Revised

A revision is defined as a correction made to any existing form, feature, or function currently resident in the AAFES driver. To qualify as a revision, the change must satisfy the following criteria:

• The basic form, feature, or functionality must be a part of the previous version of the software.

• The change must replace or repair the current item or remove it from the applica-tion.

Revisions Summarized

There are no revisions in this release.



AAFES Credit Car


In This Section...

• What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26


• What’s Revised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28• Detailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29


AAFES Credit


What’s New



There are no new features in this release.


AAFES Credit


What’s Enhanced





There are no enhancements in this release.


AAFES Credit


What’s Revised





The following table summarizes the revisions included in this version:

Feature CR ID # PageDebit Reversal Would Fail to Hold if the Credit Card Processor was Unavailable

29843 29

Credit Card Service Could Lock if Three or More Requests are Sent to the Driver

30071 29


AAFES Credit

What’s RevisedRevisions Detailed

Revisions Detailed

Debit Reversals Would Fail to Hold if the Credit Card Processor was UnavailableCR ID #: 29843

Previously, the CaAAFA driver would fail hold debit reversals if the credit card processor was unavailable. This occurred because the encrypted reversals.txt would be replaced if multiple debit reversals were in queue. This has been corrected.

Credit Card Service Could Lock if Three or More Requests are Sent to the DriverCR ID #: 30071

Previously, if three or more request are simultaneously being sent to the driver, the credit card service locks the request list. This could cause authorizations to fail to trigger until the next request is made in the queue. This has been corrected.



AAFES Credit Car


In This Section...





AAFES Credit


What’s New





AAFES Driver Installed Using an Executable File

The AAFES driver is now installed using the CaAAFES(4.6.19.1796).exe file. For new installation instructions, see the Installation section of this document on page 3.

Added Support for SSL Communications

With this release, the AAFES credit card driver will now support an encrypted SSL connection over TCP/IP.

To support this functionality the Use SSL option has been added to the POS Configurator | Devices | CA/EDC | System tab. To enable the encrypted SSL connection, enter a value of 1. If standard TCP/IP Communications Protocol method is used, enter a value of 0. This field will default to 0.

When enabled, the AAFES driver uses SSL to open a connection to the credit card host, and keeps the connection open, rather than closing the connection after the conclusion of each transaction.

Support Added for Co-branded Credit Cards

With this release, RES supports co-branded credit cards. A co-branded credit card is associated with two different accounts, providing the customer with additional flexibility when using their card. With a co-branded credit card, the customer can:

Feature PageAAFES Driver Installed Using an Executable File 31Support Added for SSL Communications 31Support Added for Co-branded Credit Cards 31


AAFES Credit

What’s NewNew Features Detailed

• Select between the two associated accounts at the time of the transaction.

• Draw funds from both accounts during the course of a single transaction. For example, if the funds in one account are exhausted, the remaining amount can be charged to the second account.

When the operator tenders a check, they will select the Auth ‘N Pay (e.g., Credit Card Tender key) and swipe the co-branded card. Once the card is swiped, the system will automatically recognize the credit card as a co-branded card. This recognition applies only to Auth ‘N Pay transactions. A co-branded card will not be recognized when used for pre-authorizations and initial authorizations.

Currently, this feature is only supported by the AAFES credit card driver using a Co-branded MasterCard account. By default, the AAFES driver will charge the Military Star account first, until the available balance is exhausted. If desired, an authorized employee may override this default setting, and apply the entire amount against the customer’s MasterCard account.

RequirementsThe following software must be installed on the MICROS RES Sever in order to use the co-branded feature:

• MICROS RES Version 4.3 HF1 or higher.

• AAFES Credit Card Driver Version 4.6.19/1796 or higher.

• Settle-to-File (STF) Driver Version 4.6.19.1796 or higher.

Using the FeatureThis section contains several cases describing scenarios where a co-branded card is used. To use this feature, the following two options must be enabled in the POS Configurator:

• Co-branded Credit Card (Sales | Tender/Media | CC Tender).

• Allow Partial Authorization (Sales | Tender/Media | Credit Auth | Authorization) must be enabled for the MasterCard tender.


AAFES Credit


• Use Case 1

The available balance on the Military Star account is $100, the transaction amount is $25. The card is swiped which means that OPS sees the account as a MasterCard account. The AAFES driver recognizes the account as a co-branded account and formats the auth request as a Military Star request using the MasterCard account number. The AAFES host approves the authori-zation for $25 so the driver sends back an approval and includes the object number of the Military Star tender. OPS overrides the tender type in the origi-nal auth request and posts the Military Star tender to the check.

• Use Case 2

The available balance on the Military Star account is $10, the transaction amount is $25. The card is swiped which means that OPS sees the account as a MasterCard account. The AAFES driver recognizes the account as a co-branded account and formats the auth request as a Military Star request using the MasterCard account number. The AAFES host approves the transac-tion for $10. The driver returns the approval to OPS which includes the amount of the approval and the Military Star object number in the response. OPS posts the Military Star tender for $10 to the check and prompts the employee to apply the remainder to the MasterCard account. If the employee agrees, OPS sends a second auth request to the driver for $15 with a flag set to force the driver to process the request as a MasterCard. The driver formats the auth request as a MasterCard request which the AAFES host approves. OPS applies the $15 MasterCard tender to the check.

• Use Case 3

The customer insists that the transaction be put through as a MasterCard trans-action rather than a Military Star transaction. A manager who is authorized to override the normal co-branded processing uses a co-branded tender key which prompts with Force processing as MasterCard?. After the manager confirms that the transaction should be processed as a MasterCard transaction POS Operations will send the authorization request to the driver with a flag set to force the driver to process the request as a MasterCard. After the driver approves the auth request POS Operations sets a flag in the auth detail indicat-ing that the default co-branded logic was overridden. This flag appears on the credit card settlement report and is similar to the flags for manually keyed account numbers and manual authorizations.


AAFES Credit


• Use Case 4

A credit card is swiped and POS Operations sends the authorization request but the AAFES host declines the transaction for any reason other than the bal-ance available on the Military Star account. Because the card is co-branded POS Operations prompts the employee to apply the full transaction amount to the MasterCard account. If the employee agrees the auth request is send again with the flag set to force the driver to process the request as a MasterCard. Because the transaction was first attempted as a Military Star transaction the employee is not required to be privileged to override the co-branded process-ing and the authorization is not flagged as having been overridden.

• Use Case 5

The site elects to require that all co-branded cards prompt with the Force pro-cessing as MasterCard? prompt. A revenue center option changes the behav-ior of the Auth N’ Pay (CC Lookup) key so that MasterCard tenders will prompt. Employees must have the privilege to override co-branded credit card processing set or have the transaction approved by a manager if they elect to force the card to be processed as a MasterCard tender.

Contingencies

If the network is down and the transaction amount is under the programmed local floor limit, the transaction will be locally approved and will default to the Military Star tender, not the MasterCard tender.

This will not apply to a Manual Override situation. If the transaction is a forced MasterCard transaction (e.g., the override functionality is used) then the local authorization will not alter the tender type and the payment will be made to the MasterCard tender.

Configuration

To support this feature, the following options have been added to POS Configurator. This section describes the location and functionality for each:

• Co-branded Credit Card (Sales | Tender/Media | CC Tender). Enable this option if the selected tender is a co-branded credit card. This option is required to used a co-branded credit card.

• The Allow Partial Authorization (Sales | Tender/Media | Credit Auth | Authorization) option must be enabled for the Master Card tender.


AAFES Credit


The following are optional:

• Override Co-branded Credit Card (Employees | Employee Classes | Transactions | Transaction Control). By default, the credit card driver will charge one account first (e.g., Military Star account), until the available balance is exhausted. This option allows a privileged employee class to override this default, and to apply the total to a second account before the first account is exhausted.

• Always Prompt for Co-branded (Revenue Center | RVC Credit Cards | General). When enabled, POS Operations will always circumvent the standard co-branded credit card sequence by prompting the operator for the co-branded Master Card and will bypass the Military Star Card.


AAFES Credit


If a co-branded transaction is overridden, then an O will be recorded in the Credit Card Batch Detail Report under the column Flags. This flag will appear any time that the default processing for a co-branded credit card is overridden by an employee.

Note A legend has been added to the Credit Card Batch Detail Report. This legend lists the following flags:

• U/D = Omitted by (U)ser/(D)river

• K = Keyed Account Entry (This flag has been changed. In the past it was listed as “M”).

• A = Manual Auth

• F = Floor Limit Auth

• S = Settled

• C = Cash Back

• O = Co-branded Override

• R = Corrective Auth


AAFES Credit


Additionally, a line will print on the credit card voucher indicating that the co-branded transaction was overridden.


AAFES Credit


What’s Enhanced





The following table summarizes the enhancements included in this version:

Enhancements Detailed

AAFES Driver Supports New Discover Credit Card Numbers

This release of the AAFES driver supports the following new Discover credit card number ranges:

Feature PageAAFES Driver Supports New Discover Credit Card Numbers 38

Start End62212600 62292599644000 644999650000 659999


AAFES Credit


What’s Revised






Revisions Detailed

CaAAFA Driver Caused the Credit Card Server to Fault Unexpectedly When an Authorization was Declined by the Host ProcessorCR ID #: N/A

Previously, the CaAAFA driver received a decline response from the Host Processor, the Credit Card Server (CCS) would fault unexpectedly. This has been corrected.

Feature CR ID # PageCaAAFA Driver Caused the Credit Card Server to Fault Unexpectedly When an Authorization was Declined by the Host Processor

N/A 39



AAFES Credit Car


In This Section...





AAFES Credit


What’s New




Feature PageMulti-Merchant Enabled 42Support Added for RES 4.0 Logging 43


AAFES Credit



Multi-Merchant Enabled

The AAFES driver now supports the creation of multiple merchants. Use this feature to configure a different record for each of the merchants associated with the POS system. This can be used for accounting and reporting purposes.

For example, the Mike Rose Cafe has three revenue centers: a restaurant, a bar, and a retail outlet for baked goods. All three revenue centers accept credit cards and all three operate via the same POS system. The Cafe has created three separate Merchant IDs, one for each revenue center.

Creating different Merchant IDs will provide separate accounting statements for each revenue center. Additionally, the retail revenue center may be subject to lower transaction fees since this center does not need to process tips. MICROS recommends that you discuss the advantages od multiple merchants with your bank representative,.

To enable this feature go to the Devices | CA/EDC Drivers section in POS Configurator and add the desired merchants. Enter the assigned Facility Number for each merchant.

For additional information on this feature see the RES 3700 Online Feature Reference Manual.


AAFES Credit


Support Added for RES 4.0 Logging

With this release, support has been added for RES 4.0 logging. Credit card driver messages will be logged in the 3700d.log file.


AAFES Credit


What’s Enhanced





There are no enhancements included in this release.


AAFES Credit


What’s Revised






Feature CR ID # PageAAFES Driver Logging Improperly N/A 46AAFES Driver Not Logging to the 3700d.log Based on the Credit Card Server Verbosity Settings

N/A 46

Change Error Message that Appears When the Driver Cannot Connect to the Host

N/A 46

Driver Logging Customer Card Information for Credit, Debit Reversals and Gift Cards

N/A 46

A Debit Transaction Will Record Full Track Data and the Card Number in the AAFES Reversal Text File

N/A 46

Unable to Handle PINPad Serial Numbers with Greater than 16 Digits

N/A 47


AAFES Credit


Revisions Detailed

AAFES Driver Logging ImproperlyCR ID #: N/A

The previous version of the AAFES Credit Card Driver was logging all information about the driver when verbosity was set to 0. Detailed messages were being sent to the 3700d.log and not to the individual driver logs. This issue has been corrected.

AAFES Driver Not Logging to the 3700d.log Based on the Credit Card Server Verbosity SettingsCR ID #: N/A

The AAFES driver was not logging to the 3700d.log file based on the configured verbosity settings in the MICROS Control Panel. The driver will now use either the credit card server verbosity settings from the Control Panel, or the driver specific verbosity level, whichever is higher.

Change Error Message that Appears When the System Cannot Connect to the HostCR ID #: N/A

Previously, the error message that displayed when the driver could not connect to the Host was “Socket Not Connected.” This message has been changed to make it easier to understand the nature of the error condition. Now, when the driver cannot connect to the host the user will receive the error message “Cannot Connect to Host.”

Driver Logging Customer Card Information for Credit, Debit Reversals and Gift CardsCR ID #: N/A

After running a credit, debit reversal, or gift card, the 3700d.log would contain sensitive customer card information when the verbosity was set to 0. This has been corrected.

A Debit Reversal Would Record Full Track Data and the Card Number in the AAFES Reversal Text FileCR ID #: N/A

Performing a debit reversal would record the full track data and the customer’s card number in the AAFESReversal.txt file. This information is now encrypted and cannot be viewed.


AAFES Credit


Unable to Handle PINPads with Serial Numbers Greater than 16 DigitsCR ID #: N/A

Previously, the AAFES driver was unable to handle PINPads with serial numbers greater than 16 digits. Now the serial number length can be either 16 or 20 digits.



AAFES Credit Car


In This Section...

• What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

• What’s Enhanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50• Detailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

• What’s Revised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51• Summarized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51


AAFES Credit


What’s New



There are no new features in this release.


AAFES Credit


What’s Enhanced


• The basic feature or functionality already exists in the previous release of the soft-ware.



The following table summarizes the enhancements included in this version:

Enhancements Detailed

Support for Gift Card Voids

The credit card driver was modified to support processing of gift card voids. The changes allow the driver to:

• Accept and return transaction numbers to and from the client.

• Use the same transaction number for both the original and void transactions.

Feature PageSupport for Gift Card Voids 50


AAFES Credit

What’s RevisionsRevisions Summarized

What’s Revisions





There are no revisions in this release.


restaurant enterprise series army/air force exchange ... · configuring the driver 5. select the...

Documents