DIN CWA 14050-14-2001 Extensions for Financial Services (XFS) interface specification - Release 3 0 - Part 14 Card embossing unit class Interface (English Version CWA 14050-14 2000.pdf

1、April 2001Extensions for Financial Services (XFS)interface specification Release 3.0 Part 14: Card Embossing Unit Class InterfaceCWA 14050-14Englische Fassung CWA 14050-14:2000ICS 35.200; 35.240.15; 35.240.40Erweiterungen fr die Schnittstellenspezifikation fr Finanzdienst-leistungen (XFS) Version 3.

2、0 Teil 14: Schnittstelle fr die Gerteklasse “Kartenprgegerte“Nationales VorwortDieses CEN Workshop Agreement CWA 14050-14, das vom CEN/ISSS XFS Workshop erarbeitet wurde,wird ausschlielich in englischer Sprache zur Verfgung gestellt.CEN Workshop Agreements werden im Rahmen eines Konsortiums entwicke

3、lt. 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 Agr

4、eements 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 event

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

6、durch Beuth Verlag GmbH, 10772 BerlinB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Leerseite B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Rue de Stassart, 36 B-1050 BruxellesTel : +32 2 550 08 11 Fax : +32 2 550 08 19EUROPEAN COMMITTEE FOR STANDARDIZATI

7、ON COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG WORKSHOPCWA 14050-14AGREEMENTNovember 2000ICS 35.200; 35.240.15; 35.240.40Extensions for Financial Services (XFS) interface specification -Release 3.0 - Part 14: Card Embossing Unit Class Interface 2000 CEN All rights of exploitation i

8、n any form and by any means reserved world-wide forCEN National MembersRef. No CWA 14050-14:2000 EThis CEN Workshop Agreement can in no way be held as being an official standardas developed by CEN National Members.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 2CWA 14050-1

9、4:2000Table of ContentsForeword . 31. Introduction . 51.1 Background to Release 3.0. 51.2 XFS Service-Specific Programming. 52. Card Embossing Units 73. References. 74. Info Commands. 84.1 WFS_INF_CEU_STATUS . 84.2 WFS_INF_CEU_CAPABILITIES. 104.3 WFS_INF_CEU_FORM_LIST . 114.4 WFS_INF_CEU_MEDIA_LIST

10、114.5 WFS_INF_CEU_QUERY_FORM 114.6 WFS_INF_CEU_QUERY_MEDIA . 124.7 WFS_INF_CEU_QUERY_FIELD 135. Execute Commands 155.1 WFS_CMD_CEU_EMBOSS_CARD . 155.2 WFS_CMD_CEU_RESET . 176. Events 186.1 WFS_SVRE_CEU_INPUTBINTHRESHOLD 186.2 WFS_SVRE_CEU_OUTPUTBINTHRESHOLD 186.3 WFS_SVRE_CEU_RETAINBINTHRESHOLD 186.

11、4 WFS_EXEE_CEU_FIELDERROR 186.5 WFS_EXEE_CEU_FIELDWARNING 196.6 WFS_EXEE_CEU_MEDIAREMOVED 196.7 WFS_SRVE_CEU_MEDIADETECTED. 196.8 WFS_EXEE_CEU_EMBOSS_FAILURE. 197. Embossing Form, Field and Media Definitions 217.1 Definition Syntax 217.2 Embossing Form and Media Measurements 217.3 Embossing Form Def

12、inition 227.4 Embossing Field Definition 237.5 Media Definition . 248. C-Header file 25B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 3CWA 14050-14:2000ForewordThis CWA is revision 3.0 of the XFS interface specification.The move from an XFS 2.0 specification (CWA 13449) to

13、 a 3.0 specification 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 ex

14、perience 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 mar

15、ket acceptance 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

16、 for existingapplications 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 C

17、WA was formally 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 pu

18、blished as a 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

19、Device Class 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 - P

20、rogrammers ReferencePart 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 - Progra

21、mmers ReferencePart 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) - M

22、igration from 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

23、2.0 (see CWA 13449) to Version 3.0(this CWA) - Programmers ReferenceB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 4CWA 14050-14:2000Part 19: Cash Dispenser Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (thisCWA) - Programmers Reference

24、Part 20: PIN Keypad Device Class Interface - Migration from Version 2.0 (see CWA 13449) 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

25、Device Class Interface - Migration from Version 2.0 (see CWA 13449) to Version 3.0(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 In

26、terface - Migration from Version 2.0 (see CWA 13449) to Version 3.0 (this CWA)- Programmers 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

27、document, called Release Notes. The Release Notes contain clarifications and explanations 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 repr

28、esents the Workshops current views on the issues discussed as of the date ofpublication. 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:3.00 October 18, 2000 Initia

29、l releaseB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 5CWA 14050-14:20001. 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

30、 XFS Workshop has extended the franchise of 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 succesfu

31、l with a current membership level of more 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.Th

32、e move from an XFS 2.0 specification to a 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

33、been pressure, through implementation experience 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, whic

34、h is nowover 2 years old. Increasing market 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 pro

35、tection of technical investment for existing 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 re

36、quest functions that are specific to one or 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

37、is as similar as possible across all services, 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 simila

38、r as possible to each other intheir syntax and data structures.In general, the specific command set for a service class is defined as the union of the specific capabilities likely to beprovided by the developers of the services of that class; thus any particular device will normally support only asu

39、bset of the defined command set.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

40、not support it, and 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 servi

41、ce provider recognizes 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.The requested capability is defined for the class of service providers by the XFS specificati

42、on, 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 callingB55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page

43、6CWA 14050-14:2000application. An example would be a request from an application to a cash 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 clas

44、s of service providers by the XFS specification. In this case,a WFS_ERR_INVALID_COMMAND error 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 t

45、heir 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 may use functions and then deal with WFS_ERR_UNSUPP_COMMAND errorreturns to make decisions as to how to use the service.B55EB1B3E14C22109E918E8EA43EDB30F09CC9B7EF8DD9NormCD - Stand 2007-03 Page 7CWA 14050-14:20002. Card Embossing UnitsThis section describes the