93577744-Manual-de-Usuario-Procash-NDC-v-1-3

ProCash/NDC

V1.3/00

ProConsult/NDC

V1.1/00

User Guide

Edition October 2004

Copyright and Trademarks Copyright © Wincor Nixdorf GmbH & Co. KG 2004. All rights, including rights of translation by printing, copying or similar methods, even of parts, are reserved. All rights, including rights created by patent grants or registration of a utility model or design, are reserved. Delivery subject to availability; right of technical modifications reserved. All names of hardware and software products mentioned in this manual are trade names and/or trademarks of their respective manufacturers. All hardware and software names used are trademarks of their respective manufacturers. Reliant® is a registered trademark of Pyramid Technology Corporation. SINIX is the UNIX System derivative of Wincor Nixdorf GmbH & Co. KG. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Base: OSF/Motif™, Copyright © Open Software Foundation, Inc. X Window System™, Copyright © Massachusetts Institute of Technology. OSF/Motif is a trademark of Open Software Foundation, Inc. X Window System is a registered trademark of Massachusetts Institute of Technology. MS-DOS® and Windows® are registered trademarks of Microsoft Corporation in the United States and other countries.

Introduction

Software Structure

System Setup

Modes of operation

Configuration Data

Security Features

Messages

Printers

Additional useful Information

Abbreviations

Figures

Tables

Related publications

Pfad: E:\FRAM EMAK\NDC_DDC.NT\USER-NDC\User1TOC.fm © Siemens Nixdorf Informationssysteme AG 1995

Contents

Contents Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 What’s new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wincor Nixdorf Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Function Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Vendor capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Products of ProCash/NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Products of ProConsult/NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15 15 15 16 17 18 19 20 21

Software Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Link Libraries (DLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter / Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatible Customization Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Screen Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Font Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23 23 26 26 27 28 29 30 31 31

System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power-up mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting power-up mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Out-of-service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offline mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspend mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service and Operating(SOP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

October 2004

41 42 42 42 43 44 44 45

Contents Automatic return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rear Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start Rear Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customize Rear Balancing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . Dispense Below Zero . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46 47 47 47 48 49

Miscellaneous Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 ADRS operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Steps processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Card Read State (A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 PIN Entry State (B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Customer Selectable PIN State (b) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Extension to state (b) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Envelope Dispense (C) State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Pre-Set Operation Code Buffer State (D) . . . . . . . . . . . . . . . . . . . . . . . . 72 – Clear mask (entry 3) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 – A, B, C, D preset masks (entries 4-7) example . . . . . . . . . . . . . . . . . 75 Extension to State (D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Four FDK Selection Function State (E) . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Amount Entry State (F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Amount Check State (G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Information Entry State (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Transaction Request State (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Extension to state (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Close State (J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 FIT Switch State (K) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Card Write State (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Enhanced PIN Entry State (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Enhanced Amount Entry State (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Extension to State (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Language Code Switch State (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Extension to State (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Card Read - PIN Entry Initiation State (T) . . . . . . . . . . . . . . . . . . . . . . . 116 Extension to State (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Language Select From Card State (V) . . . . . . . . . . . . . . . . . . . . . . . . . 120

October 2004

Pfad: E:\FRAM EMAK\NDC_DDC.NT\USER-NDC\User1TOC.fm © Siemens Nixdorf Informationssysteme AG 1995

Contents FDK Switch State (W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDK Information Entry State (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to State (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eight FDK Selection State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Language Extension to State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . Audio Control State (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Fitness State (‘h’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to State (‘h’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Smart FIT Check State (‘k’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Skip State step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screen Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Graphics as Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Screen graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Display resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying MacroMedia Flash executables . . . . . . . . . . . . . . . . . . . . . Displaying Video files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Auto Voice Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Audible Echo on Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reserved Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Unit Number (LUNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local download feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure local download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

123 126 129 132 135 136 138 142 145 148 152 153 153 158 158 158 159 159 160 160 161 162 165 166 166 166 167 173 173

Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN and PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal Identification Number (PIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Variable length PIN Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Offset Number (DES verification) . . . . . . . . . . . . . . . . . . . . . . . . . PIN Verification Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

175 175 176 177 177 178 178 179 180

October 2004

Contents Local PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – ANSI PIN/PAN Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Diebold PIN Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ID Card and FIT Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ID Card Data Tracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT (Financial Institution Table) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Library Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Card, Multi Institution Capability . . . . . . . . . . . . . . . . . . . . . . . . . . Alternate Transaction Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Data Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Institution Index (PIDDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Institution Identification (PFIID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Switch Index (PSTDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum PIN Entry Digits (PMXPN) . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Check Length (PCKLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Pad Character (PINPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAN Index (PANDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAN Length (PANLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAN Pad Character (PANPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Retry Count Index (PRCNT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offset Number Index (POFDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Decimalization Table (PDCTB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encrypted PIN Key (PEKEY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Track Locator (PINDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language Code Index (PLNDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Authentication (MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAC flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Terminal Number (Machine Number) . . . . . . . . . . . . . . . . . . . MAC data field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time variant number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical Message Authentication Procedure . . . . . . . . . . . . . . . . . . . . . MACing for State and FIT Table Load commands . . . . . . . . . . . . . . . . . Triple DES operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMV capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Key Loading (RKL) capability . . . . . . . . . . . . . . . . . . . . . . . . . . . .

October 2004

181 181 182 183 184 185 186 186 187 188 188 188 190 191 191 191 192 194 195 195 196 196 197 197 197 198 198 199 199 200 201 201 201 202 203 203 203 204

Pfad: E:\FRAM EMAK\NDC_DDC.NT\USER-NDC\User1TOC.fm © Siemens Nixdorf Informationssysteme AG 1995

Contents Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages from Terminal to Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solicited Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsolicited Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network to Terminal messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Reply command (message ID ‘4’) . . . . . . . . . . . . . . . . . . . Terminal Command message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State Tables Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screen Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Parameters Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Configuration Parameters Load . . . . . . . . . . . . . . . . . . . . . Interactive Transaction Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dispenser Currency Mapping Table Load . . . . . . . . . . . . . . . . . . . . . . Configuration ID Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date And Time Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Authentication Field Selection Load . . . . . . . . . . . . . . . . . . . Specific Command Reject Conditions . . . . . . . . . . . . . . . . . . . . . . . . . Terminal operations in Transaction Replies . . . . . . . . . . . . . . . . . . . . . . . . Print Immediate (‘4’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Next State and Print (‘5’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Night Safe Deposit and Print (‘6’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deposit and Print (‘1’ or ‘7’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dispense, Deliver and Print (‘2’ or ‘8’) . . . . . . . . . . . . . . . . . . . . . . . . . Display and Print (‘3’ or ‘9’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eject Card, Dispense and Print (‘A’) (Card before Cash) . . . . . . . . . . . Eject Card, Dispense and Print (‘F’) (Parallel CBC) . . . . . . . . . . . . . . . Parallel Eject/Dispense and Print (Fast Cash) (‘B’ or ‘C’) . . . . . . . . . . . Print Data and Stay in Present State (‘P’) . . . . . . . . . . . . . . . . . . . . . . . Print Statement and Set Next State (‘Q’) . . . . . . . . . . . . . . . . . . . . . . . Electronic Journal Upload (EJU) commands . . . . . . . . . . . . . . . . . . . . . . . Send Options And Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledge And Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledge And Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NDC Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solicited Status (terminal state) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . October 2004

205 205 209 218 223 225 226 235 239 242 245 249 254 258 261 264 267 269 272 275 280 287 288 288 289 289 291 291 292 293 294 294 295 295 296 299 301 303 303

Contents – Send Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Send Supply Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Send Error Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Send date/time information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Hardware Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Supplies Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Fitness Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Tamper and Sensor Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . – Software ID and Release Number . . . . . . . . . . . . . . . . . . . . . . . . . . – Local Configuration Option Digits . . . . . . . . . . . . . . . . . . . . . . . . . . Solicited Status (device fault) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsolicited Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Power Up (unsolicited) (DID ‘B’) . . . . . . . . . . . . . . . . . . . . . . . . . . . – Card Reader (sol./unsol.) (DID ‘D’) . . . . . . . . . . . . . . . . . . . . . . . . . – Dispenser (sol./unsol.) (DID ‘E’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . – Depository (sol./unsol.) (DID ‘F’) . . . . . . . . . . . . . . . . . . . . . . . . . . . – Envelope Dispenser (unsolicited) (DID ‘\’ . . . . . . . . . . . . . . . . . . . . – Receipt Printer (unsolicited) (DID ‘G’) . . . . . . . . . . . . . . . . . . . . . . . – Journal Printer (unsolicited) (DID ‘H’) . . . . . . . . . . . . . . . . . . . . . . . – Statement Printer (sol./unsol.) (DID ‘V’) . . . . . . . . . . . . . . . . . . . . . . – Vandal Guard (unsolicited) (DID ‘J’) . . . . . . . . . . . . . . . . . . . . . . . . . – EDM - Module (unsolicited) (DID ‘L’) . . . . . . . . . . . . . . . . . . . . . . . . – Door Access (unsolicited) (DID ‘N’) . . . . . . . . . . . . . . . . . . . . . . . . . – Sensor Status (unsolicited) (DID ‘P’) . . . . . . . . . . . . . . . . . . . . . . . . – Supervisor Key Messages (unsolicited) (DID ‘R’) . . . . . . . . . . . . . . Electronic Journal Upload (EJU) Message . . . . . . . . . . . . . . . . . . . . . .

304 313 316 320 321 324 325 327 328 330 331 335 337 338 342 346 348 349 351 353 356 357 361 361 363 364

Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic journal storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of journal information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing with the Windows GDI Interface . . . . . . . . . . . . . . . . . . . . . . . . . .

367 367 368 369 369 370 370

Additional Useful Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NDC Standard Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASCII to EBCDIC Code Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . Screen Design Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

371 371 376 378

October 2004

Pfad: E:\FRAM EMAK\NDC_DDC.NT\USER-NDC\User1TOC.fm © Siemens Nixdorf Informationssysteme AG 1995

Contents M-Status & M-Data Reference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . CSC-W32 Error Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cash Dispenser V1 (old series) (Class: 0007) . . . . . . . . . . . . . . . . . . . Cash Dispenser NG (Classes: 0018/AA18/001D) . . . . . . . . . . . . . . . . Cash Cheque Deposit Module (Classes: 001A/XX1A) . . . . . . . . . . . . . Encryption Decryption Module (Class: 000F) . . . . . . . . . . . . . . . . . . . . Encryption Decryption Software (Class: 0011) . . . . . . . . . . . . . . . . . . . Card Reader (Class: 0008/AA08) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deposit Module (Class: 0017/AA17) . . . . . . . . . . . . . . . . . . . . . . . . . . Vandal Guard (Class: 0015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorized Door (Class: 000E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer (Class: 0032) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND71/74/98/9A/9C/9E/TH30 (Class: 0033) . . . . . . . . . . . . . . . Printer ND75/75S/94 (Class: 0034) . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND79 (Class: 0035) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND99 (Class: 0038) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND97/TH97/TP01/NP01/TP05/NP05 (Class: 0039) . . . . . . . . . Printer TH21 (Class: 003E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Extensions (Class: 003F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Monitor ND9G (Class: 0040) . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Monitor TH21 (Class: 0041) . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer System Framework (Class: 0042) . . . . . . . . . . . . . . . . . . . . . . . Printer TP07 GDI (Class: 0044) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer TP07 (Class: 0045) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer USB/TP07 (Class: AA45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer TP06 (Class: 0048) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer USB/TP06 (Class: AA48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Error Classes (LYNX errors) . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction (Class: 6434) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cash Dispenser (Class: 643A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Module (Class: 643C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CashIn transaction (Class: 6446) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMV transaction (Class: 6459) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cheque transaction (Class: 645A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic Journal (Class: 0091) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WOSA Error Classes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WOSA Cash Dispenser (Class: 00B9) . . . . . . . . . . . . . . . . . . . . . . . . .

379 379 379 383 392 405 406 407 411 414 415 416 417 418 418 419 420 422 423 423 424 424 426 427 428 430 431 433 433 434 435 435 436 437 437 438 438

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

October 2004

Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user1.fm © Siemens Nixdorf Informationssystem e AG 1995

What’s new This section lists a summery of documentation changes and enhancements of the ProCash/NDC User Guide. Since November 2003 until October 2004: ●

New section ”Electronic Journal Upload (EJU) commands” on page 295

●

New section ”Electronic Journal Upload (EJU) Message” on page 364

●

New section ”Remote Key Loading (RKL) capability” on page 204

●

New section ”EMV capability” on page 203

●

New section ”Displaying MacroMedia Flash executables” on page 159

●

New section ”Smart FIT Check State (‘k’)” on page 148

●

Changed section ”Hardware Fitness State (‘h’)” on page 142

●

Changed section “Amount Check State (G)” on page 84

●

New section “Dispenser Currency Mapping Table Load” on page 267

Since May 2002 until November 2003: ●

New section ”Miscellaneous Operations” on page 51

●

Changed section ”Related publications” on page 453

●

New section ”M-Status & M-Data Reference Tables” on page 379

●

New section ”Triple DES operation” on page 203

●

Extended section ”Solicited Status messages” on page 218

●

Extended section ”Send Configuration Information” on page 304

●

Changed section ”Software Products of ProConsult/NDC” on page 21

●

Changed section ”Software Products of ProCash/NDC” on page 20

●

New section ”Printing with the Windows GDI Interface” on page 370

●

Changed section ”Dynamic Link Libraries (DLL)” on page 23

●

Changed section ”Directory Structure” on page 34

October 2004

13

What’s new Since October 2001 until May 2002:

14

●

New section “Enhanced Amount Entry State (R)” on page 107

●

New section “Audio Control State (i)” on page 138

●

New section “Voice Control” on page 160

●

New section “Dispense Below Zero” on page 49

●

Enhanced section “Unsolicited Device Status” on page 335

●

Enhanced section “Printer Models” on page 367

●

Changed section ”Related publications” on page 453

●

Enhanced section ”Directory Structure” on page 34

●

Enhanced section “Solicited Status (terminal state)” on page 303

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user1.fm © Siemens Nixdorf Informationssystem e AG 1995

Introduction

Preface

Introduction Preface In the past NCR and Diebold/Interbold have dominated the international market of automated teller machines (ATM). Both vendors have defined very similar protocols for the network integration of their systems. The existing MS-DOS based NDC-Emulation from Wincor Nixdorf is running in NCR network environments all around the world. New technologies and of course windows oriented platforms provided from Microsoft has forced Wincor Nixdorf to develope the NDC-Emulation running with Windows. The product ProCash/NDC and since October 2002 ProConsult/NDC from Wincor Nixdorf has been developed with all known advantages provided by Windows like Multithreading Processes, using WOSA services, open system environment through the ProTopas architecture from Wincor Nixdorf. The ability to integrate ProCash/NDC in multi vendor projects (ProCash/NDC running on NCR, Olivetti, or Diebold hardware) is another big advantage of this software architecture.

Wincor Nixdorf Solution ProCash/NDC and ProConsult/NDC have been developed using the C++ object oriented ProTopas architecture. ProTopas is a flexible development platform for self-service device applications in open system environments. Development with ProTopas means using existing Frameworks, modifying and creating new Frameworks for the specific self-service application. The application design allows customers to create easily new Frameworks of customer specific functions using ProTopas/KIT. Wincor Nixdorf provides ProCash/NDC and ProConsult/NDC with function messages of NCR terminals which are described in later sections. Any function restrictions against NCR can be recognized if it is not documented in this manual.

October 2004

15

Purpose of the Document

Introduction

Purpose of the Document This document will provide the software analyst with the necessary information on the functions which are supported by product ProCash/NDC and ProConsult/NDC. Furthermore all the information needed for the operation of the ATM, as far as it is NDC specific and not covered by other documentation (e.g. CSC-W32, Protopas or ProDevice documents). A detailed description of all the application specific parameters will be found in the ProCash/NDC ProConsult/NDC Installation manual along with information for installation and upgrading the products. NDC specific features like States, Screens, FIT, commands and messages will be described here in detail. Since the list of supported features keeps growing please always use the latest release of this documentation. We will make updated versions available as soon as practical, either by file download or as an online-documentation. Any feature exceeding the described ones may not be supported. In this case please refer to the protocol descriptions of the network (in case of project specific extensions) or to recent releases of the Programmers Reference Manuals of NCR.

16

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user1.fm © Siemens Nixdorf Informationssystem e AG 1995

Introduction

Function Overview

Function Overview ProCash/NDC and ProConsult/NDC written for Wincor Nixdorf terminals contain base functions from the original NCR Direct Connect (NDC) software provided by NCR. The functionality depends on the host Software (BASE24, ON/2, TP/2, etc.). The download of original NCR Customization Tables such as States, FIT’s, Screens and Parameters controls the terminal, thus defining the available functions. Those are typically (but not exclusively): ●

Withdrawal

(ProCash/NDC only)

●

Fast cash

(ProCash/NDC only)

●

Deposit

(ProCash/NDC only)

●

Balance inquiry

●

Transfer

●

Payment

●

PIN change

●

Rear Balancing

●

Multi language

●

Statement print

●

MACing

●

Triple DES security

●

EMV support

●

Cheque deposit

●

E-Journal Upload (EJU)

October 2004

17

Supported hardware

Introduction

Supported hardware Currently following systems and hardware components are supported: ATM’s: ● CSC4xx Rear/Frontload ● CSC400 Frontload ● ProCash-Compact ● ProCash 2000 ● CSC21xx, CSC1500 ● Cash Recycling System (CRS), 3100xe Info Terminals: ● ProPrint 200 ● ProPrint 2000 ● ProConsult, Certo Dispenser modules: ● CDM-V1, CDM-NG, CMD-V4, CDM-NG (6 cassettes) Needle printers: ● Journal: ND98D, ND98, ND71, NP06 ● Receipt: ND9E, ND71, ND9A, NP07 ● Statement: ND97, ND94, ND97 Thermal printers: ● Receipt: ND9C, ND99, ND9G, TH21, TH22, TP07 ● Journal: TH30, TP06 ● Statement: TH97/G, TP01, TH23 Card readers: ● ID14 (Sankyo Seiki), ID15 (Wincor Nixdorf), ID18 (OMRON), V2X, ID24 (DIP reader), ICM300 (manual smart card reader) Encryption modules: ● EDM module (restricted security), EPP’s V4, V4+, V5 (international) Deposit modules: ● Papalakko, Wincor Nixdorf ● Cheque Deposit Module (CCDM)

continued on next page ...

18

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user1.fm © Siemens Nixdorf Informationssystem e AG 1995

Introduction

Multi Vendor capability

Miscellaneous: ● Operator Panel (Low- or high end) ● Touch screen support ● Power Supply box ● Sound card ● USB support

Multi Vendor capability Since release 1.3/00 ProCash/NDC supports hardware platforms from other vendors as well. Follwing hardware platforms of other vendors are supported, which can be installed via standard installation procedure via ProInstall: ●

NCR cash systems

●

Diebold cash systems, (except OPTEVA)

Following vendors are running with ProCash/NDC, but they have to be installed with a special prepared installation set: ●

Fujitsu cash systems

●

Olivetti cash systems

●

Delarue cash systems

October 2004

19

Software Products of ProCash/NDC

Introduction

Software Products of ProCash/NDC In the following table is listed the basic software products that are required to setup a whole ProCash/NDC application: Table 1: Basic Software of ProCash/NDC

Name

current Release

Systems

Operating system Windows XP Professional

see Note2

Windows NT

4.00 Srv. 6

all

CSC-W32

2.0/53

all

ProCash/Topas

4.1/00

all

ProSop

3.1/13

all

WOSA/XFS-SSP (2.0)

3.1/72

all

WOSA/XFS-SSP (3.0)

4.0/31

all

WOSA/XFS-SSP/MV

3.1/71

all

PARAC-NT

3.2/02

all

ProView

3.7/01

all

ProCash/NDC

1.3/00

all

ProCash/NDC-SOP

Communication software SNA-Workstation

4.0

optional

Eicon software components

3.0

optional

For detailed information about function and configuration of each product refer to ProCash/NDC ProConsult/NDC Installation manual NOTE 1: ProCash/NDC is running on on PC based systems. The Windows NT system needs minimum 128 MB RAM at runtime and one hard disk with the minimum capacity of 500 MB to store the whole software. For Windows XP 256 MB RAM and hard disk space of 4 GB is required. Pure Windows XP needs 1,8 GB hard disk space. NOTE 2: Windows XP is released on Embedded PC’s only.

20

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user1.fm © Siemens Nixdorf Informationssystem e AG 1995

Introduction

Software Products of ProConsult/NDC

Software Products of ProConsult/NDC In the following table is listed the basic software products that are required to setup a whole ProConsult/NDC application: Table 2: Basic Software of ProConsult/NDC

Name

current Release

Systems

Operating systems Windows XP Professional

see Note2

Windows NT

4.00 Srv. 6

all

CSC-W32

2.0/53

all

ProCash/Topas

4.1/00

all

ProSop

3.1/13

all

WOSA/XFS-SSP (2.0)

3.1/72

all

WOSA/XFS-SSP (3.0)

4.0/31

all

WOSA/XFS-SSP/MV

3.1/71

all

PARAC-NT

3.2/02

all

ProView

3.7/01

all

ProConsult/NDC

1.1/00

all

ProConsult/NDC-SOP

Communication software SNA-Workstation

4.0

optional

Eicon software components

3.0

optional

For detailed information about function and configuration of each product refer to ProCash/NDC ProConsult/NDC Installation manual NOTE 1: ProConsult/NDC is running on on PC based systems. The Windows NT system needs minimum 128 MB RAM at runtime and one hard disk with the minimum capacity of 500 MB to store the whole software. For Windows XP 256 MB RAM and hard disk space of 4 GB is required. Pure Windows XP needs 1,8 GB hard disk space. NOTE 2: Windows XP is released on Embedded PC’s only.

October 2004

21

Software Products of ProConsult/NDC

22

October 2004

Introduction

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User2.fm © Siemens Nixdorf Informationssysteme AG 1995

Software Structure Dynamic Link Libraries (DLL) The following described Dynamic Link libraries are the part of ProCash/NDC or ProConsult/NDC, which have to be installed via ProInstall on the harddisk of the ATM. These modules control the functions of the application. The following software modules build the application part NDC on the ATM: ●

Transaction Framework (dcsttfw.dll) The Transaction Framework maps the downloaded NDC states to the belonging step function defined in the LYNXPAR section of the registry.

●

Cash Dispenser Framework (dccdmfw.dll) (not ProConsult/NDC) The Cash Dispenser Framework controls the dispensing requests from the consumer. It maps the physical cassettes to logical positions which have to match with the positions configured at the host side. It handles the cassette counters and syncronizes them with WOSA.

●

Device Status Framework (dcdevsta.dll) The Device Status Framework collects the status of the devices from the different device frameworks. It also offers the supplies of the devices. The actual status will be passed to the Message Control Framework whenever it asks for the device status.

●

Message Control Framework (dcmsgcfw.dll) The Message Control Framework handles the NDC messages sent from the host to the terminal and builds up the messages which have to be sent from the terminal to the host. It asks the Device Status Framework for the current status of the device to fill the severity and supply status fields of solicited and unsolicited messages to be sent to the host.

●

SOP User Exit Framework for ProSop (dcsuefw.dll) The ProSop User Exit Framework contains NCR service functions like “Display supply status, “Clear card capture counter”, “Rear balancing”, etc..

October 2004

23

Dynamic Link Libraries (DLL) ●

Software Structure

NDC Printer Framework (ndcprtfw.dll) The NDC Printer Framework analyzes the printer data from the host and converts it to printable printer buffers. First it reads the base settings from the registry and set it as default (sets lpi and cpi size, activates the printer font, reads the char convertion table, etc.) after that it fills the printer data with the specific macros depending on which NDC escape sequences are in the printer data from the host. The formatted print buffer will be passed to the base printer framework of ProTopas.

●

NDC Dialog Framework (ndcdiafw.dll) The NDC Dialog Framework handles the consumer FDK, PIN inputs and controls the screen flow.

●

Application Framework (dcapplfw.dll) The Application Framework has the control above the other Frameworks. It starts the Protocol Framework, Communication Framework, Step Table Framework and handles the synchronisation with the different Frameworks.

●

Converter Framework (dcconvfw.dll) The Converter Framework handles the Customisation Image (CI) downloaded from the host. It stores the host configuration (States, Screens, Timers, FIT table , Configuration parameters and Configuration ID) in the LYNXCI path of the Registry.

●

Protocol Framework (dcprotfw.dll) The Protocol Framework send to or receives messages from the Communication Framework.

●

Security Overlay Framework (dcsecure.dll) The Security Framework performes local PIN verification with the corresponded FIT data. Performs calls to security functions of Protopas basic framework.

●

SOP Service Framework (dcServic.dll) The SOP service framework contains Dialog and synchronisation functions of ProCash/NDC-SOP ProConsult/NDC-SOP.

●

SOP Dialog Framework (dcSopDia.dll) The SOP dialog framework controls the dialog screens on the facia screen or on the operator panel of ProCash/NDC-SOP or ProConsult/NDC-SOP.

24

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User2.fm © Siemens Nixdorf Informationssysteme AG 1995

Software Structure ●

Dynamic Link Libraries (DLL)

GDI Printer Overlay Framework (dcPrtGdi.dll) The GDI Printer Overlay Framework converts PrintRaw data to GDI print data, which are passed to a Windows printer (e.g. ND9G). This Overlay framework has to be configured in between the ProTopas printer framework and the NDC Printer Framework in the Repository Manager. Refer to GDI Printer Overlay Framework - User Guide for detailed descriptions about GDI printing with ProCash/NDC and ProConsult/NDC.

●

EMV Transaction Overlay Framework (dcEmvTa.dll) The EMV Transaction Overlay Framework is needed to handle transactions with EMV data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions.

●

EMV Message Control Overlay Framework (dcEmvMc.dll) The EMV Message Control Overlay Framework is needed to append messages with EMV data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions.

●

EMV Converter Overlay Framework (dcEmvCv.dll) The EMV Converter Overlay Framework is needed to handle EMV download data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions.

October 2004

25

Parameter / Data Files

Software Structure

Parameter / Data Files Types of Parameters Every terminal needs many different parameters to operate as expected. The most complex set of parameters is called "Customization" and contains the dialogs and the sequence of functional steps (e.g. card read - PIN Entry Function selection ...) which the system will perform. NCR supports the central customization by files which will be distributed to all connected ATM’s. Our ProCash/NDC and ProConsult/NDC emulation fully supports this Customization Download. The parameters will be stored into the Windows registry. Changes to those parameters may be overwritten any time by a new download. Thus permanent changes must be made to the customization files on the Host, not on the ATM. Furthermore each ATM will have a number of extended parameters which are specific to its type or to the particular machine. The Wincor Nixdorf solution, being an emulation, needs several parameters to cover the differences to the original systems and for enhanced services. Existing parameters can be edited in text files (*.ppf or *.ina type). The Registry update with the changed values will be done via PARAC-NT after the next “RUN” process and with CCRCCONV.EXE. Details will be given in the ProCash/NDC ProConsult/NDC Installation manual.

26

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User2.fm © Siemens Nixdorf Informationssysteme AG 1995

Software Structure

Parameter / Data Files

Compatible Customization Data All customization data are stored in the Windows registry location: HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ LYNXCI

●

Screen Data (LYNXCI\SCREEN\XXX [1]) [1] ’XXX’ represents the downloaded screen number

are the predefined display screens provided by the host. ●

State Table (LYNXCI\STATE) is used to define and control the logic flow of the for client transactions.

●

Financial Institution Table (LYNXCI\FIT) consists of an entry for every institution or group of institutions offering services on the ATM. Client card data are compared to data in this file to determine whether the card holder can receive services.

●

Customization Parameters (LYNXCI\PARAMETER) contain some terminal specific settings and specific definitions of the message protocol.

●

Timers (LYNXCI\TIMER) contain downloaded timer values valid for all ATM’s in the network.

●

Receipt Templates (LYNXCI\SCREEN\R00; LYNXCI\SCREEN\R01) As part of the screens download the host can send receipt header data (R00) and predefined receipt data (R01) (data that are mixed together with the host printer data of the transaction reply). Those screens are stored in sub section “..\LYNXCI\R00” and “..\LYNXCI\R01”.

●

EMV Parameters (LYNXCI\EMV) This section contain specific EMV parameters.

October 2004

27

Parameter / Data Files

Software Structure

Extended Configuration Data All non downloaded configuration data are stored in the following location of the Windows registry: HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ LYNXPAR ●

Application Parameters (LYNXPAR\APPLICATION ) This section contain parameters which are not assigned to a specific hardware device. These are global settings of NDC and can be parameters for the protocol or timers etc..

●

Cash Dispenser Parameters ( LYNXPAR\CASH_DISPENSER) This section contain parameters related to the cash dispenser like cassettes type configuration, dispense algorithm, dispenser status. (This section is missing in the non cash product ProConsult/NDC.)

●

Card Reader Parameters (LYNXPAR\CARD_READER ) This section contain parameters related to the card reader like track configuration and transport handling of the ID card.

●

Deposit Parameters (LYNXPAR\DEPOSIT) This section contain parameters related to the deposit module.

●

Printer Parameters (LYNXPAR\PRINTER) This section contain parameters related to the journal, receipt and document printers.

●

GDI Printer Parameters ( LYNXPAR\GDI_RINTER) This section contain parameters for printers using GDI.

●

Operator Screen Parameters ( LYNXPAR\OPERATOR_SCREENS) This section contain the operator screen template parameters that are used to display or print the supply counters within the user exit menu “Individual Functions” of ProSop.

28

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User2.fm © Siemens Nixdorf Informationssysteme AG 1995

Software Structure ●

Parameter / Data Files

Function ID mapping (LYNXPAR\FUNC_ID_MAP) This section contain the assignment to the ProCash/NDC or ProConsult/NDC step functions and function ID’s that are send in transaction replies.

●

State mapping (LYNXPAR\STATE_MAP ) This section contain the assignment to the ProCash/NDC or ProConsult/NDC step functions and state ID’s that are send in the states table download from host.

Global Screen Configuration The global non downloaded screen configuration contains default display settings and path for graphic files (*.PCX), Bitmaps (*.BMP) and Videos (*.AVI; *.MPG) etc.. Furthermore for each screen can be configured special display settings or idle rotations which are independend from the host download. Those parameters are stored in the following location of the Windows registry: HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ LYNXCI\SCREEN LYNXCI\SCREEN\XXX

Details will be given in the ProCash/NDC ProConsult/NDC Installation manual.

October 2004

29

Parameter / Data Files

Software Structure

Error Mapping Configuration All device errors and mapping parameters are devided in error classes. The “CLASS” section is devided in the CSC-W32 device classes inclusive the ProCash/NDC classes. Each class contains sub sections of error codes which contain the CSC-W32 error and the error mapping definitions for the message protocol. They are stored in the following location of the Windows registry: HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ CCERRMAP\CLASS

Details will be given in the ProCash/NDC ProConsult/NDC Installation manual

30

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User2.fm © Siemens Nixdorf Informationssysteme AG 1995

Software Structure

Font Files

Font Files ProCash/NDC uses the Windows font format (*.FON) for displaying text and graphic characters for downloaded NDC screens. The fonts can be created and modified via utility “FONTEDIT.EXE”. During the installation the default base set of ProCash/NDC or ProConsult/NDC fonts will be installed and activated automatically like standard Windows fonts.

The following section contains a short list of NDC Standard Fonts that are installed during the installation of ProCash/NDC or ProConsult/NDC:

Standard Fonts Table 3: Standard fonts table Font name

File name

Designation

640x480 (W * H) [1]

800x600 (W * H) [1]

1024x768 (W * H) [1]

1

NDC-SA1.FON

Single Size Alpha 1

20x30

25x37

32x48

2

NDC-SA2.FON

Single Size Alpha 2

20x30

25x37

32x48

>

NDC-DA1.FON

Double Size Alpha 1

40x30

50x37

64x48

?

NDC-DA2.FON

Double Size Alpha 2

40x30

50x37

64x48

3

NDC-GA1.FON

Standard Graphic 1

20x30

25x37

32x48

4

NDC-GA2.FON

Standard Graphic 2

20x30

25x37

32x48

5

NDC-GA3.FON

Standard Graphic 3

20x30

25x37

32x48

9

NDC-SARA.FON

Single Size Arabic

20x21

25x26

32x33

B

NDC-DARA.FON

Double Size Arabic

40x42

50x52

64x64

[1] -

Depending on the display resolution you have to select the belonging font with the correct width and height (W * H). During the installation the standard fonts are automatically installed with the display resolution currently set in the control panel of Windows.

October 2004

31

Font Files

32

Software Structure

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User3.fm © Siemens Nixdorf Informationssysteme AG 1995

System Setup Software Installation The whole software will be installed via the ProInstall Product CD, Customizing and Update diskettes. The installation process will be started via program ’SETUP.EXE’ located in the root of the ProInstall CD. During the installation you will guided via menu dialogs through the installation processes. You can set also specific parameters via a parameter configuration dialog. All details about product installation will be provided in the ProCash/NDC ProConsult/NDC Installation manual.

October 2004

33

Directory Structure

System Setup

Directory Structure ProCash/NDC or ProConsult/NDC is only one part of a bundle of software packages running on an Windows based ATM. A lot of directories and a large number of Dynamic Link Libraries (DLL’s) makes it difficult to assign configuration files and DLL’s to the right software sub product. Protopas based DLL’s and ProCash/NDC or ProConsult/NDC specific DLL’s are stored together in directory C:\PROTOPAS\BIN. The following table gives short overview about the modules and their directories: Table 4: Software structure

File Structure

Description

\CSCW32

modules of CSC-W32 operating system

\WOSASSP

modules of ProDevice (WOSA)

\PROSOP

modules of ProSop

\PROTOPAS fwstrt.bat

Starts ProCash/NDC or ProConsult/NDC

fwkill.bat

Stops ProCash/NDC or ProConsult/NDC

ccprot.log

Log file of Host and ATM messages

\PROTOPAS\BIN dcApplFW.dll

Application Framework

dcSttFW.dll

Transaction Framework

dcMsgcFW.dll

Message Control Framework

dcConvFW.dll

Converter Framework

dcCdmFW.dll

Cash Dispenser Framework

dcSueFW.dll

Sop User Exit Framework

dcSecure.dll

Security Overlay Framework

3DesEppF.dll

Triple DES EPP Overlay Framework

dcDevSta.dll

Device Status Framework

dcServic.dll

ProCash/NDC-SOP, ProConsult/NDC-SOP Service Framework

dcSopDia.dll

ProCash/NDC-SOP, ProConsult/NDC-SOP Dialog Framework

ndcDiaFW.dll

NDC Dialog Framework

ndcPrtFW.dll

NDC Printer Framework

34

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User3.fm © Siemens Nixdorf Informationssysteme AG 1995

System Setup

File Structure

Directory Structure

Description

dcPrtGdi.dll

GDI Printer Overlay Framework

dcEmvTa.dll

EMV Transaction Overlay Framework

dcEmvCv.dll

EMV Converter Overlay Framework

dcEmvMc.dll

EMV Message Control Overlay Framework

dcTcp2h.dll

TcpIP converter for 2 bytes binary headers (header length excluded)

dcTcp2hi.dll

TcpIP converter for 2 bytes binary headers (header length included)

dcTcp4a.dll

TcpIP converter for 4 bytes ASCII headers (header length excluded)

dcTcp4ai.dll

TcpIP converter for 4 bytes ASCII headers (header length included)

dcTcp3a.dll

TcpIP converter for 3 bytes ASCII headers (header length excluded)

dcTcpSTX.dll

TcpIP converter for STX and ETX message length calculation

dcSimCom.dll

Host Simulator Framework

ccrcconv.exe

Updates the Windows registry with contents of *.RCK files

\PROTOPAS\CONF Kconf.exe

Converts *.INA files to *.RCK format

Kconf.txt

Describes functionality of Kconf.exe

conv.bat

Update job for *.INA files to update existing and store new parameters in the Registry

conv-all.ok (conv-all.bat)

Batch file which is called once immediately after installation to store additional parameters in the registry (will be renamed from *.BAT to *.OK after the call).

prtmakro.bat

Batch job to store additional parameters for the journal and receipt printer to enable ’INIT’ sequences via makros.

prtmakro.ina

Parameter source file of printer parameters used by Kconf.exe

prosop.bat

Batch job to set SOP User Exit and Trace menu items for ProSop (Single DES).

October 2004

35

Directory Structure

System Setup

File Structure

Description

prosop.ina

Parameter source file of SOP User Exit and Trace (Single DES) used by Kconf.exe

sop3des.bat

Batch job to set SOP User Exit and Trace menu items for ProSop (Triple DES).

sop3des.ina

Parameter source file of SOP User Exit and Trace (Triple DES) used by Kconf.exe

gdi_prt.bat

Batch job to set GDI printer parameters.

gdi_prt.ina

Parameter source file of GDI printer parameters used by Kconf.exe

logon.bat

Batch job to set parameters in the Registry to activate automatic logon.

logon.ina

Parameter source file for automatic logon parameters

autostrt.bat

Batch job to set one parameter which activates an automatic call of ’C:\STARTUP.BAT’ after restart.

autostrt.ina

Parameter source file for the automatic ’startup.bat’ call.

ccerrmap.ina

Parameter source file of all application and CSC-W32 error codes and mapping definitions which is used during ’conv-all.bat’ process is running.

lynxsop.ina

Parameter source file of Rear Balancing step table parameters which is used during ’conv-all.bat’ process is running.

ccvtable.fil (asc, ebc)

Line convertion tables: EBCDIC - ASCII and ASCII - ASCII (default is ASCII - ASCII)

cfgmanag.lnk

Link of the Configuration Manager for the start bar of Windows.

\PROTOPAS\CONF\ TUNING.XP

Contains configuration files needed to optimize Windows XP

tune_xp.bat

Batch routine that installs the *.INF files and contents of *.REG files.

tune_xp.reg

Windows XP general optimations

explorer.inf

Windows XP Explorer optimations

36

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User3.fm © Siemens Nixdorf Informationssysteme AG 1995

System Setup

Directory Structure

File Structure

Description

perform.inf

Windows XP settings for enhanced performance

bootload.inf

Windows XP reduced boot delay time

autorun.inf

Windows XP autorun settings

nowelc.inf

Windows XP switch off welcome screen

\PROTOPAS\WORK cccmos.bin

CMOS file - stores transaction oriented counters and device statuses (e.g. Last Transaction Status information)

\PROTOPAS\BITMAPS \PROTOPAS\BITMAPS\640x480 \PROTOPAS\BITMAPS\800x600 \PROTOPAS\BITMAPS\1024x768

Resolution depended sub directories where the default graphics are stored during the installation.

*.PCX, *.BMP, *.ICN, *.JPG

Graphic and Bitmap files which are controlled via screen escape sequences or as a local definition for Background pictures or to replace downloaded NDC text screens.

dctmpoos.bmp

Bitmap which is displayed during the system shutdown initiated by the restart handler in a fatal error condition.

dcoos.bmp

Bitmap which is permanently displayed if the maximum system reboots has been initiated by the restart handler.

*.AVI, *.MPG, *.MPEG

Video animation file which can be configured instead of a ’normal’ graphic in the registry section “..\LYNXCI\SCREEN”.

\PROTOPAS\FONTS \PROTOPAS\FONTS\640x480 \PROTOPAS\FONTS\800x600 \PROTOPAS\FONTS\1024x768

Resolution depended sub directories where the default fonts are stored during the installation.

\PROTOPAS\FONTS\ GDI_PRT

Contains Windows fonts that are used if GDI printing is enabled (e.g. ND9G, TP07).

\PROTOPAS\TOOLS HostSim.exe

Dialog oriented host simulator simulates host to terminal messages.

October 2004

37

Directory Structure

System Setup

File Structure

Description

MfcDlg.exe

Dialog window where you can enter specific screens to display during runtime.

MfcVar.exe

Displays variables (e.g. Opcodes) during the transaction flow.

protlog.exe

Message analyzer of log file ’CCPROT.LOG’

reboot.exe

Initiates a system shutdown or relogon

write-id.exe

Utility to write track 1,2 or/and 3 data on ID cards via ID Card Unit.

write-id.cmd

Batch file which can be modified for calling write-id.exe to write tracks on ID cards.

fontedit.exe

Modifies and view Windows font contents

asc2fon.exe

Converts ASCII font files to Windows fonts

fon2asc.exe

Extracts Windows fonts to ASCII text files

prt-dof.exe

Sends control sequences (in *.DOF format) to the receipt or journal printer.

asc2dof.exe

Converts ASCII printer fonts to *.DOF format.

dof2asc.exe

Extracts DOF files to ASCII printer font files

asc-nd99.exe

Converts ASCII printer font files to *.SWF format for ND99 printer.

nd99-asc.exe

Extracts binary *.SWF font files of ND99 to ASCII matrix font files.

ldnd99.exe

Font and Logo loader for ND99

nd99logo.exe

Extracts ND99 logo files to ASCII matrix file

asc2logo.exe

Converts ASCII logo files to binary logo files for ND99.

nd9e-dof.exe

Converts an ASCII logo file to DOF format for ND9E printer.

pcx2asc.exe

Extracts 2 or 16 color PCX graphics to ASCII matrix text file.

cfgmanag.exe

Configuration Manager. Easy access to analyzing tools and configuration data via pull down menus.

38

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User3.fm © Siemens Nixdorf Informationssysteme AG 1995

System Setup

Directory Structure

File Structure

Description

cfgmanag.mnu

Menu definition file for the Configuration Manager that allows menu configuration. (Will not be installed, but can be ordered from WCN support).

cfgmanag.hlp

Help text file for the Configuration Manager.

ina2def.exe

Converts INA files to PARAC definition RC source files.

compregf.exe

Compares an extracted registry text file with the contents of the Windows registry.

cpyntfnt.exe

Installes and registers Windows font files.

asc2pcc.exe

Converts ASCII files to PCC/PCX files.

icn2asc.exe

Extracts ICN icon files to ASCII matrix files.

asc2icn.exe

Converts ASCII files to ICN files.

sethwppf.exe

Sets hardware depended menu for Status Overview in ProSop and deconfigures paper journal of no journal printer is installed. (used during installation).

prt-raw.exe

Test utility that can print a text file with ASCII printer data and macros via printer interface of CSC-W32.

printraw.exe

Test utility that prints raw data via ProTopas API function PrintRaw() from file C:\PROTOPAS\RAWDATA.TXT, or prints the contents of registry parameter MSGxxx via function Print(xxx).

dcsopmgr.exe

ProCash/NDC-SOP, ProConsult/NDC-SOP User Manager.

initepp.exe

Deletes keys from EPP and gives detailed information about the EPP hardware.

dof-rj03.exe

Converts ASCII printer fonts to *.DOF format for NP06/TP06 and NP07/TP07.

rj03-dof.exe

Converts hex *.DOF files of NP06/TP06 and NP07/TP07 font definitions to ASCII files.

confchck.exe

Configuration Utility. It is called during installation and by the Config. Manager

October 2004

39

Directory Structure

System Setup

File Structure

Description

addonchk.exe

Installation Utility that is called during installation only.

cfgmedit.exe

Editor with restricted file access that can be used via the Configuration Manager.

40

October 2004

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user4.fm © Siemens Nixdorf Informationssystem e AG 1995

Modes of Operation At any time, Wincor Nixdorf terminals operates in one of the following six modes: ●

power-up mode

●

out-of-service mode

●

in-service mode

●

offline mode

●

Service and Operating (supervisor mode)

●

suspend mode

The terminal changes from one mode to another when it encounters a specific event, like the SOP switch is pressed or the terminal discovers that it is no longer communicating with the network. Figure 1 shows how the terminal normally exits one mode and enters another. If the terminal loses power or is reset, the terminal abnormally exits from the mode it was in, when the reset or power failure occurred. Figure 1: Terminal operation

POWER-UP POWER-UP

OFFLINE OFFLINE

SUPERVISOR SUPERVISOR MODE MODE SUSPEND SUSPEND MODE MODE

OUT OUT OF OF SERVICE SERVICE

IN IN SERVICE SERVICE

The following paragraphs describe how the terminal enters and exits each of the modes and, if applicable, how the terminal functions when it is in that mode.

U25604-J-Z745-1-7600

October 2004

41

Power-up mode

Modes of Operation

Power-up mode The terminal enters power-up mode when the terminal is switched on. During power-up mode, the restart handler starts the WOSA services, the Protopas environment and at least the ProCash/NDC, ProConsult/NDC frameworks. After all terminal devices are opened the communication framework is waiting for line activity.

Exiting power-up mode The terminal exits to offline or out-of-service mode when it leaves power-up mode. If line connection is established, the communication framework sends the power up message as configured to the host.

Out-of-service mode The terminal may enter out-of-service mode from any one of the following modes: ●

power-up mode

●

offline mode

●

in-service mode (if the terminal receives an out-of-service command from the network)

●

supervisor mode

The terminal accepts and stores configuration data while it is in out-of-service mode. During this time, the terminal can also receive and execute print immediates, startup and shutdown commands from the network. Depending on what mode the terminal was in before going out-of-service, the terminal may perform other functions.

42

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user4.fm © Siemens Nixdorf Informationssystem e AG 1995

Modes of Operation

In-service mode

In-service mode The terminal enters in-service mode from any of the following modes: ●

out-of-service mode (if the terminal receives a startup command from the network)

●

supervisor mode (if the return to previous mode feature is enabled )

●

offline mode (if communication with the network is restored)

While in-service, the terminal uses the configuration data to make transaction sequence decisions. The terminal exits in-service mode under the following conditions: ●

The terminal receives a shutdown command from the network; the terminal exits to out-of-service mode after finishing any customer transactions in progress.

●

The terminal looses communication with the network; the terminal exits to offline mode.

●

The terminal exits to supervisor mode when there is an SOP entry on the operator panel, the SOP switch is pressed, or when the safe door is open.

●

An abnormal exit occurs.

Except when an abnormal exit occurs, the in-service mode can only be exited from State 000.

U25604-J-Z745-1-7600

October 2004

43

Offline mode

Modes of Operation

Offline mode The terminal may enter offline mode from any of the following modes: ●

in-service mode

●

out-of-service mode

●

power-up mode

●

supervisor mode

Offline mode is entered from the in-service mode if communication is lost between the network and the terminal. While in this mode, the terminal operates as follows: ●

The terminal displays the user-defined offline screen (screen C01) on the screen.

●

The terminal enters an idle loop until network communication is restored.

The terminal exits this mode under the following conditions: ●

communication with the network is restored

●

the terminal enters supervisor mode

●

an abnormal exit occurs

Suspend mode The suspend mode feature must be activated in the miscellaneous parameters (see ProCash/NDC ProConsult/NDC Installation manual for details). Suspend mode is entered from the in-service mode if a tampering suspected error has occurred and the specific error of the device class in CCERRMAP is set to Severity 3. While in this mode, the terminal operates as follows: ●

The terminal displays the suspend mode screen C05 or C02 (if screen C05 not exists) on the screen.

●

Green status lights in front and on the Operator Panel will be switched off.

●

The terminal doesn’t accept customer cards.

44

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user4.fm © Siemens Nixdorf Informationssystem e AG 1995

Modes of Operation

Service and Operating(SOP)

The terminal exits this mode under the following conditions: ●

the terminal enters supervisor mode

●

the host sends an in-service or out-of-service command

●

the suspend mode timer has expired (return to previous mode)

Service and Operating(SOP) For Wincor Nixdorf terminals the operator uses the Service and Operating to replenish supplies, change passwords and change encryption keys. While in the SOP mode, the manager or operator can enable or disable devices or device options for service and maintenance. All service and operator functions are described in the manual ProCash/SOP Service & Operating User Guide. If the manager enters the SOP, the terminal sends an unsolicited status message to the network when it enters the operator mode. Refer to section ”Unsolicited Status messages” on page 223 for further information. While in SOP mode, the terminal responds to network messages as follows: ●

The terminal processes load command messages and replies with solicited status messages indicating either a ready condition or a command reject condition.

●

The terminal responds to all other Transaction Reply command messages with a solicited status message indicating a command reject condition.

●

The terminal responds to an Terminal Command message requesting configuration information with a solicited status message containing configuration information.

●

The terminal accepts Terminal Command messages requesting start-up or shutdown but does not process or reply to them until it exits the supervisor mode.

●

If the terminal receives any Terminal Command messages requesting startup or shutdown while in the SOP, then upon exiting the SOP, the terminal processes the last such message received and sends the network a solicited status message indicating a ready condition.

U25604-J-Z745-1-7600

October 2004

45

Service and Operating(SOP)

Modes of Operation

Service & Operating (operator panel or consumer display) On rearload terminals the operator uses the operator functions via the Operator Panel. On Frontload terminals the operator can enable the Service & Operating on the consumer screen if he presses the SOP button. Service and Operating provides the following features to enhance operations: ●

menu selections that are available without device synchronization, such as viewing counters while the terminal remains in service

●

simplifies diagnostics by providing easy-to-understand entry screens and reports test results in understandable phrases

●

a sequencing capability allowing the terminal to perform each command in the sequence without any operator input except an enter keystroke

●

device self tests and operator messages to be included in sequences

●

a simplified status list that compiles supply, device and fault status on one easy-to-understand report; entries are date stamped and all codes are declared in the manual System Messages of CSC-W32.

●

allows the cash position data (balancing data) to be entered into the terminal

●

help text (extensive, context-sensitive, online help)

●

the Operator Panel has status lights that indicate the terminal status

●

messages can be displayed on the Operator Panel as soon as the situation occurs (in-service, out-of-service, door open, door closed)

Each institution can configure the service and operator functions menu structure to fit the specific needs of the institution with a special tool called SOPCONF. With SOPCONF you can create operator groups, limiting which commands each group is authorized to use. With the SOP itself you can specify special groups with own passwords.

Automatic return The automatic return to previous mode feature configures a terminal to automatically return to service after exiting SOP mode, if the terminal was in-service before entering SOP mode. If the feature is disabled, the terminal remains out-of-service after exiting SOP. This option can be downloaded with the customization table load command (see ProCash/NDC ProConsult/NDC Installation manual “Optional Parameters (NDC)”).

46

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user4.fm © Siemens Nixdorf Informationssystem e AG 1995

Modes of Operation

Rear Balancing

In-service By default, the terminal accepts load command messages while in-service. It also processes the Terminal Command message requesting configuration information, even if a customer is on the terminal.

Rear Balancing On Wincor Nixdorf terminals the rear balancing functions can be performed in two ways: ●

on rear load terminals on the operator panel

●

on front load terminals on the screen

Start Rear Balancing ●

Rear load terminals If the ProSop is in use, the rear balancing function is part of the User Exit interface and can be called within the “Individual Functions” menu. If the ProCash/NDC-SOP or ProConsult/NDC-SOP is in use, the rear balancing function is integrated in the step table configuration. If the rear balancing function has been entered, the script framework calls step functions as configured in the step configuration file “LYNXSOP.INA”. Refer to the ProCash/NDC-DDC Programmers Reference manual for details regarded to rear balancing step functions.

●

Front load terminals On front loads the rear balancing functions will be performed in the same way. The only difference is that supervisor mode is entered on the consumer display. The supervisor mode must be activated using the green SOP button on the right-hand side under the customer console in the front. You have to open the front door of the safe to reach the button. The operator screen will be displayed 2 or 3 seconds after pressing the button. Then you can select the options with the PIN PAD and softkeys.

U25604-J-Z745-1-7600

October 2004

47

Rear Balancing

Modes of Operation

Customize Rear Balancing functions To build up rear balancing functions for the operator panel or consumer screen, you have to create a step table which is stored in section “..\LYNXSOP\ REAR_BALANCING” see ProCash NDC/DDC Programmers Reference for detailed description of step functions and how to create step tables. The parameter file “LYNXSOP.INA” in “C:\PROTOPAS\CONF” can be used to enhance or replace the existing steps against your rear balancing steps. Rear Balancing default configuration [REAR_BALANCING] STEP_START = "START" STEP_ABORT = "ABORT" [REAR_BALANCING\ABORT] STEP_FUNC = "APPL_STOP_REAR_BAL" STEP_PARAM = "" JUMP_ON_RC = "RET_ERROR" [REAR_BALANCING\RET_OK] STEP_FUNC = "RETURN" STEP_PARAM = "0" [REAR_BALANCING\RET_ERROR] STEP_FUNC = "RETURN" STEP_PARAM = "1" [REAR_BALANCING\START] STEP_FUNC = "DISPLAY_CONFIRM_MSG" STEP_PARAM = "No Rear Balancing Configured!,2,1" JUMP_ON_RC = "RET_ERROR,RET_ERROR,RET_ERROR"

48

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user4.fm © Siemens Nixdorf Informationssystem e AG 1995

Modes of Operation

Dispense Below Zero

Dispense Below Zero Since release 1.2 ProCash/NDC is able to perform dispense operations when the physical cassettes counters become negative. Some customers have requested this behavior for host environments where counter actualization is not mandatory after every time when cashout cassettes will be refilled with cash. That means at least, cashout cassettes can be refilled without updating the local cassette counters where dispensing is possible immediately after cassette insertion (and cassette logon via SOP if automatic logon is NOT enabled). How to configure Dispense Below Zero: Dispense Below Zero can be enabled via following parameter in CUSTOM.PPF: SECTION

PARAMETER

[CASH_DISPENSER DISPENSE_BELOW_ZERO Please refer to ProCash/NDC ProConsult/NDC Installation manual for detailed description of this parameter. Restrictions: ●

Dispense Below Zero can be used with ProCash/NDC-SOP only. If the ProSop is in use you get counter mismatches between the ProSop counters (received from WOSA) and the recalculated counters in the User Exit function provided by ProCash/NDC.

●

Dispense Below Zero cannot be used together with ProView. Because ProView is requesting for the WOSA counters and does not get the recalculated counters from ProCash/NDC.

●

Dispense Below Zero can be used only for cash out systems when the logical WOSA service (BSATM32.DLL) is configured.

●

It is mandatory to install cashout cassettes with a physical LOW sensor to be able to send a “Money Low” unsolicited message to the host, because the logical cassettes counters never fall down below the low threshold.

U25604-J-Z745-1-7600

October 2004

49

Dispense Below Zero

Modes of Operation

Changes of cash counter behaviour: If Dispense Below Zero is enabled ProCash/NDC handles the internal counters as follows: As long as the number of notes remaining in the cassette is higher or equal than 500 notes, the counters are calculated in the standard way. If the remaining counter is lesser than 500 notes, the counter maintained in the CashUnitInfo() structure of WOSA will be encreased with 500 notes via SetCuInfo() call from ProCash/NDC framework dcCdmFW. That has the effect that the WOSA counter will not fall down to zero or below zero in any case. WOSA is not able to handle negative counters. (The counters of WOSA would remain zero for all following dispenses. The result is that the counters of rejected and dispensed notes get lost.) Temporarily the number of notes added for each cassette is stored in the CMOS. The CMOS counters are used to recalculate back the original counters for the NDC Supply counter message and SOP Cash supply counters. Send Supply Counters terminal response: If the remaining counter for a cassette becomes negative, the counter number of notes remaining in cassette is set to 65535 (FFFF) in the Supply Counters solicited message. The counters number of notes dispensed and rejected are still maintained with the actual values. Display or Print Cash Supplies in ProCash/NDC-SOP: For cassettes with negative counters only the number of rejected and dispensed notes are displayed or printed in the Cash Counters supply function. All other counter values are blanked out.

50

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user11.fm © Siemens Nixdorf Informationssysteme AG 1995

Miscellaneous Operations ADRS operation ADRS by ProCash/NDC The ProCash/NDC application periodically checks several devices of a self service terminal and the application tries to repair them if neccessary. This function is called Automatic Device Repair System (ADRS). Especially the shutters and transport ways of input and output devices (Cash Dispenser Module, Deposit Module, CashIn Module, etc.) are checked after each consumer transaction. If status requests to the device are returned with transport jams or device not operational, the application actively tries to repair them via reset, or shutter close commands. During silent service ADRS is called 3 times in a 60 second time cycle. ADRS methods in ProCash/NDC are implemented for the following devices: ●

Cash Dispenser Module Checks shutter and transport way status, performs retract or close shutter commands, sends status message to the host

●

Deposit Module Checks shutter status, sends status message to the host, performs retract

●

Receipt Printer Checks supply status, sends low/out status message to the host

●

Journal Printer Checks supply status, sends low/out status message to the host

●

Document Printer Checks supply status, sends low/out status message to the host

ADRS by WOSA WOSA (ProDevice) also uses ADRS for the Cash Dispenser device. In a configurable time cycle the status of the device is checked and if neccessary, a reset command is initiated by the WOSA service (Wincor Nixdorf systems only). ADRS by Firmware In specific conditions the firmware itself performs ADRS through automatic resets (resp. for the cash dispenser so called clearing run). The ADRS behavior can be controlled via configuration parameters. Please refer to ProCash/NDC Installation Manual and ProDevice parameter specification for ADRS configuration parameters.

U25604-J-Z745-1-7600

October 2004

51

ADRS operation

52

Miscellaneous Operations

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data Configuration data is down-line loaded from the network to each terminal using a series of load command messages. Configuration data is divided into four categories: ●

States The states table directs the terminal to the tasks to be performed during each part of a transaction. Refer to section ”States” on page 54 for details.

●

Screens Screen data contains display, control, and delimiter characters for different screens which must be shown during different parts of a transaction. Refer to section ”Screens” on page 153 for details.

●

Miscellaneous Configuration Data Consists of terminal parameters (capabilities), LUNO (a unique number identifying each terminal), and terminal timer values. Refer to section ”Miscellaneous Configuration Data” on page 166 for details.

●

FIT Financial Institution Tables entries provide information which is used for identifying which institution has issued a particular card, decoding or encoding of data and for electronic fund transfers. Refer to chapter ”Security Features” on page 175 for details.

Downloaded configuration data are stored in the registry location “LYNXCI” after a "Set Config ID" load command is received. From now on the terminal will be loaded automatically with the configuration data of the registry when the application starts up as long as the terminal has not received any new customization data. When power is restored or the terminal is turned on, the network requests a configuration ID from the terminal. If the configuration ID sent by the terminal does not match the configuration ID at the network, the network will usually send a new configuration load to the terminal. Terminals connected to the network are assigned to distinct groups. A network programmer can create unique configuration data for each group, thereby giving each group of terminals its own "personality", e.g. for systems of different type or purpose.

U25604-J-Z745-1-7600

October 2004

53

States

Configuration Data

States The states configuration data is down-line loaded using the States Table Load command message (refer to section ”State Tables Load” on page 239). Each state is associated with a specific task. For example, while the terminal is in the select function state the terminal is dedicated to the task of prompting the consumer to select a function and recognizing the key (function) selected. Only those subroutines and hardware components (such as screen and keyboard) that facilitate function selection are used. The terminal requires the repeated use, in different ways, of some states. For instance, the consumers have to select the type of transaction (deposit, withdrawal, inquiry or other) and later they have to select the type of account. Both tasks are performed using different versions of the select function state. Each state type can have one or more state tables associated with it. Each state table of the same state type is a different version of that state providing the same type of functions, but used in a different manner. The different state tables are specified by a three-digit decimal number (000 through 999). This range allows up to 1000 different state tables. Each state table contains nine entries. 1. A state table is 25 characters long (first entry, which is one character long, plus eight three-digit entries). 2. The first entry in a state table is a single character identifying the type of state (ASCII graphic character). 3. The other eight entries are used to specify the actions performed (such as screen displayed, buffers used and next state table) and are three characters long.

State table 000 is the first state table that the terminal is in when it enters in-service mode. State table 000 is usually a card read state. The terminal should always return to a close state after the consumer’s transaction(s) have been completed. The terminal may use one state type several times while processing a transaction; depending on the transaction that the costumer has requested, other state types might not be used at all. The use of these state types, in any order, defines terminal operation.

54

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

A summary of all the state types is shown in the following tables. Table 5: State summary

State Name

State Description Type

Card Read

A

Reads the magnetic stripe from the ID card and then usually indicates a PIN entry state as the next state.

PIN Entry

B

Reads the PIN number entered by the customer and verifies that the PIN entered is valid.

Unlock Envelope Dispenser

C

After this state the terminal immediately goes to the next state.

Preset Operation Code Buffer

D

Clears and sets any or all 8 bytes of the operation code buffer.

FDK Selection

E

Reads the code of each operation key pressed by the customer. The key codes are stored in the operation code buffer. The next state varies depending on the customer’s selection.

Amount Entry

F

Reads the entered amount, displays that amount on the screen, and stores it in the amount buffer. If a withdrawal transaction is being processed, an amount check state will normally be the next state. Otherwise, a Preset Operation Code Buffer state will usually be the next state.

Amount Check

G

Verifies that the amount entered is a whole amount (zero cents). If the amount entered by the customer is not a whole amount, the next state is always determined by the network configuration. Otherwise, a Preset Operation Code Buffer state will typically be the next state.

Information Entry

H

Reads in a variable-length string of numerical keys and stores that data in a general purpose buffer. Optionally, the terminal displays the data on the screen. If the customer presses the cancel key, an operation key, or times-out during data entry, the input string is terminated. The next state depends on the customer’s input.

U25604-J-Z745-1-7600

October 2004

55

States

Configuration Data

State Name

State Description Type

Transaction Request

I

Sends a Transaction Request message to the network and executes the Transaction Reply commands received from the network. The next state depends on the network response.

Close

J

Returns or retains the customer’s card and optionally issues a printed acknowledgment form to the customer. Typically, the next state table used is 000 (a card read state preparing the terminal for the next customer).

FIT Switch

K

Used to modify selection paths based on FIT table entry and institution type. The terminal can use customized state tables for the customers of a specific institution. The terminal can provide different functions to different customers depending on the customer’s institution.

Card Write

L

During this state, the terminal writes the contents of the track 3 data buffer onto the magnetic stripe of a card

Enhanced PIN Entry

M

Same functions as B state, but including updating track data on the ID card.

Card read T (Non-000 state applications)

This card read state is used, if the application requires that the number of the card read state be something other than 000.

Hardware Fitness

h

The Hardware Fitness state checks for fatal error condition of the terminal devices. It goes to the specified next state depending on devices which have a fatal condition. The extension of this state checks for warning conditions und uses the specified next state exit.

Smart FIT Check

k

The Smart FIT Check state performs a FIT check with the chip data that is read from the chip of a smart card.

Skip Step Enhanced Amount Entry

56

The Skip Step is used to skip states which are not supported by ProCash/NDC or ProConsult/NDC. R

Reads the entered amount, displays it on the screen, and stores it in the Amount buffer, General Purpose buffer B or C buffer.

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

State Name

States

State Description Type

Language S Code Switch

In this state the flow of a transaction is switched on whether a language code is present in the card data or not.

Language Select from Card

V

In this state one set of state tables can be used to display screens in different languages within the same transaction. This is determined by a code on the cardholder’s card.

FDK Switch

W

This state reads the data buffer from the 8 FDK selection state to identify which next state the terminal should go.

FDK Information

X

This state translates the FDK selected by the cardholder into a value that is placed in the specified buffer for use by an FDK switch state.

8 FDK Selection

Y

This state reads the FDK selected by the cardholder, stores the key code in an FDK buffer for use by an FDK switch state, and updates the operation code buffer.

Customer b Selected PIN

This state allows the consumer to change the PIN.

Audio Control

i

This state allows the consumer to set the audio volume for the played message and to switch audio channels.

Expanded FIT Switch

’_’

FIT switch state with enhanced number of next states depending on the specified switch index in the FIT table.

Extension

Z

The Extension state extends the functions of state ‘S’, ‘T’, ‘X’, ‘k’ and ‘Y’. The Extension state can be activated in the extension state number field of the state.

U25604-J-Z745-1-7600

October 2004

57

States

Configuration Data

Steps processing ProCash/NDC or ProConsult/NDC uses step oriented functions for each state. Every downloaded state is assigned to a specific ProCash/NDC or ProConsult/NDC step. The step assignment is stored in the Windows registry location “..\LYNXPAR\STATE_MAP” The following table shows, which NDC state is assigned to a ProCash/NDC or ProConsult/NDC step: Table 6: ProCash/NDC, ProConsult/NDC steps belonging to NDC states

State Type

Step

A

DC_CARD_READ

S

NDC_LANGUAGE_SWITCH

B

DC_PIN_ENTRY

T

NDC_CARD_PIN

C

DC_DISPENSE_ENVELOPE

V

NDC_CARD_LANGUAGE

D

DC_PRESET_OP_CODE

W

NDC_FDK_SWITCH

E

DC_FDK_SELECT4

X

NDC_FDK_INFO_ENTRY

F

DC_AMOUNT_ENTRY

Y

NDC_FDK_SELECT

G

DC_WHOLE_DOLLAR_CHECK

Z

NDC_EXT

H

DC_INFORMATION_ENTRY

’_’

NDC_EXP_FIT_SWITCH

I

DC_TRAN_REQUEST

b

NDC_CUST_SEL_PIN

J

DC_CLOSE_TRAN

i

NDC_AUDIO_CONTROL

K

DC_FIT_SWITCH

P

NDC_EXP_FIT_SWITCH

L

DC_WRITE_CARD

R

NDC_ENH_AMOUNT_ENTRY

M

DC_ENH_PIN_ENTRY

k

DC_HARDWARE_FITNESS [1]

N

DC_CAMERA_CONTROL

all states

DC_NEXT_X (X = 1-8) [1]

[1] -

Wincor Nixdorf specific state

58

State Type

October 2004

Step

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Card Read State (A) The Card Read state is usually the first state used during transaction processing. This state table is normally assigned to the state number 000. The terminal enters state number 000 automatically when placed in-service. The Card Read state table performs the following functions: ●

identifies the number of the screen displayed for prompting card entry

●

identifies the screen displayed after a misread

●

defines the card track(s) from which data is read

●

contains a flag for the card return feature (immediately or at the end of the transaction)

●

indicates the next state number for cards that are read properly

●

scans the FIT to obtain a match on the financial institution number

●

tells the terminal the next state to go to if there is no FIT match

Table 7: Card Read state entries

Entry

Definition

1

state type

2

screen number

3

correct read next state number

4

error (misread) screen number

5

read condition 1

6

read condition 2

7

read condition 3

8

card return flag

9

no FIT match next state number

U25604-J-Z745-1-7600

October 2004

59

States

Configuration Data

The card read (A) state entries are defined as follows: State type Entry number: 1 Valid range:

A

Description:

This state ID identifies this state table as a Card Read state table.

Screen number Entry number: 2 Valid range:

000-999

Description:

This is the number of the screen which prompts the customer to insert a card. This screen is displayed while the terminal is awaiting card entry.

Good read next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The number of the state the terminal enters after the customer’s card is read properly. Normally the next state is a PIN entry state type.

Error (misread) screen number Entry number: 4 Valid range:

000-999

Description:

This is the number of the screen displayed if the card is not read properly. Normally, this screen will prompt the customer to check that the card is inserted correctly and to reinsert the card.

60

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Read condition 1 Entry number: 5 Valid range:

001-015

Description:

This is one of the three entries (used with entry no. 6 and 7) that tell the terminal which card track(s) must be read. This is the first read condition. If this condition cannot be met, read condition 2 is used next. Refer to table “Card Read state entries” for the definition of the card read conditions.

Read condition 2 Entry number: 6 Valid range:

001-015

Description:

This is one of the three entries (used with entry no. 5 and 7) that tell the terminal which card track(s) must be read. This is the second read condition used. This one is used if read condition 1 cannot be done. If read condition 2 cannot be met, read condition 3 is used. Refer to table “Card Read state entries” for the definition of the card read conditions.

Read condition 3 Entry number: 7 Valid range:

001-015

Description:

This is one of the three entries (used with entry no. 5 and 6) that tell the terminal which card track(s) must be read. If neither read condition 1 or read condition 2 can be met, this read condition is used. Refer to table “Card Read state entries” for the definition of the card read conditions.

Card return flag Entry number: 8 Valid range:

000-001

Description:

This entry tells the terminal whether the card should be returned immediately or upon transaction completion. The valid values are as follows: 000 - return card immediately 001 - return card upon transaction completion

U25604-J-Z745-1-7600

October 2004

61

States

Configuration Data

No FIT match next state number Entry number: 9 Valid range:

000-254, 256-999

Description:

The number of the state the terminal enters if the FIT number on the card does not match that of any member institution.

Table 8: Read condition entry definitions

Required track(s)

Card read table Entry 5 (read condition 1) 1 only 004 2 only 002 3 only 001 1 and 2 006 1 and 3 005 2 and 3 003 1 and 2 and 3 007 2 or 3 002 1 or 3 004 1 or 2 004 1 or2or3 004 (1 and 2) or (1 and 3) 006 (2 and 1) or (2 and 3) 006 (3 and 1) or (3 and 2) 005 1 or (2 and 3) 004 2 or (1 and 3) 002 3 or (1 and 2) 001 Chip connect only 008 3 and chip connect 009 2 and chip connect 010 2, 3 and chip connect 011 1 and chip connect 012 1, 3 and chip connect 013 1, 2 and chip connect 014 1, 2, 3 and chip connect 015

62

Card read table Entry 6 (read condition 2) 004 002 001 006 005 003 007 001 001 002 002 005 003 003 003 005 006 008 009 010 011 012 013 014 015

October 2004

Card read table Entry 7 (read condition 3) 004 002 001 006 005 003 007 001 001 002 001 005 003 003 003 005 006 008 009 010 011 012 013 014 015

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Short desciption to Table 8: If read condition 1 is satisfied, the good read next state number entry (table entry 3) is taken. Otherwise, read condition 2 is attempted. If read condition 2 is satisfied, the good read next state number entry (table entry 3) is taken. Otherwise, read condition 3 is attempted. If read condition 3 is satisfied, the good read next state number entry (table entry 3) is taken. Otherwise, the card is ejected and the error screen number (table entry 4) is displayed.

U25604-J-Z745-1-7600

October 2004

63

States

Configuration Data

PIN Entry State (B) The PIN Entry state prompts the customer to enter the PIN and displays an X for each PIN digit entered. FIT determines whether the terminal performs PIN verification (local PIN verification) or whether this is done by the network (remote PIN verification). If local PIN verification is used, the terminal does not use state entry 8. If remote PIN verification is used, the terminal does not use state entry 5. For details on each PIN verification method, refer to chapter ”Security Features” on page 175. Table 9: PIN Entry state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

local PIN check, correct PIN next state number

6

local PIN check, maximum bad PIN’s next state number

7

local PIN check, error screen number

8

remote PIN check, next state number

9

local PIN check, maximum PIN attempts

The PIN Entry (B) state entries are defined as follows: State type Entry number: 1 Valid range:

B

Description:

This state ID identifies this state table as a PIN Entry state table.

64

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Screen number Entry number: 2 Valid range:

000-999

Description:

This is the number of the screen display that prompts the customer to enter the PIN. This screen is displayed when the terminal enters the PIN entry state. This screen must position the cursor at the beginning of the area where the Xs are displayed.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds if the customer fails to enter the PIN within the specified time limit. Enter 255 to deactivate the time-out function. Entering 255 keeps the terminal in this state until an operation key is pressed.

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

This is the number of the state to which the terminal proceeds if the customer presses the cancel key.

Local PIN check, good PIN next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds after it verifies that the customer entered the correct PIN (if local PIN check). The number of digits to be checked are specified by FIT field PCKLN. Normally the next state is a Pre-Set Operation Code Buffer state.

U25604-J-Z745-1-7600

October 2004

65

States

Configuration Data

Local PIN check, maximum bad PIN’s next state number Entry number: 6 Vollud data range:000-254, 256-999 Description:

The number of the state to which the terminal proceeds after the customer incorrectly enters the PIN the number of times specified by state entry 9. Normally, the next state is a close state.

Local PIN check, error screen number Entry number: 7 Valid range:

000-999

Description:

The number of the screen display that prompts the customer to enter the PIN again. This screen is displayed each time the customer enters an incorrect PIN until the retry value is reached as specified by state entry 9 (or by the card). This screen must position the screen cursor at the beginning of the area in which the Xs are displayed.

Remote PIN check, next state number Entry number: 8 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds if no local PIN check is specified in FIT.

Local PIN check, maximum PIN attempts Entry number: 9 Valid range:

000-009

Description:

This entry specifies the maximum number of times that a customer can enter an incorrect PIN before the terminal goes to the state specified by state entry 6. (This can be overridden by an entry on the card if such is specified by the FIT. Typically used in the ’M’ state.)

66

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Customer Selectable PIN State (b) This state allows the cardholder to input a new PIN. It differs from the PIN entry state (B) in the number of retries. The state will prompt for the new PIN twice and will take a good exit if both are the same and local PIN check is enabled. If checking is local, the exit will be taken when the two new PIN’s have been built into the PIN blocks for transmitting. If checking is enabled and the two PIN’s entered are not the same the cardholder wil be asked to re-enter the Customer Selectable PIN (CSP) and the state will not exit. If the FIT specifies that short PIN entry is to be tested for, short PIN’s will be regarded as one try against the limit specified in the state table. The screen association for this state is derived from screen specified in table entry 2. The cardholder PIN is entered on the facia keyboard and consists of four to sixteen digits. If the number of digits entered is less than the value specified in the FIT entry PMXPN the cardholder must press FDK A or ’ENTER’ key on the facia keyboard after the last digit entered . The ’CLEAR’ key clears all digits. Table 10: Customer Selectable PIN state entries

Entry

Definition

1

state type

2

first entry screen number

3

time-out next state number

4

cancel next state number

5

good next state number

6

CSP fail next state number

7

second entry screen number

8

mismatch first entry screen number

9

extension state number

U25604-J-Z745-1-7600

October 2004

67

States

Configuration Data

The Customer Selectable PIN (b) state entries are defined as follows: State type Entry number: 1 Valid range:

b

Description:

This state ID identifies this state table is a Customer Selectable PIN state table.

First entry screen number Entry number: 2 Valid range:

000-999

Description:

Display screen that prompts the cardholder to enter the PIN the first time.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

State number to which the terminal goes if the cardholder does not make a CSP entry within the specified time limit. Enter 255 if the time-out function is not required.

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

State number to which the terminal goes if the cardholder presses the ’CANCEL’ key to stop the CSP transaction.

Good next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

State number to which the terminal goes if the cardholder enters a matching pair of new PIN values.

68

October 2004

U25604-J-Z745-1-7600

States

CSP fail next state number Entry number: 6 Valid range:

000-254, 256-999

Description:

State number to which the terminal goes if the cardholder fails to enter a matching pair of new PIN digits or the maximum number of retries for local PIN checking is reached.

© Siemens Nixdorf Informationssystem e AG 1995

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm

Configuration Data

This state will also be taken if: 1. No FIT match 2. Cardholder tampering is detected. 3. PIN block generation fails. Second entry screen number Entry number: 7 Valid range:

000-999

Description:

Display screen used to ask for confirmation of the CSP.

Mismatch first entry screen number Entry number: 8 Valid range:

000-999

Description:

Displays a new screen that replaces the screen for table entry 2 on each attempt after a CSP pair attempt did not match or an error has occurred and there are still further retries allowed.

Extension state number Entry number: 9 Valid range:

000-254, 256-999

Description:

State number of the extension state.

U25604-J-Z745-1-7600

October 2004

69

States

Configuration Data

Extension to state (b) This state extends the Customer selected PIN state regarding number of PIN entry attempts and type of PIN verification. Table 11: Extension state entries

Entry

Definition

1

state type

2

number of attempts allowed to enter a matching CSP pair

3

use local verification of new PIN pair attempts

4-9

reserved, must be ’000’

The Extension state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies that this state table is an Extension state.

Number of attempts allowed to enter a matching CSP pair Entry number: 2 Valid range:

000-010

Description:

Limits the number of attempts the cardholder may make to select a new PIN. A zero entry means no limit.

Use local verification of new PIN pair attempts Entry number: 3 Valid range:

000-001

Description:

Specifies which attempts are to be verified locally: 0 - Do not verify locally 1 - Verify both attempts locally. Result available in transaction request field ’U’.

70

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Envelope Dispense (C) State The Envelope Dispense (C) state tells the terminal how to process a deposit operation. If there are still enough envelopes in the deposit module and the local parameter “DISPENSE_ENVELOPE” is enabled, the envelope is dispensed within the envelope dispense (C) state. If the local parameter “DISPENSE_ENVELOPE” is disabled, the Envelope Dispense (C) state immediately enters the next state exit without an envelope dispense operation. Envelope dispensing takes place in the deposit function of the transaction reply. Refer to ProCash/NDC ProConsult/NDC Installation manual for detailed parameter description. Table 12: Envelope Deposit (C) state entries

Entry

Definition

1

state type

2

next state number

3-9

reserved, must be ’000’

The Envelope Deposit (C) state entries are defined as follows: State type Entry number: 1 Valid range:

C

Description:

This state ID identifies this state table as an Envelope Deposit state.

Next state number Entry number: 2 Valid range:

000-511

Description:

The number of the state to which the terminal proceeds after entering state C.

U25604-J-Z745-1-7600

October 2004

71

States

Configuration Data

Pre-Set Operation Code Buffer State (D) The operation code buffer is eight bytes long. The Pre-Set Operation Code Buffer state can do any combination of the following: ●

Clear the operation code buffer or clear selected bytes of the operation code buffer.

●

Pre-set selected bytes of the operation code buffer with A, B, C, or D and F, G, H or I

Each bit of the masks in this state represents a byte (buffer position) in the operation code buffer. Bit 0 of the mask represents the first byte; bit 7 of the mask represents the eighth byte. Table 13: Pre-Set Operation Code Buffer state table

Entry

Definition

1

state type

2

next state number

3

clear mask

4

A preset mask

5

B preset mask

6

C preset mask

7

D preset mask

8

reserved

9

extension state number

The Pre-Set Operation Code Buffer (D) state entries are defined as follows: State type Entry number: 1 Valid range:

D

Description:

This state ID identifies this state table as a Pre-Set Operation Code Buffer state table.

72

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Next state number Entry number: 2 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds after clearing or presetting the operation code buffer.

Clear mask Entry number: 3 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be cleared to graphic "space." Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is not set (zero), the corresponding entry is cleared. If a bit is enabled (one), the corresponding entry is unchanged. Set this entry to 255 if none of the operation code buffer positions are to be cleared.

A Preset mask Entry number: 4 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to A. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to A. If a bit is disabled (zero), the corresponding entry is unchanged.

B Preset mask Entry number: 5 Valid range:

000-255

Description:

Specifies bytes of operation codeoperation code buffer buffer to be set to B. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to B. If a bit is disabled (zero), the corresponding entry is unchanged.

U25604-J-Z745-1-7600

October 2004

73

States

Configuration Data

C Preset mask Entry number: 6 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to C. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to C. If a bit is disabled (zero), the corresponding entry is unchanged.

D Preset mask Entry number: 7 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to D. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to D. If a bit is disabled (zero), the corresponding entry is unchanged.

Reserved Entry number: 8 Valid range:

000

Description:

Entry 8 is reserved and must be 000.

Extension State number Entry number: 9 Valid range:

000-254 or 256-999

Description:

State number of the extension state containing information on how the other operation codes are preset.

74

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Clear mask (entry 3) example Start with an operation code buffer that looks like the following: Buffer Bit Pos Weight

B 0 1

_ 1 2

_ 2 4

C 3 8

_ 4 16

_ 5 32

D 6 64

_ 7 128

To clear buffer position 6 (byte 6), add the weights of the positions that you do not want to clear and put that result in the clear mask entry (entry 3). Buffer Bit pos Positions not cleared Weights not cleared

B _ 0 1 X X 1 + 2 + 4

_ 2 X + 8 +

C 3 X 16 +

_ 4 X 32 +

_ D 5 6 X 128 = 191

_ 7 X

With 191 entered in entry 3, the resultant operation code buffer would appear as follows: Buffer Bit pos

B 0

_ 1

_ 2

C 3

_ 4

_ 5

_ 6

_ 7

A, B, C, D preset masks (entries 4-7) example Assume that you want to set the operation code buffer positions as follows: ●

positions 0 and 2 to A

●

positions 1 and 5 to B

●

position 3 to C

●

positions 4 and 7 to D

The buffer would appear as follows: Buffer Bit pos Weight

A 0 1

B 1 2

A 2 4

C 3 8

D 4 16

B 5 32

_ 6 64

D 7 128

The entries would have to be set as follows: ●

entry 4 (A preset mask) -

1+4

= 005

●

entry 5 (B preset mask) -

2 + 32

= 034

●

entry 6 (C preset mask) -

8

= 008

●

entry 7 (D preset mask) -

16 + 128

= 144

U25604-J-Z745-1-7600

October 2004

75

States

Configuration Data

Extension to State (D) The extension to state (D) allows presetting the operation code buffer with F, G, H or I. Table 14: Preset operation code buffer Extension state table

Entry

Definition

1

state type

2

F preset mask

3

G preset mask

4

H preset mask

5

I preset mask

6-9

reserved must be 000

The Pre-Set Operation Code Buffer Extension (Z) state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as an Pre-Set Operation Code Buffer Extension state.

F Preset mask Entry number: 2 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to F. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to F. If a bit is disabled (zero), the corresponding entry is unchanged.

76

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

G Preset mask Entry number: 3 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to G. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to G. If a bit is disabled (zero), the corresponding entry is unchanged.

H Preset mask Entry number: 4 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to H. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to H. If a bit is disabled (zero), the corresponding entry is unchanged.

I Preset mask Entry number: 5 Valid range:

000-255

Description:

Specifies bytes of operation code buffer to be set to I. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to I. If a bit is disabled (zero), the corresponding entry is unchanged.

U25604-J-Z745-1-7600

October 2004

77

States

Configuration Data

Four FDK Selection Function State (E) This state reads the operation key that has been pressed by the cardholder, stores the key code in the operation code buffer, and then advances to the next state. This state permits the customer to select one function from up to four functions displayed on the screen, by pressing one of the active operation keys. The state table data for this state type defines which of the four operation keys are to be active during this state. Table 15: Four FDK Select Function state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

operation key A next state number

6

operation key B next state number

7

operation key C next state number

8

operation key D next state number

9

operation code buffer location

The Four FDK Selection Function (E) state entries are defined as follows: State type Entry number: 1 Valid range:

E

Description:

This state ID identifies this state table as a Function Selection state table.

78

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Screen number Entry number: 2 Valid range:

000-999

Description:

The number of the display screen which prompts the customer to choose between transaction types, account names, etc.. This screen is displayed upon entry into the selection function state and must be aligned with the active operation keys (table entry 5, 6, 7, and 8) for proper operation.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer fails to make the selection within the specified time limit (specify "255" if the time-out function is not used).

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the cancel key instead of an operation key.

Operation key A next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the A operation key (specify "255" to deactivate the A operation key during this state).

Operation key B next state number Entry number: 6 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the B operation key (specify "255" to deactivate the B operation key during this state).

U25604-J-Z745-1-7600

October 2004

79

States

Configuration Data

Operation key C next state number Entry number: 7 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the C operation key (specify "255" to deactivate the C operation key during this state).

Operation key D next state number Entry number: 8 Valid range. 000-254, 256-999 Description:

The state number to which the terminal proceeds if the customer presses the D operation key (specify "255" to deactivate the D operation key during this state).

Operation code buffer location Entry number: 9 Valid range:

000-007

Description:

Specifies the operation code buffer byte in which the key code for the selected operation key is to be stored. The network down-line loads the following data to select the indicated buffer byte: 000 = buffer 001 = buffer 002 = buffer 003 = buffer 004 = buffer 005 = buffer 006 = buffer 007 = buffer

80

position 0 position 1 position 2 position 3 position 4 position 5 position 6 position 7

October 2004

Buffer positions are as follows: ________ 01234567

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Amount Entry State (F) This state reads the amount entered by the consumer, displays it on the screen and saves it in the amount buffer. This buffer is 8 or 12 bytes long. In the amount entry state, the operation keys are used by the consumer to indicate whether the displayed amount is either correct or incorrect. Table 16: Amount Entry state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

operation key A next state number

6

operation key B next state number

7

operation key C next state number

8

operation key D next state number

9

display amount screen number

The Amount Entry (F) state entries are defined as follows: State type Entry number: 1 Valid range:

F

Description:

This state ID identifies this state table as an Amount Entry state table.

Screen number Entry number: 2 Valid range:

000-999

Description:

Number of display screen that prompts an amount entry. This screen is displayed upon entry into the amount entry state.

U25604-J-Z745-1-7600

October 2004

81

States

Configuration Data

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer fails to enter the amount within the specified time limit (specify "255" if the time-out function is not used).

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the cancel key before pressing an operation key. Value "255" deactivates the CANCEL key during this state.

Operation key A next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the A operation key. Value "255" deactivates the A operation key during this state.

Operation key B next state number Entry number: 6 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the B operation key. Value "255" deactivates the B operation key during this state.

Operation key C next state number Entry number: 7 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the C operation key. Value "255" deactivates the C operation key during this state.

82

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Operation key D next state number Entry number: 8 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the D operation key. Value "255" deactivates the D operation key during this state.

Normally one operation key is used to indicate whether the amount entry is correct and another is used to indicate whether it is incorrect. The other operation keys are inactive. Display amount screen number Entry number: 9 Valid range:

000-999

Description:

Overlay screen number that sets the screen cursor position. This screen optionally defines the initial display format prior consumer amount entry. The cursor should be set on the lefthand side of the echo field on the screen. This is space filled until the required start position for the currency character is reached. Default echo field for eight digits: bbbbb$ 0.00 (where b = space) Default echo field for twelve digits: bbbbbbbbb$ 0.00 (where b = space)

U25604-J-Z745-1-7600

October 2004

83

States

Configuration Data

Amount Check State (G) This state checks to see if the amount entered is a whole amount (zero cents). This state should follow the amount entry function state when a withdrawal transaction is being performed. When checking that an amount is dispensable, Central must have downloaded the Dispenser Currency Cassette Mapping Table. If this table has not been downloaded, or a currency type identified in table entry 7 is not present in the table, processing will proceed with non-whole amount entry next state number. Table 17: Amount Check state entries

Entry

Definition

1

state type

2

whole amount entry next state number

3

non-whole amount entry next state number

4

buffer to be checked

5

zero entry next state number (if table entry 8 is zero) or integer multiple value (if table entry 8 is non zero)

6

number of decimal places

7

currency type

8

amount check condition

9

reserved must be zero

The Amount Check (G) state entries are defined as follows: State type Entry number: 1 Valid range:

G

Description:

This state ID identifies this state table as a amount check state table.

84

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Whole amount entry next state number Entry number: 2 Valid range:

000-999

Description:

The state number to which the terminal proceeds upon finding 00 (zero cents) value in the amount entry.

Non-whole amount entry next state number Entry number: 3 Valid range:

000-999

Description:

The state number to which the terminal proceeds upon finding a cents value other than 00 cents in the amount entry.

Buffer to be checked Entry number: 4 Valid range:

000-002

Description:

This field specifies which buffer is to be checked: 000 - amount buffer 001 - general purpose buffer B 002 - general purpose buffer C

Zero entry next state number Integer Multiple Value Entry number: 5 Valid range:

000-999

Description:

If table entry 8 is zero: The state number to which the terminal proceeds, if the consumer enters zero amount or does not enter any value. If table entry 8 is non-zero: Integer multiple value used in checking specified buffer. For example, to check that the specified buffer contains a multiple of the minimum denomination $5, this field would be set to '005'. This field is ignored if table entry 8 is not ‘002’.

U25604-J-Z745-1-7600

October 2004

85

States

Configuration Data

Number of decimal places Entry number: 6 Valid range:

000-004

Description:

Number of decimal places used in specified buffer. For example, $5 is sent as 500 cents, so has 002 decimal places.

Currency type Entry number: 7 Valid range:

001-255

Description:

Currency type of amount in specified buffer. Used in conjunction with the Dispenser Currency Cassette Mapping Table. This field is ignored if table entry 8 is not '003'.

Amount check condition Entry number: 8 Valid range:

000-003

Description:

If the condition being checked evaluates to 'true' then processing will proceed to the next state identified in table entry 2; otherwise processing will proceed to the next state identified in table entry 3. All conditions check the buffer indicated by table entry 4. All conditions except condition ‘000’ take account of the decimal point location via the value in table entry 6. When this entry is set to 000, the state does not use state parameters 5 to 9, to enable backwards compatibility. When this entry is set to 001, the state evaluates whether the value to the right of the decimal point position is zero. When this entry is set to 002, the state evaluates whether the value is a whole number multiple of the value identified in table entry 5. When this entry is set to 003, the state evaluates whether the value is dispensable by the terminal, taking into account the currency type required (table entry 7), currency type denominations available, dispenser status and cassette status.

Reserved Entry number: 9 Valid range:

000

Description:

Entry 9 is reserved and must be 000.

86

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Information Entry State (H) This state reads in a variable-length string of numeric keys, saves the data in one of two general purpose buffers (see table entry 9), and displays either the data or ‘X’ for each numeric key pressed. The input string is terminated by an operation key, cancel key, or a time-out. General purpose buffers B and C are variable in length. Maximum length is 32 bytes. When the terminal enters this state, the specified buffer contains only the data from the depressed numeric keys. If no keys are depressed, then the buffer contains no data. Table 18: Information Entry state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

operation key A next state number

6

operation key B next state number

7

operation key C next state number

8

operation key D next state number

9

buffer and display parameters

The Information Entry (H) state entries are defined as follows: State type Entry number: 1 Valid range:

H

Description:

This state ID identifies this state table as an information entry state table.

U25604-J-Z745-1-7600

October 2004

87

States

Configuration Data

Screen number Entry number: 2 Valid range:

000-999

Description:

The number of the display screen that prompts key entry from the customer. This screen is displayed upon entry into the information entry state and must leave the cursor at the beginning of the data or X display area.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer fails to respond to the CRT message within a specified time limit. Value "255" disables the time-out function.

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the cancel key before pressing an operation key.

Operation key A next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the A operation key. Value "255" deactivates the A operation key during this state.

Operation key B next state number Entry number: 6 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the B operation key. Value "255’ deactivates the B operation key during this state.

88

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Operation key C next state number Entry number: 7 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the C operation key. Value "255" deactivates the C operation key during this state.

Operation key D next state number Entry number: 8 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the D operation key. Value "255" deactivates the D operation key during this state.

Buffer and display parameters Entry number: 9 Valid range. 000-323 Description:

This entry specifies whether the actual data entered or X is to be displayed, beginning at the current cursor position. This entry also specifies which general purpose buffer (B or C) is used for storing the numeric data input and how many digits can be entered. The default buffer size of 32 digits can be decreased if the first two digits have a non zero value up to the maximum of 32. The valid characters are as follows: xx0 = xx1 = xx2 = xx3 =

display X for each numeric key pressed; store keys in general purpose buffer C (max. 32 digits). display data as entered; store keys in general purpose buffer C (max. 32 digits). display X for each numeric key pressed; store keys in general purpose buffer B (max. 32 digits). display data as entered; store keys in general purpose buffer B (max. 32 digits).

Set a buffer limit example: 123 =

U25604-J-Z745-1-7600

display data as entered; store keys in general purpose buffer B with max. 12 digits.

October 2004

89

States

Configuration Data

Transaction Request State (I) The Transaction Request state tells the terminal what information to include in the transaction request message, transmits the transaction request message to the network, and waits for the network response. When the network responds with a Transaction Reply command message, the terminal executes the Transaction Reply command message and goes to the next state specified in the Transaction Reply command message. If the network does not respond with a Transaction Reply command message within the time specified by timer 03 (section “Timer Data” on page 167), the terminal goes to the state specified in entry 3 of this state. Table 19: Transaction Request state entries

Entry

Definition

1

state type

2

screen number

3

network response time out next state number

4

send track 2 data

5

send track 1, track 3

6

send operation code buffer

7

send amount buffer

8

send PIN buffer (Buffer A) data / Select Extended format

9

send general purpose buffer(s) B and/or C or Extension State Number (Range 000-254, 256-999)

The Transaction Request (I) state entries are defined as follows: State type Entry number: 1 Valid range:

I

Description:

This state ID identifies this state table as a transaction request state table.

90

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Screen number Entry number: 2 Valid range:

000-999

Description:

The number of the screen displayed while the terminal transmits a request to the network and waits for the associated Transaction Reply command. This is normally a Please Wait screen.

Network response time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the network does not respond to the transaction request in the time specified by timer 03 (section “Timer Data” on page 167). This timer checks for receipt of a Transaction Reply command message in response to a transaction request.

Send track 2 data Entry number: 4 Valid range:

000-001

Description:

This field indicates whether track 2 data should be sent in the transaction request message. The valid values are as follows: 000 - do not send data 001 - send data

Send track 1, 3 Entry number: 5 Valid range:

000-007

Description:

The track 1, 3 data entry specifies whether track 1 and/or track 3 data is sent to the network. The valid values are as follows: 000 - no additional tracks 001 - send track 3 only 002 - send track 1 only 003 - send track 1 and 3

U25604-J-Z745-1-7600

October 2004

91

States

Configuration Data

Send operation key data Entry number: 6 Valid range:

000-001

Description:

This field indicates whether the operation key data should be sent in the transaction request message. The valid values are as follows: 000 - do not send data 001 - send data

Send amount buffer data Entry number: 7 Valid range:

000-001

Description:

This field indicates whether the amount buffer data should be sent in the transaction request message. The valid values are as follows: 000 - do not send data 001 - send data

Send PIN buffer data Entry number: 8 Valid range:

000-001, 128

Description:

This field indicates whether the PIN buffer data should be sent in the transaction request message or when bit 128 is enabled use table entry 9 as an extension state definition. The valid bit values are as follows: 000 - do not send data 001 - send data 128 - use extension state specified in table entry 9

92

October 2004

U25604-J-Z745-1-7600

States

Send general purpose buffers B and/or C data Entry number: 9 Valid range:

000-003, Extension state range: 000-254, 256-999

Description:

This field indicates whether the data from the general purpose buffers B and/or C should be sent in the transaction request message. If bit 128 is enabled in table entry 8 its meaning of this table entry changes to an extension state number definition.

© Siemens Nixdorf Informationssystem e AG 1995

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm

Configuration Data

The valid values are as follows: 000 - do not send data from either buffer 001 - send general purpose buffer B data only 002 - send general purpose buffer C data only 003 - send general purpose buffers B and C data

Extension to state (I) In the Extension state of the transaction request state additional buffers can be defined to be sent to the network. Table 20: Extension state entries

Entry

Definition

1

state type

2

send general purpose buffers B and/or C

3

send optional date fields ’A’ - ’H’

4

send optional data fields ’I’ - ’L’

5

send optional data fields ’Q’ - ’V’

6-9

reserved

The Extension state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as an Extension state table.

U25604-J-Z745-1-7600

October 2004

93

States

Configuration Data

Send general purpose buffers B and/or C data Entry number: 2 Valid range:

000-003

Description:

This field indicates whether the data from the general purpose buffers B and/or C should be sent in the transaction request message. The valid values are as follows: 000 - do not send data from either buffer 001 - send general purpose buffer B data only 002 - send general purpose buffer C data only 003 - send general purpose buffers B and C data

Optional data fields ’A’ - ’H’ Entry number: 3 Valid range:

000-255

Description:

This entry is bit encoded to control the sending of individual optional data fields in the transaction request message. If a bit is set, the corresponding data field is sent. If a bit is clear, the data field is not sent. BIT 1 2 3 4 5 6 7 8

94

Field ID ’A’ reserved ’B’ reserved ’C’ ’D’ ’E’ ’F’ ’G’ ’H’

October 2004

U25604-J-Z745-1-7600

States

Optional data fields ’I’ - ’L’ Entry number: 4 Valid range:

000-015

Description:

This entry is as for entry 3 but with following values:

© Siemens Nixdorf Informationssystem e AG 1995

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm

Configuration Data

BIT 1 2 3 4 5 6 7 8

Field ID ’I’ ’J’ ’K’ ’L’ ’M’ reserved ’N’ reserved ’O’ reserved ’P’ reserved

Optional data fields ’Q’ - ’V’ Entry number: 5 Valid range:

000-063

Description:

This entry is as for entry 3 but with following values: BIT 1 2 3 4 5 6 7 8

U25604-J-Z745-1-7600

Field ID ’Q’ ’R’ ’S’ ’T’ reserved ’U’ ’V’ reserved reserved

October 2004

95

States

Configuration Data

Close State (J) The Close state should terminate the customer’s current terminal interface. This state performs the following functions: ●

displays a screen

●

completes any printing on the customer or journal printer that was initiated by a Transaction Reply command message.

●

returns or retains the activator card as instructed by the Transaction Reply command message.

In addition, if the terminal returns the ID card and the consumer fails to remove the card within the time period specified by timer 02 (section “Timer Data” on page 167), the terminal will automatically retain the card. Table 21: Close state entries

Entry

Definition

1

state type

2

transaction record form delivered screen number

3

next state number

4

no transaction record form delivered screen number

5

card retained screen number

6

Statement delivered screen

7

reserved

8-9

not used

The Close (J) state entries are defined as follows: State type Entry number: 1 Valid range:

J

Description:

This state ID identifies this state table as a Close state table.

96

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Transaction record form delivered screen number Entry number: 2 Valid range:

000-999

Description:

The number of the display screen that asks the customer to please take the card and the transaction record form. This screen is displayed upon entry to the close state only if the customer’s card is returned and a transaction record form was printed.

Next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds after the close state is completed.

No transaction record form delivered screen number Entry number: 4 Valid range:

000-999

Description:

The number of the display screen that asks the customer to please take the card. This screen is displayed upon entry to the close state only if the customer’s card is returned and no transaction record form was printed.

Card retained screen number Entry number: 5 Valid range:

000-999

Description:

The number of the screen that informs the customer that the card has been retained. This screen is displayed upon entry to the close state only if the customer’s card has been retained by the terminal as instructed by the network. If the customer timesout, this screen is not displayed.

U25604-J-Z745-1-7600

October 2004

97

States

Configuration Data

Statement delivered screen Entry number: 6 Valid range:

000-999

Description:

Display screen to be overlaid when either the receipt is delivered (entry 2) or there is no receipt delivery (entry 4). This screen is only displayed if the statement is cut and delivered in a close state and the terminal has not been instructed by the last transaction reply message to capture the card

Reserved Entry number: 7 Valid range:

000

Description:

Entry 7 is reserved and must be 000.

Not used Entry number: 8-9 Valid range: Description:

98

Entries 8 and 9 are not used by ProCash/NDC or ProConsult/NDC.

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

FIT Switch State (K) The FIT Switch state allows the terminal to follow an alternate sequence of states and screens according to the value of the Primary Account Number (PAN) on the activator card. This state examines the PSTDX entry in the FIT to determine the next state number. Refer to section ”FIT (Financial Institution Table)” on page 186 for a detailed explanation of the FIT tables. Each FIT designates a next state according to the institution type to which it applies. The next state executed is indexed in this table. For example, if the FIT identified during the Card Read state contains a PSTDX of 3, state entry 5 contains the next state number. Table 22: FIT Switch state entries

Entry

Definition

1

state type

2-9

next state number

The FIT Switch (K) state entries are defined as follows: State type Entry number: 1 Valid range:

K

Description:

This state ID identifies this state table as an FIT Switch state table.

U25604-J-Z745-1-7600

October 2004

99

States

Configuration Data

Next state number Entry number: 2-9 Valid range:

000-254, 256-999

Description:

Entries 2 through 9 contain the number of the state to which the terminal proceeds depending on the value in the PSTDX value of FIT.

These entries are defined as follows: Entry

Description

2

next state number if PSTDX = 0

3

next state number if PSTDX = 1

4

next state number if PSTDX = 2

5

next state number if PSTDX = 3

6

next state number if PSTDX = 4

7

next state number if PSTDX = 5

8

next state number if PSTDX = 6

9

next state number if PSTDX = 7

100

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Card Write State (L) During a Card Read state the card data buffers are cleared of all previous data. The Card Read state defines the card tracks to be read, and stores the card track data in the corresponding card data buffer. In the transaction request state, the terminal sends a transaction request message to central. You can specify whether or not track 1, 2 or/and track 3 data are included in this message. Central responds to this message by sending a transaction reply command to the terminal. Within this command is a field which contains updated track 1/2 or/and track 3 data. This data replaces any previous data in the terminal‘s track data buffer. During the Card Write state the terminal writes the contents of the track 1/2/3 data buffer onto the magnetic stripe of the card. You specify which screen is to be displayed on the screen while writing takes place. Writing takes place only if the track data buffer contains data obtained from a successful track 3 read during a card read state, or updated track data from a transaction reply command. There are three next state numbers that the terminal can go to once it leaves the Card Write state. One exit is taken if the track write is successful. Another exit taken if the track write is unsuccessful. A third exit is taken if the track buffer is empty or contains invalid data and no writing is attempted. If the terminal is to write more than one track, the order will be first track 1, then track 2 and at least track 3. Before writing , a check is made to ensure that the data are valid. If the data are valid and a track write fails the terminal will not attempt any further requested track writes and the write state will exit. To use the Card Write state, the magnetic stripe card must still be in the reader. The following conditions must apply: ●

If table entry 8 of the Card Read state (Type A) is used, it must not be 000 (return card immediately)

●

A card before cash transaction reply must not have been performed.

●

A parallel eject/dispense and print (Fast Cash) transaction reply must not have been performed.

U25604-J-Z745-1-7600

October 2004

101

States

Configuration Data

Table 23: Card Write state entries

Entry

Definition

1

state type

2

screen number

3

good write next state

4

bad write next state

5

no write attempted

6

reserved

7

reserved

8

reserved

9

reserved

The Card Write state entries are defined as follows: State type Entry number: 1 Valid range:

L

Description:

This state ID identifies this state table as the Card Write state.

Screen number Entry number: 2 Valid range:

010-999

Description:

Screen displayed during card write operation.

Good Write next state Entry number: 3 Valid range:

000-254, 256-999

Description:

State number goes to after a satisfactory track write operation.

102

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Bad Write next state Entry number: 4 Valid range:

000-254, 256-999

Description:

State number goes to if the track write is unsuccessful.

No Write attempted Entry number: 5 Valid range:

000-254, 256-999

Description:

State number goes to if no data or invalid data is present in the track buffer. This state is also used if a start and/or end sentinel is missing.

Reserved Entry number: 6-9 Valid range:

000

Description:

Must be 000 for each table entry.

U25604-J-Z745-1-7600

October 2004

103

States

Configuration Data

Enhanced PIN Entry State (M) This state performs the same functions as the PIN Entry (B) state. It also supports track 3 retries if the FIT specifies local PIN check and indicates that there is a track 3 retry field on the card. If the FIT specifies track 3 retries but there is no data in the track 3 buffer, the Cancel Next state exit is taken. Before the customer can enter a PIN for a local PIN check with track 3 retries, the PIN retry field on the card is checked. For a Mutual Institutions Transfer System (MINTS) format card, the retry field of the track 3 data buffer must not equal or exceed the limit specified in state table entry 9. If an International Standards Organistation (ISO) format card is used, the retry field must not equal 0. If that is the case, in both situations the terminal exits to the Maximum Bad PIN’s Next state specified in table entry 6. This check is done before the start of each PIN entry attempt. After the PIN is entered by the customer and compared with the calculated PIN, the PIN retry field in the track 3 data buffer is updated. For MINTS format cards, if the entered PIN is correct, the PIN retry field is set to 0. For ISO format cards, the retry field is set to the value specified in state table entry 9. If the entered PIN is incorrect, the PIN retry field is incremented for MINTS format cards and decremented for ISO format cards. The updated track 3 data buffer is available for transmission through the Transaction Request state.The buffer can also be written on the card using the Card Write state. Table 24: Enhanced PIN Entry state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

local PIN check, correct PIN next state number

6

local PIN check, maximum bad PIN’s next state number

7

local PIN check, error screen number

8

remote PIN check, next state number

9

local PIN check, maximum PIN attempts

104

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

The Enhanced PIN Entry (M) state entries are defined as follows: State type Entry number: 1 Valid range:

M

Description:

This state ID identifies this state table as an Enhanced PIN Entry state table.

Screen number Entry number: 2 Valid range:

000-999

Description:

This is the number of the screen display that prompts the customer to enter the PIN. This screen is displayed when the terminal enters the PIN entry state. This screen must position the cursor at the beginning of the area where the Xs are displayed.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds if the customer fails to enter the PIN within the specified time limit. Enter 255 to deactivate the time-out function. Entering 255 keeps the terminal in this state until an operation key is pressed.

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

This is the number of the state to which the terminal proceeds if the customer presses the cancel key.

U25604-J-Z745-1-7600

October 2004

105

States

Configuration Data

Local PIN check, good PIN next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds after it verifies that the customer entered the correct PIN (if local PIN check). The number of digits to be checked are specified by FIT field PCKLN. Normally the next state is a Pre-Set Operation Code Buffer state.

Local PIN check, maximum bad PIN’s next state number Entry number: 6 Vollud data range:000-254, 256-999 Description:

The number of the state to which the terminal proceeds after the customer incorrectly enters the PIN the number of times specified by state entry 9. This state could be a Card Write state in order to update the track 3 PIN retry field.

Local PIN check, error screen number Entry number: 7 Valid range:

000-999

Description:

The number of the screen display that prompts the customer to enter the PIN again. This screen is displayed each time the customer enters an incorrect PIN until the retry value is reached as specified by state entry 9 (or by the card). This screen must position the screen cursor at the beginning of the area in which the Xs are displayed.

Remote PIN check, next state number Entry number: 8 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds if no local PIN check is specified in FIT.

106

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Local PIN check, maximum PIN attempts Entry number: 9 Valid range:

000-009

Description:

This entry specifies the maximum number of times that a customer can enter an incorrect PIN before the terminal goes to the state specified by state entry 6. This entry is used as the PIN retry count if the PIN retry count is not on the card (FIT entry PRCNT = FF).

Enhanced Amount Entry State (R) This state reads the amount entered by the cardholder, displays it on the screen, and saves it in the buffers specified by the state table. Exit from the Enhanced Amount Entry state occurs when an active FDK is pressed, the Cancel key is pressed or a time-out occurs. The Enter key is equivalent to FDK ‘A’. The Clear key is always active and clears the amount entered and the screen echo field to allow data entry retries within the Amount Entry state. The Digital Audio Service can echo the keys pressed on the keyboard. Table 25: Enhanced Amount Entry state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

operation key A next state number

6

operation key B next state number

7

operation key C next state number

8

operation key D next state number

9

extension state number

U25604-J-Z745-1-7600

October 2004

107

States

Configuration Data

The Enhanced Amount Entry (R) state entries are defined as follows: State type Entry number: 1 Valid range:

R

Description:

This state ID identifies this state table as an Enhanced Amount Entry state table.

Screen number Entry number: 2 Valid range:

000-999

Description:

This is the number of the screen display that prompts the consumer to enter an amount.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The number of the state to which the terminal proceeds if the consumer fails to enter the amount within the specified time limit. Enter 255 if the time-out function is not required.

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

This is the number of the state to which the terminal proceeds if the consumer presses the Cancel key.

Operation key A next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the A operation key. Value "255" deactivates the A operation key during this state.

108

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Operation key B next state number Entry number: 6 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the B operation key. Value "255" deactivates the B operation key during this state.

Operation key C next state number Entry number: 7 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the C operation key. Value "255" deactivates the C operation key during this state.

Operation key D next state number Entry number: 8 Valid range:

000-254, 256-999

Description:

The state number to which the terminal proceeds if the customer presses the D operation key. Value "255" deactivates the D operation key during this state.

Normally one operation key is used to indicate whether the amount entry is correct and another is used to indicate whether it is incorrect. The other operation keys are inactive. Extension State number Entry number: 9 Valid range:

000-254; 256-999

Description:

State number of the extension state.

U25604-J-Z745-1-7600

October 2004

109

States

Configuration Data

Extension to State (R) This state is the Extension state for the Enhanced Amount Entry state (R). Table 26: Extension state entries

Entry

Definition

1

state type

2

document amount buffer

3

display amount screen number

4

start CAV command

5-9

reserved

The Extension State entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as the Extension state to the Enhanced Amount Entry state table.

Document amount buffer Entry number: 2 Valid range:

000-002

Description:

This field determines which buffer the amount entered will be stored in: 000 - Amount Buffer 001 - General Purpose buffer B 002 - General Purpose buffer C

110

October 2004

U25604-J-Z745-1-7600

States

Display amount screen number Entry number: 3 Valid range:

000-999

Description:

Overlay screen number that sets the screen cursor position. This screen optionally defines the initial display format prior consumer amount entry. The cursor should be set on the lefthand side of the echo field on the screen. This is space filled until the required start position for the currency character is reached.

© Siemens Nixdorf Informationssystem e AG 1995

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm

Configuration Data

Default echo field for eight digits: bbbbb$ 0.00 (where b = space) Default echo field for twelve digits: bbbbbbbbb$ 0.00 (where b = space) Start CAV command Entry number: 4 Valid range:

000-001

Description:

This field determines whether to start CAV processing or not if a document is available. ProCash/NDC or ProConsult/NDC only supports value 000. If a non-zero value is downloaded, the cancel next state is taken.

U25604-J-Z745-1-7600

October 2004

111

States

Configuration Data

Language Code Switch State (S) In this state the flow of a transaction is switched depending on whether a language code is present in the card data or not. You can use this state to automatically select the language to be used from the code on the card, or to allow manual selection for cards which either have no language code, or an invalid language code. This state is subject to the same restrictions as the language select state. See section “Language Select from Card State (V)” for details. Table 27: Language Code Switch state entries

Entry

Definition

1

state type

2

no language code, next state no.

3

language code = 0, next state

4

language code = 1, next state

5

language code = 2, next state

6

language code = 3, next state

7

language code = 4, next state

8

language code = 5, next state

9

extension state number

112

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

The Language Code Switch state entries are defined as follows: State type Entry number: 1 Valid range:

S

Description:

This state ID identifies this state table as a Language Code Switch state table.

No Language Code, Next State No. Entry number: 2 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if the language code is illegal or cannot be read.

Language Code = 0, next state Entry number: 3 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 0.

Language Code = 1, next state Entry number: 4 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 1.

Language Code = 2, next state Entry number: 5 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 2.

Language Code = 3, next state Entry number: 6 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 3.

U25604-J-Z745-1-7600

October 2004

113

States

Configuration Data

Language Code = 4, next state Entry number: 7 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 4.

Language Code = 5, next state Entry number: 8 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 5.

Extension State number Entry number: 9 Valid range:

000-999

Description:

State number of the extension state containing next states for language code 6-9. A value of 255 means that there is no extension state, and language code 6-9 cause the no language code next state exit to be taken.

Extension to State (S) This state is the Extension state for the Language Code Switch state (S). Table 28: Extension state entries

Entry

Definition

1

state type

2

language code = 6, next state

3

language code = 7, next state

4

language code = 8, next state

5

language code = 9, next state

6

reserved

7

reserved

8

reserved

9

reserved

114

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

The Extension state entries of the Language Code Switch state are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as the Extension state to the Language Code Switch state.

Language Code = 6, next state Entry number: 2 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 6.

Language Code = 7, next state Entry number: 3 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 7.

Language Code = 8, next state Entry number: 4 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 8.

Language Code = 9, next state Entry number: 5 Valid range:

000-254, 256-999

Description:

State number the terminal goes to, if the language code is 9.

Reserved Entry number: 6-9 Valid range:

000

Description:

Must be 000.

U25604-J-Z745-1-7600

October 2004

115

States

Configuration Data

Card Read - PIN Entry Initiation State (T) You can use this state instead of the Card Read state (A), if you want to initiate PIN entry by the consumer at the same time as the terminal reads the card. This state performs the same functions as the card read state. This state also enables the keyboard for PIN entry while the card is being read, and displays a screen prompting the customer to enter the PIN. One difference between this state and the Card Read state is that in this state the card is always returned according to the instruction in the Transaction Reply command message. See also section “Card Read State (A)” on page 59. Table 29: Card Read - PIN Entry Initiation state entries

Entry

Definition

1

state type

2

screen number

3

good read next state number

4

error (misread) screen number

5

read condition 1

6

read condition 2

7

read condition 3

8

reserved

9

extension state number

The Card Read - PIN Entry Initiation (T) state entries are defined as follows: State type Entry number: 1 Valid range:

T

Description:

This state ID identifies this state table as a Card Read -PIN Entry Initiation state table with a parallel card read.

116

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Screen number Entry number: 2 Valid range:

000-999

Description:

This is the number of the screen display which prompts the customer to insert a card. This screen is displayed while the terminal is awaiting card entry. This screen will be displayed on the screen.

Good read next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

The state number the terminal enters after the customer’s card is read properly: Following a good read of the card if FIT’s are not used. (Table Entry 3 in Extension State = 000), or if the FIT number on the card matches a FIT number in the FIT table. Normally the next state is a PIN entry state type.

Error (misread) screen number Entry number: 4 Valid range:

010-800

Description:

This is the number of the screen displayed, if the card is not read properly. Normally, this screen will prompt the customer to check that the card is inserted correctly and to reinsert the card.

Read condition 1 Entry number: 5 Valid range:

001-015

Description:

This is one of the three entries (used with entry no. 6 and 7) that tell the terminal which card track(s) must be read. This is the first read condition. If this condition cannot be met, read condition 2 is used next. Refer to table “Card read state entries” for the definition of the card read conditions.

U25604-J-Z745-1-7600

October 2004

117

States

Configuration Data

Read condition 2 Entry number: 6 Valid range:

001-015

Description:

This is one of the three entries (used with entry numbers 5 and 7) that tell the terminal which card track(s) must be read. This is the second read condition used. This one is used if read condition 1 cannot be done. If read condition 2 cannot be met, read condition 3 is used. Refer to table “Card read state entries” for the definition of the card read conditions.

Read condition 3 Entry number: 7 Valid range:

001-015

Description:

This is one of the three entries (used with entry numbers 5 and 6) that tell the terminal which card track(s) must be read. If neither read condition 1 or read condition 2 can be met, this read condition is used. Refer to table “Card read state entries” for the definition of the card read conditions.

Card return flag Entry number: 8 Valid range:

000-001

Description:

This field is not used. The early card eject feature is not supported by this state. Card is always returned as specified be the Transaction Replay command message.

Extension State number Entry number: 9 Valid range:

000-254, 256-999

Description:

State number of the extension state containing information for parallel PIN entry.

118

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Extension to State (T) This state is the Extension state to the card read state (T). Table 30: Extension state entries

Entry

Definition

1

state type

2

screen number

3

no fit match next state number

4

clear key mask (not supported)

5

accept key mask (not supported)

6

reserved, must be 000

7

reserved, must be 000

8

reserved, must be 000

9

reserved, must be 000

The card read extension state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as the extension state to the card read state (T).

Screen number Entry number: 2 Valid range:

010-999

Description:

Display screen that prompts cardholder to enter PIN. This screen is displayed on card entry. The identified screen must leave the screen cursor positioned at the beginning of the PIN entry display area. An X is displayed for each key pressed. track 1 name cannot be displayed at this time as card has not been read.

U25604-J-Z745-1-7600

October 2004

119

States

Configuration Data

No FIT match Next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

State number terminal goes to if the financial institution number on the card does not match any FIT. If FIT’s are not used this entry must be 000.

Language Select From Card State (V) In this state you can set one of state tables to display screens in different languages within the same transaction. This is determined by one character (byte) on the cardholder’s card. This code is located using the Language Code Index parameter (PLNDX) in the FIT. See chapter “Security Features” for more details. You can use up to six screen groups in this state, and you specify which language is to be used in each group. You also specify in table entry 9 how many screens each group will contain. Table 31: Language Select From Card state entries

Entry

Definition

1

state type

2

next state number

3

language code for group 1

4

language code for group 2

5

language code for group 3

6

language code for group 4

7

language code for group 5

8

language code for group 6

9

screen group size (range 000-400)

120

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

The Language Select From Card (V) state entries are defined as follows: State type Entry number: 1 Valid range:

V

Description:

This state ID identifies this state table as a Language Select From Card state table.

Next state number Entry number: 2 Valid range:

0-9

Description:

State number terminal goes to after selecting the screen group.

Language Code Entry number: 3 Valid range:

0-9

Description:

Decimal number in range 0-9 identifying code for screen group 1.

Language Code Entry number: 4 Valid range:

0-9

Description:

Decimal number in range 0-9 identifying code for screen group 2.

Language Code Entry number: 5 Valid range:

0-9

Description:

Decimal number in range 0-9 identifying code for screen group 3.

U25604-J-Z745-1-7600

October 2004

121

States

Configuration Data

Language Code Entry number: 6 Valid range:

0-9

Description:

Decimal number in range 0-9 identifying code for screen group 4.

Language Code Entry number: 7 Valid range:

0-9

Description:

Decimal number in range 0-9 identifying code for screen group 5.

Code Entry number: 8 Valid range:

0-9

Description:

Decimal number in range 0-9 identifying code for screen group 6.

Screen Group Size Entry number: 9 Valid range:

000-400

Description:

State number of the extension state containing information for parallel PIN entry.

122

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

FDK Switch State (W) Data is placed in the FDK buffer during the FDK Selection state or the FDK Information Entry state. This data is read by the FDK Switch state in order to identify which next state the terminal should go to. Table 32: FDK Switch state entries

Entry

Definition

1

state type

2

FDK A next state no.

3

FDK B next state no.

4

FDK C next state no.

5

FDK D next state no.

6

FDK F next state no.

7

FDK G next state no.

8

FDK H next state no.

9

FDK I next state no.

The FDK Switch (W) state entries are defined as follows: State type Entry number: 1 Valid range:

W

Description:

This state ID identifies this state table as a FDK Switch state table.

FDK A Next state No. Entry number: 2 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

U25604-J-Z745-1-7600

October 2004

123

States

Configuration Data

FDK B Next state No. Entry number: 3 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

FDK C Next state No. Entry number: 4 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

FDK D Next state No. Entry number: 5 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

FDK F Next state No. Entry number: 6 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

FDK G Next state No. Entry number: 7 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

124

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

FDK H Next state No. Entry number: 8 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

FDK I Next state No. Entry number: 9 Valid range:

000-254, 256-999

Description:

State number terminal goes to depending on key code stored in FDK buffer.

U25604-J-Z745-1-7600

October 2004

125

States

Configuration Data

FDK Information Entry State (X) When the cardholder selects an FDK, this state places the corresponding value in the general purpose buffer or amount buffer that you have specified in table entry 7. Table entries 2-9 in the extension to this state contain values relating to the FDK’s. You can use this function, for example, where a screen offers a selection of fixed amounts that the cardholder can select by pressing a particular FDK. This state translates the FDK selected by the cardholder into a value that is placed in the specified buffer. The FDK key code is stored in the FDK buffer for use by an FDK Switch state. Table 33: FDK Information Entry state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number.

4

cancel next state number

5

FDK next state number

6

extension state number

7

buffer ID

8

FDK’s active mask

9

reserved

The FDK Information Entry (X) state entries are defined as follows: State type Entry number: 1 Valid range:

X

Description:

This state ID identifies this state table as the FDK Information Entry state.

126

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Screen number Entry number: 2 Valid range:

010-999

Description:

Display screen that prompts key selection by the consumer.

Time-out Next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if the consumer fails to respond to the message on screen within the permitted time limit. Enter 255 if the time-out function is not required.

Cancel Next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if the cancel key is pressed.

FDK Next state Entry number: 5 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if an FDK is pressed.

Extension State Number Entry number: 6 Valid range:

000-254, 256-999

Description:

State number of the extension state containing assigned values for the 8 FDK’s.

U25604-J-Z745-1-7600

October 2004

127

States

Configuration Data

Buffer ID Entry number: 7 Valid range:

010-039

Description:

Identifies which buffer is to be edited and the number of zeros to add to the values specified in the extension state. 01X = general purpose buffer B 02X = general purpose buffer C 03X = amount buffer X - specifies the number of zeros in the range 0-9.

If Amount buffer is used, the amount buffer will contain 8 or 12 digits, depending on the option selected. If this state is followed by an amount check state the amount entered is assumed to be a whole amount. FDK Active Mask Entry number: 8 Valid range:

000-255

Description:

Specifies the FDK’s that are active during this state. Each bit relates to an FDK. Bit 0 relates to FDK A, bit 7 relates to FDK I. If a bit is ‘1’ the relative FDK is active. If a bit is ‘0’ the relative FDK is inactive. The eight bits the binary equivalent of an FDK active mask. For example in the following mask: b7 0

b6 1

b5 0

b4 1

b3 1

b2 1

b1 0

b0 1

the three decimal characters in table entry 8 are 093 and the active FDK’s are A, C, D, F and H. Reserved Entry number: 9 Valid range:

000

Description:

Must be 000.

128

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Extension to State (X) This state is the Extension state to the FDK Information Entry state (X). Table 34: Extension state entries

Entry

Definition

1

state type

2

value stored if FDK A is pressed

3

value stored if FDK B is pressed

4

value stored if FDK C is pressed

5

value stored if FDK D is pressed

6

value stored if FDK F is pressed

7

value stored if FDK G is pressed

8

value stored if FDK H is pressed

9

value stored if FDK I is pressed

The Extension state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as the Extension state to the FDK Information Entry state.

Value stored if FDK A is pressed Entry number: 2 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

U25604-J-Z745-1-7600

October 2004

129

States

Configuration Data

Value stored if FDK B is pressed Entry number: 3 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

Value stored if FDK C is pressed Entry number: 4 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

Value stored if FDK D is pressed Entry number: 5 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

Value stored if FDK F is pressed Entry number: 6 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDk Information Entry state (table entry 7) if the specified FDK is pressed.

Value stored if FDK G is pressed Entry number: 7 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

130

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Value stored if FDK H is pressed Entry number: 8 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

Value stored if FDK I is pressed Entry number: 9 Valid range:

000-999

Description:

Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.

U25604-J-Z745-1-7600

October 2004

131

States

Configuration Data

Eight FDK Selection State (Y) This state reads the FDK selected by the cardholder, stores the key code in an FDK buffer for use by an FDK switch state, and updates the operation code buffer. If you do not specify an extension state in table entry 6, the key code of the FDK selected by the cardholder is stored directly in the operation code buffer. If you do specify an extension state, the key code is translated into three pseudo key codes, which are then stored in the operation code buffer. You can specify a second extension state in table entry 9 to identify the screen bases for multi-language screen displays. If you do not specify this extension state, then multi-language is not used. Table 35: Eight FDK Selection state entries

Entry

Definition

1

state type

2

screen number

3

time-out next state number

4

cancel next state number

5

FDK next state number

6

extension state number

7

buffer positions

8

FDK’s active mask

9

multi language extension state number

The Eight FDK Selection state (Y) state entries are defined as follows: State type Entry number: 1 Valid range:

Y

Description:

The state type entry identifies this state table as the Eight FDK Selection state table.

132

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Screen number Entry number: 2 Valid range:

000-999

Description:

Display screen which prompts key selection by the cardholder.

Time-out next state number Entry number: 3 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if the cardholder does not respond to the message on screen within the specified time limit. Enter 255 if the time-out function is not required.

Cancel next state number Entry number: 4 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if the cardholder presses the cancel key.

FDK next state number Entry number: 5 Valid range:

000-254, 256-999

Description:

State number the terminal goes to if the cardholder presses an FDK.

Extension state number Entry number: 6 Valid range:

000-254, 256-999

Description:

State number of extension state containing assigned operation codes for the 8 FDK’s. If there is no extension state enter 255.

U25604-J-Z745-1-7600

October 2004

133

States

Configuration Data

Buffer positions Entry number: 7 Valid range:

000-777

Description:

no extension state: This defines the operation code buffer position to be edited by a value in the range ‘000’ to ‘007’. extension state: This specifies three bytes of the operation code buffer to be set to the values specified in the extension state. Three numeric values, each in the range ‘0’ to ‘7’, are specified to define three positions in the 8 byte operation code buffer to be edited. These three values must be ordered to correspond with the edit characters in the extension state. If no buffer positions or less than three buffer positions are to be edited, this is specified in the extension state.

FDK’s active Mask Entry number: 8 Valid range:

000-255

Description:

Specifies the FDK’s that are active during this state. Each bit relates to an FDK. Bit 0 relates to FDK A, bit 7 relates to FDK I. If a bit is 1 the relative FDK is active. If a bit is 0 the relative FDK is inactive.

The eight bits represent the binary equivalent of an FDK active mask. For example in the following mask, the three decimal characters in the table entry are 183 and the active FDK`s are A, B, C, F, G, and I. BIT mask: b7 b6 1 0

b5 1

b4 1

b3 0

b2 1

b1 1

b0 1

Multi language Extension state number Entry number: 9 Valid range:

000-254, 256-999

Description:

If the state selects the multi language screen base, this contains the extension state number. If there is no extension state, enter 000 or 255.

134

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Extension to State (Y) This state is the Extension state to the Eight FDK Selection state (Y). Table 36: Extension state entries

Entry

Definition

1

state type

2

operation code stored if FDK A pressed

3

operation code stored if FDK B pressed

4

operation code stored if FDK C pressed

5

operation code stored if FDK D pressed

6

operation code stored if FDK F pressed

7

operation code stored if FDK G pressed

8

operation code stored if FDK H pressed

9

operation code stored if FDK I pressed

The Extension state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

Identifies this state table as the Extension state for the Eight FDK Selection state table.

U25604-J-Z745-1-7600

October 2004

135

States

Configuration Data

Operation Code stored if FDK pressed Entry number: 2-9 Valid range:

‘A’ - ‘I’, ’@’ or 1 - 9, 0

Description:

This table entry contains the operation code characters to be written to the operation code buffer if the specified FDK is pressed. Three characters are specified for each code, which must be in the range ‘A’ - ‘I’. They are written in order to the three positions specified in the Eight FDK Selection state table (entry 7). Enter ‘@’ if no character is to be written to a specified position in the buffer (fields are unchanged).

The values 1 to 9 and 0 represent the characters ’A’ - ‘I’, and ’@’.

Multi Language Extension to State (Y) This state is the Multi Language Extension state to the Eight FDK Selection state (Y). Table 37: Extension state entries

Entry

Definition

1

state type

2

screen language offset if FDK A is pressed

3

screen language offset if FDK B is pressed

4

screen language offset if FDK C is pressed

5

screen language offset if FDK D is pressed

6

screen language offset if FDK F is pressed

7

screen language offset if FDK G is pressed

8

screen language offset if FDK H is pressed

9

screen language offset if FDK I is pressed

136

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

The Multi Language Extension state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

Identifies this state table as the Multi Language Extension state for the Eight FDK Selection state table.

Screen language offset if FDK pressed Entry number: 2-9 Valid range:

000-999

Description:

Each table entry contains the screen number of the first screen for each language group. The initial offset is 000, and all unused fields should contain this value.

U25604-J-Z745-1-7600

October 2004

137

States

Configuration Data

Audio Control State (i) The Audio Control State allows the consumer to set the volume for the voice message that will be played for the duration of the current transaction. Furthermore the consumer can switch between the audio channels of the sound card. If the terminal has a sound card installed, the left the two channels (left and right channel) can be connected to a loudspeaker and the right channel can be connected to a headphone jack (if physically installed). The state table sets which audio channels are in use on entry to this state, and whether the cardholder will be given the option to adjust the volume. If the cardholder is to be given the option, then a message prompting the cardholder to adjust the volume is played repeatedly. The message is not played if the option is not offered. The cardholder may press: ●

FDKs to increase or decrease the volume This functionality can be disabled by setting entry 7 in the state table. If you map the FDKs to the numeric keyboard, the cardholder can adjust the volume by pressing numeric keys instead of the FDKs

●

ENTER to set the volume at its current level. The state takes the Function Complete Next State exit

●

CANCEL to return the volume to its default level. The state takes the Function Complete Next State exit.

If the cardholder does not press any keys within the time specified by Timer 00, then this state invokes the Time Out State. Make sure that the screen associated with the Time Out State is helpful to cardholders with visual difficulties. For example, you can map FDKs to the PIN pad and play an appropriate message. The Audio Control State's prompt screen must not contain an audio message. The volume returns to its default level on exit from the Close State.

See Table 38 on the following page for state table entry definitions:

138

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Table 38: Audio Control state entries

Entry

Definition

1

state type

2

Prompt screen

3

Timeout next state

4

Function complete next state

5

Increase Volume FDK mask

6

Decrease Volume FDK mask

7

Audio control

8

Audio message

9

Reserved

The Audio Control (‘i’) state entries are defined as follows: State type Entry number: 1 Valid range:

’i’

Description:

This state ID identifies this state table as an Audio Control state.

Prompt screen Entry number: 2 Valid range:

000-999

Description:

Prompts user to adjust volume. This screen is only displayed if table entry 7 indicates that the volume is to be adjusted.

Timeout next state Entry number: 3 Valid range:

000-254; 256-999

Description:

State number to which the terminal proceeds if the cardholder has responded within the time specified by Timer 00. Value 255 disables the time-out feature.

U25604-J-Z745-1-7600

October 2004

139

States

Configuration Data

Function complete next state Entry number: 4 Valid range:

000-254; 256-999

Description:

State number to which the terminal proceeds if: - the cardholder selects Cancel or Enter - table entry 7 selects a channel but disables volume adjustment - there is no audio file present on the terminal

Increase Volume FDK mask Entry number: 5 Valid range:

000-255

Description:

Specifies which FDKs will increase the volume in this state. Bit 0 relates to FDK A, bit 1 to FDK B etc. If a bit is 1 then the FDK referred to is active; otherwise it is inactive. The FDKs are not enabled unless the least significant bit of table entry 7 is 1. A value of 000 disables this entry and is discouraged.

Decrease Volume FDK mask Entry number: 6 Valid range:

000-255

Description:

Specifies which FDKs will decrease the volume in this state. Bit 0 relates to FDK A, bit 1 to FDK B etc. If a bit is 1 then the FDK referred to is active; otherwise it is inactive. The FDKs are not enabled unless the least significant bit of table entry 7 is 1. A value of ”000” disables this entry and is discouraged. Where the same FDK is specified as having both Increase Volume and Decrease Volume functions, Decrease Volume takes precedence.

140

October 2004

U25604-J-Z745-1-7600

States

Audio control Entry number: 7 Valid range:

000-015

Description:

This entry is bitmapped:

© Siemens Nixdorf Informationssystem e AG 1995

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm

Configuration Data

Bit Definition 0

0 - volume adjust off 1 - volume adjust on

1

0 - disables effect of bits 2 and 3 1 - enables effect of bits 2 and 3

2

0 - disables loudspeaker (left channel) 1 - enables loudspeaker (left channel)

3

0 - disables audio jack (right channel) 1 - enables audio jack (right channel)

EXAMPLE: For instance, a value of 007 enables volume adjustment and directs audio output to the speaker; 015 enables volume adjustment and enables both channels. A value of 003 is discouraged in this entry: this would turn both channels off but enable volume adjustment. If this entry does not instruct a change to the audio channel in use, the current audio channel(s) will remain in use. Audio message Entry number: 8 Valid range:

000 or 999

Description:

Specifies which audio message will be played. Provided that table entry 7 indicates that the volume is to be adjusted, the message will be played repeatedly until the state is exited. If there is no audio file present on the terminal, it will take the Function Complete Next State exit.

U25604-J-Z745-1-7600

October 2004

141

States

Configuration Data

Hardware Fitness State (‘h’) The Hardware Fitness state is a special state designed by Wincor Nixdorf that can be used for specific purposes on Wincor Nixdorf terminals. This state allows to jump into another state flow depending on the actual hardware fitness of the devices defined in the state table. Also an extension state can be defined which allows additional decisions to jump to a defined next state. If multiple conditions apply, the priority is top down; i.e. state ‘h’ entry 3 (reboot) has the highest priority over all values. The value of the last table entry of the extension state becomes active only if no previous condition was fullfilled. The general order is: reboot, device fatal, device warning. Table 39: Hardware Fitness state entries

Entry

Definition

1

state type

2

no error next state

3

next state if reboot requested (defined in CCERRMAP)

4

next state if CDM fatal error

5

next state if journal fatal error

6

next state if receipt fatal error

7

next state if deposit fatal error

8

reserved for future use

9

extension state number

The Hardware Fitness (‘h’) state entries are defined as follows: State type Entry number: 1 Valid range:

‘h’

Description:

This state ID identifies this state table as a Hardware Fitness state.

142

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

No error next state Entry number: 2 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if none of the subsequent hardware conditions apply.

Next state if reboot requested Entry number: 3 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if a system reboot has been requested. This reboot request can be issued by errors of classes which have set the reboot flag. This can be used to prevent offering other functions to the customer after serious malfunctions requiring a system reboot have occurred.

Next state if Cash Dispenser fatal error Entry number: 4 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the cash dispenser is fatal.

Next state if Journal fatal error Entry number: 5 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the journal printer is fatal.

Next state if Receipt fatal error Entry number: 6 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the receipt printer is fatal.

U25604-J-Z745-1-7600

October 2004

143

States

Configuration Data

Next state if Deposit fatal error Entry number: 7 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the deposit module is fatal.

Reserved for future use Entry number: 8 Valid range:

000 or 255

Description:

Entry 8 is reserved and must be 000 or 255.

Extension state number Entry number: 9 Valid range:

000-999

Description:

State number of the extension state (Z) containing additional device conditions.

144

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Extension to State (‘h’) The Extension state to the Hardware Fitness state contains additional conditions to go to the specified next state. Typically for NDC the Hardware Fitness Extension state is a Z state. Table 40: Hardware Fitness Extension state entries

Entry

Definition

1

state type

2

denomination type

3

next state if denomination not available

4

next state if journal warning

5

next state if receipt warning

6

next state if deposit warning

7

reserved for future use

8

reserved for future use

9

reserved for future use

The Hardware Fitness Extension (Z) state entries are defined as follows: State type Entry number: 1 Valid range:

Z

Description:

This state ID identifies this state table as a Hardware Fitness Extension state.

U25604-J-Z745-1-7600

October 2004

145

States

Configuration Data

Denomination Type Entry number: 2 Valid range:

000-044

Description:

The data field is divided in three digits:

First digit: Reserved, always zero. Second digit:

Specifies the denomination type of cash cassettes which should be verified as out of notes (fatal condition). The entry range 1-4 indicates denomination Type 1 to 4.

Third digit: Specifies which cassette position will be checked for low notes (warning condition). The entry range 1-4 indicates the denomination Type 1 to 4. Next state if Denomination not available Entry number: 3 Valid range:

000-999

Description:

The number of state to which the terminal proceeds if the Denomination is not available.

Next state if Journal warning Entry number: 4 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the journal printer has a warning status.

Next state if Receipt warning Entry number: 5 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the receipt printer has a warning status.

146

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Next state if Deposit warning Entry number: 6 Valid range:

000-999

Description:

The number of the state to which the terminal proceeds if the deposit module has a warning status.

Reserved Entry number: 7-9 Valid range:

000 or 255

Description:

Entries 6-9 are reserved and must be 000 or 255.

U25604-J-Z745-1-7600

October 2004

147

States

Configuration Data

Smart FIT Check State (‘k’) This state is only required when chip data is to be used in a FIT check. The Smart FIT Check state should be entered after the chip data a read from the smart card and stored in the magnetic track buffers of the application. The Smart FIT Check state then performs a FIT check on the contents of the three track buffers. It is possible to create more than one Smart FIT Check state to accomodate multiple FIT checks. This would allow different FIT checks to be performed on data from the same card. Table 41: Smart FIT Check State

Entry

Definition

1

state type

2

reserved

3

good read next state number

4

error (misread) screen number

5

read Condition 1

6

read Condition 2

7

read Condition 3

8

card return flag

9

no FIT match next state

The Smart FIT Check (’k’) state entries are defined as follows: State type Entry number: 1 Valid range:

’k’

Description:

This state ID identifies this state table as a Smart FIT Check state.

148

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

Reserved Entry number: 2 Valid range:

0

Description:

Not used - set to 0. This is left blank to align the following table entries to the same positions as those in the Card Read State, allowing common FIT check procedures to be used.

Good read next state number Entry number: 3 Valid range:

000-999

Description:

State number to which the terminal goes if the Financial Institution number on the card matches a Financial Institution number in the FIT.

Error (misread) screen number Entry number: 4 Valid range:

000-999

Description:

If the read conditions are not satisfied due to a bad card or a mechanism error, the card is ejected and this screen is displayed.

Read condition 1 Entry number: 5 Valid range:

see description

Description:

First of three entries indicating which card track buffer(s) will be read. Bit 0 1 2 3-7

U25604-J-Z745-1-7600

Description Read track 3 Read track 2 Read track 1 Reserved

October 2004

149

States

Configuration Data

Read condition 2 Entry number: 6 Valid range:

see description

Description:

Second of three entries indicating which card track buffer(s) will be read. Bit 0 1 2 3-7

Description Read track 3 Read track 2 Read track 1 Reserved

Read condition 3 Entry number: 7 Valid range:

see description

Description:

Third of three entries indicating which card track buffer(s) will be read. Bit 0 1 2 3-7

Description Read track 3 Read track 2 Read track 1 Reserved

Card return flag Entry number: 8 Valid range:

000-999

Description:

Tells the terminal when the card should be returned to the cardholder: 000 - eject the card immediately 001 - return the card as specified by a transaction reply message.

150

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

States

No FIT match next state number Entry number: 9 Valid range:

000 or 999

Description:

This is the state is executed if the FIT check fails. It may be a close state or a return to another Chip exit state which places the chip data in the read buffers before calling a different Smart FIT Check state with different read conditions. If FITs are not used, this entry must be 000.

U25604-J-Z745-1-7600

October 2004

151

States

Configuration Data

Skip State step The Skip state steps can be used to skip non supported states which can be just ignored through a good next state number definition. Table 42: Skip state step

Step name

Definition

DC_NEXT_1

uses field 1 for good state next operation

DC_NEXT_2

uses field 2 for good state next operation

DC_NEXT_3

uses field 3 for good state next operation

DC_NEXT_4

uses field 4 for good state next operation

DC_NEXT_5

uses field 5 for good state next operation

DC_NEXT_6

uses field 6 for good state next operation

DC_NEXT_7

uses field 7 for good state next operation

DC_NEXT_8

uses field 8 for good state next operation

152

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

Screens Screen data is also a type of configuration data. All screens are assigned to a decimal number between 000 and 999. Furthermore the NDC+ protocol is using reserved screen numbers like C00 through C06, Axx, Dxx, Exx, and so on that can be used for specific functions. Restrictively ProCash/NDC and ProConsult/NDC just can store the reserved screens in the registry if they are downloaded from host. The only reserved screens supported, are C00 - C06. For detailed descripton see section “Reserved Screens” on page 162. Normally, the screen number and following data are down-line loaded to the terminal using the Screens Table Load command message. Refer to section “Screen Data Load” on page 242 for details. However, new screens can be sent by the network in a Transaction Reply command message. Unused screens do not need to be down-line loaded. The terminal stores the screen data in the registry location “..\LYNXCI\SCREEN”. Wincor Nixdorf terminals can display screens in the grid of 32 columns by 16 rows. See section “Screen Design Worksheet” on page 378.

Screen Control Characters Nearly in all screens serveral control characters are included, like cursor positioning, set an overlay screen, clear screen, display Track 1 information, etc.. A global overview gives Table “Screen control characters” on page 154. ProCash/NDC and ProConsult/NDC support following major control functions: ●

Clears a screen

●

Sets the screen cursor

●

Delays then shows a character

●

Shows inverse video characters

●

Allows blinking

U25604-J-Z745-1-7600

October 2004

153

Screens

Configuration Data

Screen delimiters The field separator (FS) or group separator (GS) at the end of the message are screen delimiters. Each screen data field must be terminated by one of these two screen delimiters. Normally, FS separates each screen data field in a Screens Table Load command message. The end of the message terminates the last screen data field in a Screens Table Load command message. Table 43: Screen control characters cross-reference

Control Code CR FF HT SI SO VT

ASCII HEX Equivalent 0D 0C 09 0F 0E 0B

EBCDIC HEX Equivalent 0D 0C 05 0F 0E 0B

Table 44: Screen control characters

Control Code CR FF HT

SI

SO

VT

154

Description moves the cursor to the first position in the current row clears the screen and positions the cursor to position @,@ on the display grid causes the customer’s name, encoded on track 1 of the customer’s card, to be shown on the customer display, starting at the current customer display cursor position sets the cursor to the position specified by the two bytes following SI. the first byte is the row, and the second byte is the column. data shown on the screen remains unchanged. overlays the screen specified by the three bytes following SO. screen data can be nested or overlaid to five levels using the control character SO. shows an alternate character on the customer display. the alternate character is specified by the byte following VT

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

CR control character The CR control character moves the cursor to column @ in the following row. FF control character The FF control character clears the screen with the default foreground and background colors. The cursor is set to the top left hand corner (row @, column @) of the screen. Screen blinking will be switched off. HT control character The HT control character inserts the name from track 1 of the customer’s activator card into the screen data. The terminal displays the name starting at the current cursor position. SI control character The SI control sequence moves the cursor to a specified row and column. The format of the control sequence is as follows: SI 1A The terminal places the cursor at row 1, column A. Any of the 16 rows can be selected by using a row select character from ’@’ through 3. Any of the 32 columns can be selected by using a column select character ’@’ through ’?’. See also the grid graphic in section “Screen Design Worksheet” on page 378. VT control character The VT control sequence is used to display characters from secondary character set. ASCII codes in the range 20 - 7F hex, preceded by a ’VT’ character, forces displaying characters from the Customer Graphic 1 character set. The format of the control sequence is as follows:

VT C

U25604-J-Z745-1-7600

October 2004

155

Screens

Configuration Data

SO control character The SO control sequence inserts a specified screen into the current screen. The format of the control sequence is as follows: SO nnn The network uses the control character SO to call another screen. This technique is called nesting. Nesting is accomplished by placing control character SO followed by a three-digit screen number within a current screen. The maximum number of nesting levels is five. When using nested screens, the maximum number of characters per screen is as follows: ●

screen 1: 600 characters

●

screens 2 through 6: 310 characters each

The network can use an SO control sequence along with an ESC [z control sequence to show animated screens. In a typical animation sequence, the last screen calls the first screen again. To prevent infinite nesting when using animation, the ESC [z control sequence must be the last instruction in each animation screen.

156

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

Table 45: Screen escape sequences cross-reference

Escape Sequence ESC P ESC [ ESC ( ESC )

ASCII HEX Equivalent 1B 50 1B 5B 1B 28 1B 29

EBCDIC HEX Equivalent 27 D7 27 63 27 4D 27 5D

Table 46: Screen escape sequences

Escape Parameters Description Sequence ESC [...m kk;ff;bb Activates blinking characters and sets foreground and background color. Example: kk = 00 - blinking off; 10 - blinking on (max. 100 ESC characters per screen) [10;67;71m ff = foreground color bb = background color ESC [...z ttt Display idle sequence. Displays the screen in the specified time ttt. ESC ( c Select primary character set; (c = font type) ESC ) c Select secondary character set; (c = font type) ESC P0... nnn Voice control; Defines a voice message number ;0ESC\ that is played when the screen is displayed. Voice files have to be stored in the path locations defined via parameter AUDIOx_PATH for each language group (x = language group) in section “..\LYNXCI\SCREEN”. ESC P1.. nn Logo control; displays number nn logo. (e.g. ESC\ ESCP199ESC\) ESC P2... nnn Picture control; diplays number nnn picture. (e.g. ESC\ ESCP2999ESC\) ESC PE... path Picture control; diplays a graphic specified via ESC\ path. (e.g. ESCPEC:\PICT\PICTURE.PCXESC\) The backslash character (\) is stored in hexadecimal format (\5c) in the registry. ESC is stored as \1b. Example entry for ESCPE: CONTENTS = “\1bPEC:\5cPICT\5cPICTURE.PCX\1b\5c”

U25604-J-Z745-1-7600

October 2004

157

Screens

Configuration Data

Displaying Graphics as Icons ProCash/NDC and ProConsult/NDC can display *.pcx, or *.bmp files which are smaller than the whole screen as an icon. Therefore a cursor positioning is required to fit the icon in the right place. You can add text above or below the icon without modifying icon data. Also, text can share a row with an icon. However, if text and the icon share a row, one cannot overlap on the other, and one space must separate the text and the icon. Their combined lengths cannot extend beyond the end of the row. Non supported graphic extensions, for example specified in a downloaded screen using the ESCPE control sequence can be mapped to another file extension supported by ProCash/NDC via parameter “PICTURE_EXT_XXX”. See ProCash/NDC ProConsult/NDC Installation manual section Graphic and Video file extension mapping for detailed descriptions how to map graphic and video files.

Full Screen graphics Wincor Nixdorf terminals support full screen graphics as *.pcx, or *.bmp formats. With these graphics it is possible to show animation’s and text together instead of using icons and/or text using WIN-NT font files. Additionally the text from the font files can be overlaid (transparent mode) onto full screen graphics. The possibilities are endless. Mixtures of all kinds of graphics in one customization image are possible, PCX’s, BMP’s with/without overlaid text. Display resolutions ProCash/NDC and ProConsult/NDC support following display resolutions and color depths: Mode

Resolution

color depths [1]

VGA

640x480

16

SVGA

640x480

256, 65535 (16 bit)

SVGA

800x600

256, 65535 (16 bit)

SVGA

1024x768

256, 65535 (16 bit)

[1] -

158

PCX graphics are supported in 16 or 256 colors only.

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

Displaying MacroMedia Flash executables ProCash/NDC and ProConsult/NDC are able to display Flash video animations. Flash files can be created via different utilities like MacroMedia Flash. A Flash animation has to be stored as an executable file like “MyFlash.exe”. Please refer to ProCash/NDC ProConsult/NDC Installation manual to get detailed information how to configure Flash animations in ProCash/NDC and ProConsult/NDC. Important Note:

You have to install Internet Explorer 5.5 or higher to be able to display Flash files.

Displaying Video files In addition to the graphics, ProCash/NDC and ProConsult/NDC are able to display AVI and MPG video files. They can be configured in the same way as the graphic files. The only difference is the file extension, which has to be *.avi, *.mpg or *.mpeg. If a video file is specified within the screen flow, an external program named “ccMciPly.exe” located in directory “C:\PROTOPAS\BIN” is called that performs function calls to the API of the MCI player. If you want to play video files it is necessary to check if the video file can be played with the current installed codec on the ATM. This can be easily tested if you double click the video file. After you have double clicked the file, the Microsoft MCI player should come up automatically to play the video. If you get an error or the MCI player doesn’t come up, you have to install the correct Video Compression Codec. Some codecs will be installed together with the Internet Explorer or Media Player installation. The current version of the Video Compression Codecs can be viewed in the “Multimedia” dialog box in the Control Panel of Windows. IMPORTANT NOTE: Since version $MOD$ 020701 1009 of “ccMciPly.exe”, videos are running in the topmost window. That means, videos are always played in the foreground window. Other open windows behind (previously accessed via ALT-TAB) cannot be reached any more. The only chance to get access to other open windows is via key combination ALT+F4 on the alpha keyboard. ALT+F4 terminates the program “ccMciPly.exe”.

U25604-J-Z745-1-7600

October 2004

159

Screens

Configuration Data

Voice Control If the terminal has installed a sound card and the path of the voice files are configured via AUDIOx_PATH (see ProCash/NDC ProConsult/NDC Installation manual for detailed definition of this parameter), the terminal attempts to play pre-recored messages in some states. Make sure that the pre-recorded message is brief enough to play completely before the state is timed out. The terminal attempts to play messages at following times: Auto Voice Feature The following voice messages are spoken if the Auto Voice Feature option 02 is set to 001 in the “Enhanced Configuration Parameters Load” message. See also Table 47 for the message description. ●

PIN Entry (Message 7) The message starts during a PIN Entry state or Enhanced PIN Entry state when the card has been read and recognized.

●

Transaction Request (Message 1) The message starts when a Transaction Request message is sent to the host.

●

Card Taken (Message 8) The message starts as soon as a card is taken in the Close state. If the card has already been taken, the message starts on entry to the Close state.

Table 47: Default Voice Message files

Audio (*.WAV) file 1.WAV 7.WAV 8.WAV

Message Number 1 7 8

Message “your transaction is being processed” “please enter your personal identification number” “thank you for using this atm”

NOTE: The three WAVE message files are recorded as male voice

160

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

Audible Echo on Keyboard ProCash/NDC and ProConsult/NDC also support Audio Echo on Keyboard if Option 31 is enabled in the “Enhanced Configuration Parameters Load” message (see Table 48). Table 48 lists the wave files used if Audio Echo on Keyboard is enabled: Table 48: Default WAVE files for Audio Echo on Keyboard

Audio (*.WAV) file ZERO.WAV ONE.WAV TWO.WAV THREE.WAV FOUR.WAV FIVE.WAV SIX.WAV SEVEN.WAV EIGHT.WAV NINE.WAV

Phrase “zero” “one” “two” “three” “four” “five” “six” “seven” “eight” “nine”

NOTE: The WAVE files are recorded as female voice

U25604-J-Z745-1-7600

October 2004

161

Screens

Configuration Data

Reserved Screens Wincor Nixdorf terminals contain reserved screens C00 through C06 stored in the registry location “..\LYNXCI\SCREEN”. These screens contain default data which is displayed when no reserved screen is downloaded with its own data. Table 49: Downloaded reserved screens supported by Wincor Nixdorf terminals

Screen No.

Function

C00

More time screen; This screen prompts the customer who has failed to respond to a request for keyboard input within the specified keyboard response time.

C01

Offline screen; This screen appears on the customer display when the terminal is offline. The screen’s characters default to offline at terminal power up or reset.

C02

Out of Service screen; This screen appears on the customer display when the terminal is in out-of-service mode. The screen’s characters default to out-of-service at terminal power-up or reset.

C03

Supply screen. This screen is displayed while the terminal is in supervisor mode.

C04

Card capture screen; This screen is displayed when the terminal captures a card as a result of a card reader failure

C05

Cardholder tampering screen; This screen is displayed when cardholder tampering is suspected and the terminal enters suspend mode.

C06

Temporarily Out of Service screen

162

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

General use of default reserved C screens In addition to Diebold the reserved screens C00-C06 can be downloaded. If one of those screens is not downloaded, the following defaults are used: Default screen

Downloaded screen

C00

000

C01

001

C02

002

C03

003

C04

none

C05

C02 / 002

C06

C02 / 002 If one or more of the reserved screens are not downloaded by the host you can create your own reserved screens in PARAC configuration file ’CUSTOM.PPF’. In Registry section ”..\LYNXCI\SCREEN” the new subsections of your new defined C screens will be created and updated if you start the PARAC run. See ProCash/NDC ProConsult/NDC Installation manual for details.

Screen C00 Screen C00 prompts customers who fail to respond within a specified time interval. Screen C00 must be defined and must conform to the following operation key A and B requirements: ●

if operation key A is pressed, the terminal returns to the original state in which the time-out occurred. The customer presses this key to request more time.

●

if operation key B is pressed, the terminal returns to the time-out next state entry of the original state in which the time-out occurred. Normally, this timeout next state is a close state.

Screen C01 Screen C01 is displayed when the terminal is in offline mode.

U25604-J-Z745-1-7600

October 2004

163

Screens

Configuration Data

Screen C02 Screen 002 is displayed when the terminal is in out-of-service mode. Screen C03 Screen C03 is the supply screen. This screen is displayed when the terminal is in supervisor mode. Screen C04 Screen C04 is displayed when the terminal captures the card in case of a card reader failure. When this occurs, the next state is executed. This screen is displayed as long as in the value of Timer 2 specified. Screen C05 Screen C05 is displayed when cardholder tampering is suspected and the terminal enters Suspend mode. The Suspend mode condition as an error Severity 3 can be configured in CCERRMAP. See ProCash/NDC ProConsult/NDC Installation manual for details. Screen C06 Screen C06 is displayed when the terminal is temporarily in out of service mode. This screen is displayed under following conditions: ●

When specified in a go out of service comand from host

●

On exit supervisor mode to out of service if supervisor mode was entered from in service and the auto return to previous mode is not set.

●

If supply mode is entered from out of service while displaying screen C06.

164

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Screens

Language Selection You can create multi language customer screens to be displayed as requested from one set of state tables. This can be defined via group definitions for each language, in which the equivalent screen for all languages has the same relative position within the group. Make sure that all the screens for which a choice of languages can be made are in the group. Note that nested screens must have absolute positions. The first group must start at ’000’, and contain thos screens fro which language selection is not possible. That is, screens displayed from the Card Read state and Language Select from Card state. Screens normally associated with not in service conditions, such out of service, supervisor or offline, should also be in this group if the ’Cxx’ default screens are used. You do not need to cahnge the state tables, but you must include an Eight FDK Selection Function state, or Language Select from Card state, in order to select the language.

EXAMPLE: If four languages are required, the screen group bases could be: – Language A - ’000’ – Language B - ’100’ – Language C - ’200’ – Language D - ’300’ If a screen ’055’ is displayed from a state table, the screen is downloaded as: – ’055’ for Language A – ’155’ for Language B – ’255’ for Language C – ’355’ for Language D

U25604-J-Z745-1-7600

October 2004

165

Miscellaneous Configuration Data

Configuration Data

Miscellaneous Configuration Data Miscellaneous configuration data is down-line loaded via (Enhanced) Customisation Table Load command message from network to terminal. Refer to section ”Configuration Parameters Load” on page 245 and to section ”Enhanced Configuration Parameters Load” on page 249 for the message format. The (Enhanced) Customisation Table Load command message has three data fields: ●

terminal parameters

●

logical unit number

●

timer data

Each field is preceded by a field separator (FS). The following sections describe the contents of these data fields.

Terminal Parameters The terminal parameters data fields are described in section ”Configuration Parameters Load” on page 245 and section ”Enhanced Configuration Parameters Load” on page 249.

Logical Unit Number (LUNO) The second piece of information in the miscellaneous configuration data is called the Logical Unit No. (LUNO). The LUNO is a unique number that indicates which terminal has transmitted a message. If the key-entry person enters a machine number, the terminal places the terminal number at the end of the LUNO in the transaction request, solicited status, and unsolicited status messages (except the power failure unsolicited status message).

166

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Miscellaneous Configuration Data

Timer Data The third piece of information in the miscellaneous configuration data is called timer data. Some timers must be down-line loaded by the network because they do not have default times. Other timers may be down-line loaded, but they do not have to be as they have default settings. The time-out intervals are specified as a number of 0.8 second segments (ticks). The number of ticks assigned to a timer can be 000 to 255. This gives each timer a time-out range of 0 to 204 seconds. Unless otherwise stated in the timer descriptions that follow, specifying a time-out interval of 000 causes the terminal to never take the time-out next state exit from a state. The data for each timer is down-line loaded in the sequence the timer number (2 bytes) then the number of 800-millisecond ticks (3 bytes). Timers are stored in registry location “..\LYNXCI\TIMER”. The timer values are stored in seconds.

U25604-J-Z745-1-7600

October 2004

167

Miscellaneous Configuration Data

Configuration Data

Table 50: Timer values

Timer Default value in PPF Timer Default value in PPF number (seconds / ticks) number (seconds / ticks) 00

030 / 038

86

018 / 023 (not used)

01

015 / 019

87

030 / 038 (not used)

02

005 / 006

94

030 / 038 (not used)

03

030 / 038

95

030 / 038

04

040 / 050

96

000 / 000

05

040 / 050

97

010 / 013 (not used)

06

030 / 038

98

030 / 038 (not used)

07

001 / 001

99

030 / 038

08

040 / 050

09

020 / 025

10

001 / 001

11

-

12-14

-

15

-

16-17

-

18

-

19

-

20

-

Timer 00 Timer 00 sets the keyboard response timeout interval. When a screen is displayed that prompts the customer to make a keyboard entry, the customer must respond within the timeout interval specified for timer 00. Otherwise, the terminal will exit its present state, display screen number 000, and start timer 01.

168

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Miscellaneous Configuration Data

Timer 01 Timer 01 sets the consumer response extension timeout interval. If the customer exceeds the timeout interval allowed for keyboard entry (timer 00), for deposit envelope insertion (timer 04, 08 or timer 20), or for securomatic insertion (timer 08), screen 000 is displayed. Screen 000 asks if the customer needs more time. Timer 01 is the timeout interval for the customer’s response to screen 000. The keyboard beeper sounds while this timer is active. If this timer expires for the keyboard, the terminal advances to timeout next state; if the timer expires for the deposit, the terminal sends a solicited status message to the network. Timer 02 Timer 02 sets the close state screen time-out interval. At the end of this interval, the terminal proceeds to the next state number specified in the close state. A timeout interval of 000 is not permitted for timer 02.

Timer 03 Timer 03 sets the communication message timeout interval. When the terminal is ready to transmit a Transaction Request message to the network, the terminal starts Timer 03. If the terminal does not receive a Transaction Reply command before Timer 03 expires, the terminal exits the transaction request state by going to the network response time-out next state number. Timer 04 Timer 04 sets the envelope insertion time-out interval for the depository. When a screen is displayed that prompts the customer to insert an envelope into the depository, the customer must respond within the time-out interval specified by timer 04; otherwise, the terminal exits its present state, displays screen 000 and starts timer 01. The keyboard beeper sounds while this timer is active. Timer 05 Timer 05 sets the withdrawal time-out interval for terminals with a withdrawal door. The maximum amount of time that the terminal waits for a customer to remove the cash is the sum of timers 05 and 07. After the cash has been counted and placed in the delivery mechanism, the terminal unlocks the delivery door and starts timer 05.

U25604-J-Z745-1-7600

October 2004

169

Miscellaneous Configuration Data

Configuration Data

●

If the customer fails to fully open the withdrawal door and clear the rear withdrawal area sensors before timer 05 expires (or to just fully open the door on terminals with a manual door), the terminal transmits the withdrawal door solicited status to the network indicating a fault and waits for a new Transaction Reply command message from the network.

●

If the customer fully opens the withdrawal door and clears the rear withdrawal area sensors before timer 05 expires (or just fully opens the door on terminals with a manual door), the terminal proceeds to timer 07.

Timer 06 Timer 06 sets the communications offline timeout interval. This timer is started each time the terminal receives a poll or select sequence from the network. If the terminal has not been polled or selected within the interval specified for timer 06, the terminal proceeds to offline mode (out-of-service to customers) and displays screen 001.

A timeout interval of 000 is not permitted for timer 06.

Timer 07 Timer 07 sets the withdrawal door open timeout interval. This timer specifies the amount of time that the terminal waits after the withdrawal door is fully opened before going to the next specified state. On all terminals with a delivery door, this timer starts after the withdrawal door is fully opened and either the sensors are cleared or timer 05 expires. On all terminals without a delivery door, this timer starts after timer 10 expires.

A timeout interval of 000 is not permitted for timer 07.

Timer 08 Timer 08 sets the envelope insertion timeout interval for the night safe depository. When a screen is displayed prompting the insertion of a deposit, the customer has to respond within the timeout interval specified by timer 08. Otherwise, the terminal exits its present state, displays screen 000 and starts timer 01.

170

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Miscellaneous Configuration Data

Timer 09 Timer 09 sets the customer timeout interval before a card capture attempt. If, during a close state, the card is presented to the customer and not removed within this time period, a card capture attempt is made. This timer starts after the terminal executes the card return function ID and at the beginning of the close state if the card was not returned at the card read state. Timers 02 and 09 start at the same time. When the card is removed, timer 09 stops. The default setting for timer 09 on power-up is 30 seconds (38 ticks).

A timeout interval of 000 is not permitted for timer 09.

Timer 10 Timer 10 sets the withdrawal timeout interval for terminals without a withdrawal door. Timer 10 sets the amount of time the beeper beeps while waiting for the customer to take the cash. After the terminal counts and places the cash in the withdrawal area, the terminal displays a Take Cash screen, starts timer 10, and activates the beeper. After timer 10 expires, the terminal stops the beeper and starts timer 07. Therefore, the total amount of time that the terminal waits for a customer to remove the cash is the sum of timers 10 and 07. A value of 000 in timer 10 will result in no beeping and zero time. The default setting for timer 10 on power-up is 006 ticks. Timer 11 (CSC450 with vandal shield only) Timer 11 sets the vandal shield delay time before closing. Timer 11 sets the amount of time the vandal shield delays before it begins to close. The vandal shield uses this timer if a value of 004 is in state entry 3 of the vandal shield state. Timer 11 defaults to 080 ticks on power-up.

U25604-J-Z745-1-7600

October 2004

171

Miscellaneous Configuration Data

Configuration Data

Timer 15 Timer 15 is used with the card read ‘T’ state (not used by Wincor Nixdorf terminals). Timer 18 Timer 18 sets the swipe card reader error screen timer (not used by ProCash/NDC and ProConsult/NDC application). Timer 20 Timer 20 sets the insertion timeout interval for the depository. If timer 20 is configured to a non-zero value, it is used instead of timer 04. Timer 20 allows seven seconds of silent time, after which the beeper starts at a slow rate for the remainder of the specified time. Timer 95 Timer 95 sets the statement retract timeout. This timer is used during the Close State processing. It determines when to retract a statement that has not been taken by the customer. The default value is 30 ticks and the timer is not used if you set a zero value. This timer is also used when Transaction Reply command ’S’ is sent in the transaction reply and the statement is laying in the collection tray of the statement printer. The timer will be started when this condition is detected. If the timer expires the statement is retracted and Transaction Reply command ’S’ commences. If the statement is taken before the timer expires, Transaction Reply command ’S’ commences without retract attempt. Timer 96 Timer 96 sets the statement present timeout. This timer is used only in the statement and continue function and is started regardless of whether or not a statement has been delivered. When the timer expires, the next state specified by the transaction reply command is entered. Timer value zero means no wait. Timer 99 Timer 99 specifies after what time the vandal guard close operation should be started when the consumer transaction has been finished.

172

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user5.fm © Siemens Nixdorf Informationssystem e AG 1995

Configuration Data

Local download feature

Local download feature The local download feature is useful if you want to overload the downloaded customization image (CI) from host with local defined settings. With local downloads you can skip unsupported functions or overwrite non legal values in states or screens and it allows to enhance the host configuration with new functions locally. In addition to the download modifications you can also change local ATM settings (e.g. graphic file locations or printer settings).

Configure local download Local download procedures can be called after following two situations: ●

ATM has received Config ID (Set Config ID command) from host

●

ATM has received Go in Service command from host

The local download process can be evaluated via two batch files. Depending on the existing file name the local download is called after the ATM has received the Config ID and/or a Go in Service command. The following table describes the filenames, location and in which situations the files are called: Filename

Directory

Called when

dcCfgId.cmd

C:\PROTOPAS\CONF

after Config ID received

dcInServ.cmd

C:\PROTOPAS\CONF

after Go in Service received

The contents of the files can be any command which is supported in a Windows command line window. Contents of dcCfgId.cmd or dcInServ.cmd: regedit -s stt010.reg

Description: Calls regedit silent (no screen appears) to update contents of stt010.reg. The contents of stt010.reg could contain following entries: REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProTopas\CurrentVersion\LYNXCI\STATE\010] "STEP_PARAM"="113217217013211012013003"

overloads values of state 010. Note:

The command job must return within 30 seconds.

U25604-J-Z745-1-7600

October 2004

173

Local download feature

174

Configuration Data

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User6.fm © Siemens Nixdorf Informationssysteme AG 1995

Security Features General Overview To understand and use the information in this section, you should understand some basic terms and concepts, which are defined below.

Algorithm

An algorithm is a structured mathematical procedure for solving a specific problem. The DES algorithm is designed to encrypt and decrypt blocks of data. The DES algorithm is not confidential and can be obtained by the general public. The keys used as part of the algorithm are what provides the confidentially

Data Encryption Standard [DES]

The Data Encryption Standard (DES) specifies an algorithm to be used in electronic hardware devices for the purpose of cryptographic protection of computer data.

Encryption keys

Encryption keys are numbers that are used as part of the PIN verification process and also for encrypting messages to and from the terminals. As the DES algorithm is available to the general public, the keys must be kept secret to ensure the confidentiality of the data being encrypted.

Personal Identification Number [PIN]

The Personal Identification Number (PIN) is the customer’s way of verifying his or her identity as established by an activator card. By entering this PIN, the customer is identified and can access the relevant accounts.

PIN verification PIN verification is the method of ensuring that the PIN entered on the ATM is the proper PIN for the card inserted in the ATM.

U25604-J-Z745-1-7600

October 2004

175

PIN and PIN Verification

Financial Institution Table [FIT]

Security Features

The Financial Institution Table (FIT) provides the following items to the network: – capacity of using multiple card formats and multiple institutions – the type of PIN verification – the encryption key (if PEKEY is used) that is used to encrypt a PIN, which is sent to the network – control of the transaction sequence of the terminal via FIT switch indexes. FIT can also be used to allow the institutions to define the exact operation flow of the terminal. This is done by supplying state flow through the FIT.

Message Authentication Code [MAC]

Message Authentication Code (MAC) provides a method of ensuring that messages sent between the terminal and the network are authentic and have not been modified.

PIN and PIN Verification In order to access a Wincor Nixdorf customer service terminal, the customer must enter a Personal Identification Number (PIN). Typically, a request for PIN entry is made after the customer has inserted an activator card into the terminal. The terminal and/or the network must then verify the PIN before the transaction can continue. The processes for this verification are called PIN verification processes. This section describes both the PIN and the processes required to verify the PIN.

176

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User6.fm © Siemens Nixdorf Informationssysteme AG 1995

Security Features

Personal Identification Number (PIN)

Personal Identification Number (PIN) The PIN is generally derived from an account number. In most PIN verification methods that account number is the Primary Account Number (PAN). The examples and explanations in this document assume that the PAN is the account number associated with the PIN. It is not necessary to use the entire PAN; it is possible to use only those PAN digits that vary from customer to customer. The local PIN verification process is based on an algorithm, a sequence of mathematical steps. Usually, some type of key governs the algorithm sequence. Generally, the process that generates the customer’s PIN also verifies that PIN. A particular key and a set of PAN’s correspond to a set of PIN’s. Some of the PIN’s may be duplicated; that is, one PIN may be derived from several PAN’s, but any given PAN has only one possible PIN.

PIN Entry The first step in the PIN verification process is the customer’s PIN entry. This is done through a PIN entry state. If local PIN verification is being used, the terminal verifies the PIN and goes to the next state required. When remote PIN verification is used instead of local PIN verification, one of two transaction request messages is usually sent to the network. In the first method, the terminal can accept any PIN and continue with a transaction selection to the customer. The terminal then sends both the unverified PIN and the transaction request to the network in the same message. Then, the network can authorize or deny either the PIN or transaction. In the second way, the terminal forwards the PIN to the network in one request message, then awaits the go-ahead before giving a transaction selection to the customer. The second request message holds the current transaction information.

U25604-J-Z745-1-7600

October 2004

177

Personal Identification Number (PIN)

Security Features

Variable length PIN Entry Using FIT, the terminal can accept a variable-length PIN. The FIT field PMXPN indicates the maximum number of PIN digits that a customer may enter. As soon as the customer enters the maximum number of PIN digits, the terminal automatically completes the PIN entry state. For example, the maximum number of PIN digits may be nine. On entry of the ninth digit, the terminal automatically completes the PIN entry state. The institution may issue PIN’s shorter than the maximum PIN length defined in a FIT. Customers receiving shorter PIN’s must press operation key A (which is active on PIN entry) to signal the end of the entry. After the customer presses operation key A, the terminal automatically completes the PIN entry state. For example, if the maximum PIN length is nine digits and the customer has a fivedigit PIN, the customer must press operation key A after the five-digit PIN is entered. If the customer inadvertently presses operation key A before entering all of the required PIN digits, the terminal automatically attempts to verify the digits entered. The PIN verification will fail and a retry or error state occurs (depending on the configuration of the states).

PIN Offset Number (DES verification) For DES PIN verification, the PIN offset number allows an institution to let customers choose any PIN they wish. To accomplish this, an offset is added to or subtracted from the customer’s generated PIN to obtain the desired PIN. This is not, however, ordinary addition or subtraction, but modulo 10. In modulo 10, no figures are carried. The following example shows the difference between these two mathematical systems. 2716

2716

+ 3329

+ 3329

5035 (modulo 10) Note:

178

6045 (regular addition)

Diebold PIN and VISA/ABA PIN verification is not supported by ProCash/NDC and ProConsult/NDC.

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User6.fm © Siemens Nixdorf Informationssysteme AG 1995

Security Features

Personal Identification Number (PIN)

In the DES PIN verification process, the offset is added to the generated PIN to obtain the customer PIN. For example, if the GPIN is 5646 and the offset is 1507, the CPIN would be calculated as follows: 5646 + 1507 6143

GPIN OFFSET CPIN

An activator card data track stores the offset. FIT entry POFDX tells the terminal where to find the offset on the activator card data track. If an institution does not wish to use the offset, it may be set to zero.

PIN Verification Processes ProCash/NDC and ProConsult/NDC support following types of PIN verification: ●

DES local

●

DES remote

These PIN verification processes are the steps that either the terminal or the network performs to verify that a customer-entered PIN is valid. The type of terminal you have and the data security equipment installed may dictate the processes that are available to you. For Wincor Nixdorf cash terminals, the following equipment is available to control PIN handling: ●

DES PIN algorithm

●

Encryption Decryption Module (EDM)

U25604-J-Z745-1-7600

October 2004

179

PIN Verification

Security Features

The following paragraphs describe this equipment and list the PIN verification processes that the equipment supports. DES PIN

DES PIN encryption provides for local DES PIN verification and remote network PIN verification. This feature also encrypts the PIN before sending it to the network. This type of encryption provides increased security for the PIN.

EDM

The Encryption Decryption Module (EDM) (available in all cash out systems) provides all the features of the DES PIN Verification/ Encryption option and the following additional features: ●

Message Authentication (MAC)

●

PIN encryption using Diebold or ANSI format

DES PIN requires Financial Institution Table (FIT) entries. These FIT entries tell the terminal what PIN verification process to use and where to find the information that the terminal needs to perform the verification process. Remote PIN Verification The terminal can also send the PIN to the network for verification rather than verifying the PIN at the terminal. The EDM encrypts the PIN before sending it to the network for verification. The following sections describe some of the essentials for PIN verification and each verification process.

PIN Verification Wincor Nixdorf terminals support local or remote PIN verification. Depending on the FIT entries the terminal determine if the PIN should be checked locally or remote by the host.

180

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User6.fm © Siemens Nixdorf Informationssysteme AG 1995

Security Features

PIN Verification

Local PIN Verification In the DES PIN verification process, the key is the PIN key. This PIN key is stored at the terminal. The PIN key serves the same purpose as the ALGO. The PIN key governs a sequence of operations in the DES ALGO. This algorithm is a standard procedure available to the public. Security is achieved by keeping the PIN key confidential. To obtain greater security, the PIN key is encrypted using the DES algorithm and another secret key. The resulting encrypted PIN key (PEKEY) is put into a FIT entry. During PIN verification, the terminal (or network) decrypts PEKEY to restore the PIN key. Before adding the generated PIN to the offset, DES PIN verification must go through two algorithm procedures. The first procedure decrypts PEKEY from the FIT using the Master key. In the second procedure, the decrypted PEKEY is the PIN key that is used to encrypt the PAN. The encrypted PAN is decimalized using the decimalization table in the FIT. Decimalization ensures that the PIN digits are decimal.

Network PIN Verification Network PIN verification requires that the PIN be padded to 16 digits and encrypted before sending it to the Network. The terminal can encrypt the customer-entered PIN once or twice, then send it to the Network with unencrypted PAN and offset. The PIN may be send unencrypted, but this is not recommended only for system testing. When the encrypted PIN reaches the verification point in the network, a single (or double) decryption restores the customer entered PIN. Then the generated PIN will be compared with the calculated PIN. If the PIN is correct the transaction can be continued. The institution may choose to verify the encrypted PIN without performing decryption. This can be done by comparing the encrypted PIN to a table of encrypted PIN values. Therefore the PAN is used as a table look-up key. For remote PIN verification, the PIN is sent to the network in two different forms: ●

ANSI PIN/PAN Block

●

Diebold PIN Block

●

BANKSYS PIN Block

The terminal encrypts the block and sends it to the network. The network then handles the PIN verification. The FIT field PMXPN tells the terminal which form to use. See section ”Maximum PIN Entry Digits (PMXPN)” on page 191 for more details on PMXPN.

U25604-J-Z745-1-7600

October 2004

181

PIN Verification

Security Features

ANSI PIN/PAN Block The ANSI PIN/PAN block is a 16-hex digit block that contains the result of exclusively ORing the ANSI PIN block and the Primary Account Number (PAN) block. The ANSI PIN block is 16 hex digits and appears as follows:

PIN digits

PIN digits or hex F depending on length of PIN

Filled with hex digit F

Length of PIN (4-12)

Control field (presently 0)

The PAN block is 16 hex digits and appears as follows:

PAD digits

PAN digits

The PAD digits are always hex 0. The PAN digits are the least significant digits of the PAN. The number of digits is determined by the FIT parameters PANLN, PANDX, and PINDX. If the PAN digits are less than 12, hex 0’s are used to fill the remaining slots. The PIN block and PAN block are then exclusively ORed together to create the PIN/PAN block. This block is then encrypted according to the FIT field PINPD and sent to the network.

182

October 2004

U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User6.fm © Siemens Nixdorf Informationssysteme AG 1995

Security Features

PIN Verification

Diebold PIN Block The Diebold PIN block is 16 hex digits and appears as follows:

PIN digits

PAD digits

PIN or PAD digits depending on PIN length

Refer to section ”PIN Pad Character (PINPD)” on page 194 for more details on the Diebold PIN block. The Diebold implementation of DES uses 16 hex digits, 0-F. The encryption process results in 16 hex digits that are converted to ASCII by prefixing each hex digit with a hex 3 to convert the 16 hex digits to 16 ASCII digits. These 16 ASCII digits are sent to the host if the protocol is ASCII. If the communication protocol is EBCDIC, the 16 ASCII digits are converted prior to transmission. The host must reconvert the received 16 digits to 16 hex digits prior to decrypting PIN buffer A. If the protocol is ASCII, the only conversion required is removing the prefixed hex 3 from each digit and combining the resultant into eight bytes. If the host protocol is EBCDIC, each digit must be converted by using the conversion prior to combining the digits into eight bytes. The following table shows the conversion from ASCII to EBCDIC. HEX DIGIT

ASCII (HEX)

GRAPHIC DIGIT

EBCDIC (HEX)

0 1 2 3 4 5 6 7 8 9 A B C D E F

30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F

0 1 2 3 4 5 6 7 8 9 : ; < = > ?

F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 7A 5E 4C 7E 6E 6F

U25604-J-Z745-1-7600

October 2004

183

ID Card and FIT Definitions

Security Features

For example assume that the PIN is encrypted and F is used to pad the PIN. If the entered PIN is 4512, the 16 hex digits internal to the terminal before encryption are: 45 12 FF FF FF FF FF FF

These 16 hex digits are internal to the terminal after encryption as follows (example only): 7A 4C F2 97 31 6E 51 33

These hex digits are then converted to ASCII by prefixing each hex digit with a hex 3: 373A 343C 3F32 3937 3331 363E 3531 3333

If the host protocol is ASCII, the PIN buffer contains these ASCII digits. If the host protocol is EBCDIC, the PIN buffer will contain the following 16 bytes: F77A F44C 6FF2 F9F7 F3F1 F66E F5F1 F3F3

The graphic presentation in a line trace of these bytes will be as follows: 7:4