Download - APTRA Edge Release 2.03 Remote Configuration Guide

NCR APTRA™ EDGE Release 02.03.xx

Remote Configuration Guide

June 20, 2007

B001-0000-0114

The product described in this book is a licensed product of NCR Corporation.

APTRA™ is a trademark of NCR Corporation.

Windows and Windows XP are registered trademarks of Microsoft Corporation.

It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and firmware become available. NCR, therefore, reserves the right to change specifications without prior notice.

All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your NCR representative or NCR office for information that is applicable and current.

To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and value of this book.

Address correspondence to: Americas Professional Services Group NCR Corporation 1700 S. Patterson Blvd. Dayton, Ohio 45479

This document and information is the property of NCR Corporation. Any unauthorized use or reproduction is prohibited. Copyright © 2005-2007, NCR Corporation. All rights reserved.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE TABLE OF CONTENTS

June 20, 2007 NCR Confidential i

Table of Contents

1 Introduction..................................................................................................1

1.1 What Can Be Changed Remotely?............................................1 1.2 How Are Things Changed Remotely?........................................1

2 Making Changes Using the Screen/Keyboard Data Load Message ........3

2.1 Sample Modifications ..................................................................5 2.2 Commonly Modified Data Dictionary Entries .............................8 2.2.1 Modify the Transaction Set .......................................................12 2.2.1.1 Activate/Deactivate Transactions .............................................12 2.2.1.2 Modify Sub-Menus ....................................................................16 2.2.1.3 Modify Transaction Account Selections ...................................17 2.2.1.4 Modify Unique Main Menu Banners and Instruction Text .......21 2.2.1.5 Modify FAST CASH Settings....................................................22 2.2.2 Modify the Consumer Flow Options .........................................24 2.2.2.1 Modify Transaction Flow Based on FIT Value.........................25 2.2.2.2 Modify Surcharge Options ........................................................26 2.2.2.3 Modify the Stamp Options.........................................................27 2.2.2.4 Modify the Receipt Options.......................................................29 2.2.2.5 Modify the Envelope Dispense Option.....................................30 2.2.2.6 Modify the Card Reader Options..............................................31 2.2.2.7 Change the Language Option and Menus...............................32 2.2.2.8 Modify Voice Guidance Option .................................................34 2.2.2.9 Enable/Disable APTRA Promote..............................................35 2.2.2.10 Change Advertising Image and Message Options .............35 2.3 Modify the Currency Cassette Values......................................37 2.4 Modify Fee Values.....................................................................38 2.5 Modify Personalization ..............................................................39 2.5.1 Personalization Transaction Main Menu Button ......................40 2.5.2 CRMService Group Entry .........................................................40 2.5.3 CONSUMERFLOW Group Entries ..........................................41 2.6 Convert from Envelope Deposit to Enhanced Deposit............44 2.6.1 BNA Group.................................................................................44 2.6.2 CASHDEPOSIT Group .............................................................45


ii NCR Confidential June 20, 2007

2.6.3 CHECK Group .......................................................................... 45 2.6.4 CHECKDEPOSIT Group.......................................................... 46 2.6.5 CONSUMERFLOW Group ...................................................... 47 2.6.5.1 Disable Envelope Transactions ............................................... 47 2.6.5.2 Enable and Configure Enhanced Deposits............................. 47 2.6.6 NDCPROXYCUSTOMIZTION Group..................................... 49 2.6.7 STARTOFDAY Group.............................................................. 49 2.6.8 SUPERVISOR Group............................................................... 51 2.7 Controlling Deposit Disclaimers............................................... 53 2.8 Controlling the Paper Journal................................................... 53 2.9 Configuring a Forced Account Balance Transaction .............. 54 2.9.1 Define Your FITs and Menus................................................... 54 2.9.1.1 Data Dictionary FIT Entries ...................................................... 55 2.9.1.2 Data Dictionary Menu Setup Entries ....................................... 55 2.9.2 Forced Account Balance Screen Text and Voice Guidance................................................................................... 56 2.9.3 Define Your Button Labels ....................................................... 56

3 Data Dictionary Entries by Transaction Cross-Reference.......................58

3.1 Account Balance Inquiry........................................................... 58 3.2 Change PIN............................................................................... 58 3.3 Check Reorder.......................................................................... 59 3.4 Deposit with Cash Back ........................................................... 59 3.5 Electronic Payment................................................................... 59 3.6 Enhanced Deposit .................................................................... 60 3.7 Envelope Deposit...................................................................... 61 3.8 Envelope Payment ................................................................... 62 3.9 Envelope Payment From Account........................................... 62 3.10 Envelope Payment To Account ............................................... 62 3.11 Fast Cash.................................................................................. 63 3.12 Full Statement........................................................................... 64 3.13 Message to Bank...................................................................... 64 3.14 Mini Statement .......................................................................... 65 3.15 Personalized Fast Cash ........................................................... 65 3.16 Purchase Stamps ..................................................................... 66 3.17 Split Deposit .............................................................................. 66 3.18 Transfer ..................................................................................... 67


June 20, 2007 NCR Confidential iii

3.19 Withdrawal .................................................................................67 3.20 Settlement..................................................................................68 3.21 Supervisor..................................................................................69

4 Making Changes Using Software Distribution .........................................70

4.1 Change the Screen Graphics ...................................................70 4.1.1 Modify the Screen Appearance ................................................71 4.1.2 Replace the Advertising Files....................................................71 4.1.3 Change the Animation Files......................................................72 4.2 Change the Screen Text ...........................................................74 4.2.1 Modify the Text ..........................................................................74 4.2.2 Modify the Stylesheets ..............................................................75

5 Electronic Journal Information ..................................................................77

5.1 EJ Cutover and Backup ............................................................77 5.2 EJ Content .................................................................................78 5.3 Configuring the EJ File ..............................................................80 5.3.1 Data Dictionary Entries..............................................................81 5.3.1.1 Journal Contents Entries...........................................................81 5.3.1.2 EJ Cutover and Backup Entries................................................81 5.3.1.3 Journal Upload Entry.................................................................82

6 Retrieving Archive Files on Demand........................................................83

7 Host Configuration Items Not to Change .................................................85

A Screen / Keyboard Data Load Message..................................................86

B Data Dictionary..........................................................................................88

B.1 Data Dictionary Entries..............................................................88 7.1.1 ALLTRANSACTIONS Group....................................................88 B.1.1 APPMANAGEMENT Group .....................................................89 B.1.2 BNA Group.................................................................................89 B.1.3 CAMERA Group ........................................................................89 B.1.4 CASHDEPOSIT Group .............................................................90 B.1.5 CHECK Group ...........................................................................90 B.1.6 CHECKDEPOSIT Group ..........................................................91 B.1.7 COMX Group.............................................................................91


iv NCR Confidential June 20, 2007

B.1.8 CONSUMERFLOW Group ...................................................... 92 B.1.9 CRMSERVICE Group ............................................................ 139 B.1.10 CURRENCY Group................................................................ 139 B.1.11 CURRENCYEXPONENT Group........................................... 140 B.1.12 CUTOVER Group................................................................... 140 B.1.13 DEPOSIT Group..................................................................... 141 B.1.14 EJUPLOAD Group.................................................................. 141 B.1.15 EVENTLOG Group................................................................. 141 B.1.16 FASTCASH Group ................................................................. 142 B.1.17 GLOBAL Group ...................................................................... 143 B.1.18 JOURNAL Group.................................................................... 143 B.1.19 MACHINE Group.................................................................... 144 B.1.20 NDCBS.................................................................................... 144 B.1.21 NDCPROXY Group................................................................ 144 B.1.22 NDCPROXYCUSTOMIZATION Group ................................ 145 B.1.23 RCPT_CONFIG Group .......................................................... 147 B.1.24 SESSIONFLOW Group.......................................................... 147 B.1.25 STARTOFDAY Group............................................................ 147 B.1.26 STATEMENT.......................................................................... 158 B.1.27 SUPERVISOR Group............................................................. 158 B.1.28 SUPJRN Group ...................................................................... 164 B.1.29 SUPGENERICACTIVITY Group ........................................... 165 B.1.30 SUPSETTLEMENT Group..................................................... 165 B.1.31 TOTAL Group ......................................................................... 165 B.1.32 TRACE Group......................................................................... 166 B.1.33 VDM Group ............................................................................. 167 B.1.34 WITHDRAWAL Group............................................................ 167 B.2 Sample Data Dictionary.......................................................... 168

C APTRA Edge XML Files .........................................................................178

C.1 ButtonToKeyMap.xml............................................................. 179 C.1.1 File Format .............................................................................. 179 C.2 Coupon.xml............................................................................. 181 C.2.1 File Format .............................................................................. 181 C.3 Journal.xml.............................................................................. 183 C.3.1 File Format .............................................................................. 184


June 20, 2007 NCR Confidential v

C.4 Receipt.xml ............................................................................. 188 C.4.1 File Format .............................................................................. 188 C.5 SoundXXX.xml ....................................................................... 192 C.5.1 File Format .............................................................................. 193

D Onscreen Text Language Files ..............................................................197

D.1 Entry Formats ......................................................................... 197 D.2 Variable References and Messages ..................................... 198 D.3 Transaction Name Messages (9000-9099) .......................... 198 D.4 Language Selection Button Messages (1000-1039)............ 199 D.5 Button Messages (1040-1089) .............................................. 200 D.6 Welcome Screen Messages (1090-1099) ............................ 201 D.7 Out Of Service Screen Messages (2000) ............................. 201 D.8 Card Not Read Screen Messages (2001-2010)................... 201 D.9 End Session Screen Messages (2011-2016)....................... 202 D.10 Check Captured Messages (2135-2139).............................. 203 D.11 Enter/ReEnter PIN Messages (2020-2021).......................... 203 D.12 Another Transaction Messages (2030-2039) ....................... 204 D.13 Fee Messages (2040-2042)................................................... 205 D.14 Enter Amount Messages (2050-2059) .................................. 205 D.15 Select Language Message (2060) ....................................... 206 D.16 Receipt Messages (2070-2079) ............................................ 206 D.17 Main Menu 1 Messages and Banners (2080-2081)............. 207 D.18 Transaction Menu Messages (2082-2089)........................... 207 D.19 Please Wait Message (2090-2091)....................................... 208 D.20 More Time Message (2100-2109)......................................... 208 D.21 Account Selection Messages (2110-2119) .......................... 208 D.22 Take Cash Messages (2120-2129)....................................... 209 D.23 Card Captured Message (2130-2134) .................................. 209 D.24 Transaction Not Available Message (2140-2149) ................ 209 D.25 Balance Inquiry Messages (2150-2159) ............................... 209 D.26 Stamp Transaction Messages (2160-2169).......................... 210 D.27 Envelope Deposit Messages (2170-2189)........................... 210 D.28 Statement Messages (2190-2209)........................................ 210 D.29 Deposit with Cash Back Deposit Messages (2210-2219).... 211 D.30 Enhanced Deposit Transaction Messages (2220-2329)..... 211


vi NCR Confidential June 20, 2007

D.31 PIN Change Transaction Messages (2330-2339)................ 212 D.32 Cancel Please Wait Message (2340).................................... 213 D.33 Take Card Message (2350) ................................................... 213 D.34 Check Reorder Messages (2360).......................................... 213 D.35 Envelope Dispense Messages (2450-2499)......................... 213 D.36 Personalization Messages (2500 to 2599)............................ 213 D.37 Deposit Disclaimer.................................................................. 214 D.38 Non-Transaction Main Menu Button Text Messages (5000-5999)............................................................................. 214 D.39 Account Selection Button Text Messages (6000-6999)....... 215 D.40 Unique Consumer Flow Messages (7000-7999).................. 216 D.41 Denial Code Text Messages (000-999) ................................ 216

E Enhanced Deposit Check Endorsement Printing ..................................217

E.1 Printable Characters............................................................... 217 E.2 Defining the Endorsement Data Print Position...................... 217 E.3 Single Line Endorser .............................................................. 218 E.4 Multiple Line Endorser............................................................ 218 E.4.1 Print Zones.............................................................................. 219 E.4.1.1 Zone 1 ..................................................................................... 219 E.4.1.2 Zone 2 ..................................................................................... 219

F Index........................................................................................................220

NCR APTRA EDGE REMOTE CONFIGURATION GUIDE REVISION RECORD

June 20, 2007 NCR Confidential vii

Revision Record

Revision Date Description

1.0 September 16, 2005 Initial Issue Changes since 2.02.05 issue: • Added CONSUMERFLOW.ENVELOPEDEPOSIT[2-3]

entries on pages 8, 12 and 97. • Added Check Reorder transaction on pages 8, 12 and 89. • Added Split Deposit transaction on pages 8, 14, 112. • Added CONSUMERFLOW.DISPLAYSURCHARGE

PERTRANS on pages 37 and 92. • Added section on Controlling the Paper Journal on page 52. • Added cross-reference of data dictionary items by transaction

on pages 53 through 64. • Added information on alternate journal format (in US NDC+

format) and cutover and backup information on page 72. • Updated information on COMMANDLINEEOD on page 76. • Added CONSUMERFLOW.BALANCExNAME1 on page

87. • Expanded explanation of CONSUMERFLOW.CHECKDEN

OMINATIONOPTION on page 89. • Added CONSUMERFLOW.DISPENSERAVAILABLE on

page 91. • Re-added CONSUMERFLOW.ELECTRONICPAYMENT

FROMACCOUNTS. Entry was removed by mistake. • Changed CONSUMERFLOW.ENVDISPENSE value No to

None. • Added CONSUMERFLOW.NEXTSTATEENDSESSION

VALUE on page 114 • Added CONSUMERFLOW.NUMBEROFBALANCE on

page 114. • Added CONSUMERFLOW.SUBACCOUNTSFORACC

OUNTx on pages 114 and 124. • Added SUPERVISOR.CONTINUEPROCEDURE on page

120. • Added CONSUMERFLOW.WITHDRAWALFIXED

AMOUNT on page 129. • Re-added CONSUMERFLOW.TRANSFERFROMACCOU

NTS. Entry was removed by mistake. • Added CURRENCY.REJECTBINMAXIMUMBILLS on

page 131. • Added CURRENCYEXPONENT.USD on page 131.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE REVISION RECORD

viii NCR Confidential June 20, 2007


• Added NDCBS group on page 135. • Added NDCPROXY.CBWITHDRAWALAMOUNT on page

135. • Added NDCPROXYCUSTOMIZATION.AMOUNT on page

136. • Added NDCPROXYCUSTOMIZATION PIN Change-related

entries on pages 136 and 137. • Added SESSIONFLOW.READRAWDATA on page 138. • Moved SNMP group entries to SUPERVISOR group. • Added STARTOFDAY.ACCOUNTSERVICECOMMS

PROGID on page 138. • Added STARTOFDAY.APPMGTREPORTDEPOSITLENG

THERROR on page 139. • Added STARTOFDAY.ARCHIVEDAYSTORERETAIN on

page 139. • Added STARTOFDAY.CHECKREORDERPROGID and

STARTOFDAY.CHECKREORDERTRANSLETID on page 140.

• Added STARTOFDAY.JOURNALTXODATA on page 144. • Added STARTOFDAY.PRINTIMMEDIATEPROGID on

page 146. • Added new Translet IDs for PIN Change transaction in page

146. • Added STARTOFDAY.PRINTDEPOSITTOTAL on page

146. • Added STARTOFDAY.SCREENDOWNLOADPROGID on

page 147. • Expanded explanations for

SUPERVISOR.DISPLAYCANISTERTYPEHOST and SUPERVISOR.DISPLAYCANISTERTYPELOCAL.

• Added SUPERVISOR.DISPLAYADMINCARDDATA entry on page 150.

• Added SUPERVISOR.DNSIPCONFIGURATION on page 150.

• Added SUPERVISOR.FORMATARRAYSIZE on page 151. • Added SUPERVISOR.KEYEXCHANGETIMEOUT on page

151. • Expanded explanation of SUPERVISOR.TRACK2 and

SUPERVISOR.TRACK2FORMAT. • Removed SUPERVISOR.NETSHFILEPATH,

SUPERVISOR.WAITFORKEYEXCHANGE and STARTOFDAY.PAPERJOURNAL entries. They are no

NCR APTRA EDGE REMOTE CONFIGURATION GUIDE REVISION RECORD

June 20, 2007 NCR Confidential ix


longer used. • Added SUPERVISOR.MODESWTIMEOUT on page 152. • Added SUPJRN group on page 155. • Added additional Totals counter entries on page 156. • Added VDM.DONECOUNT on page 158. • Corrected CDWithdrawalTransletID. • Added note that FIT0 Fast Cash menu amount are used if no

Fast Cash menu amounts are defined for a FIT. • Updated sample data dictionary on pages 159. • Refreshed contents of all XML and JS files in document.

1.1 November 15, 2005 Added information on Card-based Fast Cash on pages 12 and 21. Added information on configuring advertising on the Spanish Please Wait screen on pages 34 through 36. Data Dictionary updates: • Added CASHDEPOSIT.JOURNALNOTES on page 83. • Added CHECK.REARIMAGEARCHIVEDIR on page 83. • Added CONSUMERFLOW.CARDFASTCASH on page 88. • Added CONSUMERFLOW.DENIALENDSESSION on page

90. • Added CONSUMERFLOW.IMAGEWAITSPA on page 107. • Added CONSUMERFLOW.SETTLEMENTMENU on page

121. • Added NDCPROXY.CBDEPOSITAMOUNT and

NDCPROXY.CBWITHDRAWALAMOUNT on page 136. • Added

STARTOFDAY.CHECKCASHDESPENSERBEFOREEX ECUTE on page 140.

• Added STARTOFDAY.CHECKENVELOPEDEPOSITORYBEFOREEXECUTE on page 141.

• Added STARTOFDAY.PURCHASE1TRANSLETID on page 146.

• Added SUPERVISOR.ATMCONFIGFILELOCATION on page 149.

• Added SUPERVISOR.PROXYCONFIGFILELOCATION on page 153.

1.2 January 11, 2006 Corrected number of Mini Statements and Full Statements supported throughout (mini – 10, full – 8). Added Forced Account Balance transaction configuration on pages 53-56. Added CONSUMERFLOW.PRIMARYMAINMENU data

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE REVISION RECORD

x NCR Confidential June 20, 2007


dictionary entry on page 124. Added Check Print Zone information on Appendix E starting on page 214.

1.3 January 23, 2006 Changed default values for CHECKDEPOSIT.SENDUNSOLICITEDMESSAGE and CASHDEPOSIT.SENDUNSOLICITEDMESSAGE from True to False on pages 44, 45, 87 and 88. Removed NDCPROXYCUSTOMIZATION.TransactionNameFEE from table of commonly modified dd entries on page 10. This entry is not used. Corrected a variety of typographical errors throughout.

1.4 March 6, 2006 Enhanced introduction and description of XMLUpdate program on pages 1-8 (basic information remained the same). Corrected ProgID name for EJ in OS/2 format on page 149. Correct data dictionary entry is: STARTOFDAY.EJDATAFORMATTERPROGID= NDCBSRec FrmtrNoTag.EJRcrFormater

1.5 June 20, 2007 • Changed all <XML_Update> samples to include substitution characters where necessary on pages 6 and 7.

• Updated Electronic Journal information on pages 77-82. • Changed all translet ID names to uppercase throughout

document.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE INTRODUCTION

June 20, 2007 NCR Confidential 1

1 Introduction

This document describes the methods for modifying the NCR APTRA Edge ATM software from a remote location. This document is written for network or bank personnel who are responsible for making configuration changes to the ATMs. It is assumed the reader of this document is familiar with APTRA Edge. Refer to the following documents for information on APTRA Edge:

APTRA Edge Standard Base Product Information

APTRA Edge Architecture Overview

APTRA Edge Customer Release Bulletin

1.1 What Can Be Changed Remotely?

Within the APTRA Edge product, the Consumer Flow automatically controls many of the daily operational conditions that a network used to have to control remotely in the US NDC+ environment. Examples of these include:

changing the withdrawal multiple when a canister runs out of money

changing the receipt option message displayed to the customer when the receipt printer is not operational

inactivating a transaction when a required piece of hardware has become non-operational

verifying entered amounts. Since the network application doesn’t need to control these operational conditions anymore, the question becomes, “What can, or needs to be, changed remotely?” There are many configuration options a host can change remotely. Some networks download to their ATMs all of the Consumer Flow operational parameters each time a new ATM is installed. Other networks download only the things that need to be changed on an occasional basis, such as the price of stamps displayed on the Purchase Stamps screen when the cost of stamps changes.

The amount of remote control a network imposes upon their APTRA Edge ATMs depends upon the network’s operational and business practices. Over time the download practices of a network will probably change and mature as the network becomes more familiar with APTRA Edge.

1.2 How Are Things Changed Remotely?

There are two ways to modify an APTRA Edge ATM's configuration remotely:

using a screen/keyboard data load message , or

using software distribution. Screen/keyboard data load messages should be very familiar to most NDC+ users. These messages are used to make small, simple changes. Software distribution, however, allows you to make much larger modifications, replacing all the software on an ATM, if desired. Using the screen/keyboard data load message is the more commonly used method of the two.

NCR APTRA EDGE REMOTE CONFIGURATION GUIDE INTRODUCTION

2 NCR Confidential June 20, 2007

Through the screen/keyboard data load message, you can update the following APTRA Edge configuration elements:

data dictionary (dd.dat) entries

XML files entries (selected files only) Most configuration information you will be interested in modifying resides in the data dictionary. The data dictionary is a configuration file on the ATM that controls many aspects of its operation. A complete list of all data dictionary entries is included in the Data Dictionary section in this document.

Keep in mind, however, that not all entries in the data dictionary should be modified. Some are "reserved" entries used by APTRA Edge and modifying these can produce unexpected results, or cause the ATM to become non-operational. These reserved entries are noted in the Data Dictionary section in this document.

In addition to the data dictionary, there are a number of XML files you may want to update remotely as your business and operational practices become more refined and mature within the APTRA Edge environment. These files contain information such as the audio instructions for voice guided transactions, and the definitions of the information recorded on the journal and receipts.

You need to decide what data you want to change remotely for your particular implementation of APTRA Edge. The remainder of this document explains in detail the information you can change remotely, and provides guidelines on changing it.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE MAKING CHANGES USING THE SCREEN/KEYBOARD DATA LOAD MESSAGE


2 Making Changes Using the Screen/Keyboard Data Load Message

Data dictionary and XML file updates are normally not large messages; therefore, the screen/keyboard data load message is well suited to this use. If you are not familiar with a screen/keyboard data load message, the screen number cited in the message can be any unused screen. The maximum length of the message is 2000 bytes, but this length is further decreased depending upon which communication protocol is in use. A brief description of the message is included in this document in Appendix A. Detailed information is available in the NDC+ Programmers Reference Manual (B006-2486-xxxx).

The download data in the screen/keyboard data load message must be transmitted as a nested block of commands starting with <CONFIGURATION_DATA> and ending with </CONFIGURATION_DATA>.

Some data dictionary updates and all XML file updates require a reboot. The data dictionary entries that require a reboot are identified in the Data Dictionary section in this document. Further, all updates to any CONSUMERFLOW group entries in the data dictionary require that the data dictionary be re-read. This can be accomplished by sending a go out of service command followed by a go in service command to the ATM after the update.

If the ATM should be rebooted after the update, the initial <CONFIGURATION_DATA> command must include reboot=”y” as indicated in the samples that follows this description.

Other nested commands can be inserted between the starting and ending <CONFIGURATION_DATA> commands as long as the complete <CONFIGURATION_DATA> block can be contained in a single message. Additional Screen/Keyboard Data Load messages can be transmitted from the host, but the data within each message must begin with <CONFIGURATION_DATA> and end with </CONFIGURATION_DATA>.

The configuration data can include two types of updates:

dd.dat Updates any of the values in the dd.dat file.

Each set of values must be contained in a block of data starting with <DD_UPDATE> and ending with </DD_UPDATE>. If you have multiple dd entries to update, you will have multiple sets of <DD_UPDATE> and </DD_UPDATE>.

Each value must specify the <GROUP>, <NAME>, and <VALUE> as shown below.

An update for the entry CONSUMERFLOW.FASTCASH1=YES,1,1 would be formatted:

<GROUP>CONSUMERFLOW</GROUP> <NAME>FASTCASH1</NAME> <VALUE>YES,1,1</VALUE>

Incorrect entries, invalid entries or typos will be ignored and no warning will be given that this has occurred. These types of errors could also cause



unpredictable results.

*.xml Updates any of the values in an .xml file. A reboot is required when an .xml file is updated. Updateable files and their default locations are included in the following list. These default locations can be changed through entries in the data dictionary or cross-file references, so you need to be aware if the defaults are not being used (see the APTRA Edge XML Files section of this document for more information on locating these files).

It is recommended that you do not update any xml files other than the ones that appear in this list.

ButtonToKeyMap.xml - c:\Webatm\WebPages\scripts Coupon.xml- c:\Webatm Journal.xml - c:\Webatm Receipt.xml - c:\Webatm SoundENG.xml - c:\Webatm SoundSPA.xml - c:\Webatm

Values must be contained in a block of data starting with <XML_UPDATE> and ending with </XML_UPDATE>. You must include in the initial XML_UPDATE command the complete path and filename of the .xml file to be changed.

It must be followed by an <XMLUpdate> block including a nested <Update> block, <Insert> block, or <Delete> block as shown in the samples following this description.

Update works as a replace. Insert is an insert after and inserts your entry at the same level as the path. If

you have multiple lines to insert at the same level with the same tag, you need to do multiple, separate updates or your updates will overwrite each other and you will only get the last one you sent.

Delete deletes an entry.

Following the opening <Update>, <Insert> or <Delete>, you must include a <NodeKey> node that contains the structure of the XML you are changing. Within this node, you must identify the structure of the XML as <Path>, the Attribute you are changing as <AttributeName> and the specific value you are changing as <Value>.

Finally, you must include within an <XML> node with the new value, or literal, you want to add.

You must send a Go In Service command after your update to see your changes. Detailed descriptions of the most commonly updated data dictionary entries are included in the next several sections of this document. All of the data dictionary entries are included in the Data Dictionary section in this document.

The APTRA Edge XML Files section of this document contains detailed information on the updatable XML files.



NOTE: some special characters can cause an update to fail. These include &, ", ', < and >. If you need to include these characters in any update, whether DD_UPATE or XML_UPDATE, substitute the following:

& ampersand (&) " double quote (") ' apostrophe (') < less than (<) > greater than (>)

2.1 Sample Modifications

This section contains a variety of sample modifications involving both of the update types.

The first example shows three modifications. Since reboot="y" is indicated with the CONFIGURATION_DATA in this sample, the ATM will be rebooted when the changes are complete.

The first two changes affect the dd.dat file and are surrounded with <DD_UPDATE> and </DD_UPDATE>.

The first change to dd.dat adds/updates the following line in the file which updates the location of the Envelope Deposit transaction on the menus:

CONSUMERFLOW.ENVELOPEDEPOSIT =YES,1,1

The second change to dd.dat adds/updates the following line in the file which updates the location of the Envelope Payment transaction on the menus:

CONSUMERFLOW.ENVELOPEPAYMENT=YES,1,8

<CONFIGURATION_DATA reboot=”y”> <DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>ENVELOPEDEPOSIT</NAME> <VALUE>YES,1,1</VALUE> </DD_UPDATE> <DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>ENVELOPEPAYMENT</NAME> <VALUE>YES,1,8</VALUE> </DD_UPDATE>

The final change updates the ButtonToKeyMap.xml file in the c:\WebATM\WebPages\scripts directory. This particular updates the ButtonToKeyMap.xml file in the c:\Webatm\WebPages\Scripts directory, specifically updating the FDK key settings in the file.

ENVELOPEDEPOSIT =YES,1,1

ENVELOPEPAYMENT =YES,1,8



<XML_UPDATE filename="c:\Webatm\WebPages\scripts\ButtonToKeyMap.xml">

<XMLUpdate> <Update> <NodeKey> <Path>Document/FDKKey</Path> </NodeKey> <XML> <FDKKeyMap Button="1" FDKKey="1"/>

<FDKKeyMap Button="2" FDKKey="2"/>







</XML> </Update> </XMLUpdate> </XML_UPDATE> </CONFIGURATION_DATA>

The following example shows the update necessary for a short menu that applies only to FIT2. Since these particular changes to the Consumer Flow group do not need a reboot, the reboot command is not included with the CONFIGURATION_DATA tag. Note, however, that the ATM must always go out of and then back in service so that the data dictionary will be re-read after an update that contains changes to the CONSUMERFLOW group.

<CONFIGURATION_DATA> <DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>FIT2WITHDRAWAL</NAME> <VALUE>YES,1,1</VALUE> </DD_UPDATE> <DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>FIT2DEPOSITWITHCASHBACK</NAME> <VALUE>YES,1,2</VALUE> </DD_UPDATE> <DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>FIT2ENVELOPEDEPOSIT</NAME> <VALUE>YES,1,3</VALUE> </DD_UPDATE> <DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>FIT2STAMP</NAME> <VALUE>YES,1,4</VALUE> </DD_UPDATE>

FIT2WITHDRAWAL=YES,1,1

FIT2ENVELOPEDEPOSIT=YES,1,3

FIT2DEPOSITWITHCASHBACK=YES,1,2

FIT2STAMP=YES,1,4

XML code that changes the

FDKKEY Settings

Specifies the node path to the change area within the file

Specifies the full path of the XML

file to update



<DD_UPDATE> <GROUP>CONSUMERFLOW</GROUP> <NAME>FIT2ENVELOPEPAYMENT</NAME> <VALUE>YES,1,5</VALUE> </DD_UPDATE> </CONFIGURATION_DATA> This example shows an update to the SoundENG.xml file. This update slightly changing the audio instructions voiced at the PIN Entry screen. Since all updates to XML files need a reboot, reboot="y" is included here.

<CONFIGURATION_DATA reboot="y"> <XML_UPDATE filename="c:\Webatm\SoundENG.xml">

<XMLUpdate> <Update> <NodeKey> <Path>Document/Template</Path> <AttributeName>name</AttributeName> <Value>"2020"</Value> </NodeKey> <XML>

<Script state="private"> <Text>Please enter your PIN.</Text>

</Script> </XML>

</Update> </XMLUpdate>

</CONFIGURATION_DATA>

This final example updates the existing FASTCASH1 transaction receipt handling with a modified version.

<CONFIGURATION_DATA reboot="y"> <XML_UPDATE filename=”c:\Webatm\receipt.xml”> <UPDATE> <NodeKey> <Path>ReceiptDefinition/Transaction</Path> <FieldName>Name</FieldName> <Value>FASTCASH1</Value> </NodeKey> <XML> <Name>FASTCASH1</Name> <Criteria> <AndGroup> <IfEqualTo> <Field>ReceiptRequested</Field> <Value>True</Value> </IfEqualTo> <IfEqualTo> <Field>NDCProxy.ReceiptDataFound</Field> <Value>True</Value> </IfEqualTo> </AndGroup> </Criteria> <PrintNow>1</PrintNow> <DeliverWhenDone> <DeliveryType>Cut</DeliveryType>

FIT2ENVELOPEPAYMENT=YES,1,5

Specifies the node path to the change area within the file

XML code that modifies the Receipt

handling in the FAST CASH 1

transaction

Specifies the node path to the change area

within the file

Specifies the XML code that changes the audio

instructions within the file



</DeliverWhenDone> <Form> <Name>Receipt</Name> </Form> <Form> <Name>Footer</Name> </Form> </XML> </UPDATE> </XML_UPDATE> </CONFIGURATION_DATA>

2.2 Commonly Modified Data Dictionary Entries

The charts on the next several pages show the most commonly modified data dictionary entries. All of the entries in the charts are explained more fully in the pages that follow. Further, a full list of data dictionary entries is included in the Data Dictionary section in this document. The Data Dictionary section also notes the data dictionary entries that require a reboot and the ones that should not be changed because they are maintained by the application.

The following data dictionary entries are discussed in this section.

Transaction Set

Account Selections

Consumer Flow Options

Currency Values

Fee Values

Personalization transaction

Enhanced Deposit transaction

Controlling Deposit Disclaimers

Controlling the Paper Journal As described earlier, you need to include the <GROUP>, <NAME> and <VALUE> when you send an update command to the ATM. Most of the entries you will be modifying are in the CONSUMERFLOW group. However, the currency cassette values are in the CURRENCY group and one of the fees you may want to update is in the NDCPROXYCUSTOMIZATION group. Further, Personalization is turned off and on through the CRMSERVICE group.

The descriptions in the next several sections identify the group to which data dictionary entries belong, entry names and possible values. Sample entries are included, but the <CONFIGURATION_DATA> and <DD_UPDATE> commands have not been added to these examples. Refer to the previous section in this document for the structure of the data dictionary update commands.

A data dictionary by transaction cross-reference follows this section.



Function – CONSUMERFLOW.xx…x Parameter Field(s) – comma delimited Default if Omitted

Allowed Values

FITn ACCOUNTBALANCE = YES / NO , # Menu , # Button Location NO FITn CHANGEPIN = YES / NO , # Menu , # Button Location NO FITn CHECKREORDER = YES / NO , # Menu , # Button Location NO FITn DEPOSITWITHCASHBACK = YES / NO , # Menu , # Button Location NO FITn ELECTRONICPAYMENT = YES / NO , # Menu , # Button Location NO FITn ENHANCEDDEPOSIT = YES / NO , # Menu , # Button Location NO FITn ENVELOPEDEPOSIT = YES / NO , # Menu , # Button Location NO FITn ENVELOPEDEPOSITn = YES / NO , # Menu , # Button Location NO n=2-3 FITn ENVELOPEPAYMENT = YES / NO , # Menu , # Button Location NO FITn ENVELOPEPAYMENTFROMACCOUNT = YES / NO , # Menu , # Button Location NO FITn ENVELOPEPAYMENTTOACCOUNT = YES / NO , # Menu , # Button Location NO FITn FASTCASHn = YES / NO , # Menu , # Button Location NO n = 1-8 FITn FULLSTATEMENTn = YES / NO , # Menu , # Button Location NO n = 1-8 FITn MINISTATEMENTn = YES / NO , # Menu , # Button Location NO n = 1-10 FITn MESSAGETOBANK = YES / NO , # Menu , # Button Location NO FITn PERSONALIZEDFASTCASH = YES / NO , # Menu , # Button Location NO FITn PURCHASEn = YES / NO , # Menu , # Button Location NO FITn SPLITDEPOSIT = YES / NO , # Menu , # Button Location NO FITn STAMP = YES / NO , # Menu , # Button Location NO FITn TRANSFER = YES / NO , # Menu , # Button Location NO FITn WITHDRAWAL = YES / NO , # Menu , # Button Location NO

FITn TransactionNameACCOUNTS* = Account # in button position 1-x account in button position

1-8

FITn ELECTRONICPAYMENTFROMACCOUNTS** = Account # in button position

1-x account in button position

1-8

FITn ELECTRONICPAYMENTFROMACCOUNTxTOACCOUNTS** = Account # in button position


1-8

FITn TRANSFERFROMACCOUNTS** = Account # in button position 1-x account in button position

1-8

FITn TRANSFERFROMACCOUNTxTOACCOUNTS** = Account # in button position


1-8 FITn FASTCASHAMOUNTSCREEN = YES / NO NO FITn NUMBEROFFASTCASH = # Fast Cash Buttons 0 1-8 FITn FASTCASHnAMOUNT = Amount 0 HIDEFASTCASHNAME = YES/NO FITCONSUMERTYPEn = # FIT field PSTDX byte 2 n = 1 – 15 NUMBEROFFITCONSUMERTYPE = # FIT Flow Selections 0 0 - 15



Function – CONSUMERFLOW.xx…x Parameter Field(s) – comma delimited Default if Omitted

Allowed Values

NUMBEROFSETTLEMENTCARD = # of cards 1-X, 0=No card DIPCARDREADERMULTITRANS = YES/NO NO MOTORCARDREADERMULTITRANS = YES/NO NO MOTORCARDREADERENTERPIN = YES/NO NO LANGUAGEOPTION = YES/NO BANKNAME = Text CANCELWAITFORHOSTOPTION = YES/NO ENVDISPENSEOPTION = NONE/ASK/AUTO NONE TransactionNameRECEIPTOPTION* = YES/NO PROMOTE = YES/NO

BYPASSSELECTSTAMPSTOENTERSHEETS = YES/NO

FITn STAMPFEE = 0.00 0 STAMPFEEPERSHEET = 0.00 0

STAMPSMENUBUTTONS = button position x, x Sheets

1-x sheets in button position

1-8 STAMPPRICE = 0.00 0 STAMPSPERSHEET = # of stamps

FITn TransactionNameFEE* = 0.00 0 Any valid transaction

FITn TransactionNameFEEOPTION* = YES/NO No Any valid transaction

Function – CURRENCY.xx…x Default if Omitted

Allowed Values

CASSETTE1-4UNITTYPE = Type of media in cassette 0=cash,

1=stamps, 2=other

CASSETTE1-4UNITVALUE = Denomination in cassette



Function – CRMSERVICE.xx…x (Personalization) Default if

Omitted Allowed Values

Initiate = When to retrieve preferences Never

AfterCard AfterPIN Never

* TransactionName can be any of the valid transactions. Note: Enhanced Deposits uses Envelope Deposit Accounts since they are mutually exclusive and Envelope Payment From and To Account do not repeat the word “Account.” They use EnvelopePaymentFromAccounts and EnvelopePaymentToAccounts. Also, the account for Check Reorder is hard-coded to Checking and cannot be changed. ** ELECTRONICPAYMENT and TRANSFER use a different account assignment convention.



2.2.1 Modify the Transaction Set

The transaction set displayed for an ATM customer can be modified through a DD_UPDATE data download. The CONSUMERFLOW section of the dd.dat includes entries that allow transactions to be quickly removed from or added to the transaction set. If parameter=YES, the transaction will appear on one of the menu screens. However, if parameter=NO, the transaction will not appear on a menu. Please note that unless the proxy has been coded to include the transaction, or a change is made to the CustomizerConfig.xml file, a newly added transaction will not be recognized by the proxy. Contact your NCR representative for more information on adding new transactions.

Changes to the CONSUMERFLOW section of the data dictionary do not need a reboot. Therefore, you do not need to include the reboot="y" parameter with your <CONFIGURATION_DATA> command. However, for the changes to the CONSUMERFLOW group to become effective, the data dictionary needs to be re-read. This will occur if you take the terminal out of service and the put it back in service after a dd update.

2.2.1.1 Activate/Deactivate Transactions

The parameters shown in the chart below can be modified to control the transactions shown on the menu(s). Each parameter must be followed by at least one three-entry group, with each entry in the group separated by a comma, as explained below:

Yes/No – an indicator of whether or not this transaction will appear in the menus

Menu number – the menu number where this selection will appear, where “1” specifies the main menu and larger numbers refer to succeeding menus

Button location – the button number where this selection will appear. There are 8 buttons on each menu numbered “1” through “8”, with “1” through “4” beginning on the upper left side and moving down from one button to the next. Buttons on the right of the screen are numbered “5” through “8”, starting at the upper right side and moving down the screen.

If a transaction should appear on multiple menus, you would have multiple three-entry groups for an entry. For example, if you have three transaction menus, and you want the Withdrawal transaction to appear on the first and third menus, you could use an entry similar to the following:

CONSUMERFLOW.WITHDRAWAL=YES,1,1,YES,3,7

This entry would include the Withdrawal transaction on menu 1 in button position 1, and also on menu 3 in button position 7.

Note that if you deactivate a transaction that is on a sub-menu, you may also need to deactivate the sub-menu button. Refer to the next section, Modify Sub-Menus, for more information.



Field Name Value Description Default

ACCOUNTBALANCE Specifies whether a Balance Inquiry transaction is included on the Main Menu.

No

CARDFASTCASH Specifies whether a card-based Fast Cash transaction is included on the Main Menu. Note: this is a special Fast Cash transaction that uses information stored at the host (account and amount) to process the transaction.

No

CHECKREORDER Specifies whether a Check Reorder transaction is included on the Main Menu.

No

CHANGEPIN Specifies whether a PIN Change transaction is included on the Main Menu.

No

DEPOSITWITHCASHBACK

Specifies whether a Deposit with Cash Back transaction is included on the Main Menu.

No

ELECTRONICPAYMENT Specifies whether an Electronic Payment transaction is included on the Main Menu.

No

ENHANCEDDEPOSIT Specifies whether an Enhanced Deposit transaction using the BNA and CPM is included on the Main Menu. If set to YES, ENVELOPE DEPOSIT, ENVELOPEPAYMENT, and DEPOSITWITHCASHBACK must be set to NO.

No

ENVELOPEDEPOSIT Specifies whether a standard Envelope Deposit transaction is included on the Main Menu.

No

ENVELOPEDEPOSIT[2-3] Specifies whether a second or third Envelope Deposit transaction is included on the Main Menu.

No

ENVELOPEPAYMENT Specifies whether a standard Envelope Payment transaction is included on the Main Menu. If ENHANCEDDEPOSIT is set to YES, this keyword must be set to NO.

No

ENVELOPEPAYMENTFROMACCOUNT

Specifies whether a standard Envelope Payment From Account transaction is included on the Main Menu. If ENHANCEDDEPOSIT is set to YES, this keyword must be set to NO.

No

ENVELOPEPAYMENTTOACCOUNT

Specifies whether a standard Envelope Payment To Account transaction is included on the Main Menu. If ENHANCEDDEPOSIT is set to YES, this keyword must be set to NO.

No




FASTCASH1 Specifies whether a Fast Cash transaction is included on the Main Menu. Note: If FASTCASHAMOUNTSCREEN = YES, only one generic “Fast Cash” selection will appear in the main menu(s). When that menu entry is selected, it will display a separate menu screen of Fast Cash amounts.

No

FASTCASHx The value “x” must be replaced with a number from 2 through 8 to indicate whether a second through eighth Fast Cash transaction is included on the Main Menu. FASTCASHx parameters should not be included if FASTCASHAMOUNTSCREEN = YES.

No

FULLSTATEMENT1 Specifies whether Full Statement 1 is included on one of the Main Menus. If set to Yes, it must be followed by 2 comma separated digits representing the number of the menu and the button location where the transaction should be presented. Note: if you have a main menu selection that leads to a submenu of Full Statements, the main menu item was setup as a non-transaction button. See the CONSUMERFLOW.NONTRANSACTIONBUTTON1 entry in the Data Dictionary section in this document for more information.

No

FULLSTATEMENTx The value “x” must be replaced with a number from 2 through 8 to indicate whether a second through eighth Full Statement is included on one of the Main Menus. If set to Yes, these entries must be followed by 2 comma separated digits representing the number of the menu and the button location where the transactions should be presented.

No

MESSAGETOBANK Specifies whether a message to bank transaction is included on the Main Menu. If ENHANCEDDEPOSIT is set to YES, this keyword must be set to NO.

No




MINISTATEMENT1 Specifies whether a Mini-Statement transaction is included on one of the Main Menus. Note: if you have a main menu selection that leads to a submenu of Mini-Statements, the main menu item was setup as a non-transaction button. See the CONSUMERFLOW.NONTRANSACTIONBUTTON1 entry in the Data Dictionary section of this document for more information.

No

MINISTATEMENTx The value “x” must be replaced with a number from 2 through 10 to indicate whether a second through tenth Mini-Statement transaction is included on one of the Main Menus.

No

PERSONALIZEDFASTCASH

Specifies whether a Personalized Fast Cash transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

PURCHASE1 Specifies whether a Purchase1 transaction is included in the Consumer Flow. This could be used for gift certificates, phone cards, etc. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

PURCHASEx Specifies whether a Purchase[2-x] transaction is included in the Consumer Flow. You can define as many purchase types as necessary. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

SPLITDEPOSIT Specifies whether a Split Deposit transaction is included on the Main Menu.

No

STAMP Specifies whether a Purchase Stamps transaction is included on the Main Menu.

No

TRANSFER Specifies whether a Transfer transaction is included on the Main Menu.

No

WITHDRAWAL Specifies whether a Withdrawal transaction is included on the Main Menu.

No



Note that the ATM Preferences transaction is defined as a non-transaction button and is not included in this list. See the Personalization Transaction Main Menu Button section for more information on activating the Personalization transaction.

Example:

The following parameters in the dd.dat cause 2 transaction menus to be created. The first menu contains only 3 selections (AccountBalance, Withdrawal, and DepositWithCashBack) on buttons 5, 6, and 7. The second menu contains the remaining selections (Transfer, EnvelopeDeposit, Stamp, EnvelopePayment, ElectronicPayment, and MiniStatement1) on buttons 1 through 6.

CONSUMERFLOW.ACCOUNTBALANCE=YES,1,5 CONSUMERFLOW.WITHDRAWAL=YES,1,6 CONSUMERFLOW.DEPOSITWITHCASHBACK=YES,1,7 CONSUMERFLOW.TRANSFER=YES,2,1 CONSUMERFLOW.ENVELOPEDEPOSIT=YES,2,2 CONSUMERFLOW.STAMP=YES,2,3 CONSUMERFLOW.ENVELOPEPAYMENT=YES,2,4 CONSUMERFLOW.ELECTRONICPAYMENT=YES,2,5 CONSUMERFLOW.MINISTATEMENT1=YES,2,6 CONSUMERFLOW.ENHANCEDDEPOSIT=NO

2.2.1.2 Modify Sub-Menus

Some financial institutions use sub-menus in their menu structures. Sub-menus are setup with Non-Transaction Buttons. Non-Transaction Buttons are simply buttons that, when selected, proceed to another menu instead of invoking a transaction. The diagram below demonstrates two non-transaction buttons, Next Menu and Main Menu.

If you deactivate the transactions that are accessed from a sub-menu with a non-transaction button, be sure to deactivate the non-transaction button as well. Otherwise the system will not operate as expected.



If you need to add a sub-menu structure, contact your NCR representative. Note: the Fast Cash and Withdrawal transactions implement sub-menus in a unique way and do not follow the standard sub-menu and non-transaction button logic.

2.2.1.3 Modify Transaction Account Selections

Each transaction has accounts associated with it in the CONSUMERFLOW section of the dd.dat file. These associations allow the transactions to act upon those accounts. For example, the Account Balance transaction can have either all of a bank's accounts associated with it, thus enabling the customer to get a balance on any of his accounts; or the Account Balance transaction can only have a few typical accounts, such as checking and savings, associated with it. Each account is defined in the dd.dat as ACCOUNT1-x with the account name following the parameter.


ACCOUNT1-x Specifies the account type (Checking, Savings, etc.) used by the consumer flow for Account 1-x. These entries are then used to associate Account 1-x with transactions and to define the button position for Account 1-x on transaction screens. Note: These entries must match Account 1-x in the InitialAccountList.xml file used by the proxy.

Note: the Check Reorder transaction account is hard-coded to Checking and cannot be changed through the data dictionary.

Example:

The following dd.dat entries define four account types, checking, savings, credit card and loan, that can be used for transactions. As many account types as necessary can be defined. Please note that account types cannot be added or changed with these parameters.

CONSUMERFLOW.ACCOUNT1=Checking CONSUMERFLOW.ACCOUNT2=Savings CONSUMERFLOW.ACCOUNT3=Credit Card CONSUMERFLOW.ACCOUNT4=Loan

The account designators, 1 through 4 in the case above, are what tie transactions to the accounts upon which they can act. The designators are used in the TransactionNameACCOUNTS entries in the dd.dat file to define the accounts that should be available for each individual transaction (where TransactionName is any valid transaction). The account designators must be included in an order-dependent, comma separated list which also defines their button locations (1-8) on the screen. An example of this follows the transaction account table below.

Most transactions have only one list associated with them, and any transaction that has multiple instances, such as Fast Cash and Mini Statements, will have accounts associated with



each instance. Also note that the Envelope Payment, Envelope Payment To Account and Message To Bank transactions do not have any accounts associated with them.


ACCOUNTBALANCEACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for the Account Balance transaction and the account button locations on the screen.

DEPOSITWITHCASHBACKACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Deposit with Cash Back transaction and the account button locations on the screen.

ENVELOPEDEPOSITACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Envelope Deposit transaction and the account button locations on the screen. Note: this entry is also used by Enhanced Deposits because Envelope Deposits and Enhanced Deposits are mutually exclusive.

ENVELOPEPAYMENTTOACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Envelope Payment To Account transaction and the account button locations on the screen. Note: Note: the word ACCOUNT from the transaction name is dropped in this instance.

FASTCASHxACCOUNTS Specifies the accounts (ACCOUNT1-x) available for Fast Cash x transaction and the account button locations on the screen.

Checking

FULLSTATEMENTxACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Full Statement x transaction and the account button locations on the screen.

MINISTATEMENTxACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Mini-Statement x transactions and the account button locations on the screen.

PERSONALIZEDFASTCASHACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Personalized fast Cash transactions and the account button locations on the screen.

Checking

PURCHASExACCOUNTS Specifies the accounts (ACCOUNT1-x) available for Purchasex transactions and the account button locations on the screen.

SPLITDEPOSITACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Split Deposit transactions and the account button locations on the screen.

STAMPACCOUNTS Specifies the accounts (ACCOUNT1-x) available for Stamp transactions and the account button locations on the screen.




WITHDRAWALACCOUNTS

Specifies the accounts (ACCOUNT1-x) available for Withdrawal transactions and the account button locations on the screen.

Note: the Check Reorder transaction does not have an Accounts entry because the account is hard-coded to Checking in the Consumer Flow.

Example:

Using ACCOUNT1-4 list defined earlier, the following entries in the dd.dat file allow:

Account Balances from checking (account 1, button position 5) and savings (account 2, button position 6)

Envelope Deposits to checking (account 1, button position 5) and savings (account 2, button position 6)

Fast Cash 1 withdrawals from checking only (account 1, button position 5)

Fast Cash 2 withdrawals from credit card only (account 3, button position 5)

Withdrawals from checking (account 1, button position 5), savings (account 2, button position 6) and credit card (account 3, button position 7).

CONSUMERFLOW.ACCOUNTBALANCEACCOUNTS=,,,,1,2,, CONSUMERFLOW.ENVELOPEDEPOSITACCOUNTS =,,,,1,2,, CONSUMERFLOW.FASTCASH1ACCOUNTS =,,,,1,,, CONSUMERFLOW.FASTCASH2ACCOUNTS =,,,,3,,, CONSUMERFLOW.WITHDRAWALACCOUNTS =,,,,1,2,3,

There are two transactions that need two accounts to complete the transaction; these are Electronic Payments and Transfers. With these transactions, a slight variation of the account definition method explained above is used.

Electronic Payments and Transfers have a To account list for each account type used as a From account. This means that if three account types will be used to make electronic payments or transfer funds From, there will be three To accounts lists.




ELECTRONICPAYMENTFROMACCOUNTS

Specifies the From accounts displayed on the Electronic Payment transaction Select Account screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ELECTRONICPAYMENTFROMACCOUNTS=,,,,1,2,, . Note: the TO accounts are defined a little differently. See the next two dd entries for To account definition.

ELECTRONICPAYMENTFROMACCOUNTxTOACCOUNTS

Specifies the Electronic Payment To accounts (ACCOUNT1-x) and their button locations on the screen when Accountx is selected as the From account for an Electronic Payment transaction. Different From accounts can have different To accounts. The To account numbers (1-x) must be placed in a comma separated list which defines their button positions on the screen. Note: the Account specified in this entry must be one of the accounts specified in the ELECTRONICPAYMENTFROMACCOUNTS entry.


TRANSFERFROMACCOUNTS

Specifies the From accounts displayed on the Transfer transaction Select Account screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be TRANSFERFROMACCOUNTS=,,,,1,2,, . Note: the TO accounts are defined a little differently. See the next two dd entries for To account definition.




TRANSFERFROMACCOUNTxTOACCOUNTS

Specifies the Transfer To accounts (ACCOUNT1-x) and their button locations on the screen when Accountx is selected as the From account for a Transfer transaction. Different From accounts can have different To accounts. The To account numbers (1-x) must be placed in a comma separated list which defines their button positions on the screen. Note: the Account specified in this entry must be one of the accounts specified in the TRANSFERFROMACCOUNTS entry.

Example for Transfer:

The following entries in the dd.dat file allow transfers from two accounts: checking (account 1) and savings (account 2). Transfers from checking can be made to savings (account 2, button position 5) and credit card (account 3, button position 6). Transfers from savings (account 2) can be made to checking (account 1, button position 5) and credit card (account 3, button position 6).

CONSUMERFLOW.TRANSFERFROMACCOUNTS=,,,,1,2,, CONSUMERFLOW.TRANSFERFROMACCOUNT1TOACCOUNTS =,,,,2,3,, CONSUMERFLOW.TRANSFERFROMACCOUNT2TOACCOUNTS =,,,,1,3,,

2.2.1.4 Modify Unique Main Menu Banners and Instruction Text

APTRA Edge has the ability to support unique banners and unique instructional text on each main menu displayed to the cardholder by FIT. To add or modify unique banners and/or text for each main menu, you need to modify the following sections of the TextENG.js file:

Instructional text - Messages 2080_001 through 2080_00x (maximum depends upon the number of menus you have)

Banner text - Messages 2081_001 through 2081_00x (maximum depends upon the number of menus you have)

In these entries, the first two digits after the underscore ( _ ) are the FIT number followed by the Main Menu number. This is the same menu number used when you defined your transaction set in the data dictionary (CONSUMERFLOW.WITHDRAWAL=Yes,1,4 where 1 is the menu number and 4 is the button position on that menu).

Example:

In the following example it is assumed that there are four main menus: a Main Menu screen (1), a Payments main menu (2), a Mini Statement main menu (3) and a Fast Cash main menu (4). Each menu will have its own banner and instructional text. All apply to all FITs.



vMessage2080_001 = "Please select the type of transaction <br> by pressing the appropriate key"; vMessage2080_002 = "Please select payment transactions"; vMessage2080_003 = "Please select mini statements"; vMessage2080_004 = "Please choose the appropriate fast cash amount"; vMessage2081_001 = "Main Menu"; vMessage2081_002 = "Payments"; vMessage2081_003 = "Mini Statements"; vMessage2081_004 = "Fast Cash";

2.2.1.5 Modify FAST CASH Settings

Fast Cash transactions can be enabled in two different ways:

A single Fast Cash selection can appear on one of the primary menu screens.

When selected, a sub-menu appears showing up to 8 Fast Cash amounts. The sub-menu screen is not configurable. Instead, amounts will be assigned starting at the upper right and going down through buttons 7 and 8, then continuing at the upper left down through buttons 3 and 4. You can also include an Other Amount button on this menu that leads to the Enter Amount screen to allow a cardholder to enter his Fast Cash amount.

A series of Fast Cash selections (up to the maximum of 8) can appear on the main menu screens, each showing the words “Fast Cash” followed by an associated dollar amount (e.g. “Fast Cash $20”, “Fast Cash $40”, “Fast Cash $60”, etc.).

APTRA Edge also supports a card-based Fast Cash transition for customers who offer this to their cardholders. This feature is supported through the CONSUMERFLOW.CARDFAST CASH entry, and uses account and amount information stored at the host for processing.


FASTCASHAMOUNTSCREEN

Indicates whether or not a separate FAST CASH menu screen should be displayed to allow the ATM user to select an amount. If set to YES, the Main Menu will include a single FAST CASH selection (defined by FASTCASH1). The FASTCASH1 parameter specifies where the FAST CASH selection appears on the main menu(s). Choosing that selection will display another menu, showing the different Fast Cash values that may be selected (defined by FASTCASH[2-8]AMOUNT). If set to NO, all Fast Cash transactions will appear in the main menu(s) along with the corresponding amounts.

No




NUMBEROFFASTCASH Specifies the number of Fast Cash selections that are allowed, up to a maximum of 8. This value must be coordinated with the number of FASTCASHxAMOUNT parameters. For instance, if NUMBEROFFASTCASH is 2, then 2 amounts (FASTCASH1AMOUNT and FASTCASH2AMOUNT) must be specified. If NUMBEROFFASTCASH is 8, then 8 amounts (FASTCASH1AMOUNT through FASTCASH8AMOUNT) must be specified.

0

FASTCASH1AMOUNT Up to 3 digits representing the dollar amount of the first fast cash amount button. If FASTCASHAMOUNTSCREEN=NO, this amount will appear on the main menu screens, prefixed with “Fast Cash” (e.g. “Fast Cash $20” or “Fast Cash $100”). If FASTCASHAMOUNTSCREEN=YES, this amount will appear on a separate Fast Cash menu that lists only Fast Cash amounts.

FASTCASH[2-8]AMOUNT Up to 3 digits representing the dollar amount of the first fast cash amount button. If FASTCASHAMOUNTSCREEN=NO, this amount will appear on the main menu screens, prefixed with “Fast Cash” (e.g. “Fast Cash $20” or “Fast Cash $100”). If FASTCASHAMOUNTSCREEN=YES, this amount, plus FASTCASH2-8]AMOUNT, will appear on a separate Fast Cash menu that lists only Fast Cash amounts. Note: the Fast Cash menu amounts defined for Fit0 will be used as the default if no other Fit Fast Cash amounts are defined.

No

HIDEFASTCASHNAME Yes/No entry that specifies whether or not to include the words “Fast Cash” on Main Menu buttons that contain Fast Cash amounts.

No

OTHERAMOUNTINFASTCASHMENU

Specifies that an Other Amount button be included on the Fast Cash menu. When set to Yes, the button will be positioned in button position 4 (lower left corner) (This Other Amount button navigates to the Enter Amount screen.)

No



Example1:

The following parameters in the dd.dat cause 4 Fast Cash transactions (“Fast Cash $20”, “Fast Cash $40”, “Fast Cash $60”, and “Fast Cash $80”) to be created on the main menu on buttons 1 through 4. The words “Fast Cash” is desired on the buttons, so the HideFastCashName data dictionary is set to No (or could be omitted).

CONSUMERFLOW.NUMBEROFFASTCASH=4 CONSUMERFLOW.FASTCASHAMOUNTSCREEN=NO CONSUMERFLOW.HIDEFASTCASHNAME=NO CONSUMERFLOW.FASTCASH1AMOUNT=20 CONSUMERFLOW.FASTCASH2AMOUNT=40 CONSUMERFLOW.FASTCASH3AMOUNT=60 CONSUMERFLOW.FASTCASH4AMOUNT=80 CONSUMERFLOW.FASTCASH1=YES,1,1 CONSUMERFLOW.FASTCASH2=YES,1,2 CONSUMERFLOW.FASTCASH3=YES,1,3 CONSUMERFLOW.FASTCASH4=YES,1,4

Example2:

The following parameters in the dd.dat will include a single entry on button 6 of the main menu for “Fast Cash”. When that button is pressed, a separate Fast Cash menu containing 6 fast cash transactions ($20, $40, $60, $80, $100, and $200) will be displayed. No Other Amount button will be included on the Fast Cash menu.

CONSUMERFLOW.NUMBEROFFASTCASH=6 CONSUMERFLOW.FASTCASHAMOUNTSCREEN=YES CONSUMERFLOW.FASTCASH1AMOUNT=20 CONSUMERFLOW.FASTCASH2AMOUNT=40 CONSUMERFLOW.FASTCASH3AMOUNT=60 CONSUMERFLOW.FASTCASH4AMOUNT=80 CONSUMERFLOW.FASTCASH5AMOUNT=100 CONSUMERFLOW.FASTCASH6AMOUNT=200 CONSUMERFLOW.FASTCASH1=YES,1,6 CONSUMERFLOW.OTHERAMOUNTINFASTCASHMENU=NO

2.2.2 Modify the Consumer Flow Options

The dd.dat file also contains parameters that can be changed to modify certain occurrences within the consumer flow. Any of the following can be modified through the dd.dat file:

Transaction Flow Based on FIT Value Surcharge Options Stamp Options Receipt Options Envelope Dispense Option Card Reader Options Language Option Voice Guidance Options Enable/Disable APTRA Promote Advertising Image and Message Options



Each of these is discussed in this section.

2.2.2.1 Modify Transaction Flow Based on FIT Value

Some institutions want selected transactions available to only certain groups of consumer types. For instance, perhaps a bank requires a different transaction set displayed for “on-us” customers than for “foreign” customers. The different consumer types are defined in the NDC FIT table.

The dd.dat file used by APTRA Edge can be modified to present a unique set of transaction selections to each consumer type defined in the FIT table. Up to 15 different FIT values can be specified (FIT1-FIT15). (FIT0 is reserved.) The following parameters must be included in the dd.dat file:


FITCONSUMERTYPE1-x Specifies the FIT value to use for matching to specific menu selections. The number “1” can be replaced with other numbers up to “15” to represent the maximum of 15 consumer types.

FITSUPERVISOR Specifies the FIT value for a supervisor card. The assigned value can be any value from 1 to 15. If no supervisor card is used, then FITSUPERVISOR should be set to “-2”.

NUMBEROFFITCONSUMERTYPE

Specifies the number of consumer types associated with the FIT table up to a maximum of 15. A value of 0 can be specified to indicate that no special FIT processing needs to occur (e.g. all ATM customers see the same menus).

0

In order to define the unique menus for each consumer type, each of the dd.dat parameters discussed in the Modify the Transaction Set section in the document can be preceded by “FITx”, where “x” matches the value assigned to the FITCONSUMERTYPE parameter.

If a FIT transaction should have different accounts from the ones defined for the default transaction (no FIT preceding transaction name), an account definition entry can be included for the FIT transaction. For example, if the default Withdrawal transaction allows withdrawals from accounts 1, 2 and 3, but FIT1Withdrawal should only allow withdrawals from account 1, the following entry would be included in the dd.dat:

FIT1WITHDRAWALACCOUNTS=,,,,,,,1

If a consumer uses a card that does not match any of the criteria for the defined FITs, the default transaction set (no FIT preceding transaction name) will be presented to the consumer.



Example:

The following parameters in the dd.dat cause 2 unique transaction sets to be used: one for Consumer Type 1 and another for Consumer Type 2. For this example, all FIT transactions use the same accounts as the default transaction set so no unique account entries are included.

The first transaction set is for Consumer Type 1. It displays 2 menus. The first menu contains only 3 selections (AccountBalance, Withdrawal, and DepositWithCashBack) on buttons 5, 6, and 7. The second menu contains the remaining selections (Transfer, EnvelopeDeposit, Stamp, EnvelopePayment, and MiniStatement1) on buttons 1 through 5.

The second transaction set is for Consumer Type 2. It is much more limited than the first transaction set and includes only a few transactions on a single menu.

CONSUMERFLOW.NUMBEROFFITCONSUMERTYPE=2 CONSUMERFLOW.FITCONSUMERTYPE1=3 CONSUMERFLOW.FITCONSUMERTYPE2=4 CONSUMERFLOW.FIT1ACCOUNTBALANCE=YES,1,5 CONSUMERFLOW.FIT1WITHDRAWAL=YES,1,6 CONSUMERFLOW.FIT1DEPOSITWITHCASHBACK=YES,1,7 CONSUMERFLOW.FIT1TRANSFER=YES,2,1 CONSUMERFLOW.FIT1ENVELOPEDEPOSIT=YES,2,2 CONSUMERFLOW.FIT1STAMP=YES,2,3 CONSUMERFLOW.FIT1ENVELOPEPAYMENT=YES,2,4 CONSUMERFLOW.FIT1MINISTATEMENT1=YES,2,5

CONSUMERFLOW.FIT2WITHDRAWAL=YES,1,1 CONSUMERFLOW.FIT2DEPOSITWITHCASHBACK=YES,1,2 CONSUMERFLOW.FIT2ENVELOPEDEPOSIT=YES,1,3 CONSUMERFLOW.FIT2STAMP=YES,1,4 CONSUMERFLOW.FIT2ENVELOPEPAYMENT=YES,1,5

2.2.2.2 Modify Surcharge Options

The surcharge screen advises an ATM customer that a fee will be charged if he/she chooses to continue with the transaction. The ATM customer can choose to cancel the transaction to avoid the fee. These parameters can be changed as necessary.

Note: refer to the Modify Fee Values section of this document for information on how to change fees (surcharges) for transactions.


BANKNAME Specifies the bank name to be displayed on the surcharge screen. In addition, this value will be displayed on the thank you screen. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&)




" - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

CANCELWAITFORHOSTOPTION

Indicates whether the host should be advised that a customer has cancelled the fee prior to the end of the transaction. YES indicates that the host will be notified before the transaction is complete. After refusing the surcharge, the customer will see a “Please Wait” until the host acknowledges the refusal. NO indicates that the host will be notified after the transaction is complete.

Example:

The following parameters in the dd.dat define NCR Bank as the bank name that will appear on the surcharge and thank-you screens, and also indicates that the host will be notified after the transaction is complete that a consumer cancelled a surcharged transaction.

CONSUMERFLOW.BANKNAME=NCR BANK CONSUMERFLOW.CANCELWAITFORHOSTOPTION=NO

2.2.2.3 Modify the Stamp Options

If a STAMP = YES parameter is specified in the dd.dat, then the following parameters will be included in the dd.dat. The Stamps transaction can be configured to allow the cardholder to directly enter the number of sheets of sheets of stamps he wants, or to select the number of sheets from a menu. You can update these entries as necessary.


BYPASSSELECTSTAMPSTOENTERSHEETS

Yes/No entry used to bypass the Select Stamps screen so that the user can enter the number of sheets he wants rather than selecting the number of sheets from a predefined menu. The default is No, which means always display a menu.

No

STAMPFEE Specifies the fee charged for each Purchase Stamps transaction, no matter how many sheets are purchased. This value should be entered as numeric digits with a single decimal point. This entry is mutually exclusive with STAMPFEEPERSHEET.

0.00




STAMPFEEPERSHEET Specifies the fee charged for each sheet of stamps that is purchased. This value should be entered as numeric digits with a single decimal point. This entry is mutually exclusive with STAMPFEE.

STAMPSMENUBUTTONS

This entry defines the button positions and the number of sheets associated with those buttons when a Stamp menu screen is included on the ATM. The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the number of sheets as the second entry in the pair. For example, to define button position 1-4 with the number of sheets 1, 2 3 and 4, you would use STAMPSMENUBUTTONS=1,1,2,2,3,3,4,4. These amounts also need to be included in Template 2164 of the SoundXXX.xml file.

STAMPPRICE Specifies the actual price for each sheet of stamps. This value should be entered as numeric digits with a single decimal point.

0.00

STAMPSPERSHEET Specifies the number of stamps per sheet. This value is usually 18.

0

Example:

The following parameters in the dd.dat file define an 18 stamp sheet of 37 cents stamps. There is a $.50 service fee applied to each sheet of stamps. The cardholder will enter the number of sheets he wants, rather than selecting from a menu.

CONSUMERFLOW.BYPASSSELECTSTAMPSTOENTERSHEETS =Yes CONSUMERFLOW.STAMPFEE=No CONSUMERFLOW.STAMPFEEPERSHEET=.50 CONSUMERFLOW.STAMPPRICE=6.66 CONSUMERFLOW.STAMPSPERSHEET=18

If a menu of stamp selections should be presented to the cardholder rather than letting him enter the number of sheets, the following entries could be used to define a menu offering I sheet on button 5, 2 sheets on button 6, 3 sheets on button 7 and 4 sheets on button 8.

CONSUMERFLOW.BYPASSSELECTSTAMPSTOENTERSHEETS =No CONSUMERFLOW.STAMPFEE=No CONSUMERFLOW.STAMPFEEPERSHEET=.50 CONSUMERFLOW.STAMPSMENUBUTTONS=5,1,6,2,7,3,8,4 CONSUMERFLOW.STAMPPRICE=6.66 CONSUMERFLOW.STAMPSPERSHEET=18



2.2.2.4 Modify the Receipt Options

Receipt parameters in the data dictionary define:

whether or not multiple transactions can print on one receipt (receipt chaining)

whether receipts are optional or mandatory (can be specified per transactions or for all transactions)

if receipts are optional, when the cardholder will be asked if he wants a receipt (before or after PIN entry)

The Yes/No entry, CONSUMERFLOW.CHAINRECEIPTS determines whether or not multiple transactions can print on a single receipt. Note that Enhanced Deposits have a separate dd entry (CONSUMERFLOW.DEPOSITSPERRECEIPT) for printing chained Deposit transactions on a single receipt. See section 2.6 for more information on this entry.

Giving cardholders the option of not getting a receipt for their transactions is controlled by the entry CONSUMERFLOW.TransactionNameRECEIPTOPTION, where TransactionName is replaced by any valid transaction name, for example CONSUMERFLOW.WITHDRAWAL RECEIPTOPTION. If this entry is set to Yes, cardholders will be asked the question, “Do you want a receipt?” during withdrawal transactions. If this entry is set to no, cardholders will always get a receipt.

The entry CONSUMERFLOW.RECEIPTOPTIONAFTERPINENTRY determines when the “Do you want a receipt?” question is presented to the cardholder. If set to Yes, the receipt question will display during the transaction as described above.

If set to No, the receipt question will display BEFORE the PIN entry screen, and the selection the cardholder make on this receipt option screen will apply to all transactions in the session. If any CONSUMERFLOW.TransactionNameRECEIPTOPTION entries are set, they will be ignored because the receipt question will always be asked before the PIN entry screen, which means it is before the cardholder selects a transaction.


CHAINRECEIPTS Specifies whether or not you want multiple transactions on one receipt. There is no limit to the number of transactions that can be printed on one receipt.

No

RECEIPTOPTIONAFTERPINENTRY

Specifies whether the Do You Want a Receipt screen should be displayed before (Yes) or after (No) the Main Menu. When this is set to Yes, any transaction receipt option entries for which you specify yes, for example CONSUMERFLOW.TRANSFERRECEIPTOPTION=YES or CONSUMERFLOW.WITHDRAWALRECEIPTOPTION=YES, will be ignored.

No




TransactionNameRECEIPTOPTION

YES indicates that the ATM user will be queried as to whether he/she desires a printed receipt. NO indicates that the ATM user will always get a printed receipt.

Example:

The following parameters in the dd.dat file indicate optional receipts are being offered and that the receipt question will be asked during the transactions (after the cardholder enters his PIN).

Optional receipts will be offered for withdrawal and stamp transactions, but will not be offered for Balance Inquiry and Transfer transactions, which means the cardholder will always get a receipt for these transactions.

Receipt chaining is set to yes, which means multiple transactions can appear on one receipt.

CONSUMERFLOW. RECEIPTOPTIONAFTERPINENTRY=Yes CONSUMERFLOW.WITHDRAWALRECEIPTOPTION=Yes CONSUMERFLOW.STAMPRECEIPTOPTION=Yes CONSUMERFLOW.ACCOUNTBALANCERECEIPTOPTION=No CONSUMERFLOW.TRANSFERRECEIPTOPTION=No CONSUMERFLOW. CHAINRECEIPTS =Yes

2.2.2.5 Modify the Envelope Dispense Option

The envelope dispense option can be modified to ask the consumer if he wants an envelope, automatically dispense an envelope, or never dispense an envelope. If you want to change this option, you need to modify the ENVDISPENSEOPTION entry in the dd.dat file. Normally this option is set when the ATM is installed and never changed.


ENVDISPENSEOPTION An indicator as to whether an envelope will be dispensed for deposits. Choose from one of the following: Ask During a transaction, the ATM user

will be asked if an envelope should be dispensed.

Auto An envelope is automatically dispensed during the transaction, without asking the ATM user.

None No envelope will be dispensed during a transaction.

None



Example:

The following parameter has the envelope option set to always ask the consumer if he wants an envelope.

CONSUMERFLOW.ENVDISPENSEOPTION=ask

2.2.2.6 Modify the Card Reader Options

Card reader options can be modified to support or not support “chaining” of transactions for the particular card reader type - DIP or Motorized. Further, the MOTORCARDREADEREN TERPIN parameter specifies whether or not the consumer will have to reenter his PIN on subsequent transactions in the same session. Note: this reenter PIN option does not apply to DIP and Swipe card readers; the consumer will always have to reenter his PIN with these card readers.

When transaction chaining is in effect, the question, “Do you want another transaction?” is displayed as each transaction is completed, allowing an ATM customer to chain several transactions into a single session. Normally this option is set when the ATM is installed and never changed.


DIPCARDREADERMULTITRANS

Specifies whether multiple transactions should be allowed with a DIP or SWIPE Reader. If set to YES, the question “Do You Want Another Transaction” will be displayed as each transaction is completed.

No

MOTORCARDREADERMULTITRANS

Specifies whether multiple transactions should be allowed with a Motorized Card Reader. If set to YES, the question “Do You Want Another Transaction” will be displayed as each transaction is completed.

No

MOTORCARDREADERENTERPIN

Specifies that the user of an ATM equipped with a Motorized Card Reader be prompted to re-enter his/her PIN after a transaction is completed and before another transaction can be performed.

No

Example:

The following parameters allow multiple transactions in a single session on ATMs with a motorized card reader, and require the consumer to reenter his PIN for each transaction.

CONSUMERFLOW.MOTORCARDREADERMULTITRANS =Yes CONSUMERFLOW.MOTORCARDREADERENTERPIN =Yes



2.2.2.7 Change the Language Option and Menus

The language option is used to ask the consumer to select English or Spanish to change this option, you need to modify the LANGUAGEOPTION entry in the dd.dat file. Normally this option is set when the ATM is installed and never changed. Note: if you change this option from Yes to No remotely, you also need to clear the NDCPROXY.LANGUAGE entry.


LANGUAGEOPTION An indicator as to whether a Select Language screen will be displayed, allowing the user to select Spanish as an alternate language.

No

APTRA Edge, by default, is configured to offer English and Spanish. If you want to offer additional languages there are four things you need to do:

Define the language selection menus in the data dictionary,

Define the additional language labels in the TextENG.js file,

Create additional TextXXX.js files, one for each additional language,

Create additional voice guidance Sound Files, one for each additional language (if voice guidance is desired).

2.2.2.7.1 Define the Language Selection Menus

You can define as many language selection menus as necessary to support your language set. If you have 1-8 languages, you can define only one menu, if desired, with the following CONSUMERFLOW data dictionary entry:

Field Name Value Description

LANGUAGEMENU1

This entry defines the Language Selection menu, or the first of several language menus, displayed to cardholders. The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the ISO 639 three-letter language code as the second entry in the pair. When multiple language screens are defined, two predefined entries must be included in these parings for navigation among screens: NEXT and BACK. The actual text displayed on all buttons is defined in the 1000 message range in the TextENG.js file.

If you have more than 8 languages, or want to display the 8 language selections on multiple screens, you need to include data dictionary entries for language menus 2-x, as many as required.



Field Name Value Description

LANGUAGEMENU[2-x]

These entries define the second, third, etc. Language Selection menus. You can define as many Language Selection menus as necessary. The parameters for these entries, like LANGUAGEMENU1, are paired values that define the button position on the screen as the first entry in the pair, and the ISO 639 three-letter language code as the second entry in the pair. When multiple language screens are defined, two predefined entries must be included in these parings for navigation among screens: NEXT and BACK. The actual text displayed on all buttons is defined in the 1000 message range in the TextENG.js file.

Example:

The following parameters define two language menus that offer four languages on the first menu (English, Spanish, Chinese and French) and three languages on the second screen (Portuguese, Korean and Modern Greek). The Next and Back buttons are included in position 8 on the screens.

CONSUMERFLOW.LANGUAGEMENU1=1,ENG,2,SPA,5,CHI,6,FRA,8,NEXT CONSUMERFLOW.LANGUAGEMENU2=5,POR,6,KOR,7,GRE,8,BACK

2.2.2.7.2 Language Labels in TextENG.js File After you determine how many language menus you need and define them in the data dictionary, you need to define the text shown on the buttons on these menus. These entries are defined in the 1000 message range in the TextENG.js file. For each entry, the language name is defined as the whole number value (1000, 1001, 1002, etc.) followed by the language name, and the three-character code referenced in the data dictionary menu definitions is defined as a sub-message of the first in the format _ = "3-character language code."

The text for the NEXT and BACK buttons that must be included when multiple language screens are included is defined in message numbers 1086 and 1087, regardless of the text that you elect to display on the buttons.

Example:

The following parameters show the message file values that can be used for the two menus defined in the previous example. The NEXT button has been assigned the text "More Language Options" and the BACK button has the text "Previous Menu." var vMessage1000 = "English"; var vMessage1000_1 = "eng"; var vMessage1001 = "Español"; var vMessage1001_1 = "spa"; var vMessage1002 = "Chineese"; var vMessage1002_1 = "chi"; var vMessage1003 = "Korean"; var vMessage1003_1 = "kor"; var vMessage1004 = "Français";



var vMessage1004_1 = "fra"; var vMessage1005 = "Português"; var vMessage1005_1 = "por"; vMessage1086 = "More Language Options"; vMessage1087 = "Previous Menu";

2.2.2.7.3 Additional TextXXX.js Files

APTRA Edge includes two language files: TextENG.js for English and TextSPA.js for Spanish. If you plan to support additional languages, you need to create additional TextXXX.js files. XXX is the ISO 639 three-letter language code for the particular language. Refer to Section D for more information on these files.

2.2.2.7.4 Additional Sound Files APTRA Edge voice guidance sound files contain all of the text articulated to a sight impaired cardholder through his earphones for each screen. Similar to the onscreen language files, the sound file for English is named SoundENG.xml and SoundSPA.xml for Spanish. The sound files are, however, xml files, not javascript files. Each sound file contains a series of templates for each screen. Each template has a "Template name" which is actually a number that corresponds to the Message number for the same message in the TextXXX.js file. For example, the Template names for the text to be articulated for the Card Not Read screens are Template name 2001 through Template name 2006, and the Message numbers in the TextENG.js file for the same screens are Message2001-Message2006. If you add languages to your APTRA Edge application, you need to create additional sound files, one for each additional language. Additionally, you may need to purchase a license for additional Text to Speech engines. Refer to Section C.5 for more information on Sound files.

2.2.2.8 Modify Voice Guidance Option

2.2.2.8.1 CONSUMERFLOW Group Entries The VOICEGUIDANCE=YES parameter specified in the dd.dat turns voice guidance on during transactions. When you turn voice guidance on, you also need to specify the bank name that will be voiced during the Welcome sequence and on the Thank You screen, and several description sequences for finding the modules on the ATM (how to find card reader, for example).


VOICEGUIDANCE Indicates whether Voice Guidance will be used during transaction processing to verbally guide a sight-impaired user through the screens.

No




VOICEBANKNAME Indicates the words to use whenever VOICEGUIDANCE=Yes and the VOICEBANKNAME variable is included in the .xml file. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

Example:

These parameters turn voice guidance on and set NCR Bank as the bank name.

CONSUMERFLOW.VOICEGUIDANCE =Yes CONSUMERFLOW.VOICEBANKNAME=NCR Bank

2.2.2.9 Enable/Disable APTRA Promote

The PROMOTE parameter turns APTRA Promote on and off on the ATM.


PROMOTE Indicates whether or not APTRA Promote is being used for advertising support. Review separate documentation that is available on APTRA Promote for further information.

No

2.2.2.10 Change Advertising Image and Message Options

NCR recommends using APTRA Promote for extensive advertising and full campaign management. However, APTRA Edge does support simple advertising on the Please Wait, Thank You, and Welcome screens through data dictionary entries.

Images - user-defined JPG only images can display on the Welcome screen and on the English and Spanish Please Wait screens. Images must be in the c:\webatm\webpages\images directory on the ATM. When multiple images are defined for a screen, the images will be cycled through sequentially, one after another, until the next action for the transaction occurs (such as host replies during a Please Wait, or cardholder inserts a card on the Welcome). You can define as many images per screen as desired (no upper limit).

Text messages - text messages, in both English and Spanish, can display on the Please Wait, Thank You and Welcome screens. These will display in approximately the center of



the screen using the default background. You can define as many text messages per screen as desired (no upper limit).

The data dictionary entries to support this advertising are shown the tables below. These entries can be changed remotely when necessary.

Note: the actual image .jpg files used ore the images must be distributed either through software distribution, or copied onto the ATM through copyfile.

Field Name Description

NUMBEROFIMAGEWAIT Specifies the number of images to display on the Please Wait screen (whether English or Spanish).

NUMBEROFIMAGEWELCOME

Specifies the number of images to display on the Welcome screen.

IMAGEWAIT[1-x] Image files to play on the Please Wait screen. The total number of images is determined by the CONSUMERFLOW.NUMBEROFIMAGEWAIT entry. Images must be in the c:\webatm\webpages\images directory on the ATM.

IMAGEWAIT[1-x]SPA Image files to play on the Spanish Please Wait screen. The total number of images is determined by the CONSUMERFLOW.NUMBEROFIMAGEWAIT entry. Images must be in the c:\webatm\webpages\images directory on the ATM.

IMAGEWELCOME[1-x] Image files to play on the Welcome screen. The total number of images is determined by the CONSUMER FLOW.NUMBEROFIMAGEWELCOME entry. Images must be in the c:\webatm\webpages\images directory on the ATM.


NUMBEROFMSGTHANK Specifies the number of text messages to display on the Thank You screen.

MSGTHANK[1-x] Specifies the text message to display on the Thank You screen in English.

MSGTHANK[1-x]SPA Specifies the text message to display on the Thank You screen in Spanish.

NUMBEROFMSGWAIT Specifies the number of text messages to display on the English Please Wait screen.

MSGWAIT[1-x] Specifies the text message to display on the Please Wait screen in English.

MSGWAIT[1-x]SPA Specifies the text message to display on the Please Wait screen in Spanish.

NUMBEROFMSGWELCOME

Specifies the number of text messages to display on the Welcome screen.




MSGWELCOME[1-x] Specifies the text message to display on the Welcome screen in English.

MSGWELCOME[1-x]SPA Specifies the text message to display on the Welcome screen in Spanish.

NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>) Example:

The following parameters display text messages on the Please Wait and Thank You screens and two images on both the English and Spanish Please Wait screens.

CONSUMERFLOW.NUMBEROFMSGWAIT=1 CONSUMERFLOW.MSGWAIT1=We have new Line of Credit rates. Watch your mailbox for details. CONSUMERFLOW.NUMBEROFMSGTHANK=1 CONSUMERFLOW.MSGWAIT1=We have added 10 new ATMs in your areas for your banking convenience. CONSUMERFLOW.NUMBEROFIMAGEWAIT=2 CONSUMERFLOW.IMAGEWAIT1=Graduate.jpg CONSUMERFLOW.IMAGEWAIT2=House.jpg CONSUMERFLOW.IMAGEWAIT1SPA=Graduate1.jpg CONSUMERFLOW.IMAGEWAIT2SPA=House1.jpg

2.3 Modify the Currency Cassette Values

The cassette media types and values are set when the ATM is installed. If necessary, these can be changed by the replenisher if he has access to the configuration menus, or remotely if the replenisher does not have access to the configuration menus. If these are changed remotely, your changes need to be coordinated with the replenisher, or the ATM will be out of balance.

Each cassette has the four entries in the dd.dat; however, the only one you will probably want to change is the denomination in the cassette (CURRENCY.CASSETTExVALUE). If you change the media in a cassette (from cash to stamps, for example), you would also need to change CURRENCY.CASSETTExUNITTYPE.




CASSETTE1-4UNITTYPE A code representing the type of media stored in cassette #1-4, where 0=cash, 1=stamps, and 2=other documents.

CASSETTE1-4VALUE The denomination of the notes, in whole dollars, in cassette 1-4.

Example:

The following parameter changes the denomination in cassette 1 to $20 bills

CURRENCY.CASSETTE1VALUE=20

2.4 Modify Fee Values

The data dictionary entry for the fee (surcharge) associated with a transaction needs to be set in the data dictionary only if the fee amount is stored locally and not sent from host. In this case, the fee displays to the cardholder before the transaction request is sent to host.

If the fee is not stored locally, and is always sent from host, nothing needs to be set in the data dictionary.

If the fee needs to be displayed before the transaction request is sent to host, the fee value is defined in the CONSUMERFLOW.TransactionNameFEE and CONSUMERFLOW.TransactionNameFEEOPTION data dictionary entries, where TransactionName can be any of the valid transactions defined in the consumer flow. Each transaction can have a unique fee value associated with it.


TransactionNameFEE Specifies the fee charged for a TransactionName transaction. The fee value should be entered as numeric digits with a single decimal point.

0.00

TransactionNameFEEOPTION

Specifies that a fee will be charged for TransactionName. This is a Yes or No value.

No

Example:

The following parameters in the dd.dat set the fees for the Withdrawal, Fast Cash 1, FIT1 Fast Cash 1 and Fast Cash 2 transactions.

CONSUMERFLOW.WITHDRAWALFEE=1.00 CONSUMERFLOW.WITHDRAWALFEEOPTION=YES CONSUMERFLOW.FASTCASH1FEE=1.50 CONSUMERFLOW.FASTCASH1FEEOPTION=YES



CONSUMERFLOW.FIT1FASTCASH1FEE=2.00 CONSUMERFLOW.FASTCASH2FEEOPTION=YES CONSUMERFLOW.FASTCASH2FEE=1.50 One final entry that controls Fees is the DISPLAYSURCHARGEPERTRANS entry. This entry applies per session and determines whether a cardholder will see the fee for every transaction that has a fee associated with it, or if the cardholder will see the fee screen only on the first surcharged transaction, regardless of the number of surcharged transactions he performs during his session.

YES=present fee screen on every surcharged transaction

NO=show surcharge screen only on first surcharged transaction Example:

The following parameter will display the surcharge screen to the cardholder for all surcharged transactions he performs during his session.

COMSUMERFLOW.DISPLAYSURCHARGEPERTRANS=YES

2.5 Modify Personalization

Note: Implementation and support of this transaction required a custom PS Engagement.

The APTRA Edge Personalization transaction allows you to define/modify a series of screens that permit a cardholder to "Personalize" certain transactions and aspects of transactions; for example, define his personal Fast Cash withdrawal amount, preferred language or receipt print/no print preference. This information is then stored on a Customer Relationship Management (CRM) server that is accessible to APTRA Edge.

Within APTRA Edge, a cardholder accesses the personalization transaction either from an automatically displayed screen (Want to set preferences screen), or from a button on the Main Menu (ATM Preferences). When the cardholder selects Yes to the "Want to set preferences" screen, or presses the ATM Preferences button, he is taken to a screen that contains the items he can personalize. Personalization choices that can be included are:

Language Selection

Fast Cash Withdrawal Amount

Print/no print Receipt for:

Personalized Fast Cash transaction only

All Fast Cash and Withdrawal transactions

All Other Transactions To add/change Personalization, you need to modify data dictionary entries. These data dictionary entries define the Personalization choices you want to make available to your cardholders, and to what cardholders (FITs) to make them available. The Personalization data dictionary entries that control these options are explained in the next three sections.



2.5.1 Personalization Transaction Main Menu Button

The main menu button for Personalization is implemented as a non-transaction button that points to a webpage. To include the Personalization transaction on a menu, you need to include the following CONSUMERFLOW data dictionary entry, and it must be the last non-transaction button you define among all your non-transaction buttons.

CONSUMERFLOW.NONTRANSBUTTONx=ATM Preferences,1,2,0,PreferencesMenu. htm,2500

This entry is described in the following bullets.

• NONTRANSBUTTONx - x is the number of the non-transaction button (up to 40 can be supported in APTRA Edge), but this must be the last one you define. For example, if you have six non-transactions button in all, the Personalization button must be non-transaction button 6.

ATM Preferences - is the text that will appear on the button

1,2,0 - 1 is the menu on which you want the transaction to display, 2 is the button number on that menu and 0 is normally a submenu number, but in this case it is a placeholder because the button actually points to a webpage

PreferencesMenu.htm - the fixed name of the webpage for the ATM Preference transaction

2500 - the fixed TextENG.js file message number to display on the PreferencesMenu.htm when it displays

2.5.2 CRMService Group Entry

This entry allows you to define when APTRA Edge should retrieve a cardholder's preferences from the CRM server.


INITIATE Defines when to retrieve the cardholder's preferences. Value are: AFTERCARD - immediately after card is inserted/dipped/swiped AFTERPIN - after cardholder enters his PIN NEVER - Personalization not available on this ATM

Never

To make sure you get the consumer flow you want, you need to take the order of your Language Selection and PIN Entry screens into consideration when you set the INITIATE entry to AFTERPIN.

If you set CONSUMERFLOW.LANGUAGEFIRSTANDPINNEXT to Yes (see next

section), the cardholder will always have to select his language regardless of whether or not he sets his language preference.



If you set CONSUMERFLOW.LANGUAGEFIRSTANDPINNEXT to No (which means the Enter PIN screen will display before the Language Selection screen), and the cardholder has his language preference set already, the cardholder will not see the Select Language screen because his language preference will already have been sent to the ATM from the CRM server.

2.5.3 CONSUMERFLOW Group Entries

These entries define the personalization screens that will display to cardholders.


CRMSERVICETIMEOUTBEFOREPLEASEWAIT

Number of seconds to wait before displaying the Please Wait screen while getting Preferences from the CRM server. If a response is received before this timer expires, the flow will proceed to the Enter PIN screen. Otherwise the flow will go to the Please Wait while waiting for a response from the server. If set to 0, the Please Wait screen will always display.

0

DISPLAYMESSAGEWHENPREFERENCESUNAVAILABLE

If preferences are unavailable for some reason, setting this to Yes will display a message on the Language or PIN screen (whichever comes first) stating that Preferences are Temporarily Unavailable.

No

DISPLAYPERSONALIZEDOTHERAMOUNTBUTTON

Yes/No entry that determines whether or not to display an Other Amount button on the personalized Fast Cash screen.

LANGUAGEFIRSTANDPINNEXT

This entry determines the order that the Language selection and PIN Entry screens will display to the cardholder. Values are: YES - display language screen first NO - display PIN entry screen first

Yes

NEVERSETPREFERENCEBUTTON

Yes puts a button on the "Do you want to set Preferences" screen that says “Never Set Preferences.” This button is in addition to the Yes and No buttons.

No

PERSONALIZATIONCARDFITS

FITs to which Personalization is available. Values are ALL (all FITs) or a comma-separated list of individual FITs. For example, PERSONALIZATIONCARDFITS=1,2,3 allows personalization and stores preferences only for Fits 1, 2 and 3.




PERSONALIZEDENTERAMOUNTSCREEN

Yes/No entry that determines whether or not to allow cardholders to define a Personalized Fast Cash amount. When you select Yes, you must also define the menu buttons as explained in the next entry -PERSONALIZEDFASTCASHMENUBUTTONS.


Specifies whether a Personalized Fast Cash transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. The button text is defined in message 9044 in the TextENG.js file.

No


Defines the accounts that can be used for a personalized Fast Cash transaction. The accounts you want to make available should be contained in a comma separated list. If you make only 1 account available, checking for example, then the Select Account screen will not display to the cardholder during the Personalized Fast Cash transaction. These entries must match the account types defined in your CONSUMERFLOW.ACCOUNT1-x data dictionary entries.

1 (checking)

PERSONALIZEDFASTCASHMENUBUTTONS

Defines the layout of the personalized Fast Cash amount selection screen. The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the dollar amount to display on the button as the second entry in the pair. For example, to define button position 1-6 with the dollar values 20, 60, 60, 100, 140 and 200, you would use PERSONALIZEDFASTCASHMENUBUTTONS =1,20,2,40,3,60,4,100,5,140,6,200. Button position 7 is reserved for the No Preference: Always Ask button, if it is desired You can also define an Other Amount button for the Fast Cash amount screen. See DISPLAYPERSONALIZEDOTHERAMOUNTBUTTON and PERSONALIZEDOTHERAMOUNTPOSITIONFASTCASHMENU.




PERSONALIZEDNOPREFERENCEOTHERAMOUNTPOSITION

This specifies the position of the No Preference: Always Ask button on the Personalized Fast Cash amount selection screen. Currently, this button must be in position 7.

7

PERSONALIZEDOTHERAMOUNTPOSITIONFASTCASHMENU

Defines the Other Amount button location (1-8) on the Personalized Fast Cash screen. Button 7 is reserved and cannot be used. The DISPLAYPERSONALIZEDOTHERAMOUNTBUTTON entry determines whether or not this button is included on the menu.

SHOWWANTTOENTERPERFERENCESSCREEN

Yes/No entry that specifies whether or not to show a screen that allows the cardholder to enter preferences if he has no preferences defined already. If set to Yes, this screen will display after the PIN entry screen regardless of whether the CRMSERVICE.INITIATE is set to AfterCard or AfterPIN.

UPDATEPREFERENCESWHENSESSIONCLOSES

Yes/No entry that determines when a cardholder's preferences are saved. If set to Yes, his preferences will not be saved until the end of the session, avoiding the delay of sending to host during the session. If set to No, the cardholder's preferences are sent to host when the cardholder presses the Save button on the preferences screen.

Yes

Example:

The following parameters define the personalization transaction available to FIT 1. APTRA Edge application will retrieve the cardholder's personalization setting immediately after he enters his PIN. A "Want to set preferences" screen will display to the cardholder if he has not already defined his preferences. The ATM Preferences transaction selection button will appear on menu 1 in button position 2.

The Enter PIN screen will display before the Language Selection screen. This works well when CRMSERVICES.INITIATE=AFTERPIN because if the cardholder has his language preference set, he will never see the Language Selection screen.

The Personalized Fast Cash transaction selection button appears on menu 1 in button position 4.

The Fast Cash account selection screen will not display because only the checking account (1) is defined for the Personalized Fast Cash Accounts. The Fast Cash Amount preference screen will contain six amounts: $20 on button 1, $40 on button 2, $60 on button 3, $100 on button 4, $140 on button 5 and $200 on button 6. Button position 7 will, by default, contain the "No



Preference: Always Ask" selection. No "Other Amount" button will display on the Fast Cash personalization menu.

The UpdatePreferencesWhenSessionCloses entry is set to Yes, so the cardholder's preferences will not be saved until the end of the session and this will avoid the delay during the session.

CRMSERVICES.INITIATE=AFTERPIN CONSUMERFLOW.NONTRANSBUTTON3=ATM Preferences,1,2,0,PreferencesMenu .htm,2500 CONSUMERFLOW.PERSONALIZATIONCARDFITS=1 CONSUMERFLOW.LANGUAGEFIRSTANDPINNEXT=NO CONSUMERFLOW.PERSONALIZEDFASTCASH=Yes,1,4 CONSUMERFLOW.SHOWWANTTOENTERPERFERENCESSCREEN=YES CONSUMERFLOW.PERSONALIZEDFASTCASHACCOUNTS=1 CONSUMERFLOW.PERSONALIZEDFASTCASHMENUBUTTONS=1,25,2,50,3,100,4,200 CONSUMERFLOW.DISPLAYPERSONALIZEDOTHERAMOUNTBUTTON=NO CONSUMERFLOW.UPDATEPREFERENCESWHENSESSIONCLOSES=YES

2.6 Convert from Envelope Deposit to Enhanced Deposit

When you convert an ATM from Envelope Deposits/Payments to Enhanced Deposits, you need to disable all Envelope data dictionary entries and enable all Enhanced Deposits entries. This is because Envelope transactions cannot currently coexist with Enhanced Deposit transactions due to hardware restrictions.

The data dictionary entries you need to modify are from a variety of groups. These are explained in this section by group.

2.6.1 BNA Group

The BNA (Bunch Note Acceptor) group controls the operation of the BNA. You need to review these entries and set them to values that fit your needs.


COMMSTIMEOUT Amount of time, in milliseconds, to wait for the BNA to become enabled.

ENABLETIMEOUT Amount of time after the bunch note acceptor receives an enable signal that it will wait for the customer to insert the first bill. A value of 0 defers to the BNA default value of 40 seconds.

0

MAXBILLS Specifies the maximum number of bills a customer can insert into the BNA at one time.



2.6.2 CASHDEPOSIT Group

There is currently only one entry in this group.


SENDUNSOLICITEDMESSAGE

This entry determines whether or not an unsolicited message will be sent to host when the BNA becomes inoperable. True - send message False - do not send message

False

2.6.3 CHECK Group

The Check group controls check imaging and image archiving.


ARCHIVEDIR Directory on the ATM to where the check files are moved when they are archived.

0

BATCHFILENAME Used in the journal.xml to identify the name of the check batch file and by supervisor to find the check batch file.

ENDORSEMENTPRINTZONE

This entry is used with a multiple line endorser only. The entry defines the print zone on the back of the check in which the endorsement will print. There are two possible entries: 0 for zone 1 and 1 for zone 2. See the endorsement discussion in Appendix E in this document for more information.

1

IMAGERESOLUTION The resolution of the check image file in dpi. 200 LIFTFRONT If True, captures the image of the front of the

check.

LIFTREAR If True, captures the image of the back of the check.

NBRIMAGEARCHIVES Tells how many image archives to store in the archive directory. When creating a new archive causes the total archives to be greater than this number, the system deletes the oldest archive. If this field does not appear in the data dictionary, archives are not deleted.




NUMBEROFDAYS Specifies the number of days to keep files in the Upload directory. This directory contains Enhanced Deposit files and can also contain EJ and Activity log files. The default is 14. This entry is only relevant when CHECK.UPLOADARCHIVE is set to Yes.

14

RETURNCHECKTIMEOUT

Number of seconds of time after the CPM returns a check that the ATM will wait for the customer to take the check before it is retracted.

SCANCHECKTIMEOUT Specifies the number of seconds the system waits for the customer to insert a check before timing out.

UPLOADARCHIVE If set to Yes, the Deposit End of Day service will copy the EJ and activity log files to the Upload directory and it is assumed that all files in this directory will be uploaded. Set this entry to No if you will not be uploading the files in the Upload directory. If you set this entry to No, the Deposit End of Day service will delete everything in the Upload directory at end of day. The default is No.

No

2.6.4 CHECKDEPOSIT Group

The CheckDeposit group addresses validation of the check and host notification if the iTran 1000 becomes inoperable.



This entry determines whether or not an unsolicited message will be sent to host when the iTran 1000 becomes inoperable. True - send message False - do not send message

False

VALIDATEENDORSEMENT

Specifies whether or not the check endorsement should be validated before a check is accepted by the CPM.

VALIDATEMICR Specifies whether or not the check MICR should be validated before a check is accepted by the CPM.



2.6.5 CONSUMERFLOW Group

There are two types of entries you must modify in the CONSUMERFLOW group: entries that turn off Envelope transactions, and entries that control the Enhanced Deposit transaction.

2.6.5.1 Disable Envelope Transactions

If you have any of these set to Yes, you must change it to No when you add Enhanced Deposits.


DEPOSITWITHCASHBACK

Specifies whether the Deposit with Cash Back transaction is included in the Consumer Flow.

No

ENVELOPEDEPOSIT Specifies whether the Envelope Deposit transaction is included in the Consumer Flow.

No

ENVELOPEPAYMENT Specifies whether the Envelope Payment transaction is included in the Consumer Flow.

No


Specifies whether an Envelope Payment From Account transaction is included in the Consumer Flow.

No


Specifies whether an Envelope Payment To Account transaction is included in the Consumer Flow.

No

MESSAGETOBANK Specifies whether the Message to Bank transaction is included in the Consumer Flow.

No

2.6.5.2 Enable and Configure Enhanced Deposits

The entries enable and control different aspects of the Enhanced Deposit transaction.


DEPOSITSPERRECEIPT Specifies the number of consecutive check and/or cash deposits that will print on a single receipt. Values are: 0 - all deposits on one receipt; do not cut receipt until cardholder selects "Deposit Complete" (default) Specific value - print only this number of deposits on a receipt, then cut.

0




ENHANCEDDEPOSIT Specifies whether the Enhanced Deposit transaction using the BNA and CPM is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No


Specifies the accounts (ACCOUNT1-x) available for Envelope Deposit or Enhanced Deposit transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ENVELOPEDEPOSITACCOUNTS =,,,,1,2,,. Note: this entry is also used by Enhanced Deposits because Envelope Deposits and Enhanced Deposits are mutually exclusive.

ENHANCEDDEPOSITFEE

Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

ENHANCEDDEPOSITFEEOPTION

Specifies that a fee is charged for this transaction. The FEE must also be set.

No

ENHANCEDDEPOSITMODE

Specifies how the Enhanced Deposit transaction flow should behave and depends upon the hardware installed on the ATM. Values are: 0 - both iTran 1000 and BNA installed 1 - iTran 1000 only installed 2 - BNA only installed

0

ENHANCEDDEPOSITRECEIPTOPTION

Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for this transaction. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt.

Yes




FORCEENHANCEDDEPOSITS

Yes/No entry that determines whether or not to send a normal transaction completion to host during an Enhanced Deposit when a jam or some other condition occurs but it is certain that ATM does have the check or bills.

No

2.6.6 NDCPROXYCUSTOMIZTION Group


ENHANCEDDEPOSITMODE

This entry synchronizes the Business Services with the data dictionary. When Enhanced Deposits are used on the ATM, this entry must be set to MigrationEmulation. A reboot is required after adding this entry.

2.6.7 STARTOFDAY Group

You need to deactivate the Program Ids for all Envelope transactions and activate the Program IDs for Enhanced Deposits.


CASHDEPOSITPROGID Cash Deposit Program ID—Must be CashDepositTxn.CashDeposit. This entry is for Enhanced Deposits. It must be blank if Enhanced Deposits are not being used.

CASHDEPOSITTRANSLETID

Translet ID of the Cash Deposit TXO—must be ENVDEPOSIT

CBENVDEPOSITPROGID Deposit with Cash Back Deposit Program ID—must be: DepositTxn.Deposit. When Enhanced Deposits are used, this entry must be blank.

CHECKDEPOSITPROGID Check Deposit Program ID—Must be NCRCheckDeposit.CheckDeposit. The Check Deposit program does the deposit-specific processing. This entry is for Enhanced Deposits. It must be blank if Enhanced Deposits are not being used.




CHECKDEPOSITTRANSLETID

Translet ID of the Check Deposit TXO—must be ENVDEPOSIT

CHECKSERVICEPROGID

Check Service Program ID—Must be NCRCheck.Check. The Check program does the CPM-related processing. This entry must be blank if Enhanced Deposits are not being used.

ENHDEPEODPROGID Enhanced Deposit End of Day Program ID—must be: EnhDepEOD.EnhDepEODTXn. . This entry is for Enhanced Deposits. It must be blank if Enhanced Deposits are not being used.

ENVDESPOSITPROGID Envelope Deposit Program ID - DepositTxn.Deposit. When Enhanced Deposits are used, this entry must be blank.

ENVPAYMENTPROGID Envelope Payment Program ID - DepositTxn.Deposit. When Enhanced Deposits are used, this entry must be blank.

ENVPMTFROMACCTPROGID

Envelope Payment From Account Program ID — DepositTxn.Deposit. When Enhanced Deposits are used, this entry must be blank.

ENVPMTFROMACCTTRANSLETID

Translet ID of the Envelope Payment From Account TXO—must be ENVPMTFROMACCT. When Enhanced Deposits are used, this entry must be blank.

ENVPMTTOACCTPROGID

Envelope Payment To Account Program ID — DepositTxn.Deposit. When Enhanced Deposits are used, this entry must be blank.

ENVPMTTOACCTTRANSLETID

Translet ID of the Envelope Payment To Account TXO—must be ENVPMTTOACCT. When Enhanced Deposits are used, this entry must be blank.

MESSAGETOBANKPROGID

Message To Bank transaction Program ID – must be DepositTxn.Deposit. When Enhanced Deposits are used, this entry must be blank.




MESSAGETOBANKTRANSLETID

Translet ID of the Message To Bank TXO - must be MESSAGETOBANK. When Enhanced Deposits are used, this entry must be blank.

PRINTDEPOSITTOTAL Yes/No entry used with check and cash deposits (Enhanced Deposits) that determines whether a locally maintained deposit total will be printed on the cardholder’s receipt (Yes), or if this locally maintained deposit total will not be printed on the receipt (No). If host sends the deposit total to print on the receipt, this local total printing can be redundant.

2.6.8 SUPERVISOR Group

This entry controls the content of the printed receipt when Local Totals are printer or cleared.


PRINTCHECKLIST Determines whether or not a list of all checks deposited through the Enhanced Deposit transaction will be printed when the local totals are printed or cleared. When printed, the list contains the Sequence #, Amount and Time Stamp for each individual check deposited since the last time local totals were cleared. The default for this entry is No (do not print check list).

No

Example

The following parameters define an Enhanced Deposit transaction available to all FITs. The BNA entries are set as follows. The application will wait for 120,000 milliseconds for the BNA to become enabled. It will wait 60 seconds for the cardholder to insert his first bill. A maximum of 40 bills can be entered at one time.

A message will be sent to host when either the BNA or iTran 1000 becomes unavailable. This is defined by the SENDUNSOLICITEDMESSAGE=True entry for the CASHDEPOSIT and CHECKDEPOSIT groups.

The archive directory for check images has been defined as c:\archivedir\check. The check batch file is located in the c:\webatm directory and is named check.xml. No entries with



defaults are included which means the default values will be used for CHECK.ENDORSEMENTPRINTZONE, CHECK.IMAGERESOLUTION, CHECK.NUMBEROFDAYS and CHECKUPLOADARCHIVE. The front image of the check will be captured, but not the rear image. 100 image archives will be maintained and both timeouts, Scancheck and ReturnCheck, are set to 30 seconds.

The CHECKDEPOSIT entries determine that the MICR will be validated, but the endorsement will not.

The CONSUMERFLOW section has all envelope related transactions turned off and the Enhanced Deposit transaction turned on. The Deposit transaction will appear on menu 1 in button position 4. Four accounts are defined as being available for deposits (defined by the CONSUMERFLOW.ENVELOPEDEPOSITACCOUNTS=,,,,1,2,3,4 Entry). No fee is charged for an Enhanced Deposit transaction. Both a BNA and iTran 1000 are installed on the ATMs as determined by the CONSUMERFLOW.ENHANCEDDEPOSITMODE=0 entry. A forced deposit will occur if a jam occurs. And finally, a maximum of two Enhanced Deposits will print per receipt.

The STARTOFDAY section has all envelope transaction-related Program IDs and Translet IDs configured to be removed.

The final entry, SUPERVISOR.PRINTCHECKLIST=YES, specifies that a list of checks will be printed when local totals are cleared.

BNA.COMMSTIMEOUT=120000 BNA.ENABLETIMEOUT=60 BNA.MAXBILLS=40 CASHDEPOSIT.SENDUNSOLICITEDMESSAGE=TRUE CHECK.ARCHIVEDIR=c:\archivedir\check CHECK.BATCHFILENAME=c:\webatm\check.xml CHECK.LIFTFRONT=True CHECK.LIFTREAR=False CHECK.NBRIMAGEARCHIVES=100 CHECK.RETURNCHECKTIMEOUT=30 CHECK.SCANCHECKTIMEOUT=30 CHECKDEPOSIT.SENDUNSOLICITEDMESSAGE=TRUE CHECKDEPOSIT.VALIDATEENDORSEMENT=False CHECKDEPOSIT.VALIDATEMICR=True CONSUMERFLOW.DEPOSITWITHCASHBACK=No CONSUMERFLOW.ENVELOPEDEPOSIT=No CONSUMERFLOW.ENVELOPEPAYMENT=No CONSUMERFLOW.ENVELOPEPAYMENTFROMACCOUNT=No CONSUMERFLOW.ENVELOPEPAYMENTTOACCOUNT=No CONSUMERFLOW.MESSAGETOBANK=No CONSUMERFLOW.DEPOSITDENIALLINES=0 CONSUMERFLOW.DEPOSITSPERRECEIPT=2 CONSUMERFLOW.ENHANCEDDEPOSIT=Yes,1,2 CONSUMERFLOW.ENHANCEDDEPOSITMODE=0



CONSUMERFLOW.ENVELOPEDEPOSITACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.ENHANCEDDEPOSITFEE=0.00 CONSUMERFLOW.ENHANCEDDEPOSITFEEOPTION=No CONSUMERFLOW.ENHANCEDDEPOSITRECEIPTOPTION=Yes CONSUMERFLOW.FORCEENHANCEDDEPOSITS=Yes STARTOFDAY.CBENVDEPOSITPROGID STARTOFDAY.CBENVDEPOSITTRANSLETID STARTOFDAY.CBWITHDRAWALPROGID STARTOFDAY.CBWITHDRAWALTRANSLETID STARTOFDAY.CASHDEPOSITPROGID= CashDepositTxn.CashDeposit STARTOFDAY.CASHDEPOSITTRANSLETID= ENVDEPOSIT STARTOFDAY.CHECKDEPOSITPROGID= NCRCheckDeposit.CheckDeposit. STARTOFDAY.CHECKDEPOSITTRANSLETID=ENVDEPOSIT STARTOFDAY.CHECKSERVICEPROGID=NCRCheck.Check STARTOFDAY.ENHDEPEODPROGID=EnhDepEOD.EnhDepEODTXn STARTOFDAY.ENVDEPOSITPROGID STARTOFDAY.ENVDEPOSITTRANSLETID STARTOFDAY.ENVPAYMENTPROGID STARTOFDAY.ENVPAYMENTTRANSLETID STARTOFDAY.ENVPMTFROMACCTPROGID STARTOFDAY.ENVPMTFROMACCTTRANSLETID STARTOFDAY.ENVPMTTOACCTPROGID STARTOFDAY.ENVPMTTOACCTTRANSLETID STARTOFDAY.MESSAGETOBANKPROGID STARTOFDAY.MESSAGETOBANKTRANSLETID SUPERVISOR.PRINTCHECKLIST=YES

2.7 Controlling Deposit Disclaimers

The displaying of a Disclaimer screen for Deposit transactions is controlled by the data dictionary entry:

CONSUMERFLOW.SHOWDEPOSITDISCLAIMER

If this entry is set to Yes, the disclaimer screen will display. The text for this screen is defined in message 2600 in the TextXXX.js file.

If this entry is set to No, a disclaimer screen will not display for Deposit transactions.

2.8 Controlling the Paper Journal

The paper journal for APTRA Edge is turned off by default. To turn the paper journal on, you need to set the following entry in the data dictionary:

JOURNAL.PAPERJOURNAL=True

Also by default, only Host data is logged. However, you can also have TXO data logged, if desired. The data dictionary entries that control the data logged are:

STARTOFDAY.JOURNALHOSTDATA STARTOFDAY.JOURNALTXODATA



2.9 Configuring a Forced Account Balance Transaction

This section explains the configuration of the APTRA Edge Forced Account Balance transaction. A Forced Account Balance transaction provides, normally to foreign cardholders, the opportunity to perform a Balance Inquiry prior to viewing the main transaction menu. This is considered a revenue generating transaction because the cardholder is normally charged for the Balance Inquiry. Note: this implementation is not restricted to the Account Balance transaction. Any transaction can be set up this way.

In a consumer flow that includes a Forced Account Balance, the first screen a foreign cardholder will see after he performs his normal login is a screen that offers a Balance Inquiry transaction and a button to bypass this transaction, similar to the screen below.

This screen is defined as a menu screen - the first menu in the foreign cardholder flow.

If the cardholder elects to perform a Balance Inquiry transaction by pressing the Balance Inquiry button, the flow proceeds to a normal Balance Inquiry transaction.

If the cardholder elects not to perform a Balance Inquiry and presses the Main Menu button, the flow proceeds to the normal main transaction menu.

2.9.1 Define Your FITs and Menus

As was stated earlier, the Forced Account Balance screen is a menu - menu 1 in the flow. If you already have menus defined for this FIT, you will need to increment each menu in your scheme by 1. If you do not already have menus defined by FIT, you will have to define a menu scheme, with this menu being the first. See Modify Transaction Flow Based on FIT Value for more information.



After you have your FIT menu scheme defined, you need to identify what menu should be considered the Primary menu; that is, the menu to which the foreign cardholder will be taken:

after he performs the Balance Inquiry (assuming transaction chaining is on),

if he skips the Balance Inquiry transaction,

or if he answers Yes to the question “Do you want another transaction?” at the end of any transaction (again assuming chaining is on).

When transaction chaining it on, all normal transaction chaining rules apply at the end of the Balance Inquiry transaction (such as the requirement to re-enter the PIN if that option is turned on).

If transaction chaining is off, the session will end after the Balance Inquiry. See Modify the Card Reader Options for more information about transaction chaining.

The data dictionary entries that support the setup of the Forced Account Balance flow includes FIT entries and menu setup entries for these FITs.

2.9.1.1 Data Dictionary FIT Entries

The data dictionary entries used to setup your FITs are:

CONSUMERFLOW.NUMBEROFFITCONSUMERTYPE - specifies the number of consumer types associated with the FIT table up to a maximum of 15.

CONSUMERFLOW.FITCONSUMERTYPE[1-x] - specifies the FIT value to use for matching to specific menu selections. The number “1” can be replaced with other numbers up to “15” to represent the maximum of 15 consumer types.

The following two sample entries set up one FIT defined as index 1.

CONSUMERFLOW.FITCONSUMERTYPE1=1 CONSUMERFLOW.NUMBEROFFITCONSUMERTYPE=1

2.9.1.2 Data Dictionary Menu Setup Entries

The data dictionary menu flow entries required for the Forced Account Balance transaction define:

the menus on which the Balance Inquiry transaction will appear (always menu 1 and usually also on another menu)

a non-transaction button that allows the cardholder to bypass the Balance Inquiry transaction and proceed to the main menu (Primary menu)

the menu that is the Primary menu. There is only one menu set up entry that is new:

CONSUMERFLOW.FITxPRIMARYMAINMENU – specifies the menu to which the cardholder will be taken after he performs the Balance Inquiry transaction, or if he elects not to perform the Balance Inquiry in a Forced Account Balance flow.



For your existing menu entries, you now need to precede them with a FIT number to apply them to one or more FITs. If you are defining the Forced Account Balance transaction for multiple FITs, you would have to define multiple iterations of these entries, one for each FIT.

The sample data dictionary entries below show a typical flow for FIT1. They define:

the Balance Inquiry on two menus – 1 and 2 (line 1)

a non transaction button called Main Menu on the Forced Account Balance menu (menu 1) (lines 2 and 3)

menu 2 as the menu to which the cardholder will be taken after he performs his Balance Inquiry (with chaining on), or if he elects not to perform the Balance Inquiry, but rather presses the Main Menu button.

CONSUMERFLOW.FIT1ACCOUNTBALANCE=YES,1,7,YES,2,7 CONSUMERFLOW.FIT1NUMBEROFNONTRANSBUTTONS=2 CONSUMERFLOW.FIT1NONTRANSBUTTON1=Main Menu,1,8,2 CONSUMERFLOW.FIT1PRIMARYMAINMENU=2

2.9.2 Forced Account Balance Screen Text and Voice Guidance

The TextENG.js message number for the text on the Forced Account Balance screen is 2080_0x1, where x equals the index number assigned for foreign cards (the n value of the dd entry CONSUMERFLOW.FITCONSUMERTYPE1=n).

The voice guidance template number for the SoundENG.xml file is the same number as the message number you use for the TextENG.js file using the FIT index number.

For example, if you use:

var vMessage2080_011 = "Would you like to have an account balance?";

for FIT1 for the TextENG.js file, you would use <Template name="2080_011"> for the equivalent voice guidance lead-through.

2.9.3 Define Your Button Labels

The button label for the Account Balance button is fixed, but the Main Menu button label is not. You could, for example, use a “No Thanks You” button instead of the Main Menu button. To do this, you need to add a No Thank You button label into the Non-Transaction Main Menu Button Text Messages 5000-5999 group in the TextENG.js file and then use that button text on this menu. In this case, the entry:

CONSUMERFLOW.FIT1NONTRANSBUTTON1=Main Menu,1,8,2 in the above example would be replaced with:

CONSUMERFLOW.FIT1NONTRANSBUTTON1=No Thank You,1,8,2



The following entries setup main menu 2, which is also the primary menu:

CONSUMERFLOW.FIT1FASTCASH1=YES,2,1 CONSUMERFLOW.FIT1TRANSFER=YES,2,2 CONSUMERFLOW.FIT1ENVELOPEDEPOSIT=YES,2,3 CONSUMERFLOW.FIT1ENVELOPEPAYMENT=YES,2,4 CONSUMERFLOW.FIT1WITHDRAWAL=YES,2,5 CONSUMERFLOW.FIT1STAMP=YES,2,6 CONSUMERFLOW.FIT1NONTRANSBUTTON2=Next Menu,2,8,3

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE DATA DICTIONARY ENTRIES BY TRANSACTION CROSS-REFERENCE


3 Data Dictionary Entries by Transaction Cross-Reference

This section contains a listing of the most commonly changed data dictionary entries by transaction, settlement and supervisor. Since you now have a general understanding of how the application can be controlled through the data dictionary, you can use this section as a quick reference to make sure you get what you want when you make a change to a transaction, settlement or supervisor through a DDUpdate.

For a full description or additional information about these entries, refer to Appendix B.

3.1 Account Balance Inquiry

CONSUMERFLOW.ACCOUNTBALANCE – turns on and off the Account Balance Inquiry transaction

CONSUMERFLOW.ACCOUNTBALANCEACCOUNTS – sets the account for which an Account Balance Inquiry transaction can be performed

CONSUMERFLOW.ACCOUNTBALANCEFEE – sets the fee amount for an Account Balance Inquiry transaction

CONSUMERFLOW.ACCOUNTBALANCEFEEOPTION – turns on and off the fee association for an Account Balance Inquiry transaction

CONSUMERFLOW.ACCOUNTBALANCERECEIPTOPTION – turns on and off the option to allow a cardholder to not print a receipt for the Account Balance Inquiry transaction

CONSUMERFLOW.DISPLAYBALANCERECEIPTOPTION – optionally displays a screen to allow cardholder to Display, Print and Display & Print his balance(s)

CONSUMERFLOW.DISPLAYPRINTRECEIPTBUTTON – optionally displays a button on the Balance Inquiry screen to allow a cardholder to both Display & Print his balance

3.2 Change PIN

CONSUMERFLOW.CHANGEPIN – turns on and off the Change PIN transaction

CONSUMERFLOW.CHANGEPINFEE - sets the fee amount for a Change PIN transaction

CONSUMERFLOW.CHANGEPINFEEOPTION - turns on and off the fee association for a Change PIN transaction

CONSUMERFLOW.CHANGEPINRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Change PIN transaction



3.3 Check Reorder

CONSUMERFLOW.CHECKREORDER– turns on and off the Check Reorder transaction

CONSUMERFLOW.CHECKREORDERFEE - sets the fee amount for a Check Reorder transaction

CONSUMERFLOW.CHECKREORDERFEEOPTION - turns on and off the fee association for a Check Reorder transaction

CONSUMERFLOW.CHECKREORDERRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Check Reorder transaction

3.4 Deposit with Cash Back

CONSUMERFLOW.BYPASSPREPAREENVELOPE – removes the Prepare Your Envelope screen from all Deposit-type transactions

CONSUMERFLOW.CHECKDENOMINATIONOPTION – allows the Consumer Flow to automatically coordinate the denominations in the cassettes with the “Multiples” amount displayed to the cardholder

CONSUMERFLOW.DEPOSITWITHCASHBACK - turns on and off the Deposit with Cash Back transaction

CONSUMERFLOW.DEPOSITWITHCASHBACKACCOUNTS - sets the account for which a Deposit with Cash Back transaction can be performed

CONSUMERFLOW.DEPOSITWITHCASHBACKFEE - sets the fee amount for a Deposit with Cash Back transaction

CONSUMERFLOW.DEPOSITWITHCASHBACKFEEOPTION - turns on and off the fee association for a Deposit with Cash Back transaction

CONSUMERFLOW.DEPOSITWITHCASHBACKRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Deposit with Cash Back transaction

3.5 Electronic Payment

CONSUMERFLOW.ELECTRONICPAYMENT - turns on and off the Electronic Payment transaction

CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNTS - sets the FROM accounts from which a cardholder can make an Electronic Payment

CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT1TOACCOUNTS - sets the TO accounts for which an Electronic Payment can be made from a cardholder’s type 1 account (normally Checking)



CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT2TOACCOUNTS - sets the TO accounts for which an Electronic Payment can be made from a cardholder’s type 2 account (normally Savings)

CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT3TOACCOUNTS - sets the TO accounts for which an Electronic Payment can be made from a cardholder’s type 3 account (normally Credit Card)

CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT4TOACCOUNTS - sets the TO accounts for which an Electronic Payment can be made from a cardholder’s type 4 account (normally Other)

CONSUMERFLOW.ELECTRONICPAYMENTFEE - sets the fee amount for an Electronic Payment transaction

CONSUMERFLOW.ELECTRONICPAYMENTFEEOPTION - turns on and off the fee association for an Electronic Payment transaction

CONSUMERFLOW.ELECTRONICPAYMENTRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Electronic Payment transaction

3.6 Enhanced Deposit

BNA.MAXBILLS – specifies the maximum number of cash bills a cardholder can insert into the BNA at one time

CONSUMERFLOW.DEPOSITSPERRECEIPT – specified the number of consecutive check and/or cash deposits included on one receipt

CONSUMERFLOW.ENHANCEDDEPOSIT - turns on and off the Enhanced Deposit transaction

CONSUMERFLOW.ENHANCEDDEPOSITFEE - sets the fee amount for an Enhanced Deposit transaction

CONSUMERFLOW.ENHANCEDDEPOSITFEEOPTION - turns on and off the fee association for an Enhanced Deposit transaction

CONSUMERFLOW.ENHANCEDDEPOSITMODE – defines the flow of the Enhanced Deposit transaction based on the hardware installed

CONSUMERFLOW.ENHANCEDDEPOSITRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Enhanced Deposit transaction

CONSUMERFLOW.ENVELOPEDEPOSITACCOUNTS - sets the account for which an Enhanced Deposit transaction can be performed (entry is shared with Envelope Deposit)

CONSUMERFLOW.FORCEENHANCEDDEPOSITS – sends a successful completion to host when ATM knows deposit was accepted, but status of Deposit is now unknown (jam, etc.)



STARTOFDAY.PRINTDEPOSITTOTAL - optionally prints local deposit total on receipt

SUPERVISOR.PRINTCHECKLIST – optionally prints a list of all checks deposited when local totals are printed or cleared

3.7 Envelope Deposit

CONSUMERFLOW.BYPASSPREPAREENVELOPE - removes the Prepare Your Envelope screen from all Deposit-type transactions

CONSUMERFLOW.ENVDISPENSEOPTION – optionally dispenses an envelope during all Deposit-type transactions

CONSUMERFLOW.ENVELOPEDEPOSIT - turns on and off the Envelope Deposit transaction

CONSUMERFLOW.ENVELOPEDEPOSITACCOUNTS - sets the account for which an Envelope Deposit transaction can be performed (entry is shared with Enhanced Deposit)

CONSUMERFLOW.ENVELOPEDEPOSIT2 – turns on and off a second type of Envelope Deposit transaction action

CONSUMERFLOW.ENVELOPEDEPOSIT2ACCOUNTS - sets the account for which the second type of Envelope Deposit transaction can be performed

CONSUMERFLOW.ENVELOPEDEPOSIT2RECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Envelope Deposit 2 transaction

CONSUMERFLOW.ENVELOPEDEPOSIT3 - turns on and off a third type of Envelope Deposit transaction action

CONSUMERFLOW.ENVELOPEDEPOSIT3ACCOUNTS - sets the account for which the third type of Envelope Deposit transaction can be performed

CONSUMERFLOW.ENVELOPEDEPOSIT3RECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Envelope Deposit 3 transaction

CONSUMERFLOW.ENVELOPEDEPOSITFEE - sets the fee amount for an Envelope Deposit transaction

CONSUMERFLOW.ENVELOPEDEPOSITFEE OPTION - turns on and off the fee association for an Envelope Deposit transaction

CONSUMERFLOW.ENVELOPEDEPOSIT[2-3]FEE - sets the fee amount for an Envelope Deposit 2 or 3 transaction

CONSUMERFLOW.ENVELOPEDEPOSIT[2-3]FEE OPTION - turns on and off the fee association for an Envelope Deposit 2 or 3 transaction



3.8 Envelope Payment

CONSUMERFLOW.BYPASSPREPAREENVELOPE - removes the Prepare Your Envelope screen from all Deposit-type transactions (including Envelope Payments)

CONSUMERFLOW.ENVDISPENSEOPTION - optionally dispenses an envelope during all Deposit-type transactions (including Envelope Payments)

CONSUMERFLOW.ENVELOPEPAYMENT - turns on and off the Envelope Payment transaction

CONSUMERFLOW.ENVELOPEPAYMENTFEE - sets the fee amount for an Envelope Payment transaction

CONSUMERFLOW.ENVELOPEPAYMENTFEEOPTION - turns on and off the fee association for an Envelope Payment transaction

CONSUMERFLOW.ENVELOPEPAYMENTRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Enhanced Deposit transaction

3.9 Envelope Payment From Account

CONSUMERFLOW.BYPASSPREPAREENVELOPE - removes the Prepare Your Envelope screen from all Deposit-type transactions (including Envelope Payment From Account)

CONSUMERFLOW.ENVDISPENSEOPTION - optionally dispenses an envelope during all Deposit-type transactions (including Envelope Payment From Account)

CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNT - turns on and off the Envelope Payment From Account transaction

CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNTS - sets the account from which an Envelope Payment From Account transaction can be performed

CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNTFEE - sets the fee amount for an Envelope Payment From Account transaction

CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNTFEEOPTION -- turns on and off the fee association for an Envelope Payment From Account transaction

CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNTRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Envelope Payment From Account transaction

3.10 Envelope Payment To Account

CONSUMERFLOW.BYPASSPREPAREENVELOPE - removes the Prepare Your Envelope screen from all Deposit-type transactions (including Envelope Payment To Account)

CONSUMERFLOW.ENVDISPENSEOPTION - optionally dispenses an envelope during all Deposit-type transactions (including Envelope Payment To Account)



CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNT - turns on and off the Envelope Payment To Account transaction

CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNTS - sets the accounts to which an Envelope Payment To Account transaction can be performed CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNTFEE - sets the fee amount for an Envelope Payment To Account transaction

CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNTFEEOPTION - turns on and off the fee association for an Envelope Payment To Account transaction

CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNTRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for the Envelope Payment To Account transaction

3.11 Fast Cash

CONSUMERFLOW.CHECKDENOMINATIONOPTION – allows the Consumer Flow to periodically download the available denomination values from the currency dispenser and update the “multiples” amount for withdrawals

CONSUMERFLOW.DISPLAYMESSAGEWHENUNAVAILABLE – allows the application to display a message to the cardholder when cash (or stamps) are unavailable

CONSUMERFLOW.FASTCASH[1-x] – turns on one or more [1-x] Fast Cash transactions on the main menu, or turns on a main menu Fast Cash non-transaction button that leads to a menu of Fast Cash amounts (when only FASTCASH1 is defined and NUMBEROFFASTCASH and FASTCASHAMOUNTSCREEN entries are also defined)

CONSUMERFLOW.FASTCASH[1-x]ACCOUNTS - sets the accounts from which a Fast Cash transaction can be performed. If multiple Fast Cash transactions are defined (FASTCASH1, FASTCASH2, etc.), each can be assigned a different account.

CONSUMERFLOW.FASTCASH[1-x]AMOUNT – sets dollar amount(s) for one or more Fast Cash transaction(s), whether they appear on the main menu or on a menu of Fast Cash amounts.

CONSUMERFLOW.FASTCASHAMOUNTBUFFER – specifies to put the Fast Cash amount or the FDK key designation in the amount buffer

CONSUMERFLOW.FASTCASH[1-x]FEE - sets the fee amount for one or more Fast Cash transactions

CONSUMERFLOW.FASTCASH[1-x]FEEOPTION - turns on and off the fee association for one or more Fast Cash transaction(s)

CONSUMERFLOW.FASTCASH[1-x]RECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for one or more Fast Cash transaction(s)

CONSUMERFLOW.HIDEFASTCASHNAME – turns on and off the words “Fast Cash” on Main Menu buttons that contains Fast Cash amounts



CONSUMERFLOW.HIDEWHENUNAVAILABLE – optionally hides the Fast Cash, Withdrawal and Stamps transactions on the Main Menu when cash or stamps are unavailable

CONSUMERFLOW.NUMBEROFFASTCASH – specifies the number of Fast Cash transactions available on the Main Menu

CONSUMERFLOW.OTHERAMOUNTINFASTCASHMENU – specifies whether or not to include an Other Amount button (position 4) on the Fast Cash menu

STARTOFDAY.FASTCASHCARDAFTERCASH – True specifies to return the cardholder card immediately after the cash is dispensed and before the receipt is printed

3.12 Full Statement

CONSUMERFLOW.FULLSTATEMENT[1-x] – turns on or off one or more Full Statement transactions on the Main Menu

CONSUMERFLOW.FULLSTATEMENT[1-x]ACCOUNTS – specifies the accounts for which a cardholder can get full statements. Each statement [1-x] can have different accounts associated with it.

CONSUMERFLOW.FULLSTATEMENT[1-x]FEE - sets the fee amount for one or more Full Statement transactions

CONSUMERFLOW.FULLSTATEMENT[1-x]FEEOPTION - turns on and off the fee association for one or more Full Statement transaction(s)

CONSUMERFLOW.FULLSTATEMENT[1-x]RECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for one or more Full Statement transaction(s)

3.13 Message to Bank

CONSUMERFLOW.BYPASSPREPAREENVELOPE - removes the Prepare Your Envelope screen from all Deposit-type transactions (including Message To Bank)

CONSUMERFLOW.ENVDISPENSEOPTION - optionally dispenses an envelope during all Deposit-type transactions (including Message To Bank)

CONSUMERFLOW.MESSAGETOBANK - turns on and off the Message To Bank transaction

CONSUMERFLOW.MESSAGETOBANKFEE – sets the fee amount for a Message To Bank transaction

CONSUMERFLOW.MESSAGETOBANKFEEOPTION - turns on and off the fee association for a Message To Bank transaction

CONSUMERFLOW.MESSAGETOBANKRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for a Message To Bank transaction



3.14 Mini Statement

CONSUMERFLOW.MINISTATEMENT[1-x] – turns on or off one or more Mini Statement transactions on the Main Menu

CONSUMERFLOW.MINISTATEMENT[1-x]ACCOUNTS – specifies the accounts for which a cardholder can get mini statements. Each statement [1-x] can have different accounts associated with it.

CONSUMERFLOW.MINISTATEMENT[1-x]FEE - sets the fee amount for one or more Mini Statement transactions

CONSUMERFLOW.MINISTATEMENT[1-x]FEEOPTION - turns on and off the fee association for one or more Mini Statement transaction(s)

CONSUMERFLOW.MINISTATEMENT[1-x]RECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for one or more Mini Statement transaction(s)

3.15 Personalized Fast Cash

CONSUMERFLOW.PERSONALIZATIONCARDFITS – FITs to which personalization is available

CONSUMERFLOW.PERSONALIZEDENTERAMOUNTSCREEN – turns on and off the option to allow cardholders to define a Personalized Fast Cash amount. If Yes, you must also define the menu buttons as explained in the CONSUMERFLOW.PERSONALIZEDFAST CASHMENUBUTTONS entry. The actual transaction is made available through the CONSUMERFLOW.PERSONALIZEDFASTCASH entry.

CONSUMERFLOW.PERSONALIZEDFASTCASH – turns on and off the Personalized Fast Cash transaction on the Main Menu

CONSUMERFLOW.PERSONALIZEDFASTCASHACCOUNTS - sets the accounts from which a Personalized Fast Cash transaction can be performed

CONSUMERFLOW.PERSONALIZEDFASTCASHFEE - sets the fee amount for Personalized Fast Cash transactions

CONSUMERFLOW.PERSONALIZEDFASTCASHFEEOPTION - turns on and off the fee association for a Personalized Fast Cash transaction

CONSUMERFLOW.PERSONALIZEDFASTCASHMENUBUTTONS – sets the amounts and button positions for the Personalized Fast Cash menu

CONSUMERFLOW.PERSONALIZEDNOPREFERENCEOTHERAMOUNTPOSITION – sets the position of the No Preference: Always Ask button on the Personalized Fast Cash amount screen (this is always set to position 7 when used)



CONSUMERFLOW.PERSONALIZEDOTHERAMOUNTPOSITIONFASTCASHMENU – sets the position of the Other Amount button on the Personalized Fast Cash amount screen (this is always set to position 8 when used)

3.16 Purchase Stamps

CONSUMERFLOW.BYPASSSELECTSTAMPSTOENTERSHEETS – used to allow cardholder to enter the number of sheets of stamps they want rather then selecting the amount from a menu.

CONSUMERFLOW.DISPLAYMESSAGEWHENUNAVAILABLE – allows the application to display a message to the cardholder when stamps (or cash) are out

CONSUMERFLOW.STAMP - turns on and off the Purchase Stamps transaction

CONSUMERFLOW.STAMPACCOUNTS – sets the accounts from which a Purchase Stamps transaction can be performed.

CONSUMERFLOW.STAMPAMOUNTBUFFER – determines whether the number of sheets or purchase amount is placed in the amount buffer

CONSUMERFLOW.STAMPFEE – sets the fee for a Purchase Stamp transaction when the fee is charge per transaction, not by sheet

CONSUMERFLOW.STAMPFEEPERSHEET – sets the fee per sheet when a fee per sheet rather than a fee per transaction is charged

CONSUMERFLOW.STAMPPRICE – sets the price for a sheet of stamps

CONSUMERFLOW.STAMPRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for a Purchase Stamps transaction

CONSUMERFLOW.STAMPSMENUBUTTONS – sets the button positions and number of sheets per button for the Stamp menu

CONSUMERFLOW.STAMPSPERSHEET – specifies the number of stamps per sheet

3.17 Split Deposit

CONSUMERFLOW.BYPASSPREPAREENVELOPE - removes the Prepare Your Envelope screen from all Deposit-type transactions (including Split Deposit)

CONSUMERFLOW.ENVDISPENSEOPTION - optionally dispenses an envelope during all Deposit-type transactions (including Split Deposit)

CONSUMERFLOW.SPLITDEPOSIT – turns on and off the Split Deposit transaction

CONSUMERFLOW.SPLITDEPOSITACCOUNTS - sets the accounts to which a Split Deposit transaction can be performed.



CONSUMERFLOW.SPLITDEPOSITFEE – sets the fee amount for a Split Deposit transaction

CONSUMERFLOW.SPLITDEPOSITFEEOPTION - turns on and off the fee association for a Split Deposit transaction

CONSUMERFLOW.SPLITDEPOSITRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for a Split Deposit transaction

3.18 Transfer

CONSUMERFLOW.TRANSFER - turns on and off the Transfer transaction

CONSUMERFLOW.TRANSFERFROMACCOUNTS - sets the FROM accounts from which a cardholder can transfer funds

CONSUMERFLOW.TRANSFERFROMACCOUNT1TOACCOUNTS – sets the To accounts for a transfer from Checking (ACCOUNT1) transaction

CONSUMERFLOW.TRANSFERFROMACCOUNT2TOACCOUNTS – sets the To accounts for a Transfer from Savings (ACCOUNT2) transaction

CONSUMERFLOW.TRANSFERFEE – sets the fee amount for a Transfer transaction

CONSUMERFLOW.TRANSFERFEEOPTION - turns on and off the fee association for a Transfer transaction

CONSUMERFLOW.TRANSFERRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for a Transfer transaction

3.19 Withdrawal

CONSUMERFLOW.CHECKDENOMINATIONOPTION – allows the Consumer Flow to periodically download the available denomination values from the currency dispenser and update the “multiples” amount for withdrawals

CONSUMERFLOW.DISPLAYMESSAGEWHENUNAVAILABLE – allows the application to display a message to the cardholder when cash (or stamps) are unavailable

CONSUMERFLOW.HIDEWHENUNAVAILABLE – optionally hides the Fast Cash, Withdrawal and Stamps transactions on the Main Menu when cash or stamps are unavailable

CONSUMERFLOW.OTHERAMOUNTPOSITIONONWITHDRAWALMENU – specifies whether or not to include an Other Amount button on the Withdrawal amount menu

CONSUMERFLOW.WITHDRAWAL – turns on and off the Withdrawal transaction

CONSUMERFLOW.WITHDRAWALACCOUNTS - sets the accounts from which a Withdrawal transaction can be performed.



CONSUMERFLOW.WITHDRAWALFEE – sets the fee amount for a Withdrawal transaction

CONSUMERFLOW.WITHDRAWALFEEOPTION - turns on and off the fee association for a Withdrawal transaction

CONSUMERFLOW.WITHDRAWALMENUBUTTONS – sets the dollar amounts and button positions for a Withdrawal amount sub-menu screen

CONSUMERFLOW.WITHDRAWALMENUSCREEN – turns on and off the Withdrawal amount sub-menu screen

CONSUMERFLOW.WITHDRAWALRECEIPTOPTION - turns on and off the option to allow a cardholder to not print a receipt for a Withdrawal transaction

3.20 Settlement

CONSUMERFLOW.MENUSETTLEMENTCARD[1-x] – specifies the menus used for each settlement card define [1-x]

CONSUMERFLOW.NUMBEROFSETTLEMENTCARD – specifies the number of cards used for settlement

CONSUMERFLOW.SETTLEMENT – turns on and off Settlement as a transaction on the Main Menu

SUPERVISOR.DISPLAYAMOUNT – controls whether replenisher is prompted for dollar amount or bill count

SUPERVISOR.DISPLAYCANISTERTYPEHOST – control whether host settlement will be displayed by canister, or by a single total for all canisters

SUPERVISOR.DISPLAYCANISTERTYPELOCAL - – control whether local settlement will be displayed by canister, or by a single total for all canisters

SUPERVISOR.DISPLAYMEDIAAMOUNT – controls whether replenisher is prompted for the dollar amount of stamps or sheet count

SUPERVISOR.PINTOUSE – determines whether to used one of the four-digit passwords assigned in the dd.dat for Host Settlement, or to prompt the user to enter a password which will be validated by host

SUPERVISOR.SENDBALANCEINQUIRY – controls whether or not to send a Balance Inquiry to host for a settlement print function

SUPERVISOR.SETTLEMENTPASSWORD - sets the 4-digit password to automatically use for settlement

SUPERVISOR.SETTLEMENTPIN – sets the 4-digit PIN to automatically use for settlement

SUPERVISOR.TRACK2 – contains the track 2 card data used for settlement cards (use to set up cardless settlement)



SUPERVISOR.TRACK2FORMAT - defines the format of the Track 2 card data for a settlement card (used to set up cardless settlement)

3.21 Supervisor

SUPERVISOR.SAFEDOORTIMEOUT – amount of time to allow for the replenisher to close the safe door before the dispenser test will fail

SUPERVISOR.EXITKEYTIMEOUT – controls the amount of time to wait after exiting Supervisor before the ATM will automatically go back to the application (when user lets Press ENTER to Continue prompt timeout)

SUPERVISOR.KEYTIMEOUT – sets the number of seconds supervisor should wait for a key press before timing out. On timeout, supervisor returns to the previous menu.

SUPERVISOR.MODESWTIMEOUT – controls the amount of time to wait after exiting Supervisor before the ATM will automatically go back to the application (when user does not move the mode switch to Normal)

SUPERVISOR.MAINTANDSUPPLIESPASSWORD – sets the 4-digit password to use to make maintenance and supplies changes

SUPERVISOR.SYSTEMCONFIGURATIONPASSWORD – sets the 4-digit password to use to make system configuration changes

SUPERVISOR.DIAGNOSTICSPASSWORD – sets the 4-digit password to use to run diagnostics

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE MAKING CHANGES USING SOFTWARE DISTRIBUTION


4 Making Changes Using Software Distribution

Using Software Distribution you can change everything referenced in the Making Changes Using the Screen/Keyboard Data Load Message section plus:

Screen Graphics

Screen Text

Animations

Advertising Files

Transaction objects

Script files

HTML code

Registry entries Details on several of these file type are included in the next several sections. You need to be very careful when you make drastic changes. You could render your ATM inoperable or unintelligible. Be sure to test in your lab thoroughly before you roll out an update.

Since ATMs run in a live environment, your software distribution package must be built in a special manner to allow for terminating the application, rebooting the ATM, etc. NCR has an application program called SWDUpdate that allows you to easily handle, through an XML file, all of the mechanics of installing software on an ATM. Refer to the Software Distribution Update User’s Guide for more information. You can get a copy of this document from your NCR representative.

4.1 Change the Screen Graphics

There are actually several different types of graphic files used by the NCR APTRA Edge software. These include:

.JPG files are used to represent the background wallpaper for all screens, as well as any logos that appear on the screens and any ads that are displayed during “Please wait” and "Welcome" cycles.

.GIF files are used to represent the different appearances of the buttons (up, down, or grayed-out) on the screens.

.SWF files are used to provide animations that demonstrate various parts of the hardware included in the NCR APTRA Edge ATM. In addition, the animations shown during the Welcome attract sequence are .swf files.

The screens discussed in this section were created using 800 x 600 resolution. However, not all ATMs will use the 800 x 600 resolution screens. The instructions that follow explain how to modify or replace the existing 800 x 600 screens with modified 800 x 600 screens. Similar instructions apply if you are changing 640 x 480 screens or 1024 x 768 screens; however, the specific size values will be different. If the existing screens are being changed to a different



resolution, additional changes must be made to the stylesheet to re-position buttons and text fields. Contact an APTRA Certified Engineer for assistance.

Further, your implementation may have a customized version of these "standard" graphics. You need to be fully aware of what is on your ATM before you make changes.

4.1.1 Modify the Screen Appearance

To modify the general appearance of the screens used in the APTRA Edge software, the following graphic files can be modified or re-done and updated through software distribution or with the Supervisor COPY FILE function:

Background.jpg This is the background wallpaper graphic that will be used for all screens displayed by the application.

Size: Full Screen (800 x 600) Location: \webatm\webpages\images\Background.jpg

ButtonX[off].gif ButtonX[on].gif

There are actually 8 buttons on each screen, each mapped to a corresponding FDK key. For each button, there are 2 graphic files that must be present: one for the normal button and another for the depressed button.

ButtonXoff.gif is displayed whenever the button is displayed in its normal, undepressed state.

Size: Height = 76, Width = 380 Location: \webatm\webpages\images\ButtonXOff.gif

ButtonXon.gif is displayed whenever the button has been selected (or depressed).

Size: Height = 76, Width = 380 Location: \webatm\webpages\images\ButtonXOn.gif

Note: The filenames for the graphic files for the buttons are named ButtonXoff.gif and ButtonXon.gif where “X” is a number between 1 and 8, indicating which of the 8 buttons is being referenced. For example, button3off.gif represents the normal version of button 3 on the screen, while button7on.gif represents the depressed version of button 7.

4.1.2 Replace the Advertising Files

NCR recommends using APTRA Promote for extensive advertising and full campaign management. However, as was discussed earlier in this document, APTRA Edge does support simple text messages, in both English and Spanish, on the Please Wait, Thank You and Welcome screens, and JPG images on the Please Wait and Welcome screens.

The text messages are defined in the data dictionary and can be downloaded through a DDUpdate. The displaying of images is likewise controlled through data dictionary entries, but



you must use software distribution, or copyfile, to get the actual image files, JPG files, to the required directory on the ATM. This directory is c:\webatm\webpages\images.

4.1.3 Change the Animation Files

Animation files are used by the NCR APTRA Edge software to demonstrate where and how a particular action takes place. For instance, an animation is available to show an ATM user where and how to insert a check, while another animation shows where and how to insert an envelope. The files shown below are used by the software and can be replaced by using software distribution or the Supervisor COPY FILE function.

All animations files were created as 1024 x 768 swf files. They are all located on the ATM in the \webatm\webpages\images\ directory.

Note: The animation files distributed with NCR APTRA Edge were designed and created by a professional computer artist so that the files display as high-quality moving images. If these files are replaced or modified, use caution in your choice of a vendor. A poorly done animation file tends to downplay the professional look of the APTRA Edge software.

Further, if you plan to use your own animations, they must be created as 1024 x 768 swf files with a frame rate of no more than 6 frames per second.

Filename Description

AutoLoan.swf Full screen generic advertisement for an auto loan. This file can be used in conjunction with Promote to create customer-specific ads.

CardDip.swf Animation of card being dipped into a dip card reader (generic ATM card image can be replaced with a bank’s ATM card image)

CardEject.swf Animation of card being ejected from a motorized card reader (generic ATM card image can be replaced with a bank’s ATM card image)

CardMotor.swf Animation of card being inserted into a motorized card reader (generic ATM card image can be replaced with a bank’s ATM card image)

CardSwipe.swf Animation of card being swiped through a swipe card reader (generic ATM card image can be replaced with a bank’s ATM card image)

Depositbag.swf Animation showing a night drop bag being inserted into the night depository

Dispense.swf Animation showing cash being dispensed (new $20) EndorseCheck.swf Animation of a check being turned over and signed FlattenCheck.swf Animation showing a check being removed from a money

clip, unfolded, and smoothed out GiftCertificate.swf Animation showing a gift certificate being dispensed from

the cash dispenser




HomeEquity.swf Full screen generic advertisement for a home equity loan. This file can be used in conjunction with Promote to create customer-specific ads.

InsertCash.swf Animation showing cash (new $20) being inserted into the BNA

InsertCheck.swf Animation showing a check with a flashing arrow showing the proper orientation being inserted into the iTran 1000

Insert Deposit Envelope.swf Animation showing a Deposit envelope being inserted into the depository

InsertEnvelope.swf Animation of generic envelope being inserted into the depository

InsertMessage.swf Animation showing a message to bank envelope being inserted into the depository

Insert Payment Envelope.swf Animation showing a Payment envelope being inserted into the depository

MiniStatement.swf Animation showing a mini statement being printed on the receipt printer

PINEntry.swf Animation of PIN pad and hand entering a PIN (controlled thru dd.dat entry)

PrepareDeposit.swf Animation showing a deposit slip and cash (new $20) being inserted into an envelope

PrepareDepositBag.swf Animation showing a deposit slip and cash (new $20) being inserted into a Business Deposit night drop bag

PrepareMessage.swf Animation of message to bank being inserted into an envelope

PreparePayment.swf Animation showing a payment slip and cash (new $20) being inserted into an envelope

Receipt.swf Animation showing a generic receipt being printed on the receipt printer (can be changed to print bank logo instead of “ATM Receipt”)

RejectCash.swf Animation showing cash (new $20) being ejected from the BNA

RejectCheck.swf Animation showing a check being ejected by the iTran 1000 Retirement.swf Full screen generic advertisement for retirement investments.

This file can be used in conjunction with Promote to create customer-specific ads.

SmoothCash.swf Animation showing cash (new $20) being removed from a money clip, unfolded, and smoothed out

Stamps.swf Animation showing a sheet of postage stamps being ejected from the cash dispenser

Statement.swf Animation showing a full statement being printed by the statement printer




TravelersCheques.swf Full screen generic advertisement for traveler's checks. This file can be used in conjunction with Promote to create customer-specific ads.

WelcomeDIP.swf WelcomeMotor.swf WelcomeSwipe.swf

These are full-screen animations that provide instruction on beginning a cardholder session. The Welcome file plays whenever the ATM is in service, but not currently in use. There are 3 different .swf files that are shipped with the NCR APTRA Edge software: one demonstrating a swipe reader, another showing a motorized reader and a third showing a dip reader. The APTRA Edge software will evaluate the hardware and determine the correct file to use automatically.

4.2 Change the Screen Text

The text shown on each screen is dynamically built using the contents of one or more special text files. One file indicates where the text should be displayed on the screen and describes the size and color of the text, while another file contains the actual words that will be displayed on each screen. A separate text file is used for each language to be supported on the ATM.

4.2.1 Modify the Text

All of the text viewed on the APTRA Edge screens originates from the TextXXX.js file described below. This includes generic information like transaction names and button titles, as well as text specific to a particular screen. Any of the text can be modified as necessary.

Caution: When changing text that will appear on a button, it is easy to mistakenly insert too much text to “fit” on the button. Use caution to make sure that the modified text can be displayed correctly within the borders of the button.

Note: The text files described in this section can only be edited by an editor capable of saving the file as “Unicode” text. Any other editor will corrupt this file and the application will not function. NCR has experienced similar corruption problems originating from the Windows 98 version of Notepad. Therefore, it is strongly suggested that the file be edited with a more recent version of Notepad or some other editor.

The following files can be modified to change the screen text:

TextXXX.js This file contains the screen text to be displayed on each of the application screens. “XXX” in the filename is actually replaced with one of the below acronyms to represent a specific language. For instance, TextENG.js contains the screen text for the English screens, while TextSPA.js contains the text for the Spanish screens. Refer to Section D for information on this file.

ENG English SPA Spanish



Location: \webatm\webpages\scripts\TextXXX.js Note: Other languages can be added as required.

If Voice Guidance is used on the ATM, the SoundENG.xml, SoundSPA.xml, etc. files should also be modified to correspond to any screen text that is modified. These files include all text used by Voice Guidance on each of the application screens in English and Spanish.

4.2.2 Modify the Stylesheets

The stylesheets in the Standard Product control the look of the screens. The stylesheets indicate where the text, buttons, logos, static images and animations are displayed on each screen. In addition, the stylesheets specify the font, size, and color for text.

There are 36 stylesheets in APTRA Edge that address the four color schemes and three resolutions supported for three different monitor size groups:

StyleA.css is for monitor sizes 8.4” and 10”.

StyleB.css is for monitor sizes 13”, 14” and 15”.

StyleC.css is for monitor size 12”. During the APTRA Edge installation, the appropriate stylesheet is determined by the combination of color and monitor size selections. Resolution is determined automatically. The appropriate stylesheet is then copied to the \webatm\webpages directory as style.css.

NCR does not recommend making major modifications to the stylesheet since the application appearance can be changed drastically. However, if the background screens are modified to a customer-specific background, text colors may need to be changed to a different color.

Caution: If the font or size of the text is changed, the resulting application must be reviewed carefully for screens where the text no longer “fits” within the borders of a button or box. Make sure that the text is displayed correctly in the final product.

Major selector sections in the style.css file include:

Bannertext Color for text in the top banner area of every screen. Set to black by default.

Body Size and formatting of the image used for the background on screens.

TableNotes Color of the text used to list the various denominations the customer deposits for a cash deposit. Set to white by default.

TextButton Color of the text displayed on buttons. Set to white by default.

TextLarge Color of the large-sized screen text. Set to white by default.



TextMedium Color of the medium-sized screen text. Set to white by default.

TextSmall Color of the small-sized screen text. Set to white by default.

TextTiny Color of the smallest-sized screen text. Set to white by default.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE ELECTRONIC JOURNAL INFORMATION


5 Electronic Journal Information

The APTRA Edge electronic journal, called ej.xml, provides information that allows the reader to understand exactly what happened during each event at the ATM. These events can include:

Transactions

Supervisor activities

Device faults The actual content of the electronic journal is configurable. Whether or not supervisor entries, transaction data (which can include transaction data from the host) and device status information is recorded in the EJ is controlled in the data dictionary.

Regardless of the content of the EJ, the format of that content is controlled by the journal.xml file and its associated schema file, journal_schema.xdr. A default journal.xml file is provided with APTRA Edge, but this file can be customized to meet the needs of any particular customer. Refer to the Journal.xml section on page 183 for more information about the Journal.xml file.

The ej.xml, journal.xml, journal_schema.xdr and the data dictionary are all located in the c:\WebATM directory on the ATM.

The details of this APTRA Edge format, plus cutover and backup information, are included in this section. Refer to the NDC+ Supervisor Reference Manual (B006-2487-C000) for details on the US NDC+ EJ format if you are not familiar with it.

5.1 EJ Cutover and Backup

The electronic journal file (ej.xml) can be cutover automatically at end of day, or manually through the Supervisor Copy EJ function.

Automatic electronic journal cutover is determined in the CUTOVER.NextTime data dictionary entry. The default value is 23:45. Each day at that time, all the files to be archived, including the current EJ file, are zipped up and copied to the c:\archive directory on the ATM. (Refer to the next section, Retrieving Archive Files on Demand, for a list of the files that are archived.) The original files are then deleted. Each archive has the name format:

ArchiveYYYYMMDDHHMMSS.zip

Multiple archive zips are maintained on the ATM. The exact number is determined by the data dictionary entry STARTOFDAY.ArchiveDaysToRetain. The default number is 30.

Manual cutover can be performed using the Copy EJ Supervisor function. When this function is run, the current EJ file is zipped and copied to one or more flex disks. A copy of the zipped file is stored in the c:\ejarchive directory on the ATM, and the original EJ file is deleted. The backup file is overwritten each time the Copy EJ File function is run. The backup EJ file can be retrieved using the Copy EJBackup Supervisor function.



5.2 EJ Content

The APTRA Edge electronic journal file (ej.xml) can contain host data, device data, transaction data and supervisor data depending upon the journal definition file, and the STARTOFDAY.JournalTXOData, STARTOFDAY.JournalHostData, STARTOFDAY.JournalDeviceData, and SUPERVISOR.JournalTXOData entries in the data dictionary. When these entries are set to True, transaction data, supervisor data and host data will be included in the journal.

Each transaction generates values for a series of specific variables. The journal can log any of the transactions, using any of these values.

The list below shows the common values used by the APTRA Edge application. Note that each record type includes the SYSTEMDate and SYSTEMTime fields for compatibility with the Gasper EJ Viewer (G500-1062-0000).

<Tran> - a series of fields containing transaction data. For example, the below list shows the common values used in APTRA Edge:

AcquirerType

Amount

CardNumber

ConsumerMessageID

DestinationAcquirerType

DisputeReference

DisputeStatus

Fee

FeeAmountNOT ON US

Global.MachineNumber

Result

SourceAcquirerType

SYSTEMDate

SYSTEMTime

TotalAmount

Transaction ID

TransactionTimeStamp

<HostData> - a series of print line images containing the same data as <Tran> but the data is not parsed into separate fields. Up to 17 lines can be referenced by following the samples below:

SYSTEMDate

SYSTEMTime

TRANSACTION.JRNL_PRINTLINE00



.

.

. TRANSACTION.JRNL_PRINTLINE16

<DeviceStatus> - a series of fields containing the information on device errors, such as:

Device

CDM = cash dispenser

DEP = envelope depository

DPTR = full statement printer

ENV = envelope dispenser

IDC = card reader

JPTR = journal printer

NS = night safe

PIN = PIN Pad

RPTR = receipt printer

SIU = sensor indicator

Fitness

0 = Good

1 = Internal error

2 = Warning

3 = Suspend (tamper)

4 = Fatal

Mstatus

Mdata

Supplies

0 = No change/not initialized

1 = Good

2 = Low

3 = Out

4 = Overfill

SYSTEMDate

SYSTEMTime

Vendorerror

<Activity> - A series of fields containing information about which screens have been displayed as part of this transaction activity, including the following:




SYSTEMDate

SYSTEMTime

Global.FinancialID

ActivityLog.SequenceNumberEventName

EventData

<Supervisor> - A series of fields that relate to supervisor functions, including the following:

ActivityLog.SequenceNumber

ActivityName

Amount

Global.FinancialID


Status

SupJournal.Amount

SupJournal.CanisterType

SupJournal.CardNumber

SupJournal.Date

SupJournal.DeviceName

SupJournal.EventName

SupJournal.LocalAmountTotal

SupJournal.LocalCountTotal

SupJournal.LocalDateTime

SupJournal.LocalDateTime

SupJournal.Status

SupJournal.Time

SupJournal.TermSeqNum

SYSTEMDate

SYSTEMTime

5.3 Configuring the EJ File

As was mentioned in the previous section, the contents of the EJ are controlled through the data dictionary, and the format of the data in the EJ is controlled through the journal.xml file. These topics are discussed in this section.



5.3.1 Data Dictionary Entries

Data dictionary entries control what data is recorded in the journal, the location of the EJ backup file, automatic cutover and whether or not XML tags should remain in the file when it is uploaded using the NDC+ Upload EJ Data message.

5.3.1.1 Journal Contents Entries

The electronic journal can include host data, device status data, supervisor data and application transaction data. There are three STARTOFDAY entries and one SUPERVISOR data dictionary entry that control this content. The data dictionary entries and their default values are:

STARTOFDAY.JOURNALDEVICEDATA=True (include device data)

STARTOFDAY.JOURNALHOSTDATA=True (include host data)

STARTOFDAY.JOURNALTXODATA=True (include transaction data)

SUPERVISOR.JOURNALTXODATA=True (include transaction data) To omit the journaling of the data referenced in any of these entries, set the appropriate data dictionary entry to False.

One additional entry controls the journaling of the bills as they are entered into the Bunch Note Acceptor on the ATM during an Enhanced Deposit transaction. This entry is:

CASHDEPOSIT.JOURNALNOTES There is no default for this entry. If you want the bills journaled, you must set this entry to True.

5.3.1.2 EJ Cutover and Backup Entries

The data dictionary entry and default value that controls automatic end of day archiving and, therefore, automatic EJ cutover is:

CUTOVER.NEXTTIME=23:45 The default value shown above causes EJ to be cut over at 23:45. You can change this default time if desired.

The location of EJ backup file that is created after a Copy EJ function is performed from Supervisor is also specified in the data dictionary. This entry and its default value are:

STARTOFDAY.EJARCHIVEFOLDER=c:\ejarchive



5.3.1.3 Journal Upload Entry

There is one data dictionary entry that controls whether or not XML tags are included in the uploaded EJ file when it is uploaded using the NDC+ Upload EJ Data command. This entry and its possible values are:

STARTOFDAY.EJDATAFORMATTERPROGID=

NDCBSRecFrmtNoTag.EJRcrFormater – removes XML tags from uploaded data (this is the default setting)

NDCBBSRecFrmtrTag.EJRecordFormatter – keep XML tags in the uploaded data Regardless of whether or not XML tags are included in the data, carriage returns are included at the end of each line.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE RETRIEVING ARCHIVE FILES ON DEMAND


6 Retrieving Archive Files on Demand

APTRA Edge includes a function that allows you to create and retrieve the end of day archive files on demand. To do this you need to include the following command in a script file and send the script file to the ATM while the ATM is online and running the APTRA Edge application:

COMMANDLINEEOD This command will cause the archives to be created immediately, ready to be retrieved by host. The archives will be located in the c:\archivedir directory on the ATM and use the naming convention:

ArchiveYYYYMMDDHHMMSS.zip

If you run COMMANDLINEEOD multiple times, you will get multiple archive files. Each new archive files will contain only the data since the last archive run. This applies both to COMMANDLINEEOD and to automatic end of day archiving. Each archive will be kept the number of days specified in the data dictionary entry STARTOFDAY.ARCHIVEDAYSTO RETAIN. The default is 30 days.

Each archive will include the following files.

act.xml Activity.log All XML files in the NDC Business Services directory comps.csv, compscd1.csv - list of software components and release levels from the CD

Release Media. contents of the check directory contents of the eventlog directory contents of the Install\logs directory contents of the ProxyTraces directory contents of the trace directory contents of the xfs\logs directory cpmDrvDbg.log - CPM Driver debug log CreateKeynames_Results.txt dd.dat - data dictionary ej.xml - electronic journal IFXTrace.txt journal.xml log files in the CPM directory Log files in the PcChequeProcessingModule\Logs directory memory.dmp menu.xml rcm.log

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE RETRIEVING ARCHIVE FILES ON DEMAND


receipt.xml statement.xml TCPIPCommsServiceConfig.xml ueh.log - unexplained event handler log Versions.txt wbatm.xml WebServicesTrace.dat

The event logs, trace file and journal files are always archived. Additional files that get archived/backed up are defined in the configuration of the EndofDayService in webatm.xml. Files and directories that are configured as ArchiveFiles are added to the zip file and deleted. Files and directories that are configured as BackupFiles are simply added to the zip file.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE HOST CONFIGURATION ITEMS NOT TO CHANGE


7 Host Configuration Items Not to Change

Equally important to knowing what you can change on the ATM from the host is knowing what you should not change at the host once the proxy customizer is installed and running. You should not change the following items without coordinating your efforts with NCR. Changes to any of these will not be recognized by the proxy.

Operation codes

Acknowledgement/denial codes

Account types

Format of the receipt header

Format/location of the balance data returned from a balance inquiry

Generally, if the proxy receives data that it does not recognize from the host, an error will be logged in the Event Log, but no specific notification will be sent to the host.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE SCREEN / KEYBOARD DATA LOAD MESSAGE


A Screen / Keyboard Data Load Message

This message is used to download screen and/or keyboard data to the terminal.

Field Number of Characters

Mandatory/ Optional

Description

a Var M Header. Protocol-dependent. b 1 M Message Class. The message class is ‘3’ – Data Command. c 1 M Response Flag. Reserved for future use. FS 1 M Field Separator. d 3 M Logical Unit Number (LUNO). FS 1 M Field Separator. e 3 O Message Sequence Number. Reserved for future use. FS 1 M Field Separator. f 1 M Message Sub-Class. The message sub-class is ‘1’ – Customization Data. g 1 M Message Identifier. The message identifier is ‘1’ – Screen and/or

Keyboard Data. FS 1 M Field Separator h 3 or 5 See Note 1 Screen Number. Identifies the screen data being transmitted.

Note: The numbering for DPM, error message and SOH reserved screens consists of an alpha character followed by four numeric digits. The numbering for all other reserved screens consists of an alpha character followed by two numeric digits.

i Var See Note 1 Screen Data Field. Represents the data to be displayed on the CRT screen or printer. This field always follows a screen number field and is always followed by a field separator or protocol-dependent trailer.

GS 1 See Note 1 Group Separator j1 Var See Note 3 Keyboard Number and Keyboard Data. Identifies the physical keyboard

data being transmitted. It must have a minimum of three characters that are used to specify the keyboard number to be processed. The normal valid range for these three characters is 000-999 but 000-099 are reserved for use as defaults. The remaining characters make up a variable length data field that defines the keyboard layout. This data is made up of sets of four characters, two for the position code and two for the return code.

GS 1 See Note 3 Group Separator j2 Var See Note 3 Touch Screen Data. Identifies the touch screen keyboard data being

transmitted. The characters make up a variable length data field that defines the keyboard layout. This data is made up of sets of 34 characters, 32 for defining the touch area plus two for the return code.

GS 1 See Note 3 Group Separator j3 3 See Note 3

Nested Keyboard Data. A nested keyboard is identified by a three-digit number. This is repeated for each nested keyboard used to build up the new keyboard definition.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE SCREEN / KEYBOARD DATA LOAD MESSAGE


Field Number of Characters

Mandatory/ Optional

Description

: :

Note: When nested screens are in use, only the highest level screen is used to provide association to a keyboard layout. The nested keyboard data is repeated for the number of nested keyboards required. If the data is not a multiple of three, the excess digits are ignored.

GS 1 See Note 3 Group Separator j4 Var See Note 3 Miscellaneous Keyboard Data This field is reserved for future expansion. k Var M Trailer. Protocol-dependent.

Note: 1. Screen data and/or keyboard data may be downloaded in a message. If any part of field ‘j1’ - ‘j4’ is present, the screen data field must be terminated by a group separator to indicate the start of keyboard data.

Note: 2. Fields ‘h’ - ‘j4’ may be repeated any number of times, subject to the maximum message size defined by the comms protocol limit. The field separator preceding field ‘h’ must be repeated for each additional screen and/or keyboard definition.

Note: 3. If keyboard data is to be downloaded, it must be separated from the screen data field by a group separator even when no screen data is present in the message. Each field of keyboard data must be terminated by the associated group separator, even when that field is empty. The only exception to this is that trailing group separators may be omitted after the last keyboard field that contains actual data. This rule means that the keyboard data type can be identified by the number of group separators preceding it.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE DATA DICTIONARY


B Data Dictionary

This section contains a listing of data dictionary entries with descriptions and default values if applicable. It also contains a sample of the corresponding data dictionary file.

B.1 Data Dictionary Entries

The data dictionary file resides in the C:\Webatm directory on the ATM and is named dd.dat. The following tables list the configuration entries in the data dictionary (in alphabetical order, by group). The default is the value automatically assigned to a field if the field is not specified in the data dictionary. If no default is listed, the local data dictionary file must specify a value; otherwise, the field is ignored.

The following are general rules that apply to data dictionary entries.

All text entries preceding the equal (=) must be UPPER CASE characters. Text after the equal is not validated for case.

If you include duplicate line item entries, only the first one is read (acted upon).

If you include an entry that is no longer supported, it will be ignored.

Functions with YES / NO parameter field; if value of NO, any/all parameter fields that may follow are ignored.

Any misspellings or typos in a line entry will result in line entry being ignored and no warning will be given that this has happened.

Parameter or delimiter typos will result in unpredictable events – typically IE script errors If a reboot is required for a group or entry, this is noted in the description. Changes to the Consumer Flow group require that the data dictionary be re-read before they will take effect. This can be achieved by taking the ATM out of service and putting it back in service. Further, entries that are reserved by APTRA Edge and should not be changed are also noted.

At installation, the data dictionary contains configuration entries only. The sample data dictionary at the end of this section contains typical values for each entry. As soon as the ATM goes into operation the data dictionary starts changing dynamically as the application creates and updates entries. The application adds some entries to the data dictionary that is uses for calculations, counters, etc. These are not documented here because they should not be changed.

7.1.1 ALLTRANSACTIONS Group


AMOUNTOBJECT Specifies the name of the Amount object used by all transactions.



B.1.1 APPMANAGEMENT Group


REBOOTREASON This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.2 BNA Group


COMMSTIMEOUT Amount of time, in milliseconds, to wait for the BNA to become enabled.

ENABLETIMEOUT Amount of time after the bunch note acceptor receives an enable signal that it will wait for the customer to insert the first bill. A value of 0 defers to the BNA default value of 40 seconds.

0

MAXBILLS Specifies the maximum number of bills a customer can insert into the BNA at one time.

B.1.3 CAMERA Group


COMMSSERVICEPROGID

Program ID of the Comms Service for the camera. This entry is set by Supervisor when the camera is configured. The Comms Service Prog ID for the serial camera is NCRRS232CommsService.RS232CommsService. The Comms Service Prog ID for the IP camera is NCRaVPITCPIP.TCPIPCommsService.

DVRTYPE Driver used for the camera. This entry is set by Supervisor when the camera is configured. Possible values are LANEX_TC500 or Diebold_TC500 for a serial camera or LANEX_Enet for the IP camera.

LINKID COM port to which the serial camera is attached. This entry is set by Supervisor when the camera is configured. The LINKID for the IP camera is CAMERA.



B.1.4 CASHDEPOSIT Group


JOURNALNOTES True/False entry that controls whether or not the bills will be journaled. There is no default for this entry. If you want the bills journaled, you need to set this entry to True.


This entry determines whether or not an unsolicited message will be sent to host when the BNA becomes inoperable. True - send message False - do not send message

False

B.1.5 CHECK Group


ARCHIVEDIR Directory on the ATM to where the check files are moved when they are archived.

0

BATCHFILENAME Used in the journal.xml to identify the name of the check batch file and by supervisor to find the check batch file.

ENDORSEMENTPRINTZONE

This defines the print zone on the back of the check on which the endorsement will print. There are two possible entries: 0 for zone 1 and 1 for zone 2. See the endorsement discussion in Appendix E in this document for more information.

1

IMAGERESOLUTION The resolution of the check image file in dpi. 200 LIFTFRONT If True, captures the image of the front of the

check.

LIFTREAR If True, captures the image of the back of the check.

NBRIMAGEARCHIVES Tells how many image archives to store in the archive directory. When creating a new archive causes the total archives to be greater than this number, the system deletes the oldest archive. If this field does not appear in the data dictionary, archives are not deleted.

NUMBEROFDAYS Specifies the number of days to keep files in the Upload directory. This directory contains Enhanced Deposit files and can also contain EJ and Activity log files. The default is 14. This entry is only relevant when CHECK.UPLOADARCHIVE is set to Yes.

14




REARIMAGEARCHIVEDIR

Directory on the ATM to where the rear image check files are moved when they are archived.

c:\archivedir\rearcheckimages

RETURNCHECKTIMEOUT

Number of seconds after the CPM returns a check that the ATM will wait for the customer to take the check before it is retracted.

SCANCHECKTIMEOUT Specifies the number of seconds the system waits for the customer to insert a check before timing out.

UPLOADARCHIVE If set to Yes, the Deposit End of Day service will copy the EJ and activity log files to the Upload directory and it is assumed that all files in this directory will be uploaded. Set this entry to No if you will not be uploading the files in the Upload directory. If you set this entry to No, the Deposit End of Day service will delete everything in the Upload directory at end of day. The default is No.

No

B.1.6 CHECKDEPOSIT Group



This entry determines whether or not an unsolicited message will be sent to host when the iTran 1000 becomes inoperable. True - send message False - do not send message

False

VALIDATEENDORSEMENT

Specifies whether or not the check endorsement should be validated before a check is accepted by the CPM.

VALIDATEMICR Specifies whether or not the check MICR should be validated before a check is accepted by the CPM.

B.1.7 COMX Group


DTRENABLE True/False value set by Supervisor when a serial camera is configured.




SETTINGS Port setting for the serial camera. These values are set by Supervisor when a serial camera is configured.

4800,E,7,1

B.1.8 CONSUMERFLOW Group

Many of the field names in the CONSUMERFLOW group can be prefixed with “FITx” where “x” matches the value assigned in a FITCONSUMERTYPE parameter. This can be used to define unique menus for each consumer type.

Although changes to these entries do not require a reboot, they do require that the data dictionary be re-read for them to take effect. Therefore, the ATM should go out of service and then back in service after a change to this group.

Field Name

Can be prefixed with FITx Value Description Default

ACCOUNT[1-x] No Specifies the account type used by the consumer flow for Account 1-x (Checking, Savings, etc.). This entry is then used to associate Account 1-x with transactions and to define the button position for Account 1-x on transaction screens. This entry is used in the ACCOUNTS entry defined for each transaction type and is described later in this section. This entry must match Account 1-x in the InitialAccountList.xml file used by the proxy.

ACCOUNTBALANCE Yes Specifies whether the Account Balance transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No



Field Name


ACCOUNTBALANCEACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for the Balance Inquiry transaction and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 5-8, the entry should be ACCOUNTBALANCEACCOUNTS=,,,,1,2,3,4 .

ACCOUNTBALANCEFEE

Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

ACCOUNTBALANCEFEEOPTION

Yes Specifies that a fee is charged for this transaction. The FEE must also be set.

No

ACCOUNTBALANCERECEIPTOPTION

Yes Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for this transaction. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt. If the consumer flow includes a submenu that allows the cardholder to print or display his account balance (or both), you must set this option to Yes for the submenu to display.

Yes

ALLACCOUNTBALANCES

Yes This entry is customer specific. It specifies whether or not an All Accounts button should display on the Select Account Type screen. When included, selecting this button will provide the cardholder with the balances for all his accounts either printed on the receipt or displayed on the screen (receipt selection determines location).

No



Field Name


ALLSTATEMENTS Yes This entry is customer specific. It specifies whether or not a Statements button should be included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Having this button will create a predefined submenu that includes Full Statement Transactions on the left-hand side of the screen and Mini Statements on the right-hand.

No

BALANCExNAME No These are internal entries and should not be changed. They allow the Consumer Flow to determine which balance name it should select from the txo/translet/customizer for the transaction. This information is not displayed on the ATM screen or used on the receipt. This entry is defined at installation time and not normally changed.

BANKNAME Yes Specifies the bank name to be displayed on the surcharge screen. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

No

BYPASSPREPAREENVELOPE

No Yes specifies that the consumer flow should not display the Prepare Envelope screen, but rather go directly to the Insert Envelope screen. This applies to all transactions that required the cardholder to insert an envelope.

No



Field Name


BYPASSSELECTSTAMPSTOENTERSHEETS

No Yes/No entry used to bypass the Select Stamps screen so that the user can enter the number of sheets he wants rather than selecting from the menu of predefined number of sheets. The default is No, which means always display a menu.

No

CANCELBUTTON Yes Specifies whether or not a Cancel button should display on all screens. Yes specifies to include the Cancel button on all screens. It will be in button position 4 (lower left-hand button). This option is customer-specific and it is not recommended that you include a Cancel button on every screen as it limits the application to only seven screen buttons and the cardholder can already press the Cancel key on the keypad.

No

CANCELWAITFORHOSTOPTION

No Indicates whether the host should be advised prior to the end of the transaction that a customer has cancelled the fee. YES indicates that the host will be notified before the transaction is complete. After refusing the surcharge, the customer will see a “Please Wait” until the host acknowledges the refusal. NO indicates that the host will be notified after the transaction is complete.

No

CARDFASTCASH No Specifies whether the Card-based Fast Cash transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: this is a special Fast Cash transaction that uses information stored at the host (account and amount) to process the transaction.

No



Field Name


CHANGEPIN Yes Specifies whether the PIN Change transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

CHANGEPINFEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

CHANGEPINFEEOPTION Yes Specifies that a fee is charged for this transaction. The FEE must also be set.

No

CHANGEPINRECEIPTOPTION

Yes Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for this transaction. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt.

Yes

CHAINRECEIPTS No Specifies whether or not you want multiple transactions on one receipt. There is no limit to the number of transactions that can be printed on one receipt.

No

CHECKDENOMINATIONOPTION

No Yes indicates that the consumer flow should periodically download the available denominations from the currency dispenser and automatically update the “multiple” value used for withdrawals.

Yes

CHECKREORDER Yes Specifies whether the Check Reorder transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: the account to be debited for a check reorder is hard-coded to Checking.

No

CHECKREORDERFEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00



Field Name


CHECKREORDERFEEOPTION


No

CHECKREORDERRECEIPTOPTION


Yes

CRMSERVICETIMEOUTBEFOREPLEASEWAIT

No Number of seconds to wait before displaying the Please Wait screen while getting Preferences from the CRM server. If a response is received before this timer expires, the flow will proceed to the Enter PIN screen. Otherwise the flow will go to the Please Wait while waiting for a response from the server. If set to 0, the Please Wait screen will always display.

0

DEPOSITDENIALLINES No This parameter is maintained by the APTRA Edge application and should NOT be modified.

DENIALENDSESSION No This parameter is maintained by the APTRA Edge application and should NOT be modified.

DEPOSITSPERRECEIPT No Specifies the number of consecutive check and/or cash deposits that will print on a single receipt. Values are: 0 - all deposits on one receipt; do not cut receipt until cardholder selects "Deposit Complete" (default) Specific value - print only this number of deposits on a receipt, then cut.

0

DEPOSITWITHCASHBACK

Yes Specifies whether the Deposit with Cash Back transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No



Field Name


DEPOSITWITHCASHBACKACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Deposit with Cash Back transaction and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 1-4, the entry should be DEPOSITWITHCASHBACKACCOUNTS =1,2,3,4,,,, .

DEPOSITWITHCASHBACKFEE


0.00

DEPOSITWITHCASHBACKFEEOPTION


No

DEPOSITWITHCASHBACKRECEIPTOPTION


Yes

DIPCARDREADERENTERPIN

No Specifies a cardholder must reenter his PIN when performing multiple transactions on an ATM with a DIP or SWIPE Card Reader.

Yes

DIPCARDREADERMULTITRANS

No Specifies whether multiple transactions should be allowed with a DIP or SWIPE Reader. If set to YES, the question “Do You Want Another Transaction” will be displayed as each transaction is completed.

No

DISPENSERAVAILABLE No This is an internal flag used by the application to determine whether or not the dispenser is available. It should not be changed.



Field Name


DISPLAYBALANCERECEIPTOPTION

No When this entry is set to Yes, a screen will display for the Account Balance transaction that contains 3 buttons (Display, Print and Print & Display) regardless of the receipt option that is set in the data dictionary for the Account Balance transaction – CONSUMERFLOW.ACCOUNTBALANCERECEIPTOPTION.

No

DISPLAYMESSAGEWHENPREFERENCESUNAVAILABLE

Yes This entry is used to display a message on the Language or ENTER PIN screen (whichever displays first) telling the user that ATM Preferences are not available on this machine. The exact message is defined in the TEXTXXX.js file as message 2061.

No

DISPLAYMESSAGEWHENUNAVAILABLE

No This entry is used to display a message to the cardholder when cash or stamps transactions are not available. Possible values for this entry include: fastcash,withdrawal,stamps (comma separated, no spaces between). If the CONSUMERFLOW.HIDEWHE NUNAVAILABLE data dictionary entry is not set to fastcash,withdrawal,stamps and the cassettes are empty, a cardholder who selects a cash or stamps transaction will see the message: “This ATM is temporarily unable to dispense cash or purchased items.” If neither the HIDEWHENUNAVAILABLE nor the DISPLAYMESSAGEWHENUNAVAULABLE entry is included, the message “Transaction Unavailable” displays to the cardholder. See also: CONSUMERFLOW.HIDEW HENUNAVAILABLE.

DISPLAYPERSONALIZEDOTHERAMOUNTBUTTON

Yes Yes/No entry that determines whether or not to display an Other Amount button on the personalized Fast Cash screen.

No



Field Name


DISPLAYPRINTRECEIPTBUTTON

Specifies whether or not to display a button on the Balance Inquiry screen to allow a user to both display and print his balance. An entry of Yes causes the button to be displayed. An entry of No suppresses this option.

No

DISPLAYSURCHARGEPERTRANS

Yes Yes/No entry that applies per session and determines whether a cardholder will see the fee screen for every transaction he performs that has a fee associated with it (Yes), or if the cardholder will see the fee screen only on the first surcharged transaction, regardless of the number of surcharged transactions he performs during his session (No). Note: regardless of the option selected, the receipt will reflect each fee charged to the cardholder.

ELECTRONICPAYMENT Yes Specifies whether the Electronic Payment transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

ELECTRONICPAYMENTFEE


0.00

ELECTRONICPAYMENTFEEOPTION


No



Field Name


ELECTRONICPAYMENTFROMACCOUNTS

Yes Specifies the From accounts displayed on the Electronic Payment transaction Select Account screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ELECTRONICPAYMENTFROMACCOUNTS=,,,,1,2,, . Note: the TO accounts are defined a little differently. See the next two dd entries for To account definition.

ELECTRONICPAYMENTFROMACCOUNT1TOACCOUNTS

Yes Specifies the Electronic Payment To accounts (ACCOUNT1-x) and their button locations on the screen when Account1 is selected as the From account for an Electronic Payment transaction. Different From accounts can have different To accounts. The To account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ELECTRONICPAYMENTFROMACCOUNT1TOACCOUNTS =,,,,1,2,, . Note: the Account specified in this entry (1 in this case) must be one of the accounts specified in the ELECTRONICPAYMENTFROMACCOUNTS entry.



Field Name


ELECTRONICPAYMENTFROMACCOUNT[2-x]TOACCOUNTS

Yes Specifies the Electronic Payment To accounts (ACCOUNT1-x) and their button locations on the screen when Account[2-x] is selected as the From account for an Electronic Payment transaction. Different From accounts can have different To accounts. The To account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 7-8, the entry should be ELECTRONICPAYMENTF ROMACCOUNT[2-x]TOACCOUNTS =,,,,,,1,2 . Note: the Account specified in this entry (2-x) must be one of the accounts specified in the ELECTRONICPAYM ENTFROMACCOUNTS entry.

ELECTRONICPAYMENTRECEIPTOPTION


Yes

ENHANCEDDEPOSIT Yes Specifies whether the Enhanced Deposit transaction using the BNA and CPM is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: If set to YES, ENVELOPE DEPOSIT, ENVELOPEPAYMENT, DEPOSITWITHCASHBACK and MESSAGETOBANK must be set to NO.

ENHANCEDDEPOSITFEE


0.00



Field Name


ENHANCEDDEPOSITFEE OPTION


No

ENHANCEDDEPOSITMODE

No Specifies how the Enhanced Deposit transaction flow should behave and depends upon the hardware installed on the ATM. Values are: 0 - both iTran 1000 and BNA installed 1 - iTran 1000 only installed 2 - BNA only installed

0

ENHANCEDDEPOSITRECEIPTOPTION


Yes

ENVDISPENSEOPTION No An indicator as to whether an envelope will be dispensed for deposits. Choose from one of the following: Ask During a transaction, the ATM user will be asked if an envelope should be dispensed. Auto An envelope is automatically dispensed during the transaction, without asking the ATM user. None No envelope will be dispensed during a transaction.

None

ENVELOPEDEPOSIT Yes Specifies whether the Envelope Deposit transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: If set to Yes, EnhancedDeposit must be set to NO.

No



Field Name



Yes Specifies the accounts (ACCOUNT1-x) available for Envelope Deposit (and also for Enhanced Deposit, see note below) transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ENVELOPEDEPOSITACCOUNTS =,,,,1,2,,. Note: Envelope Deposits and Enhanced Deposits are mutually exclusive.

ENVELOPEDEPOSITFEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

ENVELOPEDEPOSITFEE OPTION


No

ENVELOPEDEPOSITRECEIPTOPTION


Yes

ENVELOPEDEPOSIT[2-3] Yes Specifies whether a second or third Envelope Deposit transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: If set to Yes, EnhancedDeposit must be set to NO.

No



Field Name


ENVELOPEDEPOSIT[2-3]ACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Envelope Deposit2 or Envelope Deposit3 transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ENVELOPED EPOSIT2ACCOUNTS =,,,,1,2,,.

ENVELOPEDEPOSIT[2-3]FEE


0.00

ENVELOPEDEPOSIT[2-3]FEE OPTION


No

ENVELOPEDEPOSIT[2-3]RECEIPTOPTION


Yes

ENVELOPEPAYMENT Yes Specifies whether an Envelope Payment transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. This transaction does not have accounts associated with it because it is assumed the payment and coupon are in the envelope. Note: If set to Yes, EnhancedDeposit must be set to NO.

No

ENVELOPEPAYMENTFEE


0.00

ENVELOPEPAYMENTFEEOPTION


No



Field Name


ENVELOPEPAYMENTRECEIPTOPTION


Yes


Yes Specifies whether an Envelope Payment From Account transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: If set to Yes, EnhancedDeposit must be set to NO.

No

ENVELOPEPAYMENTFROMACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Envelope Payment From Account transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ENVELOPEPAYMENTFRO MACCOUNTS =,,,,1,2,,.

ENVELOPEPAYMENTFROMACCOUNTFEE


0.00

ENVELOPEPAYMENTFROMACCOUNTFEEOPTION


No

ENVELOPEPAYMENTFROMACCOUNTRECEIPTOPTION


Yes



Field Name



Yes Specifies whether an Envelope Payment To Account transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. Note: If set to Yes, EnhancedDeposit must be set to NO.

No

ENVELOPEPAYMENTTOACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Envelope Payment To Account transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be ENVELOPEPAYMENTTO ACCOUNTS =,,,,1,2,,.

ENVELOPEPAYMENTTOACCOUNTFEE


0.00

ENVELOPEPAYMENTTOACCOUNTFEEOPTION


No

ENVELOPEPAYMENTTOACCOUNTRECEIPTOPTION


Yes



Field Name


FASTCASH1 Yes Specifies whether a Fast Cash transaction is included on the Main Menu. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. This button location is also used if you are presenting a separate Fast Cash menu of amounts (determined by the FASTCASHAMOUNTSCREEN entry). The main menu Fast Cash button will take the location defined for the FASTCASH1 button. In this case, no other Fast Cash button need to be defined, but the Fast Cash amounts do need to be defined and the separate Fast Cash menu will be populated with the amounts defined for FastCash1 through x (maximum of 8).

No

FASTCASH1ACCOUNTS Yes Specifies the accounts (ACCOUNT1-x) available for Fast Cash 1 transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be FASTCASH1 ACCOUNTS =,,,,1,2,,. Note: the Fast Cash accounts defined for Fit 0 will be used as the default if no other Fit Fast Cash accounts are defined.



Field Name


FASTCASH1AMOUNT Yes Up to 3 digits representing the dollar amount of the first fast cash amount button. If FASTCASHAMOUNTSCREEN =NO, this amount will appear on the main menu screens, prefixed with “Fast Cash” (e.g. “Fast Cash $20” or “Fast Cash $100”). If FASTCASHAMOUNTSCREEN= YES, this amount, plus FASTCASH2-8]AMOUNT, will appear on a separate Fast Cash menu that lists only Fast Cash amounts. Note: the Fast Cash menu amounts defined for Fit 0 will be used as the default if no other Fit Fast Cash amounts are defined.

FASTCASH1FEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

FASTCASH1FEEOPTION Yes Specifies that a fee is charged for this transaction. The FEE must also be set.

No

FASTCASH1RECEIPTOPTION


Yes

FASTCASH[2-8] Yes Specifies whether a 2nd through 8th Fast Cash value is included on the Main Menu. If set to YES, each must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. If a separate menu of fast cash amounts is being used, this entry does not need to be defined, but the FASTCASH[2-8] does need to be defined.

No



Field Name


FASTCASH[2-8]ACCOU NTS

Yes Specifies the accounts (ACCOUNT1-x) available for Fast Cash [2-8] transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be FASTCASH2 ACCOUNTS =,,,,1,2,,. If a separate menu of fast cash amounts is being used, this entry does not need to be defined, but the FASTCASH[2-8] does need to be defined.

FASTCASH[2-8]AMOU NT

Yes Up to 3 digits representing the dollar amount assigned as the second through eighth Fast Cash amount(s). Only valid when NUMBEROFFASTCASH is set to “2” or higher. If Fast Cash amounts are appearing on the main menu only (FASTCASHAMO UNTSCREEN=NO), this amount will appear on the main menu screens, prefixed with “Fast Cash” (e.g. “Fast Cash $60” or “Fast Cash $80”). If a separate menu of Fast Cash amounts is being used (FASTCASHAMOUNT SCREEN=YES), this amount will be used to populate the amounts an on the separate menu.

FASTCASH[2-8]FEE Yes Specifies the fee charged for FAST CASH 2-8 transactions. This value should be entered as numeric digits with a single decimal point.

0.00

FASTCASH[2-8]FEEOPT ION


No

FASTCASH[2-8]RECEIP TOPTION

Yes Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for Fast Cash 2-8 transactions. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt.

Yes



Field Name


FASTCASHAMOUNTBUFFER

Yes/No entry that determines what will be placed in the amount buffer for a Fast Cash transaction. Yes - Fast Cash amount No - Fast Cash number

No

FASTCASHAMOUNTSCREEN

No Indicates whether or not a separate FAST CASH menu screen should be displayed to allow the ATM user to select an amount. If set to YES, the Main Menu will include a single FAST CASH selection (defined by FASTCASH1). The FASTCASH1 parameter specifies where the FAST CASH selection appears on the main menu(s). Choosing that selection will display another menu, showing the different Fast Cash values that may be selected. If set to NO, all Fast Cash transactions will appear in the main menu(s) along with the corresponding amounts.

No

FITCONSUMERTYPE1 No Specifies the FIT value to use for matching. The number “1” can be replaced with other numbers up to “15” to represent the maximum of 15 consumer types. (FIT0 is reserved.)

FITCONSUMERTYPE[2-15]

No Specifies one or more additional FIT values to use for matching. The number “1” can be replaced with other numbers up to “15” to represent the maximum of 15 consumer types.

FITSETTLEMENTCARD1 No Specifies the FIT used with settlement card 1. This parameter defines the settlement cards specified in the NUMBEROFSETTLEMENTCARD parameter.

FITSETTLEMENTCARD[2-x]

No Specifies the FIT used with settlement card [2-x]. One entry will be included in the dd for each card. This parameter defines the settlement cards specified in the NUMBEROFSETTLEMENTCARD parameter.



Field Name


FITSUPERVISOR No Specifies the FIT value for a supervisor card. The assigned value can be any value from 1 to 15 that will be matched to the PSTDX value from the FIT entry used for Supervisor. Note: If a supervisor card is not used, FITSUPERVISOR should be set to “-2”. If a supervisor card is used, the NUMBEROFFITCONSUMERTYPE value must be increased to allow for the supervisor FIT.

FLOWSELECT No This parameter is maintained by the APTRA Edge application and should NOT be modified.

1

FORCEENHANCEDDEPOSITS

No Yes/No entry that determines whether or not to send a normal transaction completion to host during an Enhanced Deposit when a jam or some other condition occurs but it is certain that ATM does have the check or bills.

No

FULLSTATEMENT1 Yes Specifies whether Full Statement 1 is included on one of the Main Menus. If set to Yes, it must be followed by 2 comma separated digits representing the number of the menu and the button location where the transaction should be presented. Note: if you have a main menu selection that leads to a submenu of Full Statements, the main menu item was setup as a non-transaction button. See the CONSUMERFLOW.NONTRANSACTIONBUTTON1 entry for more information.

No



Field Name


FULLSTATEMENT1ACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Full Statement 1 transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be FULLSTATEMENT1ACCOUNTS =,,,,1,2,,. If you want the Full Statement fixed to one account, account 1 for example, you would use FUILLSTATEMENT1ACCOUNTS=1, and the account selection screen will not display.

FULLSTATEMENT1FEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

FULLSTATEMENT1FEE OPTION


No

FULLSTATEMENT1RECEIPTOPTION


No

FULLSTATEMENT[2-x] Yes Specifies whether a 2nd, 3rd, 4th, etc. Full Statement is included on one of the Main Menus. A maximum of 8 Full Statements are supported. If set to Yes, these entries must be followed by 2 comma separated digits representing the number of the menu and the button location where the transactions should be presented.



Field Name


FULLSTATEMENT[2-x]ACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Full Statements 2 through 8 transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list for each Mini-Statement which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 5-8, the entry should be FULLSTATEMENT2ACCOUNTS =,,,,1,2,3,4. If you want the Full Statement fixed to one account, account 2 for example, you would use FULLSTATEMENT2ACC OUNTS=1, and the account selection screen will not display.

FULLSTATEMENT[2-x] FEE

Yes Specifies the fee charged for Full Statement 2-8 transactions. This value should be entered as numeric digits with a single decimal point.

0.00

FULLSTATEMENT[2-x] FEE OPTION


No

FULLSTATEMENT[2-x] RECEIPTOPTION

Yes Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for Full Statement 2-8 transactions. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt.

No

HIDEFASTCASHNAME No Yes/No entry that specifies whether or not to include the words “Fast Cash” on Main Menu buttons that contain Fast Cash amounts.

No



Field Name


HIDEWHENUNAVAILABLE

No This entry is used to remove the Fast Cash, Withdrawal and Stamps transactions from the Main Menu when cash or stamps are not available. Possible values include: fastcash,withdrawal, stamps (comma separated, no spaces between). When the cash cassettes are out, the Fast Cash and Withdrawal transactions will be removed from the menu. Likewise, when the Stamp cassette is empty, the Stamps transaction will be removed. Entering and exiting Supervisor will reset the buttons which means they will be visible again. If the cassettes have not been replenished, the transactions will be removed again after the first transaction attempt, and a message stating such will display to the cardholder. See also: CONSUMERFLOW.DISPLAYMESSAGEWHENUNAVAILABLE.

IMAGEWAIT[1-x] No Image files to play on the Please Wait screen. The total number of images is determined by the CONSUMERFLOW. NUMBEROFIMAGEWAIT entry. Images must be in the c:\webatm\webpages\images directory on the ATM.

IMAGEWAIT[1-x]SPA No Image files to play on the Spanish Please Wait screen. The total number of images is determined by the CONSUMERFLO W.NUMBEROFIMAGEWAIT entry. Images must be in the c:\webatm\webpages\images directory on the ATM.

IMAGEWELCOME[1-x] No Image files to play on the Welcome screen. The total number of images is determined by the CONSUMERFLOW. NUMBEROFIMAGEWELCOME entry. Images must be in the c:\webatm\webpages\images directory on the ATM.



Field Name


INVALIDFIT[1-x] No Specifies the FITs that you want to deemed invalid for transactions. This entry works in conjunction with the NUMBEROFINVALIDFITS entry.

LANGUAGEFIRSTANDPINNEXT

No Determines order that the Language selection and PIN Entry screens will display to cardholder. Values are: YES - display language screen first NO - display PIN entry screen first

Yes

LANGUAGEMENU1 Yes This entry defines the Language Selection menu, or the first of several language menus, displayed to cardholders. The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the ISO 639 three-letter language code as the second entry in the pair. When multiple language screens are defined, two predefined entries must be included in these parings for navigation among screens: NEXT and BACK. The actual text displayed on all buttons is defined in the 1000 range in the TextENG.js file.

LANGUAGEMENU[2-x] Yes These entries define the second, third, etc. Language Selection menus. You can define as many Language Selection menus as necessary. The parameters for these entries, like LANGUAGEMENU1, are paired values that define the button position on the screen as the first entry in the pair, and the ISO 639 three-letter language code as the second entry in the pair. When multiple language screens are defined, two predefined entries must be included in these parings for navigation among screens: NEXT and BACK. The actual text displayed on all buttons is defined in the 1000 message range in the TextENG.js file.

LANGUAGEOPTION No An indicator as to whether a Select Language screen will be displayed, allowing the user to select Spanish as an alternate language.

No



Field Name


LOGCARDNUMBER No Specifies that the consumer's card number be logged in the Activity log as soon as the card is inserted into the ATM.

MAINMENUBUTTON No Specifies whether or not a Main Menu button should display on all screens. Yes specifies to include the Main Menu button on all screens. It will be in button position 4 (lower left-hand button). This option is customer-specific and it is not recommended that you include a Main Menu button on every screen as it limits the application to only seven screen buttons.

No

MENUSETLEMENTCARD1

No Specifies the settlement menus used for settlement card 1. This parameter defines the menus for the settlement cards specified in the NUMBEROFSETTLEMENTCARD parameter.

MENUSETTLEMENTCARD[2-x]

No Specifies the settlement menus used for settlement card [2-x]. One entry will be included in the dd for each card. This parameter defines the menus for the settlement cards specified in the NUMBEROFSETTLEMENTCARD parameter.

MESSAGETOBANK Yes Specifies whether the Message to Bank transaction is included on one of the Main Menus. If set to Yes, it must be followed by 2 comma separated digits representing the number of the menu and the button location where the transaction should be presented.

MESSAGETOBANKFEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

MESSAGETOBANKFEEOPTION




Field Name


MESSAGETOBANKRECEIPTOPTION


MINISTATEMENT1 Yes Specifies whether Mini-Statements 1 is included on one of the Main Menus. (Up to four Mini Statements can be supported.) If set to Yes, it must be followed by 2 comma separated digits representing the number of the menu and the button location where the transaction should be presented. Note: if you have a main menu selection that leads to a submenu of Mini-Statements, the main menu item was setup as a non-transaction button. See the CONSUMERFLOW.NONTRANSACTIONBUTTON1 entry for more information.

MINISTATEMENT1ACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Mini-Statement 1 transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be MINISTATEMENT1ACCOUNTS =,,,,1,2,,. If you want the Mini Statement fixed to one account, account 1 for example, you would use MINISTATEMENT1ACC OUNTS=1, and the account selection screen will not display.

MINISTATEMENT1FEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

MINISTATEMENT1FEE OPTION


No



Field Name


MINISTATEMENT1RECEIPTOPTION


No

MINISTATEMENT[2-x] Yes Specifies whether a 2nd,. 3rd, etc. Mini-Statement is included on one of the Main Menus. The maximum supported is10. If set to Yes, these entries must be followed by 2 comma separated digits representing the number of the menu and the button location where the transactions should be presented.

MINISTATEMENT[2-x]ACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for the additional Mini-Statement transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list for each Mini-Statement which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 5-8, the entry should be MINISTATEMENT2ACCOUNTS =,,,,1,2,3,4. If you want the Mini Statement fixed to one account, account 2 for example, you would use MINISTATEMENT2ACCO UNTS=1, and the account selection screen will not display.

MINISTATEMENT[2-x]F EE

Yes Specifies the fee charged for Mini Statement 2-x transactions. This value should be entered as numeric digits with a single decimal point.

0.00

MINISTATEMENT[2-x]F EE OPTION


No



Field Name


MINISTATEMENT[2-x]RECEIPTOPTION

Yes Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for Mini Statement 2-x transactions. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt.

No

MOTORCARDREADERENTERPIN

No Specifies that the user of an ATM equipped with a Motorized Card Reader be prompted to re-enter his/her PIN after a transaction is completed and before another transaction can be done during the same session.

No

MOTORCARDREADERMULTITRANS

No Specifies whether multiple transactions should be allowed with a Motorized Card Reader. If set to YES, the question “Do You Want Another Transaction” will be displayed as each transaction is completed.

No

MSGTHANK[1-x] No Specifies the text message to display on the Thank You screen in English. See also: CONSUMERFLOW.NUMBEROF MSGTHANK. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)



Field Name


MSGTHANK[1-x]SPA No Specifies the text message to display on the Thank You screen in Spanish. See also: CONSUMERFLOW.NUMBEROFMSGTHANK. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

MSGWAIT[1-x] No Specifies the text message to display on the Please Wait screen in English. See also: CONSUMERFLOW.NUMBEROFMSGWAIT. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

MSGWAIT[1-x]SPA No Specifies the text message to display on the Please Wait screen in Spanish. See also: CONSUMERFLOW.NUMBEROFMSGWAIT. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)



Field Name


MSGWELCOME[1-x] No Specifies the text message to display on the Welcome screen in English. See also: CONSUMERFLOW.NUMBEROF MSGWELCOME. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

MSGWELCOME[1-x]SPA No Specifies the text message to display on the Welcome screen in Spanish. See also: CONSUMERFLOW.NUMBEROF MSGWELCOME. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

MULTIPLEACCOUNTSELECTION

No Yes/No entry that determine whether multiple account information will come from host, or is kept locally. Yes - accounts are kept locally No - accounts come from host Also see: CONSUMERFLOW.ACC OUNT1-x and CONSUMERFLOW. SUBACCOUNTSFORACCOUNTx.

No

NEXTSTATEENDSESSIONVALUE

No When a Next State code is included for this entry, the cardholder session will end after the Consumer Flow receives this Next State code from host.



Field Name


NEVERSETPREFERENCEBUTTON

No Yes puts a button on the "Do you want to set Preferences" screen that says “Never Set Preferences.” This button is in addition to the Yes and No buttons.

No

NONTRANSBUTTON[1-x]

Yes Indicates a sub-menu selection that should appear on one of the Consumer Flow menus, along with its button location. Other selections can be specified by increasing the number 1 in the parameter (NONTRANSBUTTON2, NONTRANSBUTTON3, etc.) This keyword must be followed by comma-separated fields that specify the text to appear on the button, followed by a single-digit representing the menu number, followed by a single-digit representing the button location on that menu, followed by a single-digit representing a sub-menu to be displayed when this button is touched.

NUMBEROFACCOUNTS No Specifies the number of initial accounts. This entry must match the number of accounts in the initial accounts list, and there must be a CONSUMERFLOW. ACCOUNTx entry for each account.

NUMBEROFBALANCE No This is an internal entry and should NOT be modified. This entry is defined at installation time and not normally changed.

NUMBEROFFASTCASH Yes Specifies the number of Fast Cash selections that are allowed, up to a maximum of 8. This value must be coordinated with the number of FASTCASHxAMOUNT parameters. For instance, if NUMBEROFFASTCA SH is 2, then FASTCASH1AMOUNT and FASTCASH2AMOUNT must be specified. If NUMBEROFFASTCASH is 8, then 8 amounts (FASTCASH1AMOUNT through FASTCASH8AMOUNT) must be specified.

0



Field Name


NUMBEROFFITCONSUMERTYPE

No Specifies the number of consumer and supervisor types associated with the FIT table, up to a maximum of 15.

No

NUMBEROFIMAGEWAIT

No Specifies the number of images to display on the Please Wait screen.

NUMBEROFIMAGEWELCOME

No Specifies the number of images to display on the Welcome screen.

NUMBEROFINVALIDFITS

No Specifies the number of FITs you want to define as invalid for transactions. The invalid FITs are defined through the INVALIDFIT[1-x] entries.

NUMBEROFMSGTHANK

No Specifies the number of text messages to display on the Thank You screen.

NUMBEROFMSGWAIT No Specifies the number of text messages to display on the Please Wait screen.

NUMBEROFMSGWELCOME

No Specifies the number of text messages to display on the Welcome screen.

NUMBEROFNONTRANSBUTTONS

Yes Specifies the number of non-transaction buttons that will be used to navigate to another menu within this application. This must be coordinated with the NONTRANSBUTTON[1-x] entries.

No

NUMBEROFSETTLEMENTCARD

No Specifies the number of different settlement cards used for settlement. There is no maximum restriction. 0 = no cards.

NUMBEROFTIMEOUT No Indicates the number of webpage types that have different time-out values. The webpage type is assigned in the .js file associated with each screen. Each webpage type requires that an associated TIMEOUTFORPAGETYPEx parameter be included in the dd.dat to specify the time-out value for that type of screen.

OARACCOUNTOPTION No This is a customer-specific entry. It allows that specific customer to offer their cardholders an alternate method of getting to OAR accounts.

No



Field Name


OARACCOUNTPAGE No This is a customer-specific entry. This is the .htm page that for the above OAR scenario.

""

OTHERACCOUNTOPTION

No This is a customer-specific entry. It allows that specific customer to offer their cardholders an alternate method of getting to accounts.

No

OTHERACCOUNTPAGE No This is a customer-specific entry. This is the .htm page that for the above account selection scenario.

""

OTHERAMOUNTINFASTCASHMENU

No Specifies that an Other Amount button be included on the Fast Cash menu. When set to Yes, the button will be positioned in button position 4 (lower left corner) (This Other Amount button navigates to the Enter Amount screen.)

No

OTHERAMOUNTPOSITIONONWITHDRAWALMENU

No When WITHDRAWALMENUSCRE EN is set to Yes, this entry defines the Other Amount button position (1-8) on the withdrawal amount menu screen. The Other Amount button navigates to the Enter Amount screen. If you do not want this button, assign No to this entry. Note: the WITHDRAWALMENUSCR EEN and WITHDRAWALMENUBUT TONS entries must also be defined for this button to appear.

No

PERSONALIZATIONCARDFITS

No FITs to which Personalization is available. Values are ALL (all FITs) or a comma-separated list of individual FITs. ALL allows personalization for all FITs. For example, PERSONALIZATIONCARDFITS=1,2,3 allows personalization and stores preferences only for Fits 1, 2 and 3.

PERSONALIZEDENTERAMOUNTSCREEN

No Yes/No entry that determines whether or not to allow cardholder to define a personalized Fast Cash amount.



Field Name



Yes Specifies whether a Personalized Fast Cash transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented. The button text is defined in message 9044 in the TextENG.js file.

No


No Defines the accounts that can be used for a personalized Fast Cash transaction. These entries must match your defined account types in the CONSUMERFLOW.ACCOUNT1-x dd entries. For example, the defaults are: 1=checking 2=savings 3=credit

1 (checking)

PERSONALIZEDFASTCASHMENUBUTTONS

No Defines the layout of the personalized Fast Cash amount selection screen. The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the dollar amount to display on the button as the second entry in the pair. For example, to define button position 1-4 with the dollar values 25, 50 100 and 200, you would use PERSONALIZEDFASTCASHMENUBUTTONS =1,25,2,50,3,100,4,200. Button position 7 is reserved for the No Preference: Always Ask button. You can also define an Other Amount button for the Fast Cash amount screen. See: DISPLAYPERSONALIZEDOTHE RAMOUNTBUTTON and PERSONA LIZEDOTHERAMOUNTPOSITIONFASTCASHMENU.

PERSONALIZEDNOPREFERENCEOTHERAMOUNTPOSITION

No This specifies the position of the No Preference: Always Ask button on the Personalized Fast Cash amount selection screen. This button must be in position 7.

7



Field Name


PERSONALIZEDOTHERAMOUNTPOSITIONFASTCASHMENU

No Defines the Other Amount button location on the personalized Fast Cash screen. Button 7 is reserved and cannot be used. See DISPLAYPERSONALI ZEDOTHERAMOUNTBUTTON.

PINANIMATION No Determines whether or not the PIN animation will display on the PIN Entry screen. If yes, the animation will play.

PINAUTOENTEROPTION

No Yes indicates that the PMXPN value from the FIT Table should be used to determine when PIN Entry is complete. Once the maximum number of digits has been entered, the application will automatically continue with the next screen.

No

PINRETRIES No Determines the number of times a cardholder will be allowed to reenter his PIN after an incorrect entry. If this entry is not specified, the cardholder will have unlimited retries.

PRIMARYMAINMENU Yes Specifies the menu to which the cardholder will be taken after he performs a Forced Balance Inquiry transaction, or if he elects not to perform the Balance Inquiry in a Forced Account Balance flow. This entry is normally preceded by a FIT value to designate to which cardholders this entry will apply. Additionally FIT menus are also normally defined. See Configuring a Forced Account Balance Transaction for more information.

PROMOTE No Indicates whether or not APTRA Promote is being used for advertising support.

No



Field Name


PURCHASE1 Yes Specifies whether a Purchase1 transaction is included in the Consumer Flow. This could be used for gift certificates, phone cards, etc. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

PURCHASE1ACCOUNTS Yes Specifies the accounts (ACCOUNT1-x) available for Purchase1 transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1 and 2 display in button positions 5 and 6, the entry should be PURCHASE1ACCOUNTS =,,,,1,2,,.

PURCHASE1FEE Yes Specifies the fee charged for each Purchase1 transaction. This value should be entered as numeric digits with a single decimal point.

PURCHASE1FEEOPTION Yes Specifies that a fee is charged for this transaction. The FEE must also be set.

No

PURCHASE1PRICE No Value of each unit of [thing] defined as Purchase1. For gift certificates, this would be the value of each gift certificate. This value should be entered as numeric digits with a single decimal point.

PURCHASE1RECEIPTOPTION




Field Name


PURCHASE[2-x] Yes Specifies whether a Purchase[2-x] transaction is included in the Consumer Flow. You can define as many purchase types as necessary. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

PURCHASE[2-x]ACCOU NTS

Yes Specifies the accounts (ACCOUNT1-x) available for Purchase[2-x] transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1 and 2 display in button positions 5 and 6, the entry should be PURCHASE2ACCOUNTS =,,,,1,2,,.

PURCHASE[2-x]FEE Yes Specifies the fee charged for each Purchase[2-x] transaction. This value should be entered as numeric digits with a single decimal point.

PURCHASE[2-x]FEEOPTI ON


No

PURCHASE[2-x]PRICE No Value of each item defined as a Purchase[2-x] item. This value should be entered as numeric digits with a single decimal point.

PURCHASE[2-x]RECEIPTOPTION




Field Name


RECEIPTOPTIONAFTERPINENTRY

No Specifies whether the Do You Want a Receipt screen should be displayed before (Yes) or after (No) the Main Menu. When this is set to Yes, any transaction receipt option entries for which you specify yes, for example CONSUMERFLOW.TRANSFERRECEIPTOPTION=YES or CONSUMERFLO W.WITHDRAWALRECEIPTOPTION=YES, will be ignored.

No

SETTLEMENT Yes This entry is customer specific. It specifies whether or not a Settlement transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

SETTLEMENTMENU No This parameter is maintained by the APTRA Edge application and should NOT be modified.

M002

SHOWDEPOSITDISCLAIMER

No Yes/No entry that controls whether or not a disclaimer screen displays to the cardholder during Deposit transactions. The text for this disclaimer is defined in message 2600 in the TextXXX.js file.

No

SHOWWANTTOENTERPERFERENCESSCREEN

No Specifies whether or not to show a screen that allows the cardholder to enter preferences if he has no preferences defined already. Values are: YES - show screen if no preferences defined NO - do not show screen

SINGLEACCOUNTSELECTOPTION

No Yes indicates that when only one particular account is used in a transaction, primary checking for Purchase Stamps for example, the customer will still be prompted to select that account on the screen during the transaction. If set to No, the account selection screen for this one set account will not display to the customer during transactions.

No



Field Name


SPLITDEPOSIT Yes Specifies whether the Split Deposit transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

SPLITDEPOSITACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Split Deposit transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 5-8, the entry should be SPLITDEPOSITACCOUNTS=,,,,1,2,3,4.

SPLITDEPOSITFEE Yes Specifies the fee charged for each Split Deposit transaction. This value should be entered as numeric digits with a single decimal point.

SPLITDEPOSITFEEOPTION


No

SPLITDEPOSITRECEIPTOPTION


SST No This parameter is maintained by the APTRA Edge application and should NOT be modified.

STAMP Yes Specifies whether the Purchase Stamps transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No



Field Name


STAMPACCOUNTS Yes Specifies the accounts (ACCOUNT1-x) available for Stamps transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 5-8, the entry should be STAMPACCO UNTS =,,,,1,2,3,4.

STAMPAMOUNTBUFFER

No Yes/No entry that determines what is placed in the amount buffer for a stamp transaction. Yes - number of stamp sheets No - stamp purchase amount

No

STAMPFEE No Specifies the fee charged for each Purchase Stamps transaction, no matter how many sheets are purchased. This value should be entered as numeric digits with a single decimal point. This entry is mutually exclusive with STAMPFEEPERSHEET. Note: The FEEOPTION entry is not used with Stamps.

0.00

STAMPFEEPERSHEET No Specifies the fee charged for each sheet of stamps that is purchased. This value should be entered as numeric digits with a single decimal point. This entry is mutually exclusive with STAMPFEE.

0.00



Field Name


STAMSPMENUBUTTONS

No This entry defines the button positions and the number of sheets associated with those buttons when a Stamp menu screen is included on the ATM. The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the number of sheets as the second entry in the pair. For example, to define button position 1-4 with the number of sheets 1, 2 3 and 4, you would use STAMPSMENUBUTT ONS=1,1,2,2,3,3,4,4. These amounts also need to be included in Template 2164 of the SoundXXX.xml file.

STAMPPRICE No Specifies the price for each sheet of stamps. This value should be entered as numeric digits with a single decimal point.

0.00

STAMPRECEIPTOPTION Yes Specifies whether or not the "Do you want a receipt?" screen should be displayed to the cardholder for this transaction. If set to No, the receipt option screen will not be displayed, and the cardholder will always get a receipt.

Yes

STAMPSPERSHEET No Specifies the number of stamps per sheet. 0 SUBACCOUNTSFORACCOUNTx

Yes For each account “type” that has multiple local accounts associated with it, a SUBACCOUNTSFORACCOUNTx entry is defined. This entry identifies all subaccounts that can be accessed by pressing the account type button on the account selection screen. Also see the CONSUMERFLOW.ACC OUNTx and CONSUMERFLOW.MU LTIPLEACCOUNTSELECTION entries that are also used to set up multiple local account selections.

SWITCH No Indicates the network switch used for this installation. This value should not be changed in the field without explicit guidance from a PS Consultant in Dayton.



Field Name


TIMEOUTFORPAGETYPE1

No Indicates the number of seconds to wait before a time-out occurs on Type 1 screens. These are typically screens that provide a short informational message like “Your transaction is complete”. This parameter must be defined for each NUMBEROFTIMEOUT defined.

TIMEOUTFORPAGETYPE1VG

No Indicates the number of seconds to wait before a time-out occurs on Type 1 screens when Voice Guidance is active. Although these screens typically provide only a short informational message, a longer timeout is needed when the message is articulated. This parameter must be defined for each NUMBEROFTIMEOUT defined.

TIMEOUTFORPAGETYPE[2-x]

No Indicates the number of seconds to wait before a time-out occurs on Type 2 through x (your maximum) screens. These are typically screens that provide a somewhat lengthy informational message. This parameter must be defined for each NUMBEROFTIMEOUT defined.

TIMEOUTFORPAGETYPE[2-x]VG

No Indicates the number of seconds to wait before a time-out occurs on Type 2 through x (your maximum) screens when Voice Guidance is active. These are typically screens that provide a somewhat lengthy informational message. A longer timeout is usually needed when the message is articulated. This parameter must be defined for each NUMBEROFTIMEOUT defined.

TRACK1DATA No Specifies whether or not to display Track 1 data from the consumer's card (usually name) on the Enter PIN screen. Yes specifies to display the track 1 data.



Field Name


TRANSFER Yes Specifies whether a Transfer transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No

TRANSFERFEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

TRANSFERFEEOPTION Yes Specifies that a fee is charged for this transaction. The FEE must also be set.

No

TRANSFERFROMACCOUNTS

Yes Specifies the From accounts displayed on the Transfer transaction Select Account screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be TRANSFERFR OMACCOUNTS=,,,,1,2,, . Note: the TO accounts are defined a little differently. See the next two dd entries for To account definition.



Field Name


TRANSFERFROMACCOUNT1TOACCOUNTS

Yes Specifies the Transfer To accounts (ACCOUNT1-x) and their button locations on the screen when Account1 is selected as the From account for a Transfer transaction. Different From accounts can have different To accounts. The To account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 5-6, the entry should be TRANSFERFR OMACCOUNT1TOACCOUNTS =,,,,1,2,, . Note: the Account specified in this entry (1 in this case) must be one of the accounts specified in the TRANSFER FROMACCOUNTS entry.

TRANSFERFROMACCOUNT[2-x]TOACCOUNTS

Yes Specifies the Transfer To accounts (ACCOUNT1-x) and their button locations on the screen when Account[2-x] is selected as the From account for a Transfer transaction. Different From accounts can have different To accounts. The To account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-2 display in button positions 7-8, the entry should be TRANSFER FROMACCOUNT[2-]TOACCOUNTS =,,,,,,1,2 . Note: the Accounts specified in this entry (2-x) must be one of the accounts specified in the TRANSFERFROMACC OUNTS entry.

TRANSFERRECEIPTOPTION


Yes



Field Name


UPDATEPREFERENCESWHENSESSIONCLOSES

No Yes/No entry that determines when a cardholder's preferences are saved. If set to Yes, his preferences will not be saved until the end of the session, avoiding the delay of sending to host during the session. If set to No, the cardholder's preferences are sent to host when the cardholder presses the Save button on the preferences screen.

Yes

VGPUBLICSPEAKER No Reserved for future use. No VOICEBANKNAME No Indicates the words to use whenever

VOICEGUIDANCE=Yes and the VOICEBANKNAME variable is included in the .xml file. NOTE: some special characters can cause the DDUpdate to fail. These include &, ", ', < and >. If you need to include these characters in a DDUpdate, substitute the following: & - ampersand (&) " - double quote (") ' - apostrophe (') < - less than (<) > - greater than (>)

VOICEGUIDANCE No Indicates whether Voice Guidance will be used during transaction processing to verbally guide a sight-impaired user through the screens.

No

WITHDRAWAL Yes Specifies whether a withdrawal transaction is included in the Consumer Flow. If set to YES, it must be followed by two comma-separated digits representing the number of the menu and the button location where the transaction should be presented.

No



Field Name


WITHDRAWALACCOUNTS

Yes Specifies the accounts (ACCOUNT1-x) available for Withdrawal transactions and the account button locations on the screen. The account numbers (1-x) must be placed in a comma separated list which defines their positions on the screen. Each comma defines a button position from 1-8. For example, to have accounts 1-4 display in button positions 5-8, the entry should be WITHDRAWA LACCOUNTS =,,,,1,2,3,4.

WITHDRAWALFEE Yes Specifies the fee charged for this transaction. This value should be entered as numeric digits with a single decimal point.

0.00

WITHDRAWALFEEOPTION


No

WITHDRAWALFIXEDAMOUNT

No This is an internal flag used by the application to determine whether or not the cardholder selected a fixed amount. It should NOT be changed.

WITHDRAWALMENUBUTTONS

No This entry defines the button positions and the amounts associated with those buttons when a withdrawal menu screen is included on the ATM (WITHDRAW ALMENUSCREEN=YES). The parameters for this entry are paired values that define the button position on the screen as the first entry in the pair, and the dollar amount as the second entry in the pair. For example, to define button position 1-4 with the amounts 10, 20 30 and 40, you would use WITHDRAWAL MENUBUTTONS=1,10,2,20,3,30,4,40. These amounts also need to be included in Template 2086 of the SoundXXX.xml file.

WITHDRAWALMENUSCREEN

No Set this entry to Yes if you want a submenu of predefined amounts for withdrawal transactions.



Field Name


WITHDRAWALRECEIPTOPTION


Yes

B.1.9 CRMSERVICE Group


INITIATE Defines when to retrieve the cardholder's preferences. Value are: AFTERCARD - immediately after card is inserted/dipped/swiped AFTERPIN - after cardholder enters his PIN NEVER - Personalization not available on this ATM

Never

B.1.10 CURRENCY Group

Changes to this group require a reboot and must include the reboot="y" parameter in the <CONFIGURATION_DATA> entry in a Screen / Keyboard Data Load Message.


CASSETTE1TYPE The type of notes cassette #1 holds in ppc format where pp is the country code and c is the currency type. For example, for US dollars, pp would be US and c would be D for dollars.

CASSETTE1UNITID A code of 1 indicating that this is cassette #1. CASSETTE1UNITTYPE A code representing the type of media stored

in cassette #1, where 0=cash, 1=stamps, and 2=other documents.

CASSETTE1VALUE The denomination of the notes in cassette 1. CASSETTE2TYPE The type of notes cassette 2 holds in ppc

format where pp is the country code and c is the currency type.

CASSETTE2UNITID A code of 2 indicating that this is cassette #2.




CASSETTE2UNITTYPE A code representing the type of media stored in cassette #2, where 0=cash, 1=stamps, and 2=other documents.









CASSETTE4VALUE The denomination of the notes in cassette 4. REJECTBINMAXIMUMBILLS

This is an internal entry maintained by APTRA Edge and should NOT be modified. It contains the logical maximum number of bills that have been retracted into the reject bin. When this maximum is reached, a Bin Full error occurs and the dispenser goes fatal.

B.1.11 CURRENCYEXPONENT Group


USD This is an internal entry maintained by APTRA Edge. It should NOT be changed.

B.1.12 CUTOVER Group


NEXTDATE This parameter is maintained by the APTRA Edge application and should NOT be modified.




NEXTTIME Determines when EJ cutover will occur each day.

23:45

B.1.13 DEPOSIT Group


BNAERROR This parameter is maintained by the APTRA Edge application and should NOT be modified.

CPMERROR This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.14 EJUPLOAD Group


NEXTFILEINDEX This is an internal entry used by APTRA Edge. It should NOT be modified.

REPOSITORYDIRPATH Full path on the ATM to the transaction file sent to the host during an EJ upload. This repository is cleared after an upload.

c:\EJREPOSITORY

B.1.15 EVENTLOG Group


APPLASTDATEARCHIVED

This is the last time the event log was archived. This parameter is maintained by the APTRA Edge application and should not be changed.

ARCHIVEDIR Directory where event log files are moved when they are archived. This directory can be on a local drive or remote drive on the server. The ATM archives three different event logs: applications, security, and system.




ARCHIVEREASON This can be “SIZE”, “TIME”, “SIZETIME” or “ONDEMAND”. “SIZE” archives the event log at cutover if its size is greater than or equal to MAXSIZE. “TIME” archives the event log at cutover if ARCHIVETIME has passed. “SIZETIME” archives the event log at cutover if either its size is greater than or equal to MAXSIZE, or if ARCHIVETIME has passed. “ONDEMAND” archives the event log at cutover.

SIZE

ARCHIVETIME If ARCHIVEREASON is set to "TIME", then this value determines when the logs will be archived. This entry is the time in 24-hour HH:MM format. If the set time has passed, the event log will be moved to the archive directory at cutover.

MAXSIZE If ARCHIVEREASON is set to “SIZE,” then this value determines when the logs will be archived. This value is in kilobytes. If a log is this size or greater, it will be moved to the archive directory at cutover. This value should be between 512 and 2048. Note: The overwrite value specified for the XP Event Log settings must be greater than or equal to this value or data could be overwritten and lost.

512

SECLASTDATEARCHIVE

This parameter is maintained by the APTRA Edge application and should NOT be modified.

SYSLASTDATEARCHIVE


B.1.16 FASTCASH Group


NUMBERDISPENSEDTYPE1











B.1.17 GLOBAL Group



MACHINEADDRESS1 This is the first line of the address where the machine is located, typically a street address.

MACHINEADDRESS2 This is the second line of the address where the machine is located, typically city, state, and zip code.

MACHINENUMBER A unique terminal identification number. TERMINALOWNER The owner of the ATM services.

B.1.18 JOURNAL Group


PAPERJOURNAL True specifies this ATM will use the paper journal. False specifies this ATM will not use the paper journal. See STARTOFDAY.JOURNALHOSTDATA and STARTOFDAY.JOURNALTXODATA for information on what will be journaled.

False

PAPERSPOOLEXE This parameter is maintained by the APTRA Edge application and should NOT be modified. This is the name of the spool program to be launched by the journal service. It is normally set to c:\webatm\spool.exe.




PAPERJOURNALFORMSDIR

This parameter is maintained by the APTRA Edge application and should NOT be modified. This is the directory in which the journal printer forms are located. It is normally set to c:\xfs\data\jptr\forms.

STARTTIME This parameter is maintained by the APTRA Edge application and should NOT be modified.

TEMPLATEDEFINITIONFILENAME

Name, including the full path, of the XML template file used for the electronic journals. This is normally set to c:\webatm\journal.xml.

B.1.19 MACHINE Group


TERMINALNUMBER This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.20 NDCBS


CASSETTEMAPPINGCONFIG

This is an internal entry used by APTRA Edge. It should NOT be modified. It contains the location of the cassette mapping configuration file used by the Business Services.

CONFIGDIR This is an internal entry used by APTRA Edge. It should NOT be modified. It contains the location of all of the rest of the configuration files used by the Business Services.

B.1.21 NDCPROXY Group


ACQUIRERREQUESTED This parameter is maintained by the APTRA Edge application and should NOT be modified.




CBDEPOSITAMOUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

CBWITHDRAWALAMOUNT


LANGUAGE This parameter is maintained by the APTRA Edge application and should NOT be modified.

RECEIPT This parameter is maintained by the APTRA Edge application and should NOT be modified.

RECEIPTDATAFOUND This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.22 NDCPROXYCUSTOMIZATION Group

A change to the EnhancedDepositMode entry in this group requires a reboot and must include the reboot="y" parameter in the <CONFIGURATION_DATA> entry in a Screen / Keyboard Data Load Message.


AMOUNT This is an internal entry used by APTRA Edge. It should NOT be modified.

ENHANCEDDEPOSITMODE

This entry synchronizes the Business Services with the data dictionary. When Enhanced Deposits are used on the ATM, this entry must be set to MigrationEmulation. A reboot is required after adding this entry.

MAXAMOUNT Dollar amount used for an excessive withdrawal amount error (denial code "088"). This value is ignored for networks that do not experience a denial code of “088”.

MULTIPLE Dollar amount used as multiple for withdrawals. If CONSUMERFLOW.CHEC KDENOMINATIONOPTION is set to No, this multiple will always be used. If CONSUMERFLOW.CHECKDENOMINATIONOPTION is set to Yes, the multiple will change automatically as cassettes are depleted.




PINCHANGEALWAYSINCLUDEOPCODE

True/False entry used with a three-message PIN Change. If True, the Opcode will be included in the second and third Transaction Requests. If False, the Opcode will not be included in the second and third Transaction Requests.

PINCHANGEALWAYSINCLUDETRACK2

True/False entry use with a three-message PIN Change. If True, the track 2 data will be included in the second and third Transaction Requests. If False, the track 2 data will not be included in the second and third Transaction Requests.

PINCHANGENEXTSTATE1

For a one-message PIN Change, this is the Next State code that indicates the PIN Change transaction was authorized For a three-message PIN Change, this is the Next State code (contained in the Transaction Reply to the first Transaction Request) that indicates that the current PIN that was sent was correct, and to send the new PIN.

PINCHANGENEXTSTATE2

Used with a three-message PIN Change – this is the Next State code (contained in the Transaction Reply to the second Transaction Request) that indicates the new PIN was received OK, and that the ATM should resend the new PIN for confirmation.

PINCHANGENEXTSTATE3

For a three-message PIN Change, this is the Next State code that indicates the PIN Change transaction has been authorized.

PINCHANGEOPCODE1 For a one-message PIN Change, this is the Opcode that will be used in the Transaction Request. For a three-message PIN Change, this is the Opcode that will be used in the initial Transaction Request.

PINCHANGEOPCODE2 For a three-message PIN Change, this is the Opcode that will be used in the second Transaction Request.

PINCHANGEOPCODE3 For a three-message PIN Change, this is the Opcode that will be used in the third Transaction Request.

RECEIPTCUTBOTTOM This parameter is maintained by the APTRA Edge application and should NOT be modified.




RECEIPTCUTTOP This parameter is maintained by the APTRA Edge application and should NOT be modified.

UVALUE U Value to use in the host denial message and other transactions, as needed.

XVALUE X Value to use in the host denial message and other transactions, as needed.

YVALUE Y Value to use in the host denial message and other transactions, as needed.

ZVALUE Z Value to use in the host denial message and other transactions, as needed.

B.1.23 RCPT_CONFIG Group


LOGOLEFTMARGIN Left margin location for the receipt. This can be adjusted depending upon the logo that is being printed.

0

B.1.24 SESSIONFLOW Group


READRAWDATA This is an internal entry used by APTRA Edge. It should NOT be modified.

B.1.25 STARTOFDAY Group


Note that all Translet ID names must be in all uppercase.


ACCOUNTSERVICECOMMSPROGRID

This entry determines which Prog ID the account service should use for Comms. This is set automatically during installation and should NOT be changed.




ACCOUNTSERVICECONFIG


ACCOUNTSERVICEPROGID

Account Services Program ID—must be: INQ.INQTXN

ALLACCOUNTBALANCEPROGID

All Account Balances Program ID—must be: NDCAccountSvsPj.AccountService

ALLACCOUNTBALANCETRANSLETID

Translet ID of the All Account Balance TXO—must be ALLACCOUNTBALANCE

APPLICATIONMANAGEMENTSERVICECONFIG

Application Management Service Configuration file —must be: C:\WebATM\NDCApplicationManagementServiceConfig.xml

APPLICATIONMANAGEMENTSERVICEPROGID

Application Management Service Program ID—must be: AppMgmtFleet.ApplicationManagement

APPMGTREPORTDEPOSITLENGTHERROR

Customer-specific entry that determines whether or not to notify host when a length error occurs during a deposit.

ARCHIVEDAYSTORETAIN

# of days worth of EOD archives to keep on the ATM.

30

ATMTCPIPROLE Determines whether the ATM acts as a Server or Client in TCP/IP communications. This entry must match the configuration of the TCPIPCOMMSSERVICECONFIG. XML file.

ATTRACTPAGE Name of the HTML file that displays the first page of the Customer Application. This page displays continuously when there is no customer activity.

BALANCEPROGID Balance Program ID—must be: INQ.INQTXN

BALANCETRANSLETID Translet ID of the Balance TXO—must be BALANCE

CAMERASERVICEPROGRID

Camera Service Program ID—must be: CameraQueue.Camera

CAPTURECARDTIMEOUT

If a cardholder does not take his card after the completion of his session, the card will be captured after this number of seconds. Used with motorized card reader only.

CARDSERVICECONFIG This parameter is maintained by the APTRA Edge application and should NOT be modified.




CARDSERVICEPROGID Card Service Program ID—must be: NCRaCSSDK.StdCardService

CASHDEPOSITPROGID Cash Deposit Program ID—Must be CashDepositTxn.CashDeposit. This entry is for Enhanced Deposits. It must be blank if Enhanced Deposits are not being used.

CASHDEPOSITTRANSLETID

Translet ID of the Cash Deposit TXO—must be ENVDEPOSIT

CASHRETRACTTIMER This parameter is maintained by the APTRA Edge application and should NOT be modified.

CASHRETRACTWAITFORAUTH

Determines whether or not the ATM should wait for authorization from the host after retracting cash during any transaction that calls the retract function from the WebATM.xml.

CBENVDEPOSITPROGID Deposit with Cash Back Deposit Program ID—must be: DepositTxn.Deposit

CBENVDEPOSITTRANSLETID

Translet ID of the Deposit with Cash Back TXO—must be CBENVDEPOSIT

CBWITHDRAWALPROGID

Deposit with Cash Back Withdrawal Program ID—must be: WDL.WDLTXN

CBWITHDRAWALTRANSLETID

Translet ID of the Withdrawal portion of the Deposit with Cash Back TXO—must be CBWITHDRAWAL

CHECKCASHDISPENSERBEFOREEXECUTE

True/False entry that determines whether or not the TXO should check the availability of the cash dispenser prior to executing the transaction; if the device is not available, then the TXO will not send the transaction and will return an error. If set to False, the error will occur during fulfillment.

True

CHECKDEPOSITPROGID Check Deposit Program ID—Must be NCRCheckDeposit.CheckDeposit. This entry is for Enhanced Deposits. It must be blank if Enhanced Deposits are not being used.

CHECKDEPOSITTRANSLETID

Translet ID of the Check Deposit TXO—must be ENVDEPOSIT




CHECKENVELOPEDEPOSITORYBEFOREEXECUTE

True/False entry that determines whether or not the TXO should check the availability of the depository prior to executing the transaction; if the device is not available, then the TXO will not send the transaction and will return an error. If set to False, the error will occur during fulfillment.

True

CHECKREORDERPROGID

Check Reorder Program ID—must be: Inq.Inqtxn

CHECKREORDERTRANSLETID

Translet ID of the Check Reorder TXO—must be CHECKREORDER

CHECKSERVICEPROGID Check Service Program ID—Must be NCRCheck.Check. The Check program does the CPM-related processing. This entry must be blank if Enhanced Deposits are not being used.

CLEARAVAILABILITYONEXITSUPERVISOR

Yes specifies that all "forced unavailable" transactions should be cleared and set back to available after an exit supervisor. See FORCEUNAVAILABLEONNOCASH and FORCEUNAVAILABLEONNOST AMPS.

CLEARRECEIPTBEFOREREVERSE

Determines whether or not to clear the receipt data if a reversal of the withdrawal or deposit transaction is necessary. True - clear receipt data False - do not clear receipt data

True

CLOSECOMPLETEDELAY

Sets the number of seconds the Thank You screen is displayed beyond the 1-2 seconds required for internal processing. If this value is set to 0, the Thank you screen will display for less than 2 seconds while the code is executed.

0

CONFIGURATIONXMLFILENAME

Filename (including the path) of the configuration XML file – must be c:\webatm\webatm.xml

CONSUMERSERVICEPROGID

Consumer Service Program ID—must be: ConsumerSvcPj.ConsumerService

CRMSERVICECONFIG This parameter is maintained by the APTRA Edge application and should NOT be modified.

CRMSERVICEPROGID CRM Service Program ID—must be: SuntrustCRMService.CRMService




DEPOSITPROGID Deposit Program ID—must be: DepostTXN.Deposit

DEPOSITTIMER This parameter is maintained by the APTRA Edge application and should NOT be modified.

DISPLAYALLACCOUNTBALANCEPROGID

All Account Balance Program ID—must be: INQ.INQTXN

DISPLAYALLACCOUNTBALANCETRANSLETID

Translet ID of the All Account Balance Display TXO—must be DISPLAYALLACCOUNTBALANCE

DISPLAYBALANCEPROGID

All Account Balance Program ID—must be: INQ.INQTXN

DISPLAYBALANCETRANSLETID

Translet ID of the Display Balance TXO—must be DISPLAYBALANCE

EJDATAFORMATTERPROGID

Electronic Journal Formatter Program ID— • For the OS/2 format, this must be set to:

NDCBSRecFrmtrNoTag.EJRcrFormater This is the default.

• For the APTRA Edge EJ format, this must be set to: BaseEJRcrdFormatterPJ.EJRcr dFormatter

EJDATARETRIEVERPROGID

Electronic Journal Data Retriever Program ID—must be: EJUpLoad.QueueManager

EJECTCARDCOUNT Internal counter. This parameter is maintained by the APTRA Edge application and should NOT be modified.

EJFILLDATABLOCK This parameter is maintained by the APTRA Edge application and should NOT be modified.

EJUPLOADQUEUEMANAGERPROGID

Electronic Journal Queue Manager Program ID—must be: EJUpLoad.QueueManager

ELPAYMENTPROGID Electronic Payment Program ID - TransferTxn.Transfer

ELPAYMENTTRANSLETID

Translet ID of the Electronic Payment TXO—must be ELECTRONICPAYMENT

ENHDEPEODPROGID Enhanced Deposit End of Day Program ID—must be: EnhDepEOD.EnhDepEODTXn

ENVDEPOSITPROGID Envelope Deposit Program ID— DepositTxn.Deposit




ENVDEPOSITTRANSLETID

Translet ID of the Envelope Deposit TXO—must be ENVDEPOSIT

ENVPAYMENTPROGID Envelope Payment Program ID— DepositTxn.Deposit

ENVPAYMENTTRANSLETID

Translet ID of the Envelope Payment TXO—must be ENVPAYMENT

ENVPMTFROMACCTPROGID

Envelope Payment From Account Program ID — DepositTxn.Deposit

ENVPMTFROMACCTTRANSLETID

Translet ID of the Envelope Payment From Account TXO—must be EnvPmtFromAcct

ENVPMTTOACCTPROGID

Envelope Payment To Account Program ID — DepositTxn.Deposit

ENVPMTTOACCTTRANSLETID

Translet ID of the Envelope Payment To Account TXO—must be ENVPMTTOACCT

FASTCASHCARDAFTERCASH

Setting this entry to True will return the cardholder card immediately after the cash is dispensed and before the receipt is printed during a Fast Cash transaction. Setting this to False will return the card after the cash is dispensed and the receipt is printed.

False

FASTCASHPROGID Fast Cash Program ID - WDL.WDLTXN FASTCASHTRANSLETID Translet ID of the Fast Cash TXO—must be

FASTCASH

FORCEUNAVAILABLEONNOCASH

True specifies that all cash dispensing transactions will be unavailable to the cardholder when the dispenser runs out of cash.

FORCEUNAVAILABLEONNOSTAMPS

True specifies that the stamp transaction will be unavailable to the cardholder when the dispenser runs out of stamps.

FULLSTATEMENT1PROGID

Full Statement 1 Program ID - Statement.StatementTxn

FULLSTATEMENT1TRANSLETID

Translet ID of the Full Statement 1 TXO—must be STATEMENTFULL1

FULLSTATEMENT2PROGID

Full Statement 2 Program ID - Statement.StatementTxn

FULLSTATEMENT2TRANSLETID

Translet ID of the Full Statement 2 TXO—must be STATEMENTFULL2

FULLSTM_INTERIMPROGID

Full Statement Interim Program ID – must be StatementFull1




FULLSTM_INTERIMTRANSLETID

Translet ID of the Full Statement Interim TXO - Must be STATEMENT.STATEMENTTXN

FULLSTM_LASTMONTHLYPROGID

Full Statement Last Monthly Program ID – must be Statement.StatementTxn

FULLSTM_LASTMONTHLYTRANSLETID

Translet ID of the Full Statement Last Monthly TXO – must be STATEMENTFULL2

HEARTBEATINTERVAL Specifies the interval, in minutes, at which an SNMP heartbeat is sent to Gasper. Must be a value greater than 5.

JOURNALCREITERATRACING

When this is set to True, every detail defined in the Journal.xml file will be recorded. This would be used if you are having trouble with journaling.

False

JOURNALDEVICEDATA Indicates whether or not device data should be logged to the EJ. If this parameter is omitted from the dd.dat, all device data will be logged.

True

JOURNALHOSTDATA Indicates whether or not host data will be logged as part of the journal.xml. If this parameter is omitted from the dd.dat, host data will be logged. True Specifies that host data will be

logged as part of the journal. False Specifies that host data will not be

logged.

True

JOURNALPROGID Journal Program ID—must be NCRJournal.Journal

JOURNALTXODATA Indicates whether or not transaction data will be logged as part of the journal.xml. If this parameter is omitted from the dd.dat, all transaction data is logged. True Specifies that transaction data will be

logged as part of the journal. False Specifies that transaction data will

not be logged.

True

LOGO1 Full path (including the filename) of the .img file that is loaded at start of day so it can be printed on the receipts.

MACHINETYPE This parameter is maintained by the APTRA Edge application and should NOT be modified.




MESSAGETOBANKPROGID

Message To Bank transaction Program ID – must be DepositTxn.Deposit

MESSAGETOBANKTRANSLETID

Translet ID of the Message To Bank TXO - Must be MESSAGETOBANK

MINISTATEMENT[1-x]PROGID

Mini Statement[1-x] Program ID—must be: MiniStatement.MiniStatementTxn.

MINISTATEMENT[1-x]TRANSLETID

Translet ID of the MiniStatement[1-x] TXO - Must be MINISTATEMENT1, MINISTATEMENT2, etc.

MINISTM_LAST10TXPROGID

Mini Statement Last 10 Transactions Program ID - MiniStatement.MiniStatementTxn

MINISTM_LAST10TXTRANSLETID

Translet ID of the Mini Statement Last 10 Transactions TXO - STATEMENT10TRN

MINISTM_LAST5CARDPROGID

Mini Statement Last 5 Withdrawals Program ID - MiniStatement.MiniStatementTxn

MINISTM_LAST5CARDTRANSLETID

Translet ID of the Mini Statement Last 5 Transactions TXO – STATEMENT5CARD

MINISTM_LAST5CHECKSPROGID

Mini Statement Last 5 Checks Program ID - MiniStatement.MiniStatementTxn

MINISTM_LAST5CHECKSTRANSLETID

Translet ID of the Mini Statement Last 5 Checks TXO – STATEMENT5CHK

MINISTM_LAST5DEPOSITSPROGID

Mini Statement Last 5 Deposits Program ID - MiniStatement.MiniStatementTxn

MINISTM_LAST5DEPOSITSTRANSLETID

Translet ID of the Mini Statement Last 5 Deposits TXO – STATEMENT5DEP

MOUSECURSOR If set to YES, this shows a cursor on the screen. This is used when working on a development system without a touch screen. On a production ATM, this is set to NO.

OPENCOMPLETEPAGE Name of the HTML file that displays the first page of a customer session. This page displays when the customer first touches the screen or inserts a card in the card reader.

OUTOFSERVICEPAGE Name of the HTML file that displays the “out of service” message.

PERSONALIZEDFASTCARDAFTERCASH

Setting this entry to True will return the cardholder card immediately after the cash is dispensed and before the receipt is printed during a Personalized Fast Cash transaction. Setting this to False will return the card after the cash is dispensed and the receipt is printed.

False




PERSONALIZEDFASTCASHPROGID

Personalized Fast Cash Program ID—must be: WDL.WDLTXN

PERSONALIZEDFASTCASHTRANSLETID

Translet ID of the Personalized Fast Cash TXO—must be: WITHDRAWAL

PINCHANGEPROGID PIN Change Program ID—must be: PINChange.PinChangeTxn

PINCHANGETRANSLETID

Translet ID of the PIN Change TXO—must be one of the following: • PINCHANGE1 - used with a 1 message

PIN Change. • PINCHANGE1BC - used with a 1

message Pin Change with the old PIN in the Pin Buffer, and new PINs in Buffers B and C.

• PINCHANGE3 – used with a 3 message PIN Change.

PRINTDEPOSITTOTAL Yes/No entry used with check and cash deposits (Enhanced Deposits) that determines whether a locally maintained deposit total will be printed on the cardholder’s receipt (Yes), or if this locally maintained deposit total will not be printed on the receipt (No). If host sends the deposit total to print on the receipt, this local total printing can be redundant.

PRINTIMMEDIATEPROGID

Program ID of program used when host sends a print immediate command to the terminal. It must be set to USNDCCustomCode.Print Immediate.

PURCHASE1MIXREQUIRED

This sets the TXO property of whether or not a cash mix is required for a Purchase1 transaction. This is used with IFX.

False

PURCHASE1PROGID Purchase 1 Program ID—must be: WDL.WDLTXN

PURCHASE1TRANSLETID

Translet ID of the Purchase 1 transaction—must be: PURCHASE1

READTRACK1 True/False entry that specifies whether or not to read the track 1 data on the consumer's card to be used during transactions.

False

REBOOTONPOPUP This entry must always be set to Y for production ATMs. It allows the ATM to automatically reboot if a popup window should display.

Y




RECEIPTCREITERATRACING

When this is set to True, every detail defined in the Receipt.xml file will be recorded. This would be used if you are having trouble with receipts.

False

RECEIPTPROGID Receipt Program ID—must be: NCRReceipt.Receipt

REFRESHONHEARTBEAT

If YES, refreshes the browser page on heartbeat.

RETURNCARDIMMEDIATELY

True indicates that a motorized card reader should act like a DIP reader and return the card immediately after it is read.

REVERSALWAITFORAUTH

Determines whether or not the ATM should wait for authorization from the host after a reversal during any transaction that calls the reversal function from the WebATM.xml.

SCREENDOWNLOADPROGID

Screen Download Program ID—must be: NDCBSScreenDwnPj.ScreenDownloader.

SESSIONFLOWPROGID Session Flow Program ID—must be: SessionFlowPj.SessionFlow

SESSIONRESOURCEPROGID

Session Resource Program ID—must be: NCRSessionResource.AlwaysAvailable

SPECIALKEY This parameter is maintained by the APTRA Edge application and should NOT be modified.

STAMPSDISPENSETYPE This entry defines the canister type used for stamps. It is possible to have more than one non-cash canister.

STAMPSMIXREQUIRED This sets the TXO property of whether or not a cash mix is required for stamps. This is used with IFX.

False

STAMPSPROGID Stamps Program ID—must be: WDL.WDLTXN

STAMPSTRANSLETID Translet ID of the Stamps TXO—must be: STAMPS

STARTPAGE Name of the HTML file that displays at Start of Day.

STATEMENT20ALLPROGID

Statement Last 20 All Program ID—Must be Statement.StatementTxn

STATEMENT20ALLTRANSLETID

Translet ID of the Statement Last 20 All TXO—must be: STATEMENT20ALL

STATEMENT20CHKPROGID

Statement Last 20 Checks Program ID—Must be Statement.StatementTxn




STATEMENT20CHKTRANSLETID

Translet ID of the Statement Last 20 Checks TXO—must be: STATEMENT20CHK

STATEMENT20TRNPROGID

Statement Last 20 Transactions Program ID—Must be Statement.StatementTxn

STATEMENT20TRNTRANSLETID

Translet ID of the Statement Last 20 Transactions TXO—must be: STATEMENT20TRN

STATEMENTSERVICEPROGID

Statement Service Program ID—Must be NCRStatement.Statement

STOPALTTAB Yes/No entry that determines whether or not the Alt-Tab key combination can be used. This should always be set to Yes for production ATMs.

Yes

TRACEPROGID

Trace Program ID—Must be WebATM.Trace

TRANSFERPROGID Transfer Program ID—Must be TransferTxn.Transfer

TRANSFERTRANSLETID Translet ID of the Transfer TXO—must be: TRANSFER

VOLUMEHIGH The value of the high volume setting. VOLUMELOW The value of the low volume setting. VOLUMEMEDIUM The value of the medium volume setting. WEBPAGELOCATION Name of the directory where the Customer

Application HTML files are located.

WITHDRAWALMIXREQUIRED

This sets the TXO property of whether or not a cash mix is required for a withdrawal transaction. This is used with IFX.

False

WITHDRAWALPROGID Withdrawal Program ID—must be: WDL.WDLTXN

WITHDRAWALTRANSLETID

Translet ID of the Withdrawal TXO—must be: WITHDRAWAL

XFSRECEIPTPRINTERCOACTIONPROGID

XFS Receipt Printer Coaction Program ID—Must be ActiveXFS.XFSReceiptPrintCoAction

XFSRECEIPTPRINTERPROGID

XFS Receipt Printer Program ID—Must be ActiveXFS.ReceiptPrinter

XFSRECEIPTPROGID XFS Receipt Program ID—Must be ActiveXFS.XFSReceipt



B.1.26 STATEMENT


LINESPERPAGE This entry defines the number of lines that will print on a full statement page.

68

B.1.27 SUPERVISOR Group

A change to the ENCRYPTIONTYPE entry in this group requires a reboot and must include the reboot="y" parameter in the <CONFIGURATION_DATA> entry in a Screen / Keyboard Data Load Message.


ATMCONFIGFILELOCATION

Must be: C:\Program Files\NCR APTRA\Bra nch AidRuntime\ATMConfig.xml

CARDTRANSLETFACTORYPROGID


CLEARPURGEBINONEXIT

Yes/No entry that determines whether or not to clear the Purge Bin counts when exiting Supervisor.

No

COINDISPENSERPRESENT

Yes/No entry automatically set by Supervisor that determines whether or not to include this device on the Test Device menu and when exiting Supervisor. This parameter is maintained by the APTRA Edge application and should NOT be modified.

COLUMNS This parameter is maintained by the APTRA Edge application and should NOT be modified.

COMMSKEY This parameter is maintained by the APTRA Edge application and should NOT be modified.

COMMSKEYDATA This parameter is maintained by the APTRA Edge application and should NOT be modified.

CONTINUEPROCEDURE

Internal entry used by APTRA Edge. It should NOT be modified.

CURRENTDISPLAY This parameter is maintained by the APTRA Edge application and should NOT be modified.




DEPOSITORYPRESENT Yes/No entry automatically set by Supervisor that determines whether or not to include this device on the Test Device menu and when exiting Supervisor. This parameter is maintained by the APTRA Edge application and should NOT be modified.

DIAGNOSTICSPASSWORD

Specifies the 4-digit password that must be entered before diagnostics can be done. ‘0000’ indicates that no password is required.

DISPLAYADMINCARDDATA

Yes/No entry that determines if the Enter Admin Card Data item will be included on the settlement menu. Yes = include menu item.

DISPLAYAMOUNT Specifies whether the dollar amount or bill count should be prompted/displayed during settlement. Must be one of the following values: ‘YES’ indicates that the dollar amount is

used instead of bill counts during all settlement / replenishment functions.

‘NO’ indicates that the number of bills is used instead of amounts during all settlement / replenishment functions.

DISPLAYCANISTERTYPEHOST

Specifies whether or not host settlement will be displayed by canister. If No, a total will be displayed. Further, if set to No, the replenisher will not be prompted to enter cash for individual canisters. Rather, he will be prompted for one, total amount for all canisters.

DISPLAYCANISTERTYPELOCAL

Specifies whether or not local settlement will be displayed by canister. If No, a total will be displayed. Further, if set to No, the replenisher will not be prompted to enter cash for individual canisters. Rather, he will be prompted for one, total amount for all canisters.




DISPLAYMEDIAAMOUNT

Specifies whether the dollar amount or number of sheets should be used during settlement of media other than cash. Must be one of the following values: ‘YES’ indicates that the dollar amount is

used instead of the number of sheets during all settlement / replenishment functions.

‘NO’ indicates that the number of sheets is used instead of amounts during all settlement / replenishment functions.

No

DNSIPCONFIGURATION

Yes/No entry that determines whether or not DNS names will be accepted when configuring the Remote Host IP addresses. When set to Yes, names will be accepted.

EJARCHIVEFOLDER Specifies the location of the ej backup files that are created after a Copy EJ function is performed from Supervisor.

c:\ejarchive

ENCRYPTIONREBOOT This parameter is maintained by the APTRA Edge application and should NOT be modified.

ENCRYPTIONTYPE Specifies whether the ATM is using Single Encryption or Triple DES Encryption.

ENTRY This parameter is maintained by the APTRA Edge application and should NOT be modified.

EXITKEYTIMEOUT Specifies the number of seconds to wait for a response on the “Press Enter to Continue” prompt that occurs when exiting from supervisor mode. The ATM will return to the ATM application at the end of this timeout value, even if no response has been given.

FORMARRAYSIZE This parameter is maintained by the APTRA Edge application and should NOT be modified.

HOSTSTATUS This parameter is maintained by the APTRA Edge application and should NOT be modified.

INCLUDEMESSAGETRACE

Causes message traces to be included in the EJ.zip file created by the Supervisor Copy EJ/Copy Backup EJ functions. Yes Webatm.xml should “backup” the

message traces No Webatm.xml should “archive” the

message traces

No




JOURNAL This parameter is maintained by the APTRA Edge application and should NOT be modified.

JOURNALPRINTERPRESENT


JOURNALTXODATA True/False entry that determines whether or not Supervisor TXO data is written to the journal. True = journal the data.

KEYEXCHANGETIMEOUT

Number of seconds to wait for key exchange with host. A value of 0 specifies not to wait for key exchange.

KEYTIMEOUT Specifies the number of seconds supervisor waits for a key entry before timing out. On timeout, supervisor returns to the previous menu.

LOCALCASHAMOUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

LOCALCASHCOUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

LOCALCHECKAMOUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

LOCALCHECKCOUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

MAINTANDSUPPLIESPASSWORD

Specifies the 4-digit password that must be entered before any maintenance and supply functions can be done. ‘0000’ indicates that no password is required.

MASTERKEY This parameter is maintained by the APTRA Edge application and should NOT be modified.

MASTERKEYDATA This parameter is maintained by the APTRA Edge application and should NOT be modified.

MODESWTIMEOUT

Number of minutes the application will wait before automatically going into Normal mode if the operator does not put the Mode switch into Normal mode after exiting Supervisor.

2




NCR This parameter is maintained by the APTRA Edge application and should NOT be modified.

NEXTMENU This parameter is maintained by the APTRA Edge application and should NOT be modified.

PASSWORD This parameter is maintained by the APTRA Edge application and should NOT be modified.

PINTOUSE Specifies which 4-digit password is used for Host Settlement functions. One of the following values should be specified: ‘dd’ indicates that the value specified for

SETTLEMENTPIN should be used. ‘settlement’ indicates that the value

specified for SETTLEMENTPASSWORD should be used.

Blank indicates that the application will prompt the user for a PIN for settlement.

PRINTCHECKLIST Yes/No entry that determines whether or not a list of all checks deposited through the Enhanced Deposit transaction will be printed when the local totals are printed or cleared. When printed, the list contains the Sequence #, Amount and Time Stamp for each individual check deposited since the last time local totals were cleared.

PROXYCONFIGFILELOCATION

Specifies the locations of the proxy configuration file. Normally set to C:\Program Files\NCR APTRA\Branch Aid Runtime\ProxyConfig.xml.

ROWS This parameter is maintained by the APTRA Edge application and should NOT be modified.

SAFEDOORTIMEOUT Number of seconds to allow the replenisher to close the safe door after exiting supervisor (assuming the safe door was left open when supervisor was exited). If the safe door is not closed before this timer expires, the dispenser test will fail.

120

SCRIPTNAME Specifies the default name of the file to execute whenever the Supervisor Copy File function is performed.




SENDBALANCEINQUIRY

Set this to True if your host requires a Balance Inquiry sent for a host settlement print function.

False

SETTLEMENTCONFIGURATIONFILENAME

Specifies the locations of the settlement configuration file. Normally set to C:\Program Files\NCR APTRA\Branch Aid Runtime\Me nu.xml.

SETTLEMENTPASSWORD

Specifies the 4-digit password that must be used with host settlement. ‘0000’ indicates that no password is required.

SETTLEMENTPIN Specifies the 4-digit password that must be used with host settlement. ‘0000’ indicates that no password is required.

SKIPFAULTS This parameter is maintained by the APTRA Edge application and should NOT be modified.

SNMPSECURITY Internal counter that tracks changes to the SNMP security settings. This parameter is maintained by the APTRA Edge application and should NOT be modified.

0

SNMPTRAP Internal counter that tracks changes to the Trap settings. This parameter is maintained by the APTRA Edge application and should NOT be modified.

0

STATEMENTPRINTERPRESENT


SYSTEMCONFIGPASSWORD

Specifies the 4-digit password that must be entered before any system configuration functions can be done. ‘0000’ indicates that no password is required.

TASK This parameter is maintained by the APTRA Edge application and should NOT be modified.

TCPIPCONFIGFILEROOT This is the location of the Netshedge.script file. This script file is used to change IP addresses and is normally located in c:\WebATM.

TESTEDDEVICES This parameter is maintained by the APTRA Edge application and should NOT be modified.




TIMEOUT This parameter is maintained by the APTRA Edge application and should NOT be modified.

TRACK2 This entry should contain the actual card data used for a settlement card. A sample value for this entry would be: ;98498456128749503=25379000000?

TRACK2FORMAT This entry defines the format of the card data used for a settlement card. The values x and y are used as variables and any other special characters, such as ; ?, and = must be included. A sample value for the track 2 data shown in the Track2 entry above would be: ;xxxxxxxxxxxxxxxxx=yyyyyyyyyyy?

TTU This parameter is maintained by the APTRA Edge application and should NOT be modified.

USERNAME This parameter is maintained by the APTRA Edge application and should NOT be modified.

USERTYPE This parameter is maintained by the APTRA Edge application and should NOT be modified.

VDM This parameter is maintained by the APTRA Edge application and should NOT be modified.

VDMEXITDELAY Sets the delay, in seconds, that occurs between exit from the sysapp diagnostics and return to supervisor.

VOLUMEINCREMENT The value to use for incrementing the volume. VPICOMMSCONFIGFILEROOT

This is the location of the TCPIPCommsServiceConfig.xml file.

XMLCONFIGFILELOCATION


B.1.28 SUPJRN Group


PRINTLINEXX These are dynamic entries used for journal printing. They should NOT be modified.



B.1.29 SUPGENERICACTIVITY Group


EVENTDATA This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.30 SUPSETTLEMENT Group


SEQUENCENUMBER This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.31 TOTAL Group


BILLSADDEDTYPE[1-4] Internal Counter. This parameter is maintained by the APTRA Edge application and should NOT be modified.

BILLSDISPENSEDTYPE[1-4]

Internal Counter. This parameter is maintained by the APTRA Edge application and should NOT be modified.

BILLSRETRACTEDTYPE[1-4]


BILLSSUBTRACTEDTYPE[1-4]


TOTALDEPOSITAMOUNT


TOTALPAYMENTAMOUNT




B.1.32 TRACE Group


ARCHIVEDIR Directory where trace files are moved when they are archived. This directory can be on a local drive or remote drive on a server.

ARCHIVEREASON This can be “SIZE”, “TIME”, “SIZETIME” or “ONDEMAND”. “SIZE” archives the trace file at cutover if its size is greater than or equal to MAXSIZE. “TIME” archives the trace file at cutover if ARCHIVETIME has passed. “SIZETIME” archives the trace file at cutover if either its size is greater than or equal to MAXSIZE, or if ARCHIVETIME has passed. “ONDEMAND” archives the trace file at cutover.

SIZE

ARCHIVETIME If ARCHIVEREASON is set to "TIME", then this value determines when the trace file will be archived. This entry is the time in 24-hour HH:MM format. If the set time has passed, the trace file will be moved to the archive directory at cutover.

LASTDATEARCHIVE This parameter is maintained by the APTRA Edge application and should NOT be modified.

MAXSIZE If ARCHIVEREASON is set to “SIZE,” then this value determines when the trace file will be archived. This value is in kilobytes. When a file is this size or greater, it will be moved to the archive directory at cutover. A value less than 512 is not recommended.

512

ORIGTRACEFILENAME This parameter is maintained by the APTRA Edge application and should NOT be modified.

TRACEFILENAME This is the full path and filename of the trace log file. When the data dictionary contains this field, the trace function is on. Note: If you plan to use the separately-priced NCR EJ Viewer to view the trace, the filename must be in the format of tr*.dat.



B.1.33 VDM Group


COUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

DONECOUNT This parameter is maintained by the APTRA Edge application and should NOT be modified.

B.1.34 WITHDRAWAL Group












B.2 Sample Data Dictionary

The data dictionary file that appears below is a sample for a typical ATM. Entries in the data dictionary are not order dependent. To comment out a field so the default is used, put any character at the beginning of the line. For example, ;TRACE.ARCHIVEREASON=SIZETIME comments out the entry and defaults to ARCHIVEREASON=SIZE.

ALLTRANSACTIONS.AMOUNTOBJECT=AccountSvcPj.Amount BNA.COMMSTIMEOUT=120000 BNA.ENABLETIMEOUT=60 BNA.MAXBILLS=40 CASHDEPOSIT.SENDUNSOLICITEDMESSAGE=FALSE CHECK.ARCHIVEDIR=c:\archivedir\check CHECK.BATCHFILENAME=c:\webatm\check.xml CHECK.ENDORSEMENTPRINTZONE=1 CHECK.IMAGERESOLUTION=200 CHECK.LIFTREAR=True CHECK.NBRIMAGEARCHIVES=100 CHECK.RETURNCHECKTIMEOUT=30 CHECK.SCANCHECKTIMEOUT=30 CONSUMERFLOW.ACCOUNT1=CHECKING CONSUMERFLOW.ACCOUNT10=CHECKING2 CONSUMERFLOW.ACCOUNT11=CHECKING3 CONSUMERFLOW.ACCOUNT12=SAVINGS1 CONSUMERFLOW.ACCOUNT13=SAVINGS2 CONSUMERFLOW.ACCOUNT14=SAVINGS3 CONSUMERFLOW.ACCOUNT15=CREDIT1 CONSUMERFLOW.ACCOUNT16=CREDIT2 CONSUMERFLOW.ACCOUNT17=CREDIT3 CONSUMERFLOW.ACCOUNT18=OTHER1 CONSUMERFLOW.ACCOUNT19=OTHER2 CONSUMERFLOW.ACCOUNT2=SAVINGS CONSUMERFLOW.ACCOUNT20=OTHER3 CONSUMERFLOW.ACCOUNT21=MULTIPLE CONSUMERFLOW.ACCOUNT3=CREDIT CONSUMERFLOW.ACCOUNT4=OTHER CONSUMERFLOW.ACCOUNT5=MULTIPLECHECKING CONSUMERFLOW.ACCOUNT6=MULTIPLESAVINGS CONSUMERFLOW.ACCOUNT7=MULTIPLECREDIT CONSUMERFLOW.ACCOUNT8=MULTIPLEOTHER CONSUMERFLOW.ACCOUNT9=CHECKING1 CONSUMERFLOW.ACCOUNTBALANCE=YES,2,2 CONSUMERFLOW.ACCOUNTBALANCEACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.ACCOUNTBALANCERECEIPTOPTION=YES CONSUMERFLOW.BANKNAME=NCR Bank CONSUMERFLOW.BYPASSPREPAREENVELOPE=NO CONSUMERFLOW.BYPASSSELECTSTAMPSTOENTERSHEETS=NO CONSUMERFLOW.CANCELBUTTON=NO CONSUMERFLOW.CHANGEPIN=YES,2,5 CONSUMERFLOW.CHANGEPINRECEIPTOPTION=YES CONSUMERFLOW.CHECKREORDER=YES,1,7 CONSUMERFLOW.CHECKREORDERRECEIPTOPTION=YES CONSUMERFLOW.CRMSERVICETIMEOUTBEFOREPLEASEWAIT=0



CONSUMERFLOW.DEBUG=NO CONSUMERFLOW.DEPOSITWITHCASHBACK=YES,2,3 CONSUMERFLOW.DEPOSITWITHCASHBACKACCOUNTS=1 CONSUMERFLOW.DEPOSITWITHCASHBACKRECEIPTOPTION=YES CONSUMERFLOW.DIPCARDREADERMULTITRANS=NO CONSUMERFLOW.DISPENSERAVAILABLE=YES CONSUMERFLOW.DISPLAYMESSAGEWHENPREFERENCESUNAVAILABLE=NO CONSUMERFLOW.DISPLAYPERSONALIZEDOTHERAMOUNTBUTTON=YES CONSUMERFLOW.DISPLAYPRINTRECEIPTBUTTON=YES CONSUMERFLOW.ELECTRONICPAYMENT=YES,4,2 CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT1TOACCOUNTS=,,,,1,2,3 CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT2TOACCOUNTS=,,,,1,2,3 CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT3TOACCOUNTS=,,,,1,2,3 CONSUMERFLOW.ELECTRONICPAYMENTFROMACCOUNT4TOACCOUNTS=,,,,1,2,3 CONSUMERFLOW.ELECTRONICPAYMENTRECEIPTOPTION=YES CONSUMERFLOW.ENHANCEDDEPOSIT=YES,4,3 CONSUMERFLOW.ENHANCEDDEPOSITRECEIPTOPTION=YES CONSUMERFLOW.ENVDISPENSEOPTION=NO CONSUMERFLOW.ENVELOPEDEPOSIT=YES,1,3 CONSUMERFLOW.ENVELOPEDEPOSIT2ACCOUNTS=,,,,1,2 CONSUMERFLOW.ENVELOPEDEPOSIT2RECEIPTOPTION=YES CONSUMERFLOW.ENVELOPEDEPOSITACCOUNTS=,,,,1,2,21 CONSUMERFLOW.ENVELOPEDEPOSITRECEIPTOPTION=YES CONSUMERFLOW.ENVELOPEPAYMENT=YES,1,4 CONSUMERFLOW.ENVELOPEPAYMENTRECEIPTOPTION=YES CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNT=NO CONSUMERFLOW.ENVLOPEPAYMENTFROMACCOUNTS= CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNT=NO CONSUMERFLOW.ENVLOPEPAYMENTTOACCOUNTS=NO CONSUMERFLOW.FASTCASH1=YES,1,1 CONSUMERFLOW.FASTCASH1ACCOUNTS= CONSUMERFLOW.FASTCASH1AMOUNT=20 CONSUMERFLOW.FASTCASH2=NO CONSUMERFLOW.FASTCASH2AMOUNT=30 CONSUMERFLOW.FASTCASH3=NO CONSUMERFLOW.FASTCASH3AMOUNT=50 CONSUMERFLOW.FASTCASH4=NO CONSUMERFLOW.FASTCASH4AMOUNT=100 CONSUMERFLOW.FASTCASHAMOUNTSCREEN=YES CONSUMERFLOW.FASTCASHRECEIPTOPTION=YES CONSUMERFLOW.FIT1ACCOUNTBALANCE=NO CONSUMERFLOW.FIT1DEPOSITWITHCASHBACK=NO CONSUMERFLOW.FIT1ELECTRONICPAYMENT=NO CONSUMERFLOW.FIT1ENHANCEDDEPOSIT=NO CONSUMERFLOW.FIT1ENVELOPEDEPOSIT=NO CONSUMERFLOW.FIT1ENVELOPEPAYMENT=NO CONSUMERFLOW.FIT1FASTCASH1=NO CONSUMERFLOW.FIT1FASTCASH2=NO CONSUMERFLOW.FIT1FASTCASH3=NO CONSUMERFLOW.FIT1FASTCASH4=NO CONSUMERFLOW.FIT1FASTCASHAMOUNTSCREEN=NO CONSUMERFLOW.FIT1MINISTATEMENT1=NO CONSUMERFLOW.FIT1NONTRANSBUTTON1=Main Menu,3,8,1 CONSUMERFLOW.FIT1NONTRANSBUTTON2=Main Menu,4,8,1 CONSUMERFLOW.FIT1NUMBEROFNONTRANSBUTTONS=0 CONSUMERFLOW.FIT1STAMP=NO



CONSUMERFLOW.FIT1TRANSFER=NO CONSUMERFLOW.FIT1WITHDRAWAL=NO CONSUMERFLOW.FITCONSUMERTYPE1=1 CONSUMERFLOW.FITSETTLEMENTCARD1= CONSUMERFLOW.FLOWSELECT=0 CONSUMERFLOW.FULLSTATEMENT1=YES,2,6 CONSUMERFLOW.FULLSTATEMENT1ACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.FULLSTATEMENT2=NO CONSUMERFLOW.INVALIDFIT1= CONSUMERFLOW.LANGUAGEFIRSTANDPINNEXT=YES CONSUMERFLOW.LANGUAGEMENU1=7,eng,8,spa CONSUMERFLOW.LANGUAGEMENU2= CONSUMERFLOW.LANGUAGEOPTION=YES CONSUMERFLOW.MAINMENUBUTTON=NO CONSUMERFLOW.MENUSETTLEMENTCARD1=M023 CONSUMERFLOW.MESSAGETOBANK=YES,4,5 CONSUMERFLOW.MESSAGETOBANKACCOUNTS=1 CONSUMERFLOW.MINISTATEMENT1=YES,3,1 CONSUMERFLOW.MINISTATEMENT1ACCOUNTS=,,,,1,2 CONSUMERFLOW.MINISTATEMENT1FEE=1.00 CONSUMERFLOW.MINISTATEMENT1FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT1RECEIPTOPTION=NO CONSUMERFLOW.MINISTATEMENT2=YES,3,2 CONSUMERFLOW.MINISTATEMENT2ACCOUNTS=,,,,1,2 CONSUMERFLOW.MINISTATEMENT2FEE=1.00 CONSUMERFLOW.MINISTATEMENT2FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT2RECEIPTOPTION=NO CONSUMERFLOW.MINISTATEMENT3=YES,3,3 CONSUMERFLOW.MINISTATEMENT3ACCOUNTS=,,,,1,2 CONSUMERFLOW.MINISTATEMENT3FEE=1.00 CONSUMERFLOW.MINISTATEMENT3FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT3RECEIPTOPTION=NO CONSUMERFLOW.MINISTATEMENT4=YES,3,4 CONSUMERFLOW.MINISTATEMENT4ACCOUNTS=1 CONSUMERFLOW.MINISTATEMENT4FEE=1.00 CONSUMERFLOW.MINISTATEMENT4FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT4RECEIPTOPTION=NO CONSUMERFLOW.MINISTATEMENT5ACCOUNTS=1 CONSUMERFLOW.MINISTATEMENT5FEE=1.00 CONSUMERFLOW.MINISTATEMENT5FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT5RECEIPTOPTION=NO CONSUMERFLOW.MINISTATEMENT6ACCOUNTS=1 CONSUMERFLOW.MINISTATEMENT6FEE=1.00 CONSUMERFLOW.MINISTATEMENT6FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT6RECEIPTOPTION=NO CONSUMERFLOW.MINISTATEMENT7ACCOUNTS=1 CONSUMERFLOW.MINISTATEMENT7FEE=1.00 CONSUMERFLOW.MINISTATEMENT7FEEOPTION=YES CONSUMERFLOW.MINISTATEMENT7RECEIPTOPTION=NO CONSUMERFLOW.MOTORCARDREADERENTERPIN=NO CONSUMERFLOW.MOTORCARDREADERMULTITRANS=YES CONSUMERFLOW.MULTIPLEACCOUNTSELECTION=YES CONSUMERFLOW.NEVERSETPREFERENCEBUTTON=NO CONSUMERFLOW.NONTRANSBUTTON1=Next Menu,1,8,2 CONSUMERFLOW.NONTRANSBUTTON2=Main Menu,2,4,1 CONSUMERFLOW.NONTRANSBUTTON3=Next Menu,2,8,4



CONSUMERFLOW.NONTRANSBUTTON4=Main Menu,4,4,1 CONSUMERFLOW.NONTRANSBUTTON5=MINI STATEMENT,1,6,3 CONSUMERFLOW.NUMBEROFACCOUNTS=21 CONSUMERFLOW.NUMBEROFFASTCASH=4 CONSUMERFLOW.NUMBEROFFITCONSUMERTYPE=0 CONSUMERFLOW.NUMBEROFIMAGEWAIT=0 CONSUMERFLOW.NUMBEROFIMAGEWELCOME=0 CONSUMERFLOW.NUMBEROFINVALIDFITS=0 CONSUMERFLOW.NUMBEROFMSGTHANK=0 CONSUMERFLOW.NUMBEROFMSGWAIT=0 CONSUMERFLOW.NUMBEROFMSGWELCOME=0 CONSUMERFLOW.NUMBEROFNONTRANSBUTTONS=5 CONSUMERFLOW.NUMBEROFSETTLEMENTCARD=0 CONSUMERFLOW.NUMBEROFTIMEOUT=4 CONSUMERFLOW.OARACCOUNTOPTION=NO CONSUMERFLOW.OARACCOUNTPAGE="" CONSUMERFLOW.OTHERACCOUNTOPTION=NO CONSUMERFLOW.OTHERACCOUNTPAGE="" CONSUMERFLOW.OTHERAMOUNTPOSITIONONWITHDRAWALMENU=8 CONSUMERFLOW.PERSONALIZATIONCARDFITS=ALL CONSUMERFLOW.PERSONALIZEDENTERAMOUNTSCREEN=NO CONSUMERFLOW.PERSONALIZEDFASTCASH=NO CONSUMERFLOW.PERSONALIZEDFASTCASHACCOUNTS=1 CONSUMERFLOW.PERSONALIZEDFASTCASHMENUBUTTONS=1,20,2,40,3,60,4,80,5,100,6,200 CONSUMERFLOW.PERSONALIZEDNOPREFERENCEOTHERAMOUNTPOSITION=7 CONSUMERFLOW.PERSONALIZEDOTHERAMOUNTPOSITIONFASTCASHMENU=8 CONSUMERFLOW.PINANIMATION=YES CONSUMERFLOW.PINAUTOENTEROPTION=YES CONSUMERFLOW.PROMOTE=NO CONSUMERFLOW.PURCHASE1=NO CONSUMERFLOW.PURCHASE1FEE=0.00 CONSUMERFLOW.PURCHASE1PRICE=10.00 CONSUMERFLOW.PURCHASE1RECEIPTOPTION=YES CONSUMERFLOW.PURCHASE2=NO CONSUMERFLOW.RECEIPTOPTION=YES CONSUMERFLOW.RECEIPTOPTIONAFTERPINENTRY=NO CONSUMERFLOW.SETTLEMENT=NO CONSUMERFLOW.SHOWWANTTOENTERPREFERENCESSCREEN=YES CONSUMERFLOW.SINGLEACCOUNTSELECTOPTION=NO CONSUMERFLOW.SPLITDEPOSIT=NO 'CONSUMERFLOW.SPLITDEPOSIT=YES,4,1 CONSUMERFLOW.SPLITDEPOSITACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.SST=YES CONSUMERFLOW.STAMP=YES,2,1 CONSUMERFLOW.STAMPACCOUNTS=,,,,1,2 CONSUMERFLOW.STAMPFEE=0.00 CONSUMERFLOW.STAMPFEEPERSHEET=0.49 CONSUMERFLOW.STAMPPRICE=6.66 CONSUMERFLOW.STAMPRECEIPTOPTION=YES CONSUMERFLOW.STAMPSMENUBUTTONS=5,1,6,2,7,3,8,4 CONSUMERFLOW.STAMPSPERSHEET=18 CONSUMERFLOW.SUBACCOUNTSFORACCOUNT21=,,,,5,6,8 CONSUMERFLOW.SUBACCOUNTSFORACCOUNT4=,,,,5,6,7,8 CONSUMERFLOW.SUBACCOUNTSFORACCOUNT5=,,,,9,10,11 CONSUMERFLOW.SUBACCOUNTSFORACCOUNT6=,,,,12,13,14



CONSUMERFLOW.SUBACCOUNTSFORACCOUNT7=,,,,15,16,17 CONSUMERFLOW.SUBACCOUNTSFORACCOUNT8=,,,,18,19,20 CONSUMERFLOW.SURCHARGEACCEPTED=NO CONSUMERFLOW.SWITCH=ACI CONSUMERFLOW.TIMEOUTFORPAGETYPE1=4 CONSUMERFLOW.TIMEOUTFORPAGETYPE1VG=7 CONSUMERFLOW.TIMEOUTFORPAGETYPE2=8 CONSUMERFLOW.TIMEOUTFORPAGETYPE2VG=15 CONSUMERFLOW.TIMEOUTFORPAGETYPE3=30 CONSUMERFLOW.TIMEOUTFORPAGETYPE3VG=35 CONSUMERFLOW.TIMEOUTFORPAGETYPE4=40 CONSUMERFLOW.TIMEOUTFORPAGETYPE4VG=60 CONSUMERFLOW.TRACK1DATA=NO CONSUMERFLOW.TRANSFER=YES,1,2 CONSUMERFLOW.TRANSFERFROMACCOUNT10TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT11TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT12TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT13TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT14TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT15TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT16TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT17TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT18TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT19TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT1TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT20TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT2TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT3TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT4TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERFROMACCOUNT9TOACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.TRANSFERRECEIPTOPTION=YES CONSUMERFLOW.UPDATEPREFERENCESWHENSESSIONCLOSES=NO CONSUMERFLOW.VOICEBANKNAME=NCR Bank CONSUMERFLOW.VOICEGUIDANCE=Yes CONSUMERFLOW.WITHDRAWAL=YES,1,5 CONSUMERFLOW.WITHDRAWALACCOUNTS=,,,,1,2,3,4 CONSUMERFLOW.WITHDRAWALFIXEDAMOUNT=NO CONSUMERFLOW.WITHDRAWALMENUBUTTONS=1,10,2,20,3,30,4,40,5,50,6,60,7,70 CONSUMERFLOW.WITHDRAWALMENUSCREEN=NO CONSUMERFLOW.WITHDRAWALRECEIPTOPTION=YES CRMSERVICE.INITIATE=NEVER CURRENCY.CASSETTE1TYPE=USD CURRENCY.CASSETTE1UNITID=1 CURRENCY.CASSETTE1UNITTYPE=0 CURRENCY.CASSETTE1VALUE=20 CURRENCY.CASSETTE2TYPE=USD CURRENCY.CASSETTE2UNITID=2 CURRENCY.CASSETTE2UNITTYPE=0 CURRENCY.CASSETTE2VALUE=10 CURRENCY.CASSETTE3TYPE=USD CURRENCY.CASSETTE3UNITID=3 CURRENCY.CASSETTE3UNITTYPE=1 CURRENCY.CASSETTE3VALUE=6.66 CURRENCY.CASSETTE4TYPE=USD CURRENCY.CASSETTE4UNITID=4 CURRENCY.CASSETTE4UNITTYPE=0



CURRENCY.CASSETTE4VALUE=100 CURRENCY.REJECTBINMAXIMUMBILLS=500 CURRENCYEXPONENT. =0 CURRENCYEXPONENT.USD=0 CUTOVER.NEXTTIME=23:45 EJUPLOAD.NEXTFILEINDEX=0 EJUPLOAD.REPOSITORYDIRPATH=C:\EJREPOSITORY EVENTLOG.ARCHIVEDIR=c:\archivedir\eventlog EVENTLOG.ARCHIVEREASON=ONDEMAND EVENTLOG.MAXSIZE=2048 GLOBAL.MACHINEADDRESS1=12 W. MAIN GLOBAL.MACHINEADDRESS2=DAYTON, OH 45409 GLOBAL.MACHINENUMBER=110811 GLOBAL.TERMINALOWNER=StandardEdition JOURNAL.PAPERJOURNAL=FALSE JOURNAL.PAPERJOURNALFORMSDIR=c:\xfs\data\jptr\forms JOURNAL.PAPERSPOOLEXE=c:\webatm\spool.exe JOURNAL.STARTTIME=6/2/05 7:45:34 AM JOURNAL.TEMPLATEFILE=c:\webatm\journal.xml NDCBS.CASSETTEMAPPINGCONFIG=NDCBSCassetteMapping.xml NDCBS.CONFIGDIR=C:\Documents and Settings\All Users\Application Data\NCR APTRA\NDC Business Services NDCBS.GENERALCONFIG=NDCBSGeneralConfiguration.xml NDCPROXY.ACQUIRERREQUESTED=CHECKING NDCPROXY.LANGUAGE=ENG NDCPROXY.RECEIPT=true NDCPROXY.RECEIPTDATAFOUND=false NDCPROXYCUSTOMIZATION.AMOUNT=0 NDCPROXYCUSTOMIZATION.ENHANCEDDEPOSITMODE=MIGRATIONEMULATION NDCPROXYCUSTOMIZATION.MAXAMOUNT=780 NDCPROXYCUSTOMIZATION.MULTIPLE=10 NDCPROXYCUSTOMIZATION.PINCHANGEALWAYSINCLUDEOPCODE=TRUE NDCPROXYCUSTOMIZATION.PINCHANGEALWAYSINCLUDETRACK2=TRUE NDCPROXYCUSTOMIZATION.PINCHANGENEXTSTATE1=120 NDCPROXYCUSTOMIZATION.PINCHANGEOPCODE1=ID NDCPROXYCUSTOMIZATION.UVALUE=780 NDCPROXYCUSTOMIZATION.XVALUE=10 NDCPROXYCUSTOMIZATION.YVALUE=10 NDCPROXYCUSTOMIZATION.ZVALUE=390 NIGHTDEPOSIT.REMOTENIGHTSAFE=false NIGHTDEPOSIT.TIMEOUT=180 RCPT_CONFIG.LOGOLEFTMARGIN=15 SESSIONFLOW.READRAWDATA=1207 STARTOFDAY.ACCOUNTSERVICECOMMSPROGID=NCRaVPITCPIP.TCPIPCommsService STARTOFDAY.ACCOUNTSERVICECONFIG=C:\WebATM\NDCBSAccountServiceConfig.xml STARTOFDAY.ACCOUNTSERVICEPROGID=NCRaNDCBS1.NDCAccountService STARTOFDAY.ALLACCOUNTBALANCEPROGID=INQ.INQTXN STARTOFDAY.ALLACCOUNTBALANCETRANSLETID=ALLACCOUNTBALANCE STARTOFDAY.APPLICATIONMANAGEMENTSERVICECONFIG=C:\WebATM\NDCApplicationManagementServiceConfig.xml STARTOFDAY.APPLICATIONMANAGEMENTSERVICEPROGID=AppMgmtNDC.ApplicationManagement STARTOFDAY.APPMGMTREPORTDEPOSITLENGTHERROR=FALSE STARTOFDAY.ARCHIVEDAYSTORETAIN=30 STARTOFDAY.ATMTCPIPROLE=Client STARTOFDAY.BALANCEPROGID=INQ.INQTXN



STARTOFDAY.BALANCETRANSLETID=BALANCE STARTOFDAY.CAPTURECARDTIMEOUT=30 STARTOFDAY.CARDSERVICECONFIG=C:\WebATM\NDCBSCardServiceConfig.xml STARTOFDAY.CARDSERVICEPROGID=NCRaCS.CardService STARTOFDAY.CASHDEPOSITPROGID=CashDepositTxn.CashDeposit STARTOFDAY.CASHDEPOSITTRANSLETID=ENVDEPOSIT STARTOFDAY.CASHRETRACTTIMEOUT=30 STARTOFDAY.CASHRETRACTWAITFORAUTH=False STARTOFDAY.CBENVDEPOSITTRANSLETID=CBENVDEPOSIT STARTOFDAY.CBWITHDRAWALPROGID=WDL.WDLTXN STARTOFDAY.CBWITHDRAWALTRANSLETID=CBWITHDRAWAL STARTOFDAY.CHECKDEPOSITPROGID=NCRCHECKDEPOSIT.CHECKDEPOSIT STARTOFDAY.CHECKDEPOSITTRANSLETID=ENVDEPOSIT STARTOFDAY.CHECKREORDERPROGID=INQ.INQTXN STARTOFDAY.CHECKREORDERTRANSLETID=CHECKREORDER STARTOFDAY.CHECKSERVICEPROGID=NCRCHECK.CHECK STARTOFDAY.CLEARRECEIPTBEFOREREVERSE=True STARTOFDAY.CLOSECOMPLETEDELAY=4 STARTOFDAY.CONFIGURATIONXMLFILENAME=c:\webatm\webatm.xml STARTOFDAY.CONSUMERSERVICEPROGID=ConsumerSvcPj.ConsumerService STARTOFDAY.DEPOSITTIMER=30 STARTOFDAY.DISPLAYALLACCOUNTBALANCEPROGID=INQ.INQTXN STARTOFDAY.DISPLAYALLACCOUNTBALANCETRANSLETID=DISPLAYALLACCOUNTBALANCE STARTOFDAY.DISPLAYBALANCEPROGID=INQ.INQTXN STARTOFDAY.DISPLAYBALANCETRANSLETID=DISPLAYBALANCE STARTOFDAY.EJDATAFORMATTERPROGID=NDCBSRecFrmtrNoTag.EJRcrFormater STARTOFDAY.EJECTCARDCOUNT=2 STARTOFDAY.EJFILLDATABLOCK=TRUE STARTOFDAY.EJUPLOADQUEUEMANAGERPROGID=EjUpLoad.QueueManager STARTOFDAY.ELPAYMENTPROGID=TransferTxn.Transfer STARTOFDAY.ELPAYMENTTRANSLETID=ELECTRONICPAYMENT STARTOFDAY.ENHDEPEODPROGID=EnhDepEOD.EnhDepEODTXn STARTOFDAY.ENVDEPOSITTRANSLETID=ENVDEPOSIT STARTOFDAY.ENVPAYMENTTRANSLETID=ENVPAYMENT STARTOFDAY.ENVPMTFROMACCTTRANSLETID=ENVPMTFROMACCT STARTOFDAY.ENVPMTTOACCTTRANSLETID=ENVPMTTOACCT STARTOFDAY.FASTCASHCARDAFTERCASH=True STARTOFDAY.FASTCASHPROGID=WDL.WDLTXN STARTOFDAY.FASTCASHTRANSLETID=FASTCASH STARTOFDAY.ForceUnavailableOnNoStamps STARTOFDAY.ForceUnavailableOnNoCash= STARTOFDAY.FastCashDispenseIfCardEjectFails STARTOFDAY.FULLSTATEMENT1PROGID=Statement.StatementTxn STARTOFDAY.FULLSTATEMENT1TRANSLETID=STATEMENTFULL1 STARTOFDAY.FULLSTATEMENT2PROGID=Statement.StatementTxn STARTOFDAY.FULLSTATEMENT2TRANSLETID=STATEMENTFULL2 STARTOFDAY.FULLSTM_INTERIMPROGID=Statement.StatementTxn STARTOFDAY.FULLSTM_INTERIMTRANSLETID=STATEMENTFULL1 STARTOFDAY.FULLSTM_LASTMONTHLYPROGID=Statement.StatementTxn STARTOFDAY.FULLSTM_LASTMONTHLYTRANSLETID=STATEMENTFULL2 STARTOFDAY.HEARTBEATINTERVAL=5 STARTOFDAY.JOURNALCRITERIATRACING=FALSE STARTOFDAY.JOURNALDEVICEDATA=False STARTOFDAY.JOURNALHOSTDATA=TRUE STARTOFDAY.JOURNALPROGID=NCRJournal.Journal



STARTOFDAY.JOURNALTXODATA=TRUE STARTOFDAY.LOGO1=\webatm\logo.img STARTOFDAY.MACHINETYPE=5877 STARTOFDAY.MESSAGETOBANKPROGID=DepositTxn.Deposit STARTOFDAY.MESSAGETOBANKTRANSLETID=MESSAGETOBANK STARTOFDAY.MINISTATEMENT1PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT1TRANSLETID=MINISTATEMENT1 STARTOFDAY.MINISTATEMENT2PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT2TRANSLETID=MINISTATEMENT2 STARTOFDAY.MINISTATEMENT3PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT3TRANSLETID=MINISTATEMENT3 STARTOFDAY.MINISTATEMENT4PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT4TRANSLETID=MINISTATEMENT4 STARTOFDAY.MINISTATEMENT5PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT5TRANSLETID=MINISTATEMENT5 STARTOFDAY.MINISTATEMENT6PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT6TRANSLETID=MINISTATEMENT6 STARTOFDAY.MINISTATEMENT7PROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTATEMENT7TRANSLETID=MINISTATEMENT7 STARTOFDAY.MINISTM_LAST10TXPROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTM_LAST10TXTRANSLETID=STATEMENT10TRN STARTOFDAY.MINISTM_LAST5CARDPROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTM_LAST5CARDTRANSLETID=STATEMENT5CRD STARTOFDAY.MINISTM_LAST5CHECKSPROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTM_LAST5CHECKSPROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTM_LAST5CHECKSTRANSLETID=STATEMENT5CHK STARTOFDAY.MINISTM_LAST5DEPOSITSPROGID=MiniStatement.MiniStatementTxn STARTOFDAY.MINISTM_LAST5DEPOSITSTRANSLETID=STATEMENT5DEP STARTOFDAY.MOUSECURSOR=NO STARTOFDAY.NIGHTDEPOSITTRANSLETID=NightDeposit STARTOFDAY.PERSONALIZEDFASTCASHCARDAFTERCASH=False STARTOFDAY.PERSONALIZEDFASTCASHPROGID=WDL.WDLTXN STARTOFDAY.PERSONALIZEDFASTCASHTRANSLETID=WITHDRAWAL STARTOFDAY.PersonalizedFastCashDispenseIfCardEjectFails STARTOFDAY.PINCHANGEPROGID=PinChange.PinChangeTxn STARTOFDAY.PINCHANGETRANSLETID=PINCHANGE1 STARTOFDAY.PRINTIMMEDIATEPROGID=USNDCCustomCode.PrintImmediate STARTOFDAY.PURCHASE1MIXREQUIRED=False STARTOFDAY.PURCHASE1TRANSLETID=PURCHASE1 STARTOFDAY.READTRACK1=False STARTOFDAY.REBOOTONPOPUP=Y STARTOFDAY.RECEIPTCRITERIATRACING=FALSE STARTOFDAY.RECEIPTPROGID=NCRReceipt.Receipt STARTOFDAY.REFRESHONHEARTBEAT=NO STARTOFDAY.RETURNCARDIMMEDIATELY=False STARTOFDAY.REVERSALWAITFORAUTH=True STARTOFDAY.SCREENDOWNLOADPROGID=NDCBSScreenDwnPj.ScreenDownloader STARTOFDAY.SESSIONFLOWPROGID=SessionFlowPj.SessionFlow STARTOFDAY.SESSIONRESOURCEPROGID=NCRSessionResource.AlwaysAvailable STARTOFDAY.SPECIALKEY=99 STARTOFDAY.SPLITDEPOSITPROGID=DepositTxn.Deposit STARTOFDAY.SPLITDEPOSITTRANSLETID=SPLITDEPOSIT STARTOFDAY.STAMPSDISPENSETYPE=1 STARTOFDAY.STAMPSMIXREQUIRED=False STARTOFDAY.STAMPSPROGID=WDL.WDLTXN STARTOFDAY.STAMPSTRANSLETID=STAMPS



STARTOFDAY.STARTPAGE=GFrames.htm STARTOFDAY.STATEMENT20ALLPROGID=Statement.StatementTxn STARTOFDAY.STATEMENT20ALLTRANSLETID=STATEMENT20ALL STARTOFDAY.STATEMENT20CHKPROGID=Statement.StatementTxn STARTOFDAY.STATEMENT20CHKTRANSLETID=STATEMENT20CHK STARTOFDAY.STATEMENT20TRNPROGID=Statement.StatementTxn STARTOFDAY.STATEMENT20TRNTRANSLETID=STATEMENT20TRN STARTOFDAY.STATEMENTSERVICEPROGID=NCRStatement.Statement STARTOFDAY.STOPALTTAB=YES STARTOFDAY.TRACEPROGID=WebATM.Trace STARTOFDAY.TRANSFERPROGID=TransferTxn.Transfer STARTOFDAY.TRANSFERTRANSLETID=TRANSFER STARTOFDAY.VOLUMEHIGH=65000 STARTOFDAY.VOLUMELOW=45000 STARTOFDAY.VOLUMEMEDIUM=55000 STARTOFDAY.WEBPAGELOCATION=c:\webatm\webpages STARTOFDAY.WITHDRAWALMIXREQUIRED=False STARTOFDAY.WITHDRAWALPROGID=WDL.WDLTXN STARTOFDAY.WITHDRAWALTRANSLETID=WITHDRAWAL STARTOFDAY.XFSRECEIPTPRINTERCOACTIONPROGID=ActiveXFS.XFSReceiptPrintCoAction STARTOFDAY.XFSRECEIPTPRINTERPROGID=ActiveXFS.ReceiptPrinter STARTOFDAY.XFSRECEIPTPROGID=ActiveXFS.XFSReceipt STATEMENT.LINESPERPAGE=68 SUPERVISOR.CARDTRANSLETFACTORYPROGID=NCRaNDCBS2.NDCCardTransletFactory SUPERVISOR.CLEARPURGEBINONEXIT=NO SUPERVISOR.COINDISPENSERPRESENT=Yes SUPERVISOR.COLUMNS=32 SUPERVISOR.COMMSKEY=BKey SUPERVISOR.COMMSKEYDATA=BKeyData SUPERVISOR.CONTINUEPROCEDURE=True SUPERVISOR.CURRENTDISPLAY=FRONT SUPERVISOR.DEPOSITORYPRESENT=Yes SUPERVISOR.DIAGNOSTICSPASSWORD=0000 SUPERVISOR.DISPLAYAMOUNT=YES SUPERVISOR.DISPLAYCANISTERTYPEHOST=YES SUPERVISOR.DISPLAYCANISTERTYPELOCAL=YES SUPERVISOR.DISPLAYMEDIAAMOUNT=NO SUPERVISOR.DNSIPCONFIGURATION=NO SUPERVISOR.ENCRYPTIONTYPE=single SUPERVISOR.EXITKEYTIMEOUT=120 SUPERVISOR.HOSTSTATUS=NORM SUPERVISOR.JOURNAL=NO SUPERVISOR.JOURNALPRINTERPRESENT=Yes SUPERVISOR.KEYEXCHANGETIMEOUT=10 SUPERVISOR.KEYTIMEOUT=0 SUPERVISOR.LOCALCASHAMOUNT=0.00 SUPERVISOR.LOCALCASHCOUNT=0 SUPERVISOR.LOCALCHECKAMOUNT=1117317.35 SUPERVISOR.LOCALCHECKCOUNT=13 SUPERVISOR.MAINTANDSUPPLIESPASSWORD=0000 SUPERVISOR.MASTERKEY=MasterKey SUPERVISOR.MASTERKEYDATA=MasterKeyData SUPERVISOR.MODESWTIMEOUT=02 SUPERVISOR.NCR=YES SUPERVISOR.NDCBS=True



SUPERVISOR.NEXTMENU=M001 SUPERVISOR.PASSWORD=0000 SUPERVISOR.PINTOUSE=dd SUPERVISOR.PRINTCHECKLIST=YES SUPERVISOR.ROWS=16 SUPERVISOR.SAFEDOORTIMEOUT=120 SUPERVISOR.SCRIPTNAME=install.bat SUPERVISOR.SENDBALANCEINQUIRY=False SUPERVISOR.SETTLEMENTCONFIGURATIONFILENAME=C:\WebATM\Menu.xml SUPERVISOR.SETTLEMENTPASSWORD=0000 SUPERVISOR.SETTLEMENTPIN=1234 SUPERVISOR.SKIPFAULTS=YES SUPERVISOR.SNMPSECURITY=0 SUPERVISOR.SNMPTRAP=0 SUPERVISOR.STATEMENTPRINTERPRESENT=Yes SUPERVISOR.SYSTEMCONFIGPASSWORD=0000 SUPERVISOR.TASK=S071 SUPERVISOR.TCPIPCONFIGFILEROOT=C:\WEBATM SUPERVISOR.TESTEDDEVICES=NO SUPERVISOR.TIMEOUT=00 SUPERVISOR.TRACK2=;5006307018139586=5012? SUPERVISOR.TRACK2FORMAT=;xxxxxxxxxxxxxxxxxx=yyyyyyyyyy? SUPERVISOR.TTU=NO SUPERVISOR.USERNAME=DEFAULT SUPERVISOR.USERTYPE=00 SUPERVISOR.VDM=YES SUPERVISOR.VDMEXITDELAY=16 SUPERVISOR.VOLUMEINCREMENT=2500 SUPERVISOR.VPICOMMSCONFIGFILEROOT=C:\Program Files\NCR APTRA\CCM TCPIP SUPERVISOR.XMLCONFIGFILELOCATION=C:\webatm\ATMConfig.xml SUPJRN.PRINTLINE00=200X5670 1524 12/03/03 13:29 SUPJRN.PRINTLINE01=DEP CK 4432201890000164 100.00 SUPJRN.PRINTLINE02= 00002893016694 TOTAL.BILLSDISPENSEDTYPE1=5 TOTAL.BILLSDISPENSEDTYPE2=0 TOTAL.BILLSDISPENSEDTYPE3=1 TOTAL.BILLSDISPENSEDTYPE4=0 TRACE.ARCHIVEDIR=c:\archivedir\trace TRACE.ARCHIVEREASON=ONDEMAND TRACE.MAXSIZE=1024 TRACE.TRACEFILENAME=c:\webatm\trace.dat VDM.COUNT=1

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE APTRA EDGE XML FILES


C APTRA Edge XML Files

This section describes the xml files that you can update remotely without using software distribution. The files you can update include:

ButtonToKeyMap.xml

Coupon.xml

Journal.xml

Receipt.xml

SoundENG.xml

SoundSPA.xml It is not recommended that you update any xml files other then the ones in the list above. As was stated earlier in this document, the values you are updating must be contained in a block of data starting with <XML_UPDATE> and ending with </XML_UPDATE>. The initial XML_UPDATE command must include the complete path and filename of the .xml file to be changed. It must be followed by an <XMLUpdate> block including a nested <Update> block, <Insert> block, or <Delete> block. Xml file updates always require a reboot, so you must always include the reboot="y" parameter in your <CONFIGURATION_DATA> tag.

All files in APTRA Edge have a default location on the hard drive of the ATM. If desired, most of the files listed above can be moved to other locations. Since you need to include the path of the file in an update, you need to determine if the file is still in the default location, or if it has been moved. Use the following guidelines when locating these files:

ButtonToKeyMap.xml This file will always be in c:\Webatm\WebPages\scripts. Journal.xml The location of this file is determined by the data dictionary entry

JOURNAL.JOURNALDEFINITIONFILENAME=. (The default is c:\Webatm.)

Receipt.xml The location of this file is determined by the data dictionary entry RCPT_CONFIG.RECEIPTDEFINITIONFILENAME=. (The default is c:\Webatm.)

SoundENG.xml SoundSPA.xml

The SoundConfiguration.xml file contains a <SoundXML> entry for each language. This entry will either contain the full path of the SoundXXX.xml file, or it will contain only the filename itself, and in that case, there will be a <SoundFolder> entry that will contain the full path of the SoundXXX.xml file. The default location of the SoundConfiguration.xml file is \Webatm. If the default is not being used, you need to look in the Webatm.xml file to find the path of the SoundConfiguration.xml file. In the Webatm.xml file there is a section called <SoundService>. Within this section is a property with the Name SoundXML. The value of that property contains the full path of the SoundConfiguration.xml file.



C.1 ButtonToKeyMap.xml

The ButtonToKeyMap.xml defines the mapping of the button selections on the numeric keypad to the FDK selections. Each menu and any screen that requires customer input should have an entry in this file. If the consumer flow changes such that it affects the button/key selections on a screen, then updates to this file need to be made. A default mapping is included (called AllScreens) that applies to all screens that do not have a map defined for them.

If you rearrange menus or add entries to screens in the Consumer Flow, you will need to update this file unless you used the default mapping and it is still applicable. The file also contains the name of the associated xml-schema file, which you should not change.

C.1.1 File Format

The ButtonToKeyMap.xml file has the following format: <FDKKey> <FDKKeyMap Button="1" FDKKey="1"/> <FDKKeyMap Button="2" FDKKey="2"/> <FDKKeyMap Button="3" FDKKey="3"/> <FDKKeyMap Button="4" FDKKey="4"/> <FDKKeyMap Button="5" FDKKey="5"/> <FDKKeyMap Button="6" FDKKey="6"/> <FDKKeyMap Button="7" FDKKey="7"/> <FDKKeyMap Button="8" FDKKey="8"/> </FDKKey> <Screen name="AnotherTransaction"> <KeyMap Button="7" Key="1"/> </Screen> <Screen name="ATMTransMenu1"> <KeyMap Button="1" Key="1"/> <KeyMap Button="2" Key="2"/> <KeyMap Button="3" Key="3"/> <KeyMap Button="4" Key="4"/> <KeyMap Button="5" Key="5"/> <KeyMap Button="6" Key="6"/> <KeyMap Button="7" Key="7"/> <KeyMap Button="8" Key="8"/> </Screen> <Screen name="ATMTransMenu2"> <KeyMap Button="1" Key="1"/> <KeyMap Button="2" Key="2"/> <KeyMap Button="3" Key="3"/> <KeyMap Button="4" Key="4"/> <KeyMap Button="5" Key="5"/> <KeyMap Button="6" Key="6"/> <KeyMap Button="7" Key="7"/> <KeyMap Button="8" Key="8"/> </Screen>

FDK to Button map

Button to key map for Menu 1




<Screen name="ATMTransMenu3"> <KeyMap Button="1" Key="1"/> <KeyMap Button="2" Key="2"/> <KeyMap Button="3" Key="3"/> <KeyMap Button="4" Key="4"/> <KeyMap Button="5" Key="5"/> <KeyMap Button="6" Key="6"/> <KeyMap Button="7" Key="7"/> <KeyMap Button="8" Key="8"/> </Screen> <Screen name="ATMTransMenu4"> <KeyMap Button="1" Key="1"/> <KeyMap Button="2" Key="2"/> <KeyMap Button="3" Key="3"/> <KeyMap Button="4" Key="4"/> <KeyMap Button="5" Key="5"/> <KeyMap Button="6" Key="6"/> <KeyMap Button="7" Key="7"/> <KeyMap Button="8" Key="8"/> </Screen> <Screen name="Balance"> <KeyMap Button="8" Key="1"/> </Screen> <Screen name="AllAccountsBalance"> <KeyMap Button="8" Key="1"/> </Screen> <Screen name="BalanceReceipt"> <KeyMap Button="4" Key="4"/> <KeyMap Button="6" Key="1"/> <KeyMap Button="7" Key="2"/> <KeyMap Button="8" Key="3"/> </Screen>

<Screen name="CheckReOrder"> <KeyMap Button="7" Key="1"/> <KeyMap Button="8" Key="2"/> </Screen> <Screen name="ConfirmBills"> <KeyMap Button="7" Key="1"/> <KeyMap Button="8" Key="2"/> </Screen> <Screen name="ConfirmCheck"> <KeyMap Button="7" Key="1"/> <KeyMap Button="8" Key="2"/> </Screen>



Button to key map for balance inquiries

Button to key map for check reorder

Button to key map to confirm bills entered during cash deposit

Button to key map to confirm check entered during check deposit



<Screen name="DepositContinue"> <KeyMap Button="6" Key="1"/> <KeyMap Button="7" Key="2"/> <KeyMap Button="8" Key="3"/> </Screen>

. .

. <Screen name="AllScreens"> <KeyMap Button="1" Key="1"/> <KeyMap Button="2" Key="2"/> <KeyMap Button="3" Key="3"/> <KeyMap Button="4" Key="4"/> <KeyMap Button="5" Key="5"/> <KeyMap Button="6" Key="6"/> <KeyMap Button="7" Key="7"/> <KeyMap Button="8" Key="8"/> </Screen>

C.2 Coupon.xml

The coupon.xml file contains at least one group or flowpoint element, and a coupon element for each coupon to be printed. (Groups are included for backward compatibility.)

C.2.1 File Format

<CouponDefinition xmlns="x-schema:coupon_schema.xdr"> <Version>1.0</Version> <Group> <Name>ATMTransactions</Name> <CouponName>Coupon1 - July</CouponName> <CouponName>Coupon2 - July</CouponName> <CouponName>Coupon3 - July</CouponName> <CouponName>Coupon1 - August</CouponName> <CouponName>Coupon2 - August</CouponName> <CouponName>Coupon3 - August</CouponName> </Group> <Group> <Name>MembershipTransactions</Name> <CouponName>Food1</CouponName> <CouponName>Food2</CouponName> <CouponName>Food3</CouponName> </Group> <Coupon> <Name>Food1</Name> <FileName>c:\webatm\coupons\Joemon.pfm</FileName> </Coupon> <Coupon> <Name>Food2</Name> <FileName>c:\webatm\coupons\Bigmacbr.pfm</FileName> </Coupon>

Default button to key map

Button to key map for deposit continue screen



<Coupon> <Name>Food3</Name> <FileName>c:\webatm\coupons\Brekfsbr.pfm</FileName> </Coupon> <Coupon> <Name>Coupon1 - July</Name> <Criteria> <ValidDate> <BeginDate>7/1/2004</BeginDate> <EndDate>7/31/2004</EndDate> </ValidDate> </Criteria> <FileName>c:\webatm\coupons\csignatu.pfm</FileName> </Coupon> <Coupon> <Name>Coupon2 - July</Name> <Criteria> <ValidDate> <BeginDate>7/1/2004</BeginDate> <EndDate>7/31/2004</EndDate> </ValidDate> </Criteria> <FileName>c:\webatm\coupons\cira.pfm</FileName> </Coupon> <Coupon> <Name>Coupon3 - July</Name> <Criteria> <ValidDate> <BeginDate>7/1/2004</BeginDate> <EndDate>7/31/2004</EndDate> </ValidDate> </Criteria> <FileName>c:\webatm\coupons\cauto.pfm</FileName> </Coupon> <Coupon> <Name>Coupon1 - August</Name> <Criteria> <ValidDate> <BeginDate>8/1/2004</BeginDate> <EndDate>8/31/2004</EndDate> </ValidDate> </Criteria> <FileName>c:\webatm\coupons\ccredit.pfm</FileName> </Coupon> <Coupon> <Name>Coupon2 - August</Name> <Criteria> <ValidDate> <BeginDate>8/1/2004</BeginDate> <EndDate>8/31/2004</EndDate> </ValidDate> </Criteria> <FileName>c:\webatm\coupons\ccd.pfm</FileName> </Coupon> <Coupon> <Name>Coupon3 - August</Name> <Criteria>



<ValidDate> <BeginDate>8/1/2004</BeginDate> <EndDate>8/31/2004</EndDate> </ValidDate> </Criteria> <FileName>c:\webatm\coupons\ccheckin.pfm</FileName> </Coupon> </CouponDefinition>

C.3 Journal.xml

The Journal.xml file (journal definition file) specifies under what conditions items appear in the journal. It contains definitions for each log and for all transaction types. It also specifies a version number. An associated xml-schema file determines the structure of this file.

You should not change the log references, but may want to change the information that is logged to the journal for transactions. Most commonly, you will want to delete the journal information defined for transactions that are not implemented in your system, and add entries for transactions you are adding.

The transaction journal data is made up of several sections:

successful transaction data

paper journal data (optional)

transaction object data (optional)

host data (optional)

transaction denial data

The sections listed as optional above are controlled by data dictionary STARTOFDAY and JOURNAL entries. Samples of each journal data type are included in the next section.

C.3.1 File Format

The Journal.xml sample below shows what is logged for a withdrawal transaction. All transactions have a similar structure.

 <Transaction> <Name>Withdrawal-Authorised</Name> <Form> <Name>ProxyJournal</Name> </Form>  <XMLRecord> <Log> <Name>Camera</Name> </Log> <Log> <Name>TranJournal</Name> <Criteria> <IfNotEqualTo> <Field>STARTOFDAY.JOURNALTXODATA</Field> <Value>False</Value> </IfNotEqualTo> </Criteria> </Log> <VariableXML> <Tran> <TranName>TransactionID</TranName> <TermID>Global.MachineNumber</TermID> <TermSeq>DisputeReference</TermSeq> <Date format="mm/dd/yyyy">SYSTEMDate</Date> <Time format="Hh:Nn:Ss">SYSTEMTime</Time> <TransactionTimeStamp>TransactionTimeStamp</TransactionTimeStamp> <AccountType>AcquirerType</AccountType> <PAN>CardNumber</PAN> <WithdrawalAmount>Amount</WithdrawalAmount> <Fee>FeeAmountNOT ON US</Fee> <Fee>FeeAmountSURCHARGE</Fee> <Fee>FeeAmountOVERDRAFT</Fee> <TranAmount>totalAmount</TranAmount> <Result>Result</Result> <ConsumerMessageID>ConsumerMessageID</ConsumerMessageID> <DisputeStatus>DisputeStatus</DisputeStatus> </Tran> </VariableXML> </XMLRecord>

Controlled by STARTOFDAY.JOURNAL TXODATA

<XMLRecord> <Log> <Name>TranJournal</Name> <Criteria> <IfNotEqualTo> <Field>STARTOFDAY.JOURNALHOSTDATA</Field> <Value>False</Value> </IfNotEqualTo> </Criteria> </Log> <VariableXML> <HostData> <Date format="mm/dd/yyyy">SYSTEMDate</Date> <Time format="Hh:Nn:Ss">SYSTEMTime</Time> <Line00>TRANSACTION.JRNL_PRINTLINE00</Line00> <Line01>TRANSACTION.JRNL_PRINTLINE01</Line01> <Line02>TRANSACTION.JRNL_PRINTLINE02</Line02> <Line03>TRANSACTION.JRNL_PRINTLINE03</Line03> <Line04>TRANSACTION.JRNL_PRINTLINE04</Line04> <Line05>TRANSACTION.JRNL_PRINTLINE05</Line05> <Line06>TRANSACTION.JRNL_PRINTLINE06</Line06> <Line07>TRANSACTION.JRNL_PRINTLINE07</Line07> <Line08>TRANSACTION.JRNL_PRINTLINE08</Line08> <Line09>TRANSACTION.JRNL_PRINTLINE09</Line09> <Line10>TRANSACTION.JRNL_PRINTLINE10</Line10> <Line11>TRANSACTION.JRNL_PRINTLINE11</Line11> <Line12>TRANSACTION.JRNL_PRINTLINE12</Line12> <Line13>TRANSACTION.JRNL_PRINTLINE13</Line13> <Line14>TRANSACTION.JRNL_PRINTLINE14</Line14> <Line15>TRANSACTION.JRNL_PRINTLINE15</Line15> <Line16>TRANSACTION.JRNL_PRINTLINE16</Line16> </HostData> </VariableXML> </XMLRecord>  <Transaction> <Name>Withdrawal-HostDenial</Name> <Criteria> <AndGroup> <IfNotEqualTo> <Field>Result</Field> <Value>4</Value> </IfNotEqualTo> <IfNotEqualTo> <Field>Result</Field> <Value>9</Value> </IfNotEqualTo> </AndGroup> </Criteria> <Form> <Name>ProxyJournal</Name> </Form>

Controlled by STARTOFDAY.JOURNALHOSTDATA

<XMLRecord> <Log> <Name>Camera</Name> </Log> <Log> <Name>TranJournal</Name> <Criteria> <IfNotEqualTo> <Field>STARTOFDAY.JOURNALTXODATA</Field> <Value>False</Value> </IfNotEqualTo> </Criteria> </Log> <VariableXML> <Tran> <TranName>TransactionID</TranName> <TermID>Global.MachineNumber</TermID> <TermSeq>DisputeReference</TermSeq> <Date format="mm/dd/yyyy">SYSTEMDate</Date> <Time format="Hh:Nn:Ss">SYSTEMTime</Time> <TransactionTimeStamp>TransactionTimeStamp</TransactionTimeStamp> <AccountType>AcquirerType</AccountType> <PAN>CardNumber</PAN> <WithdrawalAmount>Amount</WithdrawalAmount> <Fee>FeeAmountNOT ON US</Fee> <Fee>FeeAmountSURCHARGE</Fee> <Fee>FeeAmountOVERDRAFT</Fee> <TranAmount>totalAmount</TranAmount> <Result>Result</Result> <ConsumerMessageID>ConsumerMessageID</ConsumerMessageID> <DisputeStatus>DisputeStatus</DisputeStatus> </Tran> </VariableXML> </XMLRecord>

Controlled by STARTOFDAY.JOURNAL TXODATA

<XMLRecord> <Log> <Name>TranJournal</Name> <Criteria> <IfNotEqualTo> <Field>STARTOFDAY.JOURNALHOSTDATA</Field> <Value>False</Value> </IfNotEqualTo> </Criteria> </Log> <VariableXML> <HostData> <Date format="mm/dd/yyyy">SYSTEMDate</Date> <Time format="Hh:Nn:Ss">SYSTEMTime</Time> <Line00>TRANSACTION.JRNL_PRINTLINE00</Line00> <Line01>TRANSACTION.JRNL_PRINTLINE01</Line01> <Line02>TRANSACTION.JRNL_PRINTLINE02</Line02> <Line03>TRANSACTION.JRNL_PRINTLINE03</Line03> <Line04>TRANSACTION.JRNL_PRINTLINE04</Line04> <Line05>TRANSACTION.JRNL_PRINTLINE05</Line05> <Line06>TRANSACTION.JRNL_PRINTLINE06</Line06> <Line07>TRANSACTION.JRNL_PRINTLINE07</Line07> <Line08>TRANSACTION.JRNL_PRINTLINE08</Line08> <Line09>TRANSACTION.JRNL_PRINTLINE09</Line09> <Line10>TRANSACTION.JRNL_PRINTLINE10</Line10> <Line11>TRANSACTION.JRNL_PRINTLINE11</Line11> <Line12>TRANSACTION.JRNL_PRINTLINE12</Line12> <Line13>TRANSACTION.JRNL_PRINTLINE13</Line13> <Line14>TRANSACTION.JRNL_PRINTLINE14</Line14> <Line15>TRANSACTION.JRNL_PRINTLINE15</Line15> <Line16>TRANSACTION.JRNL_PRINTLINE16</Line16> </HostData> </VariableXML> </XMLRecord> </Transaction>

Controlled by STARTOFDAY.JOURNALHOSTDATA



C.4 Receipt.xml

The Receipt.xml file contains receipt definitions for all transaction type. It also specifies a version number and the name of the associated xml-schema file. You may want to delete entries for transactions you do not support, or add entries for transactions you are adding. However, you should not change the scheme file name, version number or transaction names.

Each transaction has four sections in the receipt.xml file, one for each possible result:

Successful completion

Host denial

Cancelled by cardholder

Hardware error

The sample included in the next section shows the format of each section.

C.4.1 File Format

The Receipt.xml sample below shows the generic printing definition that applies to all transactions listed later in the file.

<Transaction> <Name>GENERICTRANSACTION</Name> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.PRINTFORM1</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> <PrintNow>1</PrintNow> <Form> <Name>Footer</Name> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT1</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> </Form> <CutNow> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT1</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> </CutNow> <Form> <Name>Header</Name> <LogoFileNumber>1</LogoFileNumber> <Criteria> <AndGroup> <OrGroup>



<IfFormNotPrinted> <FormName>Header</FormName> </IfFormNotPrinted> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT1</Field> <Value>TRUE</Value> </IfEqualTo> </OrGroup> <IfNotEqualTo> <Field>RECEIPT.PRINTHEADER</Field> <Value>FALSE</Value> </IfNotEqualTo> </AndGroup> </Criteria> </Form> <Form> <Name>Receipt1</Name> </Form> <Form> <Name>Footer</Name> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT2</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> </Form> <CutNow> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT2</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> </CutNow> <Form> <Name>Header</Name> <LogoFileNumber>1</LogoFileNumber> <Criteria> <AndGroup> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.PRINTFORM2</Field> <Value>TRUE</Value> </IfEqualTo> <IfNotEqualTo> <Field>RECEIPT.PRINTHEADER</Field> <Value>FALSE</Value> </IfNotEqualTo> </AndGroup> </Criteria> </Form> <Form> <Name>Receipt2</Name> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.PRINTFORM2</Field> <Value>TRUE</Value>



</IfEqualTo> </Criteria> </Form> <Form> <Name>Footer</Name> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT3</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> </Form> <CutNow> <Criteria> <IfEqualTo> <Field>NDCPROXYCUSTOMIZATION.RECEIPTCUT3</Field> <Value>TRUE</Value> </IfEqualTo> </Criteria> </CutNow> </Transaction> For a Withdrawal transaction, a receipt using the generic definition (shown earlier) will be printed for:

successful transactions

host denials

canceled by cardholder

hardware errors

partial dispense conditions The definition for these is shown below.

All transactions include the successful, host denial entries.

All transactions that involve hardware, such as the cash dispenser or depository, include a hardware error entry, and also contain a partial dispense entry if dispensing cash is involved (as shown in the Withdrawal definition following).

<Transaction>

<Name>WITHDRAWAL</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> <Transaction> <Name>WITHDRAWAL-HostDenial</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> <Transaction>

<Name>WITHDRAWAL-Cancel</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> <Transaction> <Name>WITHDRAWAL-HardwareError</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> <Transaction> <Name>WITHDRAWAL-PartialDispense</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> Transactions that do not involve hardware , such as a Transfer, have only successful and host denial conditions defined. <Transaction> <Name>TRANSFER</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> <Transaction> <Name>TRANSFER-HostDenial</Name> <TransactionReference>GENERICTRANSACTION</TransactionReference> </Transaction> Settlement transaction receipts are also defined in this file. The following shows the receipt definitions for local count functions.

 <Transaction> <Name>SUPCLEARCASHCOUNTS</Name> <PrintNow>1</PrintNow> <DeliverWhenDone> <DeliveryType>Cut</DeliveryType> </DeliverWhenDone> <Form> <Name>SUPHEADER</Name> </Form> <Form> <Name>SUPCLEARCASHCOUNTS</Name> </Form> </Transaction>  <Transaction> <Name>SUPADDCASHLOCAL</Name> <PrintNow>1</PrintNow> <DeliverWhenDone> <DeliveryType>Cut</DeliveryType>

</DeliverWhenDone> <Form> <Name>SUPHEADER</Name> </Form> <Form> <Name>SUPADDCASHLOCAL</Name> </Form> </Transaction>  <Transaction> <Name>SUPPRINTLOCALCOUNTS</Name> <PrintNow>1</PrintNow> <DeliverWhenDone> <DeliveryType>Cut</DeliveryType> </DeliverWhenDone> <Form> <Name>SUPHEADER</Name> </Form> <Form> <Name>SUPPRINTLOCALCOUNTS</Name> </Form> </Transaction>  <Transaction> <Name>SUPSUBTRACTCASHLOCAL</Name> <PrintNow>1</PrintNow> <DeliverWhenDone> <DeliveryType>Cut</DeliveryType> </DeliverWhenDone> <Form> <Name>SUPHEADER</Name> </Form> <Form> <Name>SUPSUBTRACTCASHLOCAL</Name> </Form> </Transaction>

C.5 SoundXXX.xml

If Voice Guidance is used on the ATM, the SoundENG.xml and SoundSPA.xml files can be modified to correspond to any screen text that is modified. The Sound Service uses the contents of the SoundENG.xml and SoundSPA.xml files to obtain the voice lead-through that will be articulated for each screen.

The SoundENG.xml and SoundSPA.xml files contain a series of templates for each screen. Each template references one or more TemplateName(s) from the associated .htm file and specifies the words to be articulated. Do not change the template references.

If you plan to make changes to these files, be sure you are familiar with the nuances of the Speechify Solo text to speech product. For example, to have the present tense of the word "read" articulated correctly, as in the phrase "We are unable to read your card," the word "read" must be spelled reed.

Also, note that the amount that will be articulated for the SoundSPA.xml file must be preceded with USD. This ensures that the amount will be articulated as US dollars, not pesos.

The following excerpt from a sample SoundENG.xml file shows the voice guidance articulation for the out of service screen, welcome screens, ATM operating instructions, Enter PIN, Transaction Fee and Enter Amount screens. Each section is preceded by commented text identifying the section. The BANKNAME and VOICEBANKNAME entries included in these sections, and throughout the SoundENG.xml file, are taken from the BANKNAME entry in the data dictionary.

C.5.1 File Format

 <Template name="2000"> <Script state="private" pause="10000"> <Text>Sorry, This ATM is temporarily unavailable. We're sorry for the inconvenience.</Text> </Script> </Template>

 <Template name="1090"> <Script state="private" pause="10000"> <Text>Welcome to the </Text> <VarText>VG.VOICEBANKNAME</VarText> <Text> audio guided ATM. This ATM will provide audio instructions for navigating through transactions available on this machine. Located approximately 3 feet off the ground is the ATM keypad, which you will use to make transaction selections. The keys are arranged in a pattern similar to that of a standard telephone keypad with an extra column of keys to the right side. You may begin your transaction by inserting your card into the card reader with the raised lettering up and to the left.</Text> <VarText>VG.VOICECARDREADER</VarText> <Text> \!p300 To hear information on how to use this ATM, press the bottom left key on the keypad. You may repeat instructions on any screen by pressing the bottom left key on the keypad.</Text> </Script> </Template> <Template name="1090_HELP"> <Script state="private"> <Text>This audio guide was created to familiarize you with the location of the devices on this ATM. You may interrupt these instructions and begin your session at any time by inserting your card into the card reader with the raised lettering up and to the left. \!p300 You may operate this ATM by using the keypad. The keypad is Located approximately three feet off the ground and has 16 keys. The keys are arranged like a telephone keypad with an extra column of four keys on the right. From top down, this additional column of keys consist of Enter, designated by a raised circle, Clear, designated by a raised vertical bar, Cancel, designated by a raised X, and Volume Control, designated by a raised plus symbol.</Text> <VarText>VG.VOICECARDREADER</VarText> <Text> \!p300 </Text>

<VarText>VG.VOICECASHDISPENSER</VarText> <Text> \!p300 </Text> <VarText>VG.VOICEENVELOPEDEPOSITORY</VarText> <Text> \!p300 </Text> <VarText>VG.VOICERECEIPTPRINTER</VarText> <Text> \!p300 </Text> <VarText>VG.VOICESTATEMENTPRINTER</VarText> <Text>To repeat instructions on any screen, press the bottom left key on the keypad.</Text> </Script> </Template>

 <Template name="2020"> <Script state="private"> <Text>Use the keypad to enter your Personal Identification Number, then press Enter. For security reasons you will hear only beeps when you enter your Personal Identification Number. To re-enter your Personal Identification Number, press Clear.</Text> </Script> </Template>  <Template name="2021"> <Script state="private"> <Text>You have entered an incorrect Personal Identification Number. Use the keypad to re-enter your Personal Identification Number, then press Enter. For security reasons you will hear only beeps when you enter your Personal Identification Number. To clear the number entered, press Clear. To cancel this transaction press Cancel.</Text> </Script> </Template>  <Template name="2040"> <Script state="private"> <VarText>VG.VOICEBANKNAME</VarText> <Text> will deduct a </Text> <VarText>Surcharge</VarText> <Text> fee from your account for this transaction. This fee is in addition to any fees your financial institution may assess. To accept this fee and continue press 1. To decline this fee and terminate this transaction, press Cancel.</Text> </Script> </Template>  <Template name="2045"> <Script state="private"> <Text>Please enter the total amount in the envelope.</Text> <Text>\!p300 then press Enter. The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script>



</Template> <Template name="2046"> <Script state="private"> <Text>You entered a total deposit amount of</Text> <VarText>Amount</VarText> <Text>\!p300 Please enter the amount 2 deposit to the first account. Your receipt will indicate the amount deposited to each account.</Text> <Text>\!p300 To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template> <Template name="2047"> <Script state="private"> <Text>We're sorry, the amount entered is invalid. Entries must be less than </Text> <VarText>Amount</VarText> <Text>\!p300 Please re-enter your amount, both dollars and cents, then press enter. The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template> <Template name="2050"> <Script state="private"> <Text>We're sorry, the amount entered was not a multiple of </Text> <VarText>Multiple</VarText> <Text>. Please re-enter your withdrawal amount, in dollars, in multiples of </Text> <VarText>Multiple</VarText> <Text>. then press Enter. The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template> <Template name="2051"> <Script state="private"> <Text>We're sorry, the amount entered is invalid. Entries must be greater than $0. Please re-enter your amount, both dollars and cents, then press enter. The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template> <Template name="2052"> <Script state="private"> <Text>Please enter your withdrawal amount, in dollars, in multiples of </Text> <VarText>Multiple</VarText> <Text>. then press enter.



The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press Cancel.</Text> </Script> </Template> <Template name="2053"> <Script state="private"> <Text>Please enter the payment amount, both dollars and cents, then press enter. The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template> <Template name="2054"> <Script state="private"> <Text>Please enter the payment amount, both dollars and cents, then press enter. The decimal is inserted automatically. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template> <Template name="2055"> <Script state="private"> <Text>Please enter the total amount of all items in the deposit envelope, both dollars and cents, then press enter. The decimal is inserted automatically. The withdrawal amount will be entered on the next screen. To change the amount press Clear. To hear the amount you've entered, press the keypad key to the right of the zero. To cancel this transaction press cancel.</Text> </Script> </Template>

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE ONSCREEN TEXT LANGUAGE FILES


D Onscreen Text Language Files

APTRA Edge Language files contain all of the text that will display onscreen to the cardholder. TextENG.js is the English version of the file and similar files will exist for each language you support. These will be named TextXXX.js where XXX is the three-character ISO 639 code for the language. All Language files are located in the c:\Webatm\WebPages\scripts directory on the ATM.

Normally, your screen text is set up according to your requirements when your system is installed and configured. You can make changes, if desired, and then download the file(s) using software distribution.

This section explains the format of the TextENG.js file. Entries in this file are grouped by function or use within the application. The groups are listed in the order in which they appear in the file. The values shown in this section are the contents of the default file provided with APTRA Edge. Your specific implementation may vary. Use this information as a guideline when making changes to the onscreen text language files.

D.1 Entry Formats

The general format for entries in the TextENG.js file is Message#### ="Text" for each onscreen display (whether button text, informational text or instructional text) displayed to the cardholder. This single message entry serves as the default entry for this message. For example, the following entry is used for the onscreen text for the Enter PIN screen.

var vMessage2020 = "Please enter your<br>Personal Identification Number<br>and then press the Enter key."; When variations are desired or required for a message, for different FITs for example, additional messages (sub-messages) can be added to the TextENG.js file by the use of the underscore character ( _ ) and sequentially numbered entries. Continuing the example started above, for on-us customers the bank wants to read the customer's name from track 1 on the card and display it on the Enter PIN screen. In this case, the following entry would be used for all on-us customers, rather than the default entry.

var vMessage2020_1 = "Hello " + __FULLNAME__ + ", Please enter your<br>Personal Identification Number<br>and then press the Enter key.";

Additional entries could be defined as 2020_2, 2020_3, etc., as necessary. The FULLNAME entry in the message above is a variable that can be used in any message and is explained in the next section.

There are two exceptions to the rule explained above. Local Fees can be defined by FIT and by transaction. This is explained in the Fees section. Secondly, Main Menus can have unique banners and instructional text by FIT and by menu number. This is explained in the Main Menu 1 Message and Main Menu Banner sections.



D.2 Variable References and Messages

Variables can be used to reference transaction data, data dictionary entries, or fixed values that can be used by other messages within the TextENG.js file. Variables appear as the first group of entries in the TextENG.js file and are preceded by and underscore.

When a variable references transaction data or a data dictionary entry, it has the format:

var __BANKNAME__ = "~BANKNAME~";

The first and second group of variables in the TextENG.js file fall into this category.

var __BANKNAME__ = "~BANKNAME~"; var __SURCHARGE__ = "~SURCHARGE~"; var __OVERDRAFTFEE__ = "~OVERDRAFTFEE~"; var __TIME__ = "~TIME~"; var __STATEMENTFEE__ = "~STATEMENTFEE~"; var __FULLNAME__ = "~FULLNAME~"; var __X__ = "~X~"; var __Y__ = "~Y~"; var __Z__ = "~Z~"; var __MULTIPLE__ = "~MULTIPLE~"; var __TRANSNAME__ = "~TRANSNAME~"; var __AMOUNT__ = "~AMOUNT~"; //==Stamps var __STAMPCOST__ = "~STAMPCOST~"; var __STAMPNUMBER__ = "~STAMPNUMBER~"; var __SHEETNUMBER__ = "~SHEETNUMBER~"; The third set of variables are fixed text that can be used in conjunction with other messages. Currently these address only End Session and Another Transaction messages that display at the end of a transaction to instruct or query the cardholder. Other uses may be added in the future. var __vTakeReceipt = "<br>Please take your receipt."; var __vTakeCard = "<br><br>Please take your card."; var __vAnotherTran = "<br><br>Do you want another transaction?";

D.3 Transaction Name Messages (9000-9099)

The Transaction Name messages are used on main menu buttons for transaction selection. The last digit in the message number is the Transaction ID. This ID is used to tie transaction-specific screen text defined in other messages back to the specific transaction. See "Fees" in this section for more information.

//==Transaction Name var vMessage9000 = "Fast Cash"; var vMessage9001 = "Display Balances"; var vMessage9002 = "Balance Inquiry"; var vMessage9003 = "Withdrawal"; var vMessage9004 = "Deposit"; var vMessage9005 = "Deposit With Cash Back"; var vMessage9006 = "Transfer"; var vMessage9007 = "Purchase Stamps";



var vMessage9008 = "Payment"; var vMessage9009 = "Split Deposit"; var vMessage9010 = "Electronic Payment"; var vMessage9011 = "Deposit With Cash Back"; var vMessage9012 = "Deposit"; var vMessage9013 = "Deposit"; var vMessage9014 = "Change PIN"; var vMessage9015 = "Mini Statement1"; var vMessage9016 = "Mini Statement2"; var vMessage9017 = "Mini Statement3"; var vMessage9018 = "Mini Statement4"; var vMessage9019 = "Check Reorder"; var vMessage9020 = "Settlement"; var vMessage9021 = "Purchase1"; var vMessage9022 = "Purchase2"; var vMessage9023 = "Purchase3"; var vMessage9024 = "Purchase4"; var vMessage9025 = "Payment From Account"; var vMessage9026 = "Payment To Account"; var vMessage9027 = "Full Statement1"; var vMessage9028 = "Full Statement2"; var vMessage9029 = "Full Statement3"; var vMessage9030 = "Full Statement4"; var vMessage9031 = "Full Statement5"; var vMessage9032 = "Full Statement6"; var vMessage9033 = "Full Statement7"; var vMessage9034 = "Full Statement8"; var vMessage9035 = "Mini Statement5"; var vMessage9036 = "Mini Statement6"; var vMessage9037 = "Mini Statement7"; var vMessage9038 = "Mini Statement8"; var vMessage9039 = "Mini Statement9"; var vMessage9040 = "Mini Statement10"; var vMessage9041 = "Message To Bank"; var vMessage9042 = "Message To Bank"; var vMessage9043 = "Message To Bank"; var vMessage9044 = "Personalized Fast Cash"; var vMessage9045 = "Receipt"; Note: 9004 is for Envelope Deposit, 9012 is for Cash Deposit and 9013 is for Check Deposit.

D.4 Language Selection Button Messages (1000-1039)

These messages define the text displayed on the buttons on the Language Selection screens. The main message entry is the button text, and the corresponding sub-message is the three-character ISO 639 language code. All language selection button entries must have this format. //==Language var vMessage1000 = "English"; var vMessage1000_1 = "eng"; var vMessage1001 = "Español"; var vMessage1001_1 = "spa"; var vMessage1002 = "Chineese"; var vMessage1002_1 = "chi"; var vMessage1003 = "Korean"; var vMessage1003_1 = "kor"; var vMessage1004 = "Français"; var vMessage1004_1 = "fra"; var vMessage1005 = "Português"; var vMessage1005_1 = "por";



D.5 Button Messages (1040-1089)

These entries define the common buttons that can be used during any transaction or operation.

//== Button var vMessage1040 = "Cancel"; var vMesage1040_1 = “For cancel, press Cancel Key.”; var vMessage1041 = "Enter"; var vMessage1042 = "Clear"; var vMessage1043 = "OK"; var vMessage1044 = "Yes"; var vMessage1045 = "No"; var vMessage1046 = "Continue"; var vMessage1047 = "Done"; var vMessage1048 = "Exit"; var vMessage1049 = "Return Card"; var vMessage1050 = "Accept Fee"; var vMessage1051 = "Decline Fee"; var vMessage1052 = "Primary Checking"; var vMessage1053 = "Primary Savings"; var vMessage1054 = "Primary Credit"; var vMessage1055 = "Other Accounts"; var vMessage1056 = "Checking"; var vMessage1057 = "Savings"; var vMessage1058 = "Credit"; var vMessage1059 = "Checking to Savings"; var vMessage1060 = "Savings to Checking"; var vMessage1061 = "Checking to Checking"; var vMessage1062 = "Savings to Savings"; var vMessage1063 = "Press When Ready"; var vMessage1064 = "Cash"; var vMessage1065 = "Check"; var vMessage1066 = "Insert More Cash"; var vMessage1067 = "Done with Deposit"; var vMessage1068 = "Credit to Checking"; var vMessage1069 = ""; var vMessage1070 = ""; var vMessage1071 = ""; var vMessage1072 = "Print Receipt"; var vMessage1073 = "Display Balance"; var vMessage1074 = "More Accounts"; var vMessage1075 = "Line of Credit"; var vMessage1076 = "Credit Card"; var vMessage1077 = "Previous Accounts"; var vMessage1078 = "Print and Display"; var vMessage1078_1 = "For Print and Display, press 3."; var vMessage1079 = "Return Check"; //==General var vMessage1080 = "ATM Transactions"; var vMessage1081 = "Payments"; var vMessage1082 = "Deposit"; var vMessage1083 = "From"; var vMessage1084 = "Other Amount"; var vMessage1085 = "; var vMessage1086 = "More Language Options"; var vMessage1087 = "Previous Menu";



var vMessage1089 = "Another Deposit";

D.6 Welcome Screen Messages (1090-1099)

The Welcome screen displays while the ATM is idle. Several messages have been defined for the Welcome screen. These messages contain the BANKNAME variable and an additional message has been defined for each default messages. Each additional message references the default message plus any additional text that should display (+ "<br><br>Por favor, inserte su tarjeta.", for example).

//==Welcome var vMessage1090 = "Welcome to this<br><br>" + __BANKNAME__ + " ATM<br><br> Please Insert Your Card."; var vMessage1090_1 = vMessage1090 + "<br><br>Por favor, inserte su tarjeta."; var vMessage1091 = "Welcome to this<br><br>" + __BANKNAME__ + " ATM<br><br> Please Insert And Remove Your Card."; var vMessage1091_1 = vMessage1091 + "<br><br>Por favor, inserte y retire su tarjeta."; var vMessage1092 = "Please Swipe Your Card."; var vMessage1092_1 = vMessage1092 + "<br><br>Por favor, deslice su tarjeta.";

D.7 Out Of Service Screen Messages (2000)

Currently the Out of Service screen has only one message and one variant. The variant does not include the Spanish translation of the English text.

//==OutofService var vMessage2000 = "This ATM is temporarily unavailable.<br>We're sorry for the inconvenience.<br><br>Este ATM está temporalmente fuera de servicio. <br>Lamentamos el inconveniencia."; var vMessage2000_1 = "This ATM is temporarily unavailable.<br>We're sorry for the inconvenience.";

D.8 Card Not Read Screen Messages (2001-2010)

The Card Not Read messages address all types of card readers. Since the cardholder has not selected his language yet in the transaction sequence, no Spanish translation is currently included.

//===CardNotRead var vMessage2001 = "Please Insert Your Card."; var vMessage2002 = "Please Insert And Remove Your Card."; var vMessage2003 = "Please Swipe Your Card."; var vMessage2004 = "We’re sorry, we are unable to read your card.<br> Please re-insert your card to try again."; var vMessage2005 = "We’re sorry, we are unable to read your card.<br> Please re-insert then remove your card to try again."; var vMessage2006 = "We’re sorry, we are unable to read your card.<br> Please swipe your card to try again.";



D.9 End Session Screen Messages (2011-2016)

The End Session messages are used for successful transactions and transaction denied by host. Since these messages are called when the session is ending, the "Do you want another transaction?" variable is not used. Three of the fixed text variables referenced in the Variable References and Messages section earlier are used in these messages. These variables used are:

2=TakeCard

3=Receipt

5=TakeCard+Receipt

When a message and variable, or two variables are joined with a +, both messages will display. Since "Do you want another transaction?" is not an option with these messages, _1 and _4 are always blank. Refer to the Another Transaction messages for use of all 5 variables. //==EndSession var vMessage2011 = "Thank you for using this<br><br>" + __BANKNAME__ + " ATM"; var vMessage2011_1 = vMessage2011; var vMessage2011_2 = __vTakeCard; var vMessage2011_3 = __vTakeReceipt; var vMessage2011_4 = vMessage2011; var vMessage2011_5 = __vTakeReceipt + __vTakeCard; var vMessage2012 = "Your transaction has been cancelled."; var vMessage2012_1 = vMessage2012; var vMessage2012_2 = vMessage2012 + __vTakeCard; var vMessage2012_3 = vMessage2012; var vMessage2012_4 = vMessage2012; var vMessage2012_5 = vMessage2012 +__vTakeReceipt + __vTakeCard; var vMessage2013 = "Your transaction is complete but we can not print your receipt."; var vMessage2013_1 = vMessage2013; var vMessage2013_2 = vMessage2013 + __vTakeCard; var vMessage2013_3 = vMessage2013; var vMessage2013_4 = vMessage2013; var vMessage2013_5 = vMessage2013 +__vTakeReceipt + __vTakeCard; var vMessage2014 = "Your transaction has been cancelled."; var vMessage2014_1 = vMessage2014; var vMessage2014_2 = vMessage2014 + __vTakeCard; var vMessage2014_3 = vMessage2014 + __vTakeReceipt; var vMessage2014_4 = vMessage2014; var vMessage2014_5 = vMessage2014 + __vTakeReceipt + __vTakeCard; var vMessage2015 = "Card is Invalid. Last Transaction Cancelled. <br>Please contact your Financial Institution."; var vMessage2015_1 = vMessage2015; var vMessage2015_2 = vMessage2015 + __vTakeCard; var vMessage2015_3 = vMessage2015 + __vTakeReceipt; var vMessage2015_4 = vMessage2015; var vMessage2015_5 = vMessage2015 + __vTakeReceipt + __vTakeCard; var vMessage2016 = "Your transaction is complete but we are unable to dispense the amount you requested. Please refer to your receipt"; var vMessage2016_1 = vMessage2015; var vMessage2016_2 = vMessage2015 + __vTakeCard; var vMessage2016_3 = vMessage2015 + __vTakeReceipt; var vMessage2016_4 = vMessage2015; var vMessage2016_5 = vMessage2015 + __vTakeReceipt + __vTakeCard;



//==CheckCaptured var vMessage2135 = "Your Check has been retained.<br>We're sorry for the inconvenience.<br>Please contact your financial institution."; var vMessage2135_1 = vMessage2135; var vMessage2135_2 = vMessage2135 + __vTakeCard; var vMessage2135_3 = vMessage2135 + __vTakeReceipt; var vMessage2135_4 = vMessage2135; var vMessage2135_5 = vMessage2135 + __vTakeReceipt + __vTakeCard;

D.10 Check Captured Messages (2135-2139)

These messages are used with the Enhanced Deposit transaction. Three of the fixed text variables are used in these messages. When a check is captured, the session is canceled, so the "Do you want another transaction?" variables are not used.

As with the End Session messages, the underscore values used are:

2=TakeCard

3=Receipt

5=TakeCard+Receipt

When a message and variable, or two variables are joined with a +, both messages will display. Since "Do you want another transaction?" is not an option with these messages, _1 and _4 are always blank. Refer to the Another Transaction messages for use of all 5 variables. //==CheckCaptured var vMessage2135 = "Your Check has been retained.<br>We're sorry for the inconvenience.<br>Please contact your financial institution."; var vMessage2135_1 = vMessage2135; var vMessage2135_2 = vMessage2135 + __vTakeCard; var vMessage2135_3 = vMessage2135 + __vTakeReceipt; var vMessage2135_4 = vMessage2135; var vMessage2135_5 = vMessage2135 + __vTakeReceipt + __vTakeCard;

D.11 Enter/ReEnter PIN Messages (2020-2021)

These messages are used to prompt the user to enter his PIN, or reenter his PIN after he has entered an incorrect PIN. The _1 message is used with banks that wants to read the customer's name (FULLNAME variable) from track 1 on the card.

//==EnterPin var vMessage2020 = "Please enter your<br>Personal Identification Number<br>and then press the Enter key."; var vMessage2020_1 = "Hello " + __FULLNAME__ + ", Please enter your<br>Personal Identification Number<br>and then press the Enter key."; var vMessage2022 = "ATM Preferences are not available on this machine. Please enter your Personal Identification Number<br>and then press the Enter key."; //==ReEnterPin var vMessage2021 = "You have entered an incorrect PIN.<br>Please re-enter your PIN<br>and press Enter on the keypad."; var vMessage2021_1 = vMessage2021;



D.12 Another Transaction Messages (2030-2039)

Another Transaction messages display at the conclusion of a transaction when chained transactions are permitted. All five of the fixed text variables referenced in the Variable References and Messages section earlier are used with these messages. These variables used are:

1=AnotherTran

2=TakeCard

3=Receipt

4=AnotherTran+Receipt

5=TakeCard+Receipt

When two variables are joined with a +, both messages will be displayed.

//==AnotherTransaction //== 1=AnotherTran 2=TakeCard 3=Receipt //== 4=AnotherTran+Receipt 5=TakeCard+Receipt var vMessage2030 = "Your transaction is complete."; var vMessage2030_1 = vMessage2030 + __vAnotherTran; var vMessage2030_2 = vMessage2030 + __vTakeCard; var vMessage2030_3 = vMessage2030 + __vTakeReceipt; var vMessage2030_4 = vMessage2030 + __vTakeReceipt + __vAnotherTran; var vMessage2030_5 = vMessage2030 + __vTakeReceipt + __vTakeCard; var vMessage2031 = "We are unable to process<br>your transaction at this time.<br>Your transaction has been cancelled."; var vMessage2031_1 = vMessage2031 + __vAnotherTran; var vMessage2031_2 = vMessage2031 + __vTakeCard; var vMessage2031_3 = vMessage2031 + __vTakeReceipt; var vMessage2031_4 = vMessage2031 + __vTakeReceipt + __vAnotherTran; var vMessage2031_5 = vMessage2031 + __vTakeReceipt + __vTakeCard; var vMessage2032 = "Your transaction is complete but we can not print your receipt."; var vMessage2032_1 = vMessage2032 + __vAnotherTran; var vMessage2032_2 = vMessage2032 + __vTakeCard; var vMessage2032_3 = vMessage2032; var vMessage2032_4 = vMessage2032 + __vAnotherTran; var vMessage2032_5 = vMessage2032 + __vTakeCard; var vMessage2033 = "Your transaction has been cancelled."; var vMessage2033_1 = vMessage2033 + __vAnotherTran; var vMessage2033_2 = vMessage2033 + __vTakeCard; var vMessage2033_3 = vMessage2033 + __vTakeReceipt; var vMessage2033_4 = vMessage2033 + __vTakeReceipt + __vAnotherTran; var vMessage2033_5 = vMessage2033 + __vTakeReceipt + __vTakeCard; var vMessage2034 = "Last transaction cancelled at your request."; var vMessage2034_1 = vMessage2034 + __vAnotherTran; var vMessage2034_2 = vMessage2034 + __vTakeCard; var vMessage2034_3 = vMessage2034 + __vTakeReceipt; var vMessage2034_4 = vMessage2034 + __vTakeReceipt + __vAnotherTran; var vMessage2034_5 = vMessage2034 + __vTakeReceipt + __vTakeCard; var vMessage2035 = "Your transaction has been cancelled."; var vMessage2035_1 = vMessage2035 + __vAnotherTran; var vMessage2035_2 = vMessage2035 + __vTakeCard; var vMessage2035_3 = vMessage2035 + __vTakeReceipt; var vMessage2035_4 = vMessage2035 + __vTakeReceipt + __vAnotherTran; var vMessage2035_5 = vMessage2035 + __vTakeReceipt + __vTakeCard; var vMessage2036 = "Your transaction is complete but we are unable to dispense the amount you requested. Please refer to your receipt";



var vMessage2036_1 = vMessage2036 + __vAnotherTran; var vMessage2036_2 = vMessage2036 + __vTakeCard; var vMessage2036_3 = vMessage2036 + __vTakeReceipt; var vMessage2036_4 = vMessage2036 + __vTakeReceipt + __vAnotherTran; var vMessage2036_5 = vMessage2036 + __vTakeReceipt + __vTakeCard;

D.13 Fee Messages (2040-2042)

Fees are handled two ways in APTRA Edge. The fee can be returned from host, or the fee can be stored locally. The TransFee message (2040) is used when the fee is returned from host. The BANKNAME and SURCHARGE in these messages are taken from the data dictionary.

//==TransFee var vMessage2040 = __BANKNAME__ + " will charge a fee of " + __SURCHARGE__ + " for this transaction. This fee is in addition to any fees which may be charged by your financial institution.<br>If you agree to this fee, press <b>Yes</b>. <br>If you wish to cancel this transaction, press <b>No</b>."; When fees are stored locally, the LocalFee messages (2041) are used. The actual fee for each transaction is defined in the data dictionary by FIT (ConsumerFlow.FITxTransactionNameFee) and ConsumerFlow.FITxTransactionNameFeeOption). In the messages file, you can define different onscreen messages per FIT and/or per transaction. To do this, you use the sub-messages (2041_XXX) with the first two digits after the underscore as the FIT and the last digit as the transaction number from the "Transaction Message Numbers" group for the transaction numbers.

//==LocalTransFee var vMessage2041 = __BANKNAME__ + " will charge a fee of " + __SURCHARGE__ + " for this transaction. This fee is in addition to any fees which may be charged by your financial institution.<br>If you agree to this fee, press <b>Yes</b>. <br>If you wish to cancel this transaction, press <b>No</b>."; var vMessage2041_000 = ""; var vMessage2041_001 = ""; var vMessage2041_002 = ""; var vMessage2041_003 = ""; var vMessage2042 = "<br>Press <b>Yes</b> to continue. Press <b>No</b> to cancel this transaction.";

D.14 Enter Amount Messages (2050-2059)

The Enter Amount messages include a separate message for each type of transaction that requires the cardholder to enter an amount: withdrawal, payment, envelope deposit, envelope deposit with cash back, transfer, and check deposit.

//==EnterAmount var vMessage2045 = "Please enter the total amount in the envelope."; var vMessage2046 = "You entered a total deposit amount of " + __AMOUNT__ + ".<br>Please enter the amount to deposit to the first account. <br>Your receipt will indicate the amount deposited to each account." ; var vMessage2047 = "You have entered an invalid deposit amount.<br>Amount must be less than " + __AMOUNT__ + "."; var vMessage2050 = "You have entered an invalid withdrawal amount.<br>Amount must be in multiples of " + __MULTIPLE__ + "."; var vMessage2051 = "Invalid " + __TRANSNAME__ + " amount.<br>Amount must be greater than $0.00."; var vMessage2052 = "Please enter the withdrawal amount <br> in multiples of " + __MULTIPLE__ + ".";



var vMessage2053 = "Please enter the payment amount"; var vMessage2054 = "Please enter the payment amount"; var vMessage2055 = "Please enter the total amount of all the items in the deposit envelope.<br>(The withdrawal amount will be entered <br> on the next screen)"; var vMessage2056 = "You entered a deposit amount of " + __AMOUNT__ + ".<br>Please enter the withdrawal amount <br> in multiples of " + __MULTIPLE__ + "."; var vMessage2057 = "Please enter the transfer amount"; var vMessage2058 = "Please enter the deposit amount"; var vMessage2059 = "Please enter check amount";

D.15 Select Language Message (2060)

Only one select language message is currently defined; however, additional messages can be defined for message numbers 2061 through 2069 if required. The button labels for the select language screen are defined in messages 1000-1039.

//==Language var vMessage2060 = "Please select the language you wish to use"; var vMessage2060_1 = "Please select the language you wish to use"; var vMessage2061 = "Sorry, ATM Preferences are not available on this machine. Please select the language you wish to use";

D.16 Receipt Messages (2070-2079)

These messages address all instances where the cardholder needs receipt instructions when the session is not ending; for example, "Do you want a receipt? " or "We cannot print a receipt. Do you want to continue?" displayed during a transaction.

//==Receipt var vMessage2070 = "Do you want a receipt with your transaction?"; //==NoReceipt var vMessage2071 = "This ATM is temporarily unable to print a receipt.<br>Would you like to continue without a receipt?"; //==ReceiptFailed var vMessage2072 = "We can not print your receipt.<br>We're sorry for the inconvenience."; //==TakeReceipt var vMessage2073 = "Please take your receipt."; //==BalanceReceipt var vMessage2074 = "Where would you like your balance ?";



D.17 Main Menu 1 Messages and Banners (2080-2081)

These messages allow you to define unique instructional text and banners for each main menu you have defined. In the sub-messages for these entries, the first two digits after the underscore ( _ ) are the FIT number followed by the Main Menu number. This is the same menu number used when you defined your transaction set in the data dictionary (CONSUMERFLOW.WITHDRAWAL=Yes,1,4 where 1 is the menu number and 4 is the button position on that menu).

For example, if main menu 2 contains all payment transactions, and assuming all FITs see the same menus, your unique entries for the payment main menu Text and Banner could be:

var vMessage2080_002 = "Please select the type of Payment <br> by pressing the appropriate key."; var vMessage2081_002 = "Payment Menu";

If different FITs will see different payment main menus, you would have multiple entries for these sub-messages, one for each FIT.

//==MainMenu1 Instruction Message var vMessage2080 = "Please select the type of transaction <br> by pressing the appropriate key"; var vMessage2080_001 = ""; var vMessage2080_002 = ""; var vMessage2080_003 = ""; var vMessage2080_004 = ""; var vMessage2080_005 = ""; //==MainMenu Banner var vMessage2081_001 = ""; var vMessage2081_002 = ""; var vMessage2081_003 = ""; var vMessage2081_004 = ""; var vMessage2081_005 = "";

D.18 Transaction Menu Messages (2082-2089)

These messages define the onscreen text for transaction menus - menus displayed from a non-transaction button on main menu. The most common transaction menus are included in the file.

//==PaymentMenu var vMessage2082 = "Please select how you would like to make payment"; //==Transfer var vMessage2083 = "Please select the type of transfer"; //==DepositMenu var vMessage2084 = "Please select a deposit type"; //==FastCashMenu var vMessage2085 = "Please select Fast Cash amount"; //==WithdrawalMenu var vMessage2086 = "Please select a Withdrawal amount";



//==TransferMenu var vMessage2087 = "Please select account type";

D.19 Please Wait Message (2090-2091)

Two messages are available for the Please Wait screen. 2090 is a generic Please Wait, and 2091 is customer-specific used during account search.

//==PleaseWait var vMessage2090 = "Please wait while we process this transaction..."; //==PlsWaitFindAccount //==PlsWaitFindSelectedAccount var vMessage2091 = "Please wait while we look up your accounts...";

D.20 More Time Message (2100-2109)

One "More Time?" message is defined, with one additional to be used as necessary.

//==TimeOut var vMessage2100 = "Would you like more time?"; var vMessage2100_1 = vMessage2100

D.21 Account Selection Messages (2110-2119)

The account selection messages are used when a cardholder need to select an account for his transaction. Transfer and payment transactions have their own unique account selection messages due to the unique account selection scenarios of these transactions. The SelectOARAccount messages are customer-specific.

//==SelectAccount var vMessage2110 = "Please select account type"; var vMessage2110_1 = "Please select account type"; var vMessage2110_2 = "Please select account type"; var vMessage2110_3 = "Please select account type"; var vMessage2110_4 = "Please select account type"; var vMessage2110_5 = "Please select account type"; //==Payment var vMessage2111 = "Please select the account from which<br>you wish to make the payment."; var vMessage2112 = "Please select the type of account<br>you wish to make payment to"; //==Transfer var vMessage2113 = "Please select account type to transfer from"; var vMessage2113_1 = "to transfer from"; var vMessage2114 = "Please select account type to transfer to"; var vMessage2114_1 = "to transfer too"; //==SelectOARAccount var vMessage2115 = "Please select the from account"; var vMessage2116 = "Please select the to account"; var vMessage2118 = "Please select the desired account";



D.22 Take Cash Messages (2120-2129)

All cash instruction messages appear in this group, including the messages displayed when the cardholder does not take his cash.

//==TakeCash var vMessage2120 = "Please remove your cash"; //==TakeCashAndReceipt var vMessage2121 = "Please remove your cash and receipt"; //==CashRetracted var vMessage2122 = "We're sorry.<br>Your cash was not removed<br>in the allotted time.<br><br>Please contact your financial institution."; var vMessage2123 = "We're sorry.<br>Your cash was not removed<br>in the allotted time and<br>we cannot retract your cash.<br><br>Please contact your financial institution.";

D.23 Card Captured Message (2130-2134)

Only one card captured message is already defined, but more can be added as required.

//==CardCaptured var vMessage2130 = "Your card has been retained.<br>We're sorry for the inconvenience.<br>Please contact your financial institution.";

D.24 Transaction Not Available Message (2140-2149)

Only one Transaction Not Available message is defined, but more can be added as required.

//==TransactionNotAvail var vMessage2140 = "We're sorry,<br>this transaction is currently unavailable.<br><br>Please try again later.";

D.25 Balance Inquiry Messages (2150-2159)

These messages contain all the onscreen text required for Balance Inquiry transactions. If more balances than the ones defined are returned from host, additional messages would need to be defined.

//==Balance var vMessage2150 = "Balance Inquiry for"; var vMessage2151 = "Available Balance"; var vMessage2152 = "Current Balance"; var vMessage2153 = "Account Balance";



D.26 Stamp Transaction Messages (2160-2169)

All stamp transaction messages are defined in this group, including the messages displayed when the cardholder does not take his stamps. The variables included in these messages are from the data dictionary CONSUMERFLOW.STAMP entries.

//==TakeStamps var vMessage2160 = "Please remove your stamps."; //==TakeStampsAndReceipt var vMessage2161 = "Please remove your stamps and receipt."; //==SelectStamps var vMessage2164 = "Please select the number of " + __STAMPCOST__ + " stamps you wish to purchase. A fee of " + __SURCHARGE__ + " per sheet of stamps is included."; var vMessage2165 = __SHEETNUMBER__ + " = " + __STAMPCOST__ + " (" + __STAMPNUMBER__ + " Stamps)"; //==CashRetracted, used by StampsRetracted var vMessage2162 = "We're sorry.<br>Your stamps were not removed<br>in the allotted time and<br>we cannot retract your stamps.<br><br>Please contact your financial institution."; var vMessage2166 = "We're sorry.<br>Your stamps were not removed<br>in the allotted time.<br><br>Please contact your financial institution.";

D.27 Envelope Deposit Messages (2170-2189)

All envelope deposit messages are defined in this group including the deposit portion of the Withdrawal with Cash Back, and the envelope preparation portion of the Message to Bank transaction.

//==InsertEnvelope //==CBInsertEnvelope var vMessage2170 = "Please insert envelope into depository slot"; var vMessage2171 = "Please insert envelope into depository slot"; var vMessage2172 = "Please insert envelope into depository slot"; //==PrepareEnvelope var vMessage2180 = "Please prepare your deposit"; var vMessage2181 = "Please prepare your payment"; var vMessage2182 = "Please prepare your envelope for message to bank";

D.28 Statement Messages (2190-2209)

These messages define the onscreen text for Statement transaction menus. The Mini Statement fee message is also included in this group. The STATEMENTFEE variable comes from the data dictionary.

//==SelectStatement1 var vMessage2190 = "Please select the type of information you would like.<br>A fee may be charged for this transaction."; //==SelectStatement2 var vMessage2191 = "Please select the type of information you would like.<br>A fee may be charged for this transaction.";



//==StatementFee var vMessage2192 = "There is a " + __STATEMENTFEE__ + " fee to print Mini Statements.<br>Would you like to continue?";

D.29 Deposit with Cash Back Deposit Messages (2210-2219)

These messages instruct the cardholder as to the status of the deposit portion of his Deposit with Cash Back transaction.

//==CBDepositFailed var vMessage2210 = "Deposit failed.<br><br>Now we're processing your withdrawal request..."; var vMessage2211 = "Deposit is complete but we can not print your receipt.<br><br>Now we're processing your withdrawal request..."; var vMessage2212 = "Deposit is complete.<br><br>Now we're processing your withdrawal request..."; var vMessage2213 = "Please take your receipt.<br><br>Now we're processing your withdrawal request...";

D.30 Enhanced Deposit Transaction Messages (2220-2329)

All Enhanced Deposit messages are included in the group. The AMOUNT variable for Message 2221 is taken from the BNA.MAXBILLS data dictionary entry. The remaining AMOUNT variables come from the transaction.

//==InsertBills var vMessage2221 = "Please insert your cash.<br>You can insert up to " + __AMOUNT__ + " bill(s) at one time."; var vMessage2220 = "Please wait while we prepare to accept cash."; //==InsertCheck //var vMessage2230 = "Please insert your check."; //==ConfirmBills var vMessage2240 = "Select an option to continue"; var vMessage2241 = "Total Inserted Amount:"; var vMessage2242 = "You have inserted the maximum number of bills (30).<br>To add more bills or perform a check deposit,<br>select <b>Continue</b> to proceed to the check and cash deposit screen."; //==BNAFailForceDeposit var vMessage2250 = "We're sorry. <br>We are currently unable to return your cash.<br>Please wait while we process<br>your deposit amount of " + __AMOUNT__ + "."; var vMessage2252 = "Please wait while we process<br>your cash deposit amount of " + __AMOUNT__ + "."; //==TakeBills var vMessage2260 = "We were unable to read some of the bills<br>you inserted.<br>Please take your cash and try again."; var vMessage2261 = "Your transaction has been cancelled.<br>Please take your cash."; var vMessage2262 = "We are temporarily unable to accept cash.<br>Please take your cash and try again later."; //==ConfirmCheck var vMessage2270 = "Entered amount " + __AMOUNT__ + "<br>Is your entered amount correct?";



//==TakeCheck var vMessage2280 = "We are unable to read your check.<br>Please take your check and try again."; var vMessage2281 = "Your transaction has been cancelled.<br>Please take your check."; var vMessage2282 = "We are temporarily unable to accept check.<br>Please take your check and try again later."; //==CPMFailForceDeposit var vMessage2290 = "We're sorry. <br>We are currently unable to return your check.<br>Please wait while we process<br>your deposit amount of " + __AMOUNT__ + "."; var vMessage2291 = "We're sorry. <br>Your check has been retained.<br>Please wait while we process<br>your deposit amount of " + __AMOUNT__ + "."; var vMessage2292 = "Please wait while we process<br>your check deposit amount of " + __AMOUNT__ + "."; //==DepositContinue var vMessage2300 = "Your check has been accepted. <br>Please select <b>Check</b> or <b>Cash</b> to continue this deposit or select <b>Done with Deposit</b> if you have no more items to deposit."; var vMessage2301 = "Your cash has been accepted. <br>Please select <b>Check</b> or <b>Cash</b> to continue this deposit or select <b>Done with Deposit</b> if you have no more items to deposit."; var vMessage2302 = "Please select <b>Check</b> or <b>Cash</b> to continue this deposit or select <b>Done with Deposit</b> if you have no more items to deposit."; var vMessage2303 = "Your check has been accepted. <br>Please select <b>Another Deposit</b> to continue this deposit or select <b>Done with Deposit</b> if you have no more items to deposit."; var vMessage2304 = "Your cash has been accepted. <br>Please select <b>Another Deposit</b> to continue this deposit or select <b>Done with Deposit</b> if you have no more items to deposit."; var vMessage2305 = "Please select <b>Another Deposit</b> to continue this deposit or select <b>Done with Deposit</b> if you have no more items to deposit."; //==PrepareBills var vMessage2310 = "Please prepare your cash<br>Press <b>Continue</b> when ready<br><br> Smooth out your cash"; //==PrepareCheck var vMessage2320 = "Please prepare your check<br>Press <b>Continue</b> when ready<br><br> Smooth your check Endorse your check";

D.31 PIN Change Transaction Messages (2330-2339)

These messages contain all onscreen messages for the PIN Change transaction, including all incorrect PIN entered error text.

//==ChangePIN var vMessage2330 = "Please enter your <br>NEW Personal Identification Number on the keypad.<br> Then press Enter key."; var vMessage2331 = "Your Personal Identification Number must be between 4 and 10 characters in length. <br>Please re-enter your Personal Identification Number.<br> Then press Enter key to proceed."; var vMessage2332 = "For verification, please re-enter your NEW Personal Identification Number on the keypad.<br> Then press Enter key."; var vMessage2333 = "We did not recognize your<br> Personal Identification Number.<br> Please re-enter it on the keypad below.<br> Then press Enter key."; var vMessage2334 = "Your second entry did not match your first entry.<br> Please start again and enter your NEW Personal Identification Number.<br> Then press the Enter key.";



D.32 Cancel Please Wait Message (2340)

This message displays on the CancelPleaseWait screen which displays to the cardholder after he presses the Cancel button during a transaction.

//==CancelPleaseWait var vMessage2340 = "Please wait while we cancel your transaction...";

D.33 Take Card Message (2350)

This message displays on the standalone Take Card screen (no Take Receipt or Another Transaction text included).

//==TakeCard var vMessage2350 = "Please take your card";

D.34 Check Reorder Messages (2360)

This message is for a customer-specific, check reorder transaction.

//==CheckReorder var vMessage2360 = "Automated check re-orders are available at the ATM if changes in style, quantity or pre-printed information are not needed. Please call us to place other orders.<br><br>Would you like to continue?";

D.35 Envelope Dispense Messages (2450-2499)

All messages associated with the dispensing of an envelope are in this group.

//===DSNoEnvelope var vMessage2450 = "We're sorry. <br> We are unable to dispense an envelope. <br><br> Would you like to continue?"; //===DSAskEnvelope var vMessage2460 = "Do you need an envelope?"; //===DSDispenseEnvelope var vMessage2470 = "Please take your envelope.";

D.36 Personalization Messages (2500 to 2599)

All Personalization transaction messages and buttons are included in this group.

//==Personalization. The series 2500 to 2600 is reserved for personalization. var vMessage2500 = "Please select your ATM preferences"; var vMessage2501 ="Your current preference is" var vMessage2502 = "Please select your <br> ATM Language preference"; var vMessage2503 = "Please enter your <br>ATM Personalized Fast Cash preference<br>Amount must multiple of " + __MULTIPLE__ + ".";



var vMessage2504 = "Please select a personalized fast cash amount"; var vMessage2505 = "Please select your Receipt option preferences for"; var vMessage2506 = "Invalid " + __TRANSNAME__ + " amount.<br>Amount must be greater than $0.00."; var vMessage2507 = "You have entered an invalid personalized fast cash preference.<br>Amount must be in multiples of " + __MULTIPLE__ + "."; var vMessage2508 = "Please select your <br> ATM Receipt preference"; var vMessage2509 = "Do you want to enter ATM Preferences?"; var vMessage2510 = "Please wait while we retrieve your preferences." //==Personalization buttons var vMessage2520 = "Language"; var vMessage2521 = "Fast Cash Amount"; var vMessage2522 = "Receipt Options"; var vMessage2523 = "Save Options"; var vMessage2524 = "Back to preferences"; var vMessage2525 = "No preference: Always ask"; var vMessage2526 = "Personalized Fast Cash"; var vMessage2527 = "Fast Cash and Withdrawal"; var vMessage2528 = "Other Transactions"; var vMessage2529 = "Always print receipt"; var vMessage2530 = "Do not print receipt"; var vMessage2531 = "No Preference Always Ask"; var vMessage2532 = "Yes"; var vMessage2533 = "No"; var vMessage2534 = "Never Set Preference";

D.37 Deposit Disclaimer

This message displays on a disclaimer screen during a Deposit transaction when the data dictionary entry CONSUMERFLOW.SHOWDEPOSITDISCLAIMER is set to Yes. The screen displays just after the cardholder selects the Deposit transaction.

//==DepositDisclaimer var vMessage2600 = "Availability of Deposits <br> <br> Funds from Deposits may not be Available for<br>Immediate Withdrawal. Please refer to our<br>rules governing funds Availability for details.<br> <br>Deposits made at this ATM after 12 noon may<br>not be credited until the next business day.<br><br>Would you like to continue?";

D.38 Non-Transaction Main Menu Button Text Messages (5000-5999)

These messages contain the text for common non-transaction buttons that can appear on the Main Menu. You can change the exact word on the button, but the meaning of the buttons must remain the same because they are used in a prescribed manner throughout the application.

//==Non-Transaction Button in MainMenu var vMessage5000 = "Cancel"; var vMessage5001 = "Next Menu"; var vMessage5002 = "Main Menu"; var vMessage5003 = "Fast Cash"; var vMessage5004 = "Deposits";



var vMessage5005 = "Statements"; var vMessage5006 = "ATM Preferences"; var vMessage5007 = ""; var vMessage5008 = ""; var vMessage5009 = ""; var vMessage5010 = ""; var vMessage5011 = ""; var vMessage5012 = ""; var vMessage5013 = ""; var vMessage5014 = ""; var vMessage5015 = ""; var vMessage5016 = ""; var vMessage5017 = ""; var vMessage5018 = ""; var vMessage5019 = ""; var vMessage5020 = ""; var vMessage5021 = ""; var vMessage5022 = ""; var vMessage5023 = ""; var vMessage5024 = ""; var vMessage5025 = ""; var vMessage5026 = ""; var vMessage5027 = ""; var vMessage5028 = ""; var vMessage5029 = ""; var vMessage5030 = ""; var vMessage5031 = ""; var vMessage5032 = ""; var vMessage5033 = ""; var vMessage5034 = ""; var vMessage5035 = ""; var vMessage5036 = ""; var vMessage5037 = ""; var vMessage5038 = ""; var vMessage5039 = ""; var vMessage5040 = "Not Defined";

D.39 Account Selection Button Text Messages (6000-6999)

This group contains the text that will display on the account selection buttons. If multiple accounts are returned from host, these entries will contain the account type selections. If multiple account selection information is stored locally, every account that does not have sub-account will be defined in this group.

//==Select Account Buttons var vMessage6000 = "Cancel"; var vMessage6001 = "Checking"; var vMessage6002 = "Savings"; var vMessage6003 = "Credit"; var vMessage6004 = "All Accounts"; var vMessage6005 = ""; var vMessage6006 = ""; var vMessage6007 = "";



D.40 Unique Consumer Flow Messages (7000-7999)

These messages are used when the application must follow a customer-unique flow. //==Reserved for customer based messages var vMessage7000 = ""; var vMessage7001 = ""; var vMessage7002 = ""; var vMessage7003 = ""; var vMessage7004 = ""; var vMessage7005 = ""; var vMessage7006 = ""; var vMessage7007 = "";

D.41 Denial Code Text Messages (000-999)

Your next state codes and denial text are included in this section. There are six entries for each denial code:

Denial text (which is used by the other five entries).

Denial text and offer another transaction.

Denial text and instruct to take card (motorized card reader only).

Denial text and instruct to take receipt.

Denial text, instruct to take receipt and offer another transaction.

Denial text, instruct to take receipt and card (motorized card reader only). You normally will have all six entries for all of you denial codes. However, some may be omitted if the message does not make any sense.

//==Denial Codes //==This is a sample of Denial Code Message. All Denial Codes must have all 5 messages. var vMessage000 = "Unable to process your request."; var vMessage000_1 = vMessage000 + __vAnotherTran; var vMessage000_2 = vMessage000 + __vTakeCard; var vMessage000_3 = vMessage000 + __vTakeReceipt; var vMessage000_4 = vMessage000 + __vTakeReceipt + __vAnotherTran; var vMessage000_5 = vMessage000 + __vTakeReceipt + __vTakeCard;

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE ENHANCED DEPOSIT CHECK ENDORSEMENT PRINTING


E Enhanced Deposit Check Endorsement Printing

The iTran 1000 Check Processor can print endorsement data on the rear of a check. Depending upon the print module within the iTran 1000, either a single line endorsement or a multiple line endorsement can be printed. The endorsement data must be contained in the Printer Data Field (r) in the Transaction Reply message from the host.

This section describes the character set that is used by the iTran 1000 Check Processor printer, and the location on the check of the endorsement data when printed.

E.1 Printable Characters

The printer character set, shown below, supports a total of 72 printable ASCII characters. Two character pitches are available: standard and compressed. The standard format allows 4.5 characters per cm. and the compressed format 6 characters per cm.

Most Significant Nibble 0 1 2 3 4 5 6 7 0 0 @ P ` P

1 ! 1 A Q A Q

L 2 ” 2 B R B R

S 3 # 3 C S C S

4 $ 4 D T D T

N 5 % 5 E U E U

I 6 & 6 F V F V

b 7 ’ 7 G W G W

b 8 ( 8 H X H X

l 9 ♦ ) 9 I Y I Y

e A ↑ * : J Z J Z

B ↓ + ; K [ K

C → , < L \ L

D ← - = M ] M

E ▲ . > N ^ N

F ▼ / ? O _ O

Note - The ASCII codes for lowercase alphabet characters will be accepted by the endorser but will be printed as uppercase characters. Any other ASCII character code, either not shown in the above character set or not a valid control code, will be printed as an open square bracket “[“.

E.2 Defining the Endorsement Data Print Position

Within APTRA Edge, the print position of endorsement data for a single line endorser is fixed as described in the next section, Single Line Endorser.

With a multiple line endorser, there are two print zones, 1 and 2. You define the positioning of the printed endorsement data by setting the data dictionary entry CHECK.ENDORSEMENTPRINTZONE. There are two possible values for this entry: 0 for



zone 1 and 1 for zone 2. The Multiple Line Endorser section below describes these zones and the printing of the endorsement data in more detail.

E.3 Single Line Endorser

For single line endorsement, print is oriented along the length of the document at a fixed height from the document lower edge. As shown in the following figure, the bottom edge of the print line will be located 30mm from the bottom edge of the document.

The length of the endorse line will be dependent upon the length of the document with the only limitation being that no print should be located within 5mm of the document edges. On the shortest document, 150mm, it is possible to print up to 63 standard characters and up to 84 compressed characters. For the longest document, 225mm, the character counts become 101 and 135 respectively. Characters that would print beyond the last 5mm of the document will be truncated.

The default print start position is approximately 5mm from the reference edge of the document.

5MM

SINGLE LINE ENDORSEMENT

5MM

Reference Edge

Endorse position for single line endorsing

E.4 Multiple Line Endorser

The multiple line endorser can print 40mm long lines spaced approximately 3.5 mm apart. It is possible to print up to 18 characters per line in standard format and up to 24 characters per line in compressed format. Print lines that do not fit on a single line will wrap to the start of the next print line.

As shown in the following figure, the endorsement area starts 18mm from the bottom, to clear the MICR band, and must be at least 5mm from each of the other three document edges. Based on the minimum document height of 63mm, the endorsement will be limited to a region 40mm high.



PAYEEENDORSEMENT

INSTITUTION OFFIRST DEPOSIT

TRANSITENDORSEMENTS

DocumentTrail Edge

38.1mm76.2mm

18mm

58mm

5mm minimum

5mm

5mm

ZON

E 1

MU

LTI-LINE

END

OR

SEMEN

TA

RE

A

ZON

E 2

MU

LTI-LINE

END

OR

SEMEN

TA

RE

A

Endorsement Positions for Multiple Line Endorsements

Each endorse command will allow up to 250 printable characters. This will permit a single endorsement with more than 13 lines of standard text. The buffer size will not in anyway limit the amount of information that can be placed on the document. In fact, it will be possible to fill the entire shaded region with text by applying multiple endorsements.

E.4.1 Print Zones

As stated earlier in this section, the position of the first print line is determined by specifying either zone 1 or zone 2 in the data dictionary.

E.4.1.1 Zone 1

Printing starts at the bottom of zone 1 (38mm from the edge of the document). The endorse data is printed in a bottom up fashion. This means that the last line of endorse data will be printed first, with each subsequent line being printed closer towards the top of zone 1 (5mm from the edge of the document). Lines that would print off the end of the document will be truncated (that is, characters from the beginning of the endorse text will not be printed). A maximum of 9 lines can be printed in zone 1.

E.4.1.2 Zone 2

Printing will be performed in a conventional top down fashion starting just inside the top of the zone at 40mm from the document edge. Printing can continue to 5mm from the edge of the document. Through the use of spaces and carriage returns it is possible to place text anywhere within the shaded region shown on the document diagram.

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE INDEX


F Index

* *.xml, 4

< <CONFIGURATION_DATA>, 3 <DD_UPDATE>, 3 <XML_UPDATE>, 4, 178

A Activate/Deactivate Transactions, 12 Advertising Files, 71 Advertising Options, 35 Animation Files, 72 APTRA Promote, 35 Archive Files, 77, 83 ATM Preferences button, 40

B ButtonToKeyMap.xml, 179

C Card Reader Options, 31 Chaining

receipts, 29 tranactions, 31

Change Screen Text, 74 Change the Screen Graphics, 70 Check Endorsement Printing, 217 Configuration Items Not to Change, 85 Consumer Flow Options, 24 Coupon.xml, 181 Currency Cassette Values, 37

D Data Dictionary, 88

ALLTRANSACTIONS Group, 88 APPMANAGEMENT Group, 89 BNA Group, 89 CAMERA Group, 89 CASHDEPOSIT Group, 90 CHECK Group, 90 CHECKDEPOSITGroup, 91 commonly modified entries, 8 COMX Group, 91 CONSUMERFLOW Group, 92 CRMSERVICE Group, 139 CURRENCY Group, 139 CURRENCYEXPONENT Group, 140 CUTOVER Group, 140

DEPOSIT Group, 141 EJUPLOAD Group, 141 EVENTLOG Group, 141 FASTCASH Group, 142 GLOBAL Group, 143 JOURNAL Group, 143 MACHINE Group, 144 NDCBS Group, 144 NDCPROXY Group, 144 NDCPROXYCUSTOMIZATION Group, 145 RCPT_CONFIG Group, 147 Sample, 168 SESSIONFLOW Group, 147 STARTOFDAY Group, 147 STATEMENT Group, 158 SUPERVISOR Group, 158 SUPGENERICACTIVITY Group, 165 SUPJRN Group, 164 SUPSETTLEMENT Group, 165 TOTALS Group, 165 TRACE Group, 166 update, 3 VDM Group, 167 WITHDRAWAL Group, 167

data dictionary file location, 88 dd update

account selection, 17 advertising options, 35 APTRA promote, 35 card reader option, 31 cassette values, 37 command format, 3 consumer flow, 24 Enhanced Deposits, 44 envelope dispense option, 30 fast cash, 22 fee values, 38 FIT value, 25 language menus, 32 language option, 32 personalization, 39 receipt option, 29 stamp options, 27 surcharge options, 26 transaction set, 12 voice guidance option, 34

dd.dat, 3 Defining the Endorsement Data Print Position, 217 Deposit Disclaimers, 53

E EJ Content, 78 EJ Cutover and Backup, 77 EJ File Configuration, 80 Electronic Journal, 77 Enhanced Deposit, 44 Envelope Dispense Option, 30

NCR APTRA EDGE 2.03 REMOTE CONFIGURATION GUIDE INDEX


F FAST CASH Settings, 22 Fee Values, 38 Forced Account Balance Transaction, 54

G GIS and OOS requirement, 3, 92

I Introduction, 1

J Journal

electronic, 77 paper, 53

Journal.xml, 183

L Language button lables, 33 Language Files, 197 Language menus, 32 Language Option, 32

M Multiple Line Endorser, 218

O OOS and GIS requirement, 3, 92

P Paper Journal, 53 Personalization, 39 Personalization Transaction Main Menu Button, 40 Print Zones, 219

R receipt chaining, 29 Receipt option, 29 Receipt.xml, 188

S Sample Updates, 5 Screen Appearance, 71 Screen Graphics, 70 Screen/Keyboard Data Load Message

description, 3 format, 86

Single Line Endorser, 218 Software Distribution

advertising files, 71 animation files, 72 change screen graphics, 70 description, 70 screen appearance, 71 screen text, 74 stylesheets, 75

SoundXXX.xml, 192 Stamp Options, 27 Stylesheets, 75 Sub-Menus, 16 Surcharge Options, 26 SWDUpdate, 70

T TextENG.js File, 197 TextENG.js updates

Language button lables, 33 Unique banners and text, 21

Touch Screen, 154 Transaction Account Selections, 17 Transaction Flow Based on FIT Value, 25 Transaction Set, 12

U Unique Instruction Text, 21 Unique Main Menu Banners, 21

V Voice guidance option, 34

X xml file update

command, 4 sample, 6

xml files formats, 178

B001-0000-0114 Jun. 2007