DIN CWA 14050-7-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 7 Check reader scanner device class interface (English Version CWA 14050-7.pdf

《DIN CWA 14050-7-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 7 Check reader scanner device class interface (English Version CWA 14050-7.pdf》由会员分享，可在线阅读，更多相关《DIN CWA 14050-7-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 7 Check reader scanner device class interface (English Version CWA 14050-7.pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、April 2001Extensions for Financial Services (XFS)interface specification Release 3.0 Part 7: Check Reader/Scanner Device Class InterfaceCWA 14050-7Englische Fassung CWA 14050-7:2000ICS 35.200; 35.240.40Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-leistungen (XFS) Version 3.0 Teil

2、 7: Schnittstelle fr die Gerteklasse“Scheck-Lesegerte und Scanner“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-7, das vom CEN/ISSS XFS Workshop erarbeitet wurde,wird ausschlielich in englischer Sprache zur Verfgung gestellt.CEN Workshop Agreements werden im Rahmen eines Konsortiums entw

3、ickelt. Sie unterscheiden sich vonEuropischen Normen dadurch, dass sie grundstzlich kein ffentliches Einspruchsverfahren durchlaufenund dass auch keine nationale Meinungsbildung stattfindet. Im Gegensatz zu Europischen Normen, dieden Konsens aller interessierten Kreise darstellen, haben CEN Workshop

4、 Agreements lediglich dieZustimmung der unmittelbar beteiligten Mitglieder des Konsortiums gefunden.Fr den Inhalt sind ausschlielich die Mitglieder des Konsortiums verantwortlich (siehe ergnzendeHinweise im CWA-Vorwort). Weder das CEN-Zentralsekretariat, noch die CEN-Mitglieder haben den Inhaltauf e

5、ventuelle Fehler oder Widersprche zu Normen und Rechtsvorschriften geprft.Fortsetzung 34 Seiten CWA Beuth Verlag GmbH, 2001 .Jede Art der Vervielfltigung, auch auszugsweise, Ref. Nr. DIN CWA 14050-7:2001-04nur mit Genehmigung des Beuth Verlages gestattet. RW DIN CWA Preisgr. 05Alleinverkauf der Norm

6、en durch Beuth Verlag GmbH, 10772 Berlin Leerseite Rue de Stassart, 36 B-1050 BruxellesTel : +32 2 550 08 11 Fax : +32 2 550 08 19EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA 14050-7AGREEMENTNovember 2000ICS 35.200; 35.240.40Extensi

7、ons for Financial Services (XFS) interface specification -Release 3.0 - Part 7: Check Reader/Scanner Device Class Interface 2000 CEN All rights of exploitation in any form and by any means reserved world-wide forCEN National MembersRef. No CWA 14050-7:2000 EThis CEN Workshop Agreement can in no way

8、be held as being an official standardas developed by CEN National Members.Page 2CWA 14050-7:2000Table of ContentsForeword . 31. Introduction . 51.1 Background to Release 3.0. 51.2 XFS Service-Specific Programming. 52. Check Readers and Scanners 73. References. 84. Info Commands. 94.1 WFS_INF_CHK_STA

9、TUS. 94.2 WFS_INF_CHK_CAPABILITIES. 104.3 WFS_INF_CHK_FORM_LIST. 114.4 WFS_INF_CHK_MEDIA_LIST 114.5 WFS_INF_CHK_QUERY_FORM 124.6 WFS_INF_CHK_QUERY_MEDIA. 134.7 WFS_INF_CHK_QUERY_FIELD 155. Execute Commands 175.1 WFS_CMD_CHK_PROCESS_FORM. 175.2 WFS_CMD_CHK_RESET. 196. Events 216.1 WFS_EXEE_CHK_NOMEDI

10、A. 216.2 WFS_EXEE_CHK_MEDIAINSERTED 216.3 WFS_SRVE_CHK_MEDIAINSERTED 216.4 WFS_EXEE_CHK_FIELDERROR 216.5 WFS_EXEE_CHK_FIELDWARNING 226.6 WFS_USRE_CHK_INKTHRESHOLD 226.7 WFS_SRVE_CHK_MEDIADETECTED 227. Forms Language Usage . 237.1 Definition Syntax 237.2 XFS form/media definition files in multi-vendo

11、r environments 247.3 Form and Media Measurements. 247.4 Form Definition 257.5 Field Definition. 267.6 Media Definition . 298. C - Header file 30Page 3CWA 14050-7:20003ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from an XFS 2.0 specification (CWA 13449) to a 3.0 speci

12、fication has been prompted by a series offactors.Initially, there has been a technical imperative to extend the scope of the existing specification of the XFS Managerto include new devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through implementation experience and

13、 the advance of the Microsofttechnology, to extend the functionality and capabilities of the existing devices covered by the specification.Finally, it is also clear that our customers and the market are asking for an update to a specification, which is nowover 2 years old. Increasing market acceptan

14、ce and the need to meet this demand is driving the Workshop towardsthis release.The clear direction of the CEN/ISSS XFS Workshop, therefore, is the delivery of a new Release 3.0 specificationbased on a C API. It will be delivered with the promise of the protection of technical investment for existin

15、gapplications and the design to safeguard future developments.The CEN/ISSS XFS Workshop gathers suppliers as well as banks and other financial service companies. A list ofcompanies participating in this Workshop and in support of this CWA is available from the CEN/ISSS Secretariat.This CWA was forma

16、lly approved by the XFS Workshop meeting on 2000-10-18. The specification is continuouslyreviewed and commented in the CEN/ISSS Workshop on XFS. It is therefore expected that an update of thespecification will be published in due time as a CWA, superseding this revision 3.0.The CWA is published as a

17、 multi-part document, consisting of:Part 1: Application Programming Interface (API) - Service Provider Interface (SPI); Programmers ReferencePart 2: Service Classes Definition; Programmers ReferencePart 3: Printer Device Class Interface - Programmers ReferencePart 4: Identification Card Device Class

18、 Interface - Programmers ReferencePart 5: Cash Dispenser Device Class Interface - Programmers ReferencePart 6: PIN Keypad Device Class Interface - Programmers ReferencePart 7: Check Reader/Scanner Device Class Interface - Programmers ReferencePart 8: Depository Device Class Interface - Programmers R

19、eferencePart 9: Text Terminal Unit Device Class Interface - Programmers ReferencePart 10: Sensors and Indicators Unit Device Class Interface - Programmers ReferencePart 11: Vendor Dependent Mode Device Class Interface - Programmers ReferencePart 12: Camera Device Class Interface - Programmers Refere

20、ncePart 13: Alarm Device Class Interface - Programmers ReferencePart 14: Card Embossing Unit Class Interface - Programmers ReferencePart 15: Cash In Module Device Class Interface- Programmers ReferencePart 16: Application Programming Interface (API) - Service Provider Interface (SPI) - Migration fro

21、m Version 2.0(see CWA 13449) to Version 3.0 (this CWA) - Programmers ReferencePart 17: Printer Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA) -Programmers ReferencePart 18: Identification Card Device Class Interface - Migration from Version 2.0 (see CWA

22、 13449) to Version 3.0(this CWA) - Programmers ReferencePage 4CWA 14050-7:2000Part 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 20: PIN Keypad Device Class Interface - Migration from Version 2.0 (see CWA 1

23、3449) to Version 3.0 (thisCWA) - Programmers ReferencePart 21: Depository Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers ReferencePart 22: Text Terminal Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0

24、(this CWA) - Programmers ReferencePart 23: Sensors and Indicators Unit Device Class Interface - Migration from Version 2.0 (see CWA 13449) toVersion 3.0 (this CWA) - Programmers ReferencePart 24: Camera Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA)- Pr

25、ogrammers ReferencePart 25: Identification Card Device Class Interface - PC/SC Integration GuidelinesIn addition to these Programmers Reference specifications, the reader of this CWA is also referred to acomplementary document, called Release Notes. The Release Notes contain clarifications and expla

26、nations on theCWA specifications, which are not requiring functional changes. The current version of the Release Notes isavailable online from http:/www.cenorm.be/isss/Workshop/XFS.The information in this document represents the Workshops current views on the issues discussed as of the date ofpublic

27、ation. It is furnished for informational purposes only and is subject to change without notice. CEN/ISSSmakes no warranty, express or implied, with respect to this document.Revision History:1.0 May 24, 1993 Initial release of API and SPI specification1.01 June 11, 1993 Minor updates to BSVC member c

28、ontact list.1.1 April 14, 1994 Major updates and additions.1.11 February 3, 1995 Separation of specification into separate documents for API/SPIand service class definitions; with updates3.00 October 18, 2000 Update release encompassing:- Reintroduced with a command set targeted at stand alone check

29、readers and scanners UNICODE supportPage 5CWA 14050-7:200051. Introduction1.1 Background to Release 3.0The CEN XFS Workshop is a continuation of the Banking Solution Vendors Council workshop and maintains atechnical commitment to the Win 32 API. However, the XFS Workshop has extended the franchise o

30、f multi vendorsoftware by encouraging the participation of both banks and vendors to take part in the deliberations of the creationof an industry standard. This move towards opening the participation beyond the BSVCs original membership hasbeen very succesful with a current membership level of more

31、than 20 companies.The fundamental aims of the XFS Workshop are to promote a clear and unambiguous specification for both serviceproviders and application developers. This has been achieved to date by sub groups working electronically andquarterly meetings.The move from an XFS 2.0 specification to a

32、3.0 specification has been prompted by a series of factors. Initially,there has been a technical imperative to extend the scope of the existing specification of the XFS Manager to includenew devices, such as the Card Embossing Unit.Similarly, there has also been pressure, through implementation expe

33、rience and the advance of the Microsofttechnology, to extend the functionality and capabilities of the existing devices covered by the specification.Finally, it is also clear that our customers and the market are asking for an update to a specification, which is nowover 2 years old. Increasing marke

34、t acceptance and the need to meet this demand is driving the Workshop towardsthis release.The clear direction of the XFS Workshop, therefore, is the delivery of a new Release 3.0 specification based on a CAPI. It will be delivered with the promise of the protection of technical investment for existi

35、ng applications and thedesign to safeguard future developments.1.2 XFS Service-Specific ProgrammingThe service classes are defined by their service-specific commands and the associated data structures, error codes,messages, etc. These commands are used to request functions that are specific to one o

36、r more classes of serviceproviders, but not all of them, and therefore are not included in the common API for basic or administrationfunctions.When a service-specific command is common among two or more classes of service providers, the syntax of thecommand is as similar as possible across all servi

37、ces, since a major objective of the Extensions for FinancialServices is to standardize command codes and structures for the broadest variety of services. For example, using theWFSExecute function, the commands to read data from various services are as similar as possible to each other intheir syntax

38、 and data structures.In general, the specific command set for a service class is defined as the union of the sets of specific capabilitieslikely to be provided by the developers of the services of that class; thus any particular device will normally supportonly a subset of the command set defined fo

39、r the class.There are three cases in which a service provider may receive a service-specific command that it does not support:The requested capability is defined for the class of service providers by the XFS specification, the particularvendor implementation of that service does not support it, and

40、the unsupported capability is not considered tobe fundamental to the service. In this case, the service provider returns a successful completion, but does nooperation. An example would be a request from an application to turn on a control indicator on a passbookprinter; the service provider recogniz

41、es the command, but since the passbook printer it is managing does notinclude that indicator, the service provider does no operation and returns a successful completion to theapplication.Page 6CWA 14050-7:2000The requested capability is defined for the class of service providers by the XFS specifica

42、tion, the particularvendor implementation of that service does not support it, and the unsupported capability is considered to befundamental to the service. In this case, a WFS_ERR_UNSUPP_COMMAND error is returned to the callingapplication. An example would be a request from an application to a cash

43、 dispenser to dispense coins; theservice provider recognizes the command but, since the cash dispenser it is managing dispenses only notes,returns this error.The requested capability is not defined for the class of service providers by the XFS specification. In this case,a WFS_ERR_INVALID_COMMAND er

44、ror is returned to the calling application.This design allows implementation of applications that can be used with a range of services that provide differingsubsets of the functionalities that are defined for their service class. Applications may use the WFSGetInfo andWFSAsyncGetInfo commands to inq

45、uire about the capabilities of the service they are about to use, and modifytheir behavior accordingly, or they may use functions and then deal with WFS_ERR_UNSUPP_COMMAND errorreturns to make decisions as to how to use the service.This design allows implementation of applications that can be used w

46、ith a range of services that provide differingsubsets of the functionalities that are defined for their service class. Applications may use the WFSGetInfo andWFSAsyncGetInfo commands to inquire about the capabilities of the service they are about to use, and modifytheir behavior accordingly, or they

47、 may use functions and then deal with WFS_ERR_UNSUPP_COMMAND errorreturns to make decisions as to how to use the service.Page 7CWA 14050-7:200072. Check Readers and ScannersThis specification describes the XFS service class of check readers and scanners. Check image scanners are treatedas a special

48、case of check readers, i.e., image-enabled instances of the latter. This class includes devices with a rangeof features, from small hand-held read-only devices through which checks are manually swiped one at a time, todesktop units which automatically feed the check one at a time; recording the MICR

49、 data and check image, andendorse or encode the check. The specification of this service class includes definitions of the service-specificcommands that can be issued, using the WFSAsyncExecute, WFSExecute, WFSGetInfo and WFSAsyncGetInfofunctions.In the U.S., checks are always encoded in magnetic ink for reading by Magnetic Ink Character Recognition (MICR),and a single font is always used. In Europe some countries use MICR and some use Optical Character Recognition(OCR) character sets, with different fonts, for their checks.In al