ZVT ECR Interface Specification
ZVT ECR Interface Specification
ZVT-Protocol
Commands
Bitmaps
Error Messages
Disclaimer
The following information is based on the current state of knowledge and is provided with-
out guarantee. Modifications and errors excepted.
Revision 13.06
Date 06.05.2015
Status release
ECR-Interface PA00P015_13.06_en.docx
0 History ...................................................................................................................................................... 8
1 Definitions ...............................................................................................................................................22
1.1 Terms and Abbreviations ...................................................................................................................22
1.2 Password ............................................................................................................................................22
1.3 Currency Code ...................................................................................................................................22
2 Commands from ECR to PT ...................................................................................................................23
2.1 Registration (06 00) ............................................................................................................................23
2.2 Authorization (06 01) ..........................................................................................................................26
2.2.1 Start .........................................................................................................................................28
2.2.2 Read Card ...............................................................................................................................30
2.2.3 Transaction ..............................................................................................................................30
2.2.4 Intermediate Status-Information ..............................................................................................30
2.2.5 Release Card ..........................................................................................................................30
2.2.6 Status-Information ...................................................................................................................30
2.2.7 Reversal ..................................................................................................................................32
2.2.8 Receipt-Printout .......................................................................................................................32
2.2.9 Store Transaction in PT ...........................................................................................................33
2.2.10 Completion ..............................................................................................................................33
2.3 Account Balance Request (06 03) .....................................................................................................34
2.4 Activate Card (06 04) .........................................................................................................................35
2.5 Procurement (06 05) ..........................................................................................................................35
2.6 Book Tip (06 0C) ................................................................................................................................36
2.7 Telephonic Authorisation (06 21) .......................................................................................................36
2.8 Pre-Authorisation / Reservation (06 22) .............................................................................................37
2.9 Reversal (06 30) .................................................................................................................................38
2.10 Partial-Reversal of a Pre-Authorisation / Booking of a Reservation (06 23) ..................................39
2.10.1 Enquire if Pre-Authorisations exist (06 23)..............................................................................39
2.11 Partial Reversal with transparent APDU mode ..............................................................................40
2.12 Book Total (06 24) ..........................................................................................................................41
2.13 Pre-Authorisation Reversal (06 25) ................................................................................................42
2.14 Refund (06 31) ................................................................................................................................42
2.15 End-of-Day (06 50) .........................................................................................................................43
2.15.1 Start .........................................................................................................................................43
2.15.2 Transaction: .............................................................................................................................43
2.15.3 Intermediate Status-Information ..............................................................................................44
2.15.4 Status-Information ...................................................................................................................44
2.15.5 Receipt-Printout .......................................................................................................................44
2.15.6 Completion ..............................................................................................................................44
2.16 Diagnosis (06 70) ...........................................................................................................................45
2.16.1 Start .........................................................................................................................................45
2.16.2 Transaction: .............................................................................................................................46
2.16.3 Intermediate Status-Information ..............................................................................................46
2.16.4 Transmit Date ..........................................................................................................................46
2.16.5 Receipt-Printout .......................................................................................................................46
2.16.6 Completion ..............................................................................................................................46
2.17 Initialisation (06 93) ........................................................................................................................47
2.17.1 Start .........................................................................................................................................47
2.17.2 Transaction: .............................................................................................................................47
2.17.3 Intermediate Status-Information ..............................................................................................47
2.17.4 Receipt-Printout .......................................................................................................................48
2.17.5 Completion ..............................................................................................................................48
0 History
Revision Date Release Notes Author
04 5.3.2004 Separation of document into two documents Transport- K. Höflich
Protocol/Application-Protocol and Commands/Bitmaps/Error-
Messages
18.10.2007 Changes chapter 2.24 and 2.25 Display Text (06 E0 and 06 T.Lilienthal
85)
- Note can be ended prematurely using command „Abort“
(06 B0)
13.01 02.06.2008 Changes chapter 10, list of ZVT Card-type IDs T.Lilienthal
New Card-type ID „203 Micromoney“ (Prepaid)
New Card-type ID „204 T-Card“ (Prepaid)
New Card-type-ID „205 Blau“ (Prepaid)
New Card-type-ID „206 BILDMobil“ (Prepaid)
New Card-type-ID „207 Congstar“ (Prepaid)
New Card-type-ID „208 C3 Bestminutes“ (Prepaid)
New Card-type-ID „209 C3 Bestcard“ (Prepaid)
New Card-type-ID „210 C3 Callingcard“ (Prepaid)
New Card-type-ID „211 EDEKAMOBIL“ (Prepaid)
New Card-type-ID „212 XTRA-PIN“ (Prepaid)
06.03.2009 8-Bit default character set added and set as default R.Roos
New TLV-tags 1F13-1F18
New Card-type-IDs
"213 Klimacard"
"214 ICP-International-Fleet-Card"
New bitmap 2E in status information to read card command
New intermediate status codes 0xCB and 0xFF
Command 06 E1 optionally responds to card inserts
1 Definitions
All numerical values, unless otherwise specified, are hexadecimal.
Term Definition
APDU Application Protocol Data Unit (= a complete request or response)
BMP Bitmap, pre-defined data field
CC Currency Code according to ISO 4217, 09 78 = Euro
ECR Electronic Cash Register. System that transmits the amount to the payment terminal,
may also be a vending machine.
PS Personalisation System Host (= Background-system for OPT-Actions)
PT Payment Terminal
RC Return-Code
RFU Reserved for Future Use
TCS Terminal Configuration Server (= Server that is responsible for software-updates and
other maintenance)
TID Terminal-ID, 8 character numerical
xx Any value / undefined / dependent on the data
ZVT Zahlungsverkehrterminal (= Point-Of-Sale Terminal)
<field> A parameter shown in angled-brackets is a place-holder.The place-holder is explained
in the following text.
[<field>] A parameter shown in square-brackets is optional.
1.2 Password
Some PTs require a password from the ECR to carry out certain functions. The password consists of 6 digits
which are packed as 3 byte BCD
The PT only sends a currency code to the ECR if the ECR had also sent a currency code in its request.
Using the command Registration the ECR can set up different configurations on the PT and also control the
current status of the PT.
An Authorisation on the PT can also take place without previously registering the PT with the ECR.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 00 xx <password><config-byte>[<CC>[03<service-byte>][06<TLV-
container>]]
Data block:
<password>: 3 byte BCD.
<config-byte>: Bit-field, 1 byte, see Table 1: Definition of <config-byte>.
<CC>: 2 byte.
03<service-byte>: Bit-field, 1 byte. If <service-byte> is sent, <CC> must also be present. See values
Table 2: Definition of <service-byte>.
06<TLV-container>: Possible tags are 10, 11, 12, 14, 1A, 26, 27, 28, 29, 2A, 40, 1F04, 1F05.
As long as the ECR supports TLV-container it is strongly recommended that the ECR sends the list
of permitted commands. If <TLV-container> is sent, then <CC> must also be sent.
The tag 14 allows configuring a different character set to the PT. Only if this tag is echoed in the
Completion command, the character set is accepted by the terminal. If no tag is echoed, the stand-
ard character set is used. If the same value for tag 14 is echoed, all commands for printing and all
commands for displaying text use the selected character set. See definition of tag 27 for details.
config-byte Definition
0000 000x RFU
0000 0010 ECR assumes receipt-printout for payment functions (see also “ECR Printing - ECR
print-type”)
0: payment receipt not printed by ECR
1: payment receipt printed by ECR
This field is only used if the option “ECR assumes receipt-printout for payment func-
tions" and/or "ECR assumes receipt-printout for administration functions” is set.
Receipts which are not printed by the ECR must be printed by the PT’s own printer.
Table 1: Definition of <config-byte>
If the ECR generates the receipt using the PT-command Print Lines (06D1) or Print Textblock (06D3) it
can inform the PT about its maximum line-width in the request. This is done by sending a TLV-container
containing the line-width in tag12. The PT then delivers the line-width actually used also in tag 12 of the
Completion command.
The PT formats the receipt accordingly, where technically possible. The PT informs the ECR correspondingly
which line-width the receipt is actually formatted with. The ECR can then add leading spaces to the print-line,
to allow it to be centered when printed on the ECR printer.
config-byte Result
0xxx x00x Receipt-printout on PT
0xxx x11x Receipt-printout on the ECR, whereby the ECR constructs the receipt itself from the status-
information; the PT prints nothing
0xxx x01x Payment receipt-printout on the ECR, whereby the ECR constructs the receipt itself from the
status-information; the PT prints the administration receipts
0xxx x10x Administration receipt-printout on the ECR, whereby the ECR constructs the receipt itself from
the status-information; the PT prints the payment receipts
1xxx x00x Receipt-printout on PT
1xxx x11x Receipt-printout on ECR using command "Print Lines" (06D1)
1xxx x01x Payment receipt-printout on ECR using command "Print Lines" (06D1); the PT prints the ad-
ministration receipts, provided a printer is integrated in the PT
1xxx x10x Administration receipt-printout on ECR using command "Print Lines" (06D1); the PT prints the
payment receipts, provided a printer is integrated in the PT
Special case: ECR prints payment receipts and no receipts should be printed for administration functions
(neither on PT nor on ECR). In this case config-byte 0xxx x11x or 1xxx x11x is used, whereby the ECR does
not execute the administration receipt-printout.
service-byte Definition
xxxx xxx1 The PT service-menu may not be assigned to PT function-key.
xxxx xxx0 The PT service-menu may be assigned to PT function-key (= default if BMP03 omitted).
xxxx xx1x The display texts for the Commands Authorisation, Pre-initialisation and Reversal will be dis-
played in capitals.
xxxx xx0x The display texts for the Commands Authorisation, Pre-initialisation and Reversal will be dis-
played in standard font (= default if BMP03 omitted).
Remainder RFU
Table 2: Definition of <service-byte>
Note:
Bit 1 (font-size) has no influence on the font-size for the commands Text-Display, Text-Display with Function-
Key Input, Text-Display with numerical input and Text-display with Customer-card PIN-verification. For these
commands the font-size is switched via control-character (see relevant chapter).
Response of PT:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 1E xx 6F[<CC>]
Data block:
The PT only sends a currency code to the ECR, if the ECR had also sent a currency code in its request.
If the currency code check is positive, the Completion takes place whereupon the ECR receives the “mas-
ter-rights” back:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx [19<status-byte>] [29<TID>] [49<CC>][06<TLV-container>]
Data block:
19<status-byte>: Bit-field, 1 byte. See Table 3: Definition of <status-byte>.
06<TLV-container>: Possible tags are 10, 11, 12, 14, 1A, 26, 27, 28. Using tag 26 the PT can communi-
cate its implementation level to the ECR.
Status-byte Definition
xxxx xxx1 PT initialisation necessary
xxxx xx1x Diagnosis necessary
xxxx x1xx OPT action necessary
xxxx 1xxx PT functions in filling station mode
xxx1 xxxx PT functions in vending machine mode
xx1x xxxx RFU
x1xx xxxx RFU
1xxx xxxx RFU
Table 3: Definition of <status-byte>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
This command initiates a payment process and transmits the amount from the ECR to PT. The result of the
payment process is reported to the ECR after completion of the booking process.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
The following is an example of an authorisation sequence. Here are the particular features of the Pre-
Authorisation (see also chapter Pre-Authorisation / Reservation (06 22)) detailed.
Authorisation sequence:
1. Start via call from ECR (amount-transfer, possibly payment-type or card-data).
2. The PT reads the card, if the ECR did not send card-data with the start.
3. The PT executes the transaction.
4. Depending on the configuration the PT sends Intermediate Status-Information during the transaction
to the ECR, so that the ECR knows that the transaction is still running.
5. Release Card.
6. The PT sends a Status-Information with the transaction result (successful or not successful).
7. For vending machines:
For vending machines: issue of goods.
For filling station systems: start filling.
8. Response to Status-Information with the following function.
For normal PTs: contains transaction result.
For vending machines: result of issue of goods (goods issued or goods not issued).
For filling station systems: start filling took place.
9. Payment Reversal via PT if the issue of goods was not successful.
10. Receipt-printout (for filling station system the receipt-printout takes place during the partial-reversal).
11. Completion.
2.2.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 01 xx [04<amount>] [49<CC>] [19<payment-type>] [2D<track 1 data>]
[0E<expiry-date>] [22<card-number>] [23<track 2 data>]
[24<track 3 data>] [01<timeout>] [02<max. status-infos>]
[05<pump no.>] [3A<CVV/CVC>] [3C<additional-data>] [8A<card
type>] [06<TLV-container>]
Data block:
04<amount>: Optional for bonus-transactions. In this case the tag E1 with subtag C2 can be sent instead
of amount.
19<payment-type>: Bit-field, 1 byte. See Table 4: Definition of <payment-type>.
0E<expiry-date>: Used for payment with manual card-data entry.
22<card-number>: Used for payment with manual card-data entry. If the card-number contains an odd
number of digits, it is padded with an ‘F’.
01<timeout>: Supplies the time in seconds that the PT waits during issue of goods for a response from
the ECR. The default value is 30 seconds.
02<max. status-infos>: Defines the maximum number of times that ECR may request the result of the
issue of goods from the PT via Status-Information. The default value is infinite.
05<pump no.>: Used for the display (e.g. “Please fill-up, pump 2“) following a successful authorisation on
when using a filling station. If this field is omitted, the PT in the filling station displays the text without a
pump number (e.g. “Please fill-up”).
3A<CVV/CVC>: Used for Mail-Order.
3C<additional-data>: Depending on the ECR-system and application different additional-data can be
transmitted (see chapter Additional Data).
06<TLV-container>: Possible tags are 15, 20, 30, 41, 43, E1 (for C1 value '4D 45' or '4D 53' is possible),
E8, 1F04, 1F05, 1F15, 1F25, 1F36.
For cards which can’t identified by the BIN, like CUP, the card type has to be sent with the command.
Therefor the field 8A or TLV tag 41 is used.
All other data are ignored by the PT.
Background:
If the ECR cannot complete the issue of goods within time <timeout>, the ECR responds to the PT a Status-
Information with “84-9C”. In this case the PT waits 2 seconds and sends then a Status-Information again.
The parameter <max. status-infos> prevents this sequence from running in an infinite-loop.
Notes:
If the payment-type is not specifically defined, for example payment-type = ‘0100xxxx’, the PT selects the
payment-type itself. For a girocard, selection of “GeldKarte” is only possible via pre-selection of the pay-
ment-type.
If the payment-type selected by the ECR is inhibited in the PT, the PT either responds with an error-
message in the Status-Information or ignores the payment-type.
If fields 23 or 24 (= track-data) or 0E and 22(= manual card-data) are contained in the data for command
Authorisation, it is attempted to complete the payment using this data without requesting further insertion
of the card.
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
For swipe-reader:
The magnet-stripe is read during swiping of the card. Reading of the chip is not possible.
For chip-reader:
The chip is read after inserting the card. Reading of the magnet-stripe is not possible.
For manual-insertion reader with hybrid-reader function:
If the customer inserts the card in the reader, the PT locks the card (depending on the reader-type). If
the PT determines that the payment will be carried out using magnet-stripe, the PT releases the card
immediately to allow the magnet-stripe to be read during removal.
For chip-transactions the card remains locked for the whole transaction.
For PTs with manual-insertion readers without locking-function the customer take care that the card
is not removed too early from the card-reader.
For motor-insertion reader:
The PT reads chip and magnet-stripe and makes the technology selection (chip or magnet) according to
the pre-determined payment-type and / or the limits set in the PT. The card remains in the card-reader.
2.2.3 Transaction
After reading the card-data, or manual card-data input, the PT begins with the payment. If necessary the PT
connects online to the host. This takes place, depending on the configuration of the PT and ECR, either via
the communications-module of the PT or via a communications-module connected to the ECR (see chapter
Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up (06 DA)).
2.2.6 Status-Information
The PT responds after the payment procedure with the Status-Information. An additional Status-
Information may be sent after the final completion of the transaction (e.g. GeldKarte, girogo) to return final
transaction data:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [27<result-code>] [<transaction-data>] [06<TLV-container>]
Data block:
For <result-code> and <transaction-data> see chapter Status-Information after Authorisation, Reversal,
Pre-Authorisation/Reservation, DCC or Prepaid-Top-Up.
For result-code decimal 55 “PIN incorrect” the PT can repeat the prompt for PIN, depending on the pay-
ment-type, and re-start the payment. In this case the PT sends the commands for Intermediate Status-
Information, Dial-Up, Print and Status-Information once again. Alternatively the PT can also abort the
payment with an error-code.
06<TLV-container>: see chapter Status-Information (04 0F).
Response to Status-Information
The ECR answers after the issue of goods, after start of filling (for Pre-Authorisation) or if it is a “normal”
ECR immediately with:
a) ECR response following successful issue of goods (for vending machines), start of filling (for Pre-
Authorisation) or if not supported, no issue of goods is carried-out (ECRs):
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Alternative:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 00 00
Both ECR responses have the same meaning: issue of goods succeeded or filling started.
b) ECR response, if issue of goods cannot be completed within the timeout sent as part of the command
Authorisation (see parameters for request Authorization (06 01)) or if the customer has not yet begun filling:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 9C 00
The response 84-9C-00 implies that the PT shall send the Status-Information again after a wait-time of 2
seconds because the ECR has not yet completed the issue of goods.
c) ECR response for unsuccessful issue of goods or for filling not yet started:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 yy xx xx
(any value,
excepting 00
and 9C)
The response 84-yy-xx-xx with ‘yy’ as any value (except ‘00’ or ‘9C’) implies that the issue of goods was not
successful or filling was not yet started. In this case the PT reverses the payment.
Notes:
If the ECR sends 84-9C-00 so often, that <max. status-infos> (see parameters for request Authorization
(06 01)) is exceeded (= <max. status infos> + 1), the PT reverses the payment and afterwards sends a
Status-Information with error-message 04-0F-03-27-6C.
If no response from the ECR is received within <timeout> (see parameters for request Authorization (06
01)), then the PT reverses the payment.
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 9D 7 04<amount>
If only a partial issue of goods was possible the ECR responds with APRC 9D and sends the price of the
issued goods back in the data block.
2.2.7 Reversal
If the issue of goods is not successful or Filling was not started PT reverses the payment.
2.2.8 Receipt-Printout
Subsequently the receipt printout takes place – also for failed Authorisations. If the PT function ECR-Receipt
is activated (= setting in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-
by-line to the ECR using “Print Line”-Commands (see chapter Print line (06 D1)) or Print Textblock-
Commands (06 D3).
There is no receipt printout for a successful pre-authorisation (instead it is done during Partial-Reversal after
filling) – otherwise the receipt printout is only carried out here if pre-authorisation is unsuccessful.
If the ECR does not send a response or the PT does not receive the response, then the PT executes an
Auto-Reversal, possibly requiring an additional Dial-Up. The Auto-Reversal itself carried out only after the
card has been removed.
2.2.10 Completion
If transaction and issue of goods were successful, (or filling was started) the PT sends command Comple-
tion whereupon the ECR is given back the “master-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If transaction and/or issue of goods failed (or filling was not started), the PT sends command Abort where-
upon the ECR is given back the “master-rights”:
PT ECR
APDU
Control field Length Data block
CCRC APRC
06 1E xx <result-code> [<CC>] [06<TLV-container>]
Data block:
The possible result-codes are described in chapter Error-Messages.
The currency code of the PT is only sent with result-code 6F. The PT only sends a currency code to the
ECR, if the ECR had also sent a currency code in its request.
06<TLV-container>: Possible tags are 1F16, 1F17.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
As soon as the PTs Status-Information is acknowledged by the ECR the payment is successfully completed.
Even if an error occurs during command Completion, the payment is judged to be successful and not to be
reversed. If in doubt the ECR can attempt to resynchronise using the command Repeat-Receipt. A reversal
only takes place if the ECR does not acknowledge the Status-Information.
This command starts an Account Balance Request on the PT, e.g. for bonus-points. The credit is reported to
the ECR in the Status-Information.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 03 xx [22<card-number>] [0E<expiry-date>] [2D<track 1 data>]
[23<track 2 data>] [24<track 3 data>] [06<TLV-container>]
Data block:
22<card-number>: see chapter Authorization (06 01)
0E<expiry-date>: see chapter Authorization (06 01)
2D<track 1 data>: see chapter Authorization (06 01)
23<track 2 data>: see chapter Authorization (06 01)
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
The further sequence of events is – apart from checking the issue of goods or filling – identical to Authoriza-
tion (06 01).
This command activates a card. Depending on the card-type, the activation may take place on a host system
or offline and details are out of the scope of the ECR-Interface document.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 04 xx [04<amount>] [49<CC>] [2D<track 1 data>] [0E<expiry-date>]
[22<card-number>] [23<track 2 data>] [24<track 3 data>]
[3A<CVV/CVC>] [06<TLV-container>]
Data block:
04<amount>: If included the PT may execute a top-up function if necessary. Otherwise top-up is handled
via command Refund.
06<TLV-container>: Possible tags are 15; 20, 41, 43, E1, 1F04, 1F05.
All other data will be ignored by the PT.
The further sequence of events is – apart from checking the issue of goods – identical to the Authorization
(06 01).
This command initiates a money procurement transaction in order to top-up e.g. a GeldKarte.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 05 xx 04<amount>] [49<CC>] [19<payment-type>] [2D<track 1 data>]
[0E<expiry-date>] [22<card-number>] [23<track 2 data>]
[24<track 3 data>] [01<timeout>] [02<max. status infos>]
[3A<CVV/CVC>] [3C<additional-data>] [8A<card type>] [06<TLV-
container>]
Data block:
See chapter Authorization (06 01).
For further sequence of events for the transaction see Authorization (06 01).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 0C xx 04<amount> 87<receipt-no> [49<CC>] [19<payment-type>]
[2D<track 1 data>] [0E<expiry-date>] [22<card-number>]
[23<track 2 data>] [24<track 3 data>] [3B<AID>] [06<TLV-container>]
Data block:
04<amount>: Tip amount.
87<receipt-no>: See chapter Status-Information (04 0F).
3B<AID>: Must be sent for telephonic tip booking. See Status-Information (04 0F).
Remaining bitmaps see Authorization (06 01).
All other data will be ignored by the PT.
For further sequence of events for the transaction see Authorization (06 01).
This command initiates a telephonic authorisation and transmits the amount from the ECR to PT. The
authorization number is either sent by the ECR, otherwise it is requested during the payment procedure on
the PT.
The result of the payment procedure is reported to the ECR after Completion of the booking procedure.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 21 xx <password> 04<amount> [49<CC>] [19<payment-type>]
[2D<track 1 data>] [0E<expiry-date>] [22<card-number>]
[23<track 2 data>] [24<track 3 data>] [01<timeout>] [02<max. status
infos>] [05<pump no.>] [3C<additional-data>] [3B<AID>]
[3A<CVV/CVC>] [8A<card type>][06<TLV-container>]
Data block:
3B<AID>: See chapter Status-Information (04 0F).
3C<additional-data>: See chapter Additional Data.
06<TLV-container>: Possible tags are 20, 41, 43, E1, E8, 1F15.
Remaining bitmaps see Authorization (06 01).
For cards which can not identified by the BIN, like CUP, the card type has to be sent with the command.
Therefor the BMP 8A or TLV tag 41 is used.
For further sequence of events for the transaction see chapter Authorisation (06 01).
Using the command Pre-Authorisation/Reservation the ECR can request the PT to reserve a certain pay-
ment-amount for the sales-process. This is particularly necessary when the final payment-amount is only
established after the authorisation (e.g. Service-stations; Hotels). In this case the ECR firstly reserves an
amount (= max. possible payment-amount) and then, after the sales-process, releases the unused amount
via a Partial-Reversal or Book Total.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 22 xx [04<amount>] [49<CC>] [19<payment-type>] [0E<expiry-date>]
[22<card-number>] [2D<track 1 data>] [23<track 2 data>]
[24<track 3 data>] [01<timeout>] [02<max. status infos>]
[05<pump no.>] [0B<trace-number>] [3B<AID>] [3C<additional-data>]
[8A<card type>][06<TLV-container>]
Data block:
04<amount>: If not sent, then the PT uses the default amount stored as Pre-Authorisation Amount for
that particular card-type.
06<TLV-container>: Possible tags are 15, 20, 41, 43, E1, E8, 1F06, 1F15, 1F2B.
0B<trace-number>: See Status-Information (04 0F).
For further sequence of events for the transaction see Authorization (06 01).
This command reverses a payment-procedure and transfers the receipt-number of the transaction to be re-
versed from the ECR to PT. The result of the reversal-process is sent to the ECR after Completion of the
booking-process.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 30 xx <password> 87<receipt-no> [04<amount>] [49<CC>]
[19<payment-type>] [2D<track 1 data>] [0E<expiry-date>] [22<card-
number>] [23<track 2 data>] [24<track 3 data>] [3C<additional-data>]
[06<TLV-container>]
Data block:
All other data will be ignored by the PT.
The reversal is only carried-out if a payment with the supplied receipt-number is found in the turnover-
storage and amount (optional) as well as card-data (optional) match that payment.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
The further sequence of events is – apart from checking the issue of goods or filling – identical to the Author-
ization (06 01).
This command executes a Partial-Reversal for a Pre-Authorisation to release the unused amount of the res-
ervation. This command is also used for the Booking of a Reservation.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 23 xx [87<receipt-no>] [04<amount>] [49<CC>] [3C<additional-data>]
[0B<trace-number>] [3B<AID>] [06<TLV-container>]
Data block:
87<receipt-no>: Is only sent for Partial-Reversal.
04<amount>: Unused partial-amount of the pre-authorised transaction. Default is 0.
3C<additional-data>: See chapter Additional Data.
06<TLV-container>: Possible tags are 1F06, 1F2B (see also chapter Pre-Authorisation / Reservation (06
22)).
0B<trace-number>: See chapter Status-Information (04 0F).
BMP 0B or TLV tag 1F2B must be sent for a reservation booking or reservation extension or partial
reversal.
For telephonic extensions the BMP 0B or TLV-Tag 1F2B are optional.
3B<AID>: See chapter Status-Information (04 0F). BMP 3B must be sent for a reservation booking or
reservation extension or for a telephonic reservation booking or telephonic reservation extension. See
tag 1F06.
All other data will be ignored by the PT.
The Partial-Reversal is only carried-out if a Pre-Authorisation with the passed receipt number is found in the
turnover-records.
Caution:
This is special-case of the command Partial-Reversal of a Pre-Authorisation / Booking of a Reservation (06
23). Also valid for credit-cards and fleet-cards for which typically Book Total (06 24) instead Partial-Reversal
of a Pre-Authorisation / Booking of a Reservation (06 23) is executed.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 23 03 87 FF FF
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 04xx B8 [87<receipt-no>] [06<TLV-container>]
Data block:
B8 is the error-code decimal 184.
87<receipt-no>: States the receipt-number of the first pre-authorisation not yet reversed. If no pre-
authorisations exist in the PT, <receipt-no> is set to ‘FFFF’.
06<TLV-container>: Possible tags are 23.
Instead of a single receipt-number the PT can also transmit a receipt-number list as a TLV-container.
However, for this the ECR must have sent a BMP 06 in the triggering command or in the registration.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
This chapter describes the process of partial reversal in combination with the transparent APDU mode.
The figure below shows the communication between ECR, POS and the PSP.
When using the partial reversal with transparent APDU mode the following conditions should be respected.
- Partial reversal with APDU mode can only be used in combination with the procurement command (06
05). When using the procurement command, the card will be locked in the reader after processing the
authorization. It is not possible to change the card in this sequence.
- When the vending machine is processing card communication (“Issueing of goods”) it is possible to send
several APDU commands (Send APDU 06 C6).
Procurement 0605
Authorization
Status 040F
Response 84-9D
Partial amount
Partial reversal
060F
This command executes booking of the total amount for a Pre-Authorisation / Reservation (06 22). The por-
tion of the amount from the Pre-Authorisation / Reservation (06 22) that was used up is booked.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 24 xx 87<receipt-no> [04<amount>] [49<CC>] [19<payment-type>]
[3C<additional-data>] [0B<trace-number>] [3B<AID>] [8A<card type>]
[06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 15, 41, 1F06 (see also Pre-Authorisation / Reservation (06 22)).
0B<trace-number>: See Status-Information (04 0F).
BMP 0B or TLV tag 1F2B must be sent for a reservation booking or reservation extension or partial
reversal.
For telephonic extensions the BMP 0B or TLV-Tag 1F2B is optional.
3B<AID>: See Status-Information (04 0F). BMP 3B must be sent for a reservation booking or reservation
extension or for a telephonic reservation booking or telephonic reservation extension. See tag 1F06.
For cards which can not identified by the BIN, like CUP, the card type has to be sent with the command.
Therefor the BMP 8A or TLV tag 41 is used.
The further sequence of events is identical to the Partial-Reversal of a Pre-Authorisation / Booking of a Res-
ervation (06 23).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 25 xx 87<receipt-no> [04<amount>] [49<CC>] [19<payment-type>] [06<TLV-
container>]
The further sequence of events is – apart from checking the issue of goods or filling – identical to the Partial-
Reversal of a Pre-Authorisation / Booking of a Reservation (06 23).
Note:
The command Pre-Authorisation Reversal cannot be carried out with ec-cash and Maestro cards. For these
cards types an Auto-Reversal is executed instead.
This command starts a Refund on the PT. The result of the Refund is reported to the ECR after completion
of the booking-process.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 31 xx <password> [04<amount>] [49<CC>] [19<payment-type>]
[2D<track 1 data>] [0E<expiry-date>] [22<card-number>]
[23<track 2 data>] [24<track 3 data>] [3B<AID>] [3C<additional-data>]
[8A<card type>] [06<TLV-container>]
Data block:
04<amount>: For bonus-transactions the amount is optional. In this case the tag E1 with subtag C2 can
be sent instead of the amount.
3B<AID>: Is used in refunds after an encashing transaction of bonus-points, using the BMP 3B from the
Status-Information (04 0F) of this transaction.
06<TLV-container>: Possible tags are 15, 20, 30, 41, 43, E1 (for C1 values '47 4C' and '4D 57' possible),
E8.
For cards which can not identified by the BIN, like CUP, the card type has to be sent with the command.
Therefore the BMP 8A or TLV tag 41 is used.
Remaining bitmaps see Authorization (06 01).
All other data will be ignored by the PT.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR induces the PT to transfer the stored turnover to the host.
Caution:
If the receipt printout shall be carried out by the ECR, this may only send the command to the PT if the ECR
printer is ready and enough paper for the receipt is available.
2.15.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 50 03 <password> [06<TLV-container>]
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.15.2 Transaction:
Following the response the PT begins with the transaction.
For this purpose the PT makes an online-connection to the host. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
2.15.4 Status-Information
The PT responds following successful End-of-Day with the Status-Information after End-Of-Day / Send
Turnover Totals:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [27<result-code>] [<transaction-data>]
Data block:
27<result-code>: 1 byte. See chapter Error-Messages.
<transaction-data>: See chapter Status-Information (04 0F).
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Following the Status-Information, if the PT function ECR-Receipt is activated (= setting in PT, that the ECR
assumes the print-function), then the PT transmits the receipt line-by-line to the ECR using „Print Line“
Commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out using the „Print
Text-Block“ Command (see chapter Print line (06 D3)).
2.15.5 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out
using the „Print Text-Block“ command (see chapter Print line (06 D3)).
2.15.6 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <error-code>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR forces the PT to send a diagnostic message to the host.
2.16.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 70 xx [06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 1B.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.16.2 Transaction:
Following the response the PT starts the transaction.
For this purpose the PT makes an online-connection to the host. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
2.16.5 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ Commands (see chapter Print line (06 D1)) or Print Textblock-Commands (06 D3).
2.16.6 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte, defined in chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR forces the PT to send a initialisation message to the host.
2.17.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 93 03 <password>
Data block:
<password>: See chapter Password.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.17.2 Transaction:
Following the response the PT begins with the transaction.
For this purpose the PT makes an online-connection to the host. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
2.17.4 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out
using the „Print Text-Block“ command (see chapter Print line (06 D3)).
2.17.5 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte, defined in chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.18.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 12 xx <password> <from> [<to>]
Data block:
<password>: See chapter Password.
<from>: 2 byte, BCD. Receipt number the printing should start from.
<to>: 2 byte, BCD. Receipt number the printing should end at (including this receipt). If omitted the PT
only prints the receipt given in <from> (i.e. <from> = <to>).
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.18.2 Receipt-Printout
If the PT function ECR-Receipt is activated (= setting in PT, that the ECR assumes the print-function), then
the PT transmits the receipt line-by-line to the ECR using „Print Line“ Commands (see chapter Print line (06
D1)). Alternatively the receipt printout is carried out using the „Print Text-Block“ Command (see chapter Print
line (06 D3)).
2.18.3 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
This command serves to repeat printing of the last stored payment-receipts or End-of-Day-receipt.
2.19.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 20 03 <password> [03<service-byte>][06<TLV-container>]
Data block:
<password>: See chapter Password.
03<service-byte>: Bit-field, 1 byte; default = ‘00’. See Table 5: Definition of <service-byte>.
06<TLV-container>: Possible tags are 1F01, 1F02, 1F03.
Service-byte Definition
xxxx xxx1 1: ECR requires Status-Information (as in the original transaction)
0: Do not send Status-Information
xxxx xx1x 1: No print receipt (neither Print line commands sent from PT nor printed on PT itself)
0: Print receipt (either Print line commands sent from PT or printed on PT itself)
Rest RFU
Table 5: Definition of <service-byte>
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.19.2 Status-Information
Depending on the service-byte the PT sends the Status-Information of the last transaction executed. This
ensures that the ECR can resynchronise in case of an inconclusive ending of a transaction.
2.19.3 Receipt-Printout
If the PT function ECR-Receipt is activated (= setting in PT, that the ECR assumes the print-function), then
the PT transmits the receipt line-by-line to the ECR using „Print Line“ Commands (see chapter Print line (06
D1)). Alternatively the receipt printout is carried out using the „Print Text-Block“ Command (see chapter Print
line (06 D3)). Alternatively the PT prints the receipt on its own printer.
2.19.4 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “master-
rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the PT reads a chip-card/magnet-card and transmits the card-data to the ECR.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 C0 xx [<timeout>[19<card-type>][FC<dialog-control>][06<TLV-container>]]
Data block:
<timeout>: 1 byte. The time in seconds the PT waits for the card. <timeout> = ‘00’ means infinite. If
<timeout> is omitted the default-value of the PT is used. This timeout overrides the T3 timeout.
19<card-type>: 1 byte. If <card-type> and TLV tag 1F60 are omitted the magnet-stripe will be read. For a
motor-insertion reader both chip and magnet-stripe are read. See Table 6: Definition of <card-type>.
If <card-type> is entered then <timeout> must also be entered.
FC<dialog-control>: Bit-field, 1 byte. See Table 7: Definition of <dialog-control>.
06<TLV-container>: Possible tags are 1F15, 1F60 (overrides field 19).
card-type Definition
0001 xxxx chip card
0010 xxxx chip card
0101 xxxx chip-card and magnet-card
all others magnet-card
Table 6: Definition of <card-type> (only for non-motor-insertion reader relevant)
dialog-control Definition
xxxx xxx1 PT controls display prompts for insertion and removal of the card (default).
xxxx xxx0 ECR controls display prompts for insertion and removal of the card. That means the PT
does not display its own text for command Read Card, therefore the ECR must send its
own text via command text to the PT.
all others RFU
Table 7: Definition of <dialog-control>
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
If the ECR requested Intermediate-Status from the PT during registration, these commands are sent be-
tween PT and ECR. See Intermediate Status Information (04 FF).
The PT responds after the read-process with the Status-Information transferring the card-data. Thereby an
implicit master-rights change to the ECR takes place, i.e. there is no Completion command. A full description
can be found in Status-Information (04 0F).
Note:
Using the command Abort the ECR can release a retained card from the PT without waiting for a release via
timeout.
Caution:
A protocol-conflict can occur if the ECR sends an Abort command during transmission of the card-data from
the PT. Example: Another customer inserts a card whilst Partial-Reversal after a completed Filling-process
is taking place.
If the ECR sends an Abort command to the PT whilst the PT is also transmitting data to the ECR (e.g. be-
cause a Partial-Reversal has to be executed), both commands (from ECR and PT) result in an error since
the required responses from the partner are not correctly answered – at transport-protocol level each partner
must send an ACK, and at application-protocol level a 80-00-00, but instead only one command is sent.
This results in both messages being repeated twice (which causes further collisions), and the PT falls-back
into its basic-state. Therewith is the ECR master again and can repeat the Abort command (to release the
card), which the PT will then execute correctly.
For new implementations the ECR should not send the command Read-Card with infinite timeout, but
rather should use command Status-Readout until a card is inserted. Following this the card can be
read.
With this command the ECR can activate the insertion-mechanism of a motor-insertion on the PT. Only after
sending this commands is it possible to insert a card in motor-insertion reader.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 50 xx [FA<card-reader-activation>]
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 xx 00
With this command the ECR can instruct the PT to abort execution of a command. Additionally, a card which
remained in the PT after a Read-Card command will be released or extracted using this command.
The Abort command may only be sent from the ECR when the ECR is the master, or when the command
explicitly allows that the ECR can send an Abort command (e.g. in command “Read Card” or the text-display
commands).
Depending on the implementation of the PT, transaction steps and other actions within the PT may be abort-
ed if pre-defined states have not been reached.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 B0 xx [D2<card-output-direction>][FA<card-reader-activation>]
Data block:
FA<card-reader-activation>: This option can be used to optimize the number of ZVT commands by omit-
ting the Activate Card-Reader (08 50) command after the Abort (06 B0) command.
For motor-readers which can park the card in a second position, the Abort command without parameter
<card-output-direction>, or with <card-output-direction> not equal to 02 results in the card in the reading-
area being rejected and the parked card being transported to the reading-area.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 <result-code> 00
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 02 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR can set the system-time in the PT.
2.24.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 91 0B <password> AA<date> 0C<time>
Data block:
<password>: See chapter Password.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.24.2 Completion
After setting the new system-time the PT sends a Completion command:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR can cause the PT to display a certain text on the PT-display.
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 E0 xx [F0<display-duration>] [F1<text line 1>] [F2<text line 2>]
[F3<text line 3>] [F4<text line 4>] [F5<text line 5>] [F6<text line 6>]
[F7<text line 7>] [F8<text line 8>] [F9<beep-tones>] [FD<display-
device>]
Data block:
F0<display-duration>: The display duration overrides the T3 timeout.
Text encoding: 7-bit ASCII ZVT-Characterset, e.g. F0 F3 01 23 45 (F0 F3 means 3 byte length, followed
by the ASCII-Codes). Character codes > 127 are displayed according to the 8-bit ZVT-Characterset
(CP437, OEM-US)
Note: The encoding of the display text in BMP F1-F8 must match to current character set of the PT that
can be configured by ECR with tag 14 in Registration command.
Switch to larger font: each line can be individually switched to a larger font (height +width) via a pre-fix
control-character ‚14‘ (ASCII-Code). This reduces the number of lines it is possible to display and also
the number of characters per line.
Each line can be controlled individually. On each line only one font-type can be used.
The bitmaps are optional.
The illustrated order is variable.
Notes:
Omitted text-lines are displayed empty.
If all text-lines are omitted the display is left off.
If the ECR sends a new Display-text command or another command which influences the PT display, the
PT displays the new text immediately, before the display-duration of the initial command has expired.
If the ECR sends a command which does not influence the PT display, the PT displays the original text
until the display-duration of the initial command has expired.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR can cause the PT to display a certain text on the PT-display.
Following an optional timeout, a further text can be displayed.
Caution:
This command is included to retain downwards-compatibility, for new implementations use Display Text (06
E0)!
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 85 xx <display-data>
Data block:
<display-data>:consists of a number of fields, the fields are not prefixed with a bitmap
Format of the text-field: <position><text><00>, the text must always be terminated with binary ‘00’. <po-
sition> (BCD encoded) is the start-position on the display, ‘00’ is the first line (from top) left edge; on
reaching the right edge a line is automatically wrapped. For 20 characters per line is ‘20’ the left edge of
the second line etc.
The maximum displayable number of characters = max. number of characters per line * max. number of
lines, additional characters will not be displayed.
Text encoding: 7-bit ASCII with umlauts. If the ms-bit of a character is set, this generates a beep-tone,
alternatively the character BEL (= ‘07’) can be sent.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR can cause the PT to display a certain text on the PT-display and then to wait for
a function-key to be pressed. The code for the function-key is returned to the ECR.
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 E1 xx <display-data> [06<TLV-container>]
Data block:
<display-data>: See chapter Display Text (06 E0).
If the ECR sends a new command for which no display on the PT is required then the PT displays this
display-text until the end of the display-duration.
06<TLV-container>: Possible tags are 1F18.
If tag 1F18 equals to 1 or bitmap F9 in the <display data> equals to ‘FF’ the PT responds to card in-
serts also.
Text encoding:
7-bit ASCII ZVT-Characterset, e.g. F0 F3 01 23 45 (F0 F3 means 3 byte length, followed by the ASCII-
Codes). Character codes > 127 are displayed according to the 8-bit ZVT-Characterset (CP437, OEM-
US)
Note: The encoding of the display text in BMP F1-F8 must match to current character set of the PT that
can be configured by ECR with tag 14 in Registration command.
After key-entry or timeout the PT sends the key-code to the ECR. The timeout has the value of T3, e.g. 5s.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 01 <key-code>
Data block:
<key-code>: 1 byte.
2.28 Display Text with Function-Key Input (old version) (06 88)
With this command the ECR can cause the PT to display a certain text on the PT-display and then to wait for
a function-key to be pressed. The code for the function-key is returned to the ECR.
Caution:
This command is included to retain downwards-compatibility, for new implementations use Display Text with
Function-Key Input (06 E1)!
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 88 xx <display-data>
Data block:
<display-data>: See chapter Display Text (old version) (06 85).
After key-entry or if timeout the display is cleared.
If the ECR sends a new command for which no display on the PT is required, then the PT displays this
display-text until the end the display-duration.
Text encoding
7-bit ASCII with umlauts. If the ms-bit of a character is set, this generates a beep-tone, alternatively the
character BEL (= ‘07’) can be sent.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 01 <key-code>
Data block:
<key-code>: 1 byte.
With this command the ECR can cause the PT to display a certain text (text1) on the PT-display and then to
wait for a numerical-input. The number entered is returned to the ECR. Optionally a second text (text2) may
be sent, which is displayed by the PT after input of the first character. If the character is deleted with <C> the
PT displays text1 again.
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 E2 xx [F0<display-duration>] [F1<text line 1>] [F2<text line 2>]
[F3<text line 3>] [F4<text line 4>] [F5<text line 5>] [F6<text line 6>]
[F7<text line 7>] [F8<text line 8>] [F9<beep-tones>] [FB<confirmation>]
[E0<min. length>] [E1<text2 line 1>] [E2<text2 line 2>]
[E3<text2 line 3>] [E4<text2 line 4>] [E5<text2 line 5>]
[E6<text2 line 6>] [E7<text2 line 7>] [E8<text2 line 8>]
[E9<max. Length>] [EA<echo>] [EB<MAC>] [06<TLV-container>]
Data block:
bitmap Definition
F0 display-duration in seconds, 1 byte (not BCD packed), ‘00’ means infinite.
default-value: ‘00’
F1 text1 line 1
F2 text1 line 2
F3 text1 line 3
F4 text1 line 4
F5 text1 line 5
F6 text1 line 6
F7 text1 line 7
F8 text1 line 8
F9 number the beep-tones, 1 byte
FB confirmation of the input with <OK> required; ‘00’ = no, otherwise yes, 1 byte ;
default: yes
E0 min. length of the input; ‘00’ = input not enforced, 1 byte. default-value: ‘00’
E1 text2 line 1
E2 text2 line 2
E3 text2 line 3
E4 text2 line 4
E5 text2 line 5
E6 text2 line 6
E7 text2 line 7
E8 text2 line 8
E9 Max. length of the input, 1 byte. default-value: 20 decimal
EA echo the input yes/no; ‘FF’ = echo on, ‘00’ echo off, otherwise display “*” for
each digit; 1 byte. default-value: ‘01’ = „*“
EB MAC over text 1 and text 2 (BMPs: F1 - F8 and E1 - E8); 8 byte: mandatory
field !
06<TLV-container>: Possible tags are 1F35.
Text encoding:
7-bit ASCII ZVT-Characterset, e.g. F0 F3 01 23 45 (F0 F3 means 3 byte length, followed by the ASCII-
Codes). Character codes > 127 are displayed according to the 8-bit ZVT-Characterset (CP437, OEM-
US)
Note: The encoding of the display text in BMP F1-F8 and E1-E8 must match to current character set of
the PT that can be configured by ECR with tag 14 in Registration command.
Switch to larger font: each line can be individually switched to a larger font (height + width) via a pre-fix
control-character ‘14’ (ASCII-Code). This reduces the number of lines it is possible to display and also
the number of characters per line.
Each line can be controlled individually. On each line only one font-type can be used.
The MAC is a safeguard of the display-text to prevent mis-use of the PT for PIN request. The correct
value for each text can be obtained from the hotline.
The bitmaps are optional.
The illustrated order is variable.
Text-lines not received are shown empty on the display.
If all text-lines are missing the display stays off.
Note:
Depending on the PT, the line used for numerical input may not contain text. If so, the PT ignores the corre-
sponding BMP.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 xx <key-codes>
Data block:
<key-codes>
Value Definition
‚xyz‘ ASCII-code of the input in hex-notation
1B abort-key <STOP>
46 Function-/Info-key <F>, <Info> or <?>
31 Function-key <F1>
32 Function-key <F2>
33 Function-key <F3>
34 Function-key <F4>
6C timeout
2.30 Display Text with Numerical Input (old version) (06 86)
With this command the ECR can cause the PT to display a certain text (text1) on the PT-display and then to
wait for a numerical-input. The number entered is returned to the ECR. Optionally a second text (text2) may
be sent, which is displayed by the PT after input of the first character. If the character is deleted with <C> the
PT displays text1 again.
Caution:
This command is included to retain downwards-compatibility, for new implementations use Display text with
Numerical Input (06 E2)!
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 86 xx <display-data>
Data block:
<display-data>: Consists of several:
Definition
Definition
max. length of the input, length 1 byte
confirmation required, length 1 byte
confirmation-position, length 2 byte (will be ignored)
start-position for echo of the input, length 1 byte (will be ignored)
text 1, length variable
text 2, length variable
MAC over all previous parameters
Format of the text-field: <position><text><00>, the text must always be terminated with binary ‘00’. <po-
sition> (BCD encoded) is the start-position on the display, ‚00‘ is the first line (from top) left edge; on
reaching the right edge a line is automatically wrapped. For 20 characters per line is ‘20’ the left edge of
the second line etc.
The maximum displayable number of characters = max. number of characters per line * max. number of
lines, additional characters will not be displayed.
Text encoding: 7-bit ASCII with umlauts. If the ms-bit of a character is set, this generates a beep-tone,
alternatively the character BEL (= ‘07’) can be sent.
The MAC is a safeguard of the display-text to prevent mis-use of the PT for PIN request. The correct
value for each text can be obtained from the hotline.
confirmation = ‘00’ means confirmation the input with <OK> not required; other value means confirmation
of the input with <OK> required.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 xx <key-codes>
Value Definition
‚xyz‘ ASCII-code of the input in hex-notation
1B abort-key <STOP>
46 Function-/Info-key <F>, <Info> or <?>
31 Function-key <F1>
32 Function-key <F2>
33 Function-key <F3>
34 Function-key <F4>
6C timeout
Following the input and its confirmation, or abort or if timeout, the display is cleared.
Sequence:
The ECR causes the PT to show a certain text on the display of the PT (text1) and then to wait for a numeri-
cal input (customer-card PIN). Afterwards the inputted number is compared to a pre-defined encrypted num-
ber from the ECR (encrypted Customer-card-PIN). Optionally a second text (text2) can be supplied which the
PT displays after the first digit is inputted. If the digits are deleted <C> the PT displays text1 again.
The inputted digits are shown as ‚*‘.
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 E3 xx <parameter-list>
Data block:
<parameter-list> consists of several fields, whereby each field is preceded by a bitmap
bitmap Definition
D3 key-position, 1 byte
Text encoding:
7-bit ASCII ZVT-Characterset, e.g. F0 F3 01 23 45 (F0 F3 means 3 byte length, followed by the ASCII-
Codes). Character codes > 127 are displayed according to the 8-bit ZVT-Characterset (CP437, OEM-
US)
Note: The encoding of the display text in BMP F1-F8 and E1-E8 must match to current character set of
the PT that can be configured by ECR with tag 14 in Registration command.
Switch to larger font: each line can be individually switched to a larger font (height +width) via a pre-fix
control-character ‘14’ (ASCII-Code). This reduces the number of lines it is possible to display and also
the number of characters per line.
Each line can be controlled individually. On each line only one font-type can be used.
Algorithm-key: depending on the card used, different algorithms are used for calculating the customern-
PIN. These are listed below.
algorithm-ID fleet-card
0x00 Hectronic
0x01 Venture Card
0x02 UTA
0x03 BICA
0x04 Proeda
0x05 Wayne Dresser
0x06 Shell
0x07 LeasePlan
0x08 DKV classic
0x09 Huth
0x0A LOMO
0x0B frei & flott
0x13 BICA 2
0x14 DataStandards CH
0x24 ESSO MK2
0x25 EuroShell
0x38 BFT
0x46 DKV Selection Card
0x56 DEA/DEKRA
0x57 DUKPT
Note:
Depending on the PT, the line used for numerical input may not contain text. If so, the PT ignores the corre-
sponding BMP.
Following customer-card PIN input the PT compares the entered customer-card PIN with the encoded PIN
from the command call.
Data block:
06<TLV-container>: Possible tags are 1F31, 1F32.
Data block:
06<TLV-container>: Possible tags are 1F16.
Following the input and its confirmation, or abort or if timeout, the display is cleared.
Sequence:
The ECR causes the PT to show a certain text on the display of the PT (text1) and then to wait for a numeri-
cal input (customer-card PIN). Afterwards the inputted number is compared to a pre-defined encrypted num-
ber from the ECR (encrypted Customer-card-PIN). Optionally a second text (text2) can be supplied which the
PT displays after the first digit is inputted. If the digits are deleted <C> the PT displays text1 again.
The inputted digits are shown as ‘*’.
Caution:
This command is included to retain downwards-compatibility, for new implementations use PIN-Verification
for Customer-Card (06 E3)!
This command can be terminated prematurely using the command Abort (06 B0).
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 87 xx <parameter-list>
Data block:
<parameter-list> consists of several fields.
Definition
algorithm-Key, length 1 byte
PIN-length, length 1 byte
confirmation PIN required, length 1 byte, 00 = no; otherwise yes
start-position for echo of the input, length 1 byte (will be ignored)
PIN-request text, length variable; format 00<Text>00
driver-code length, length 1 byte, optional
confirmation driver-code required, length 1 byte, 00 = no; other-
wise yes, optional
start-position driver-code for echo the driver-code-Input, length 1
byte (will be ignored), optional
driver-code request text, length variable; format 00<Text>00, op-
tional
cards-specific data for checking the customer-card PIN, length
variable (see card-issuer specification)
Note:
Depending on the PT, the line used for numerical input may not contain text. If so, the PT ignores the corre-
sponding BMP.
Following customer-card PIN input the PT compares the entered customer-card PIN with the encoded PIN
from the command call.
Data block:
<driver-code>, optional
Following the input and its confirmation, or abort or if timeout, the display is cleared.
With this command the ECR selects the language in the PT.
2.33.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 30 01 <language >
Data block:
<language-number>: 1 byte. See Table 8: Definition of <language>.
language Definition
0x00 German (=factory-setting)
0x01 English
0x02 French
0x03 Italian
0x04 Hungarian
language Definition
0x05 Slovenian
0x06 Spanish
0x07 Czech
0x08 Swedish
0x09 Dutch
0x0A Polish
0x0B Slovak
0x0C Danish
0x0D Greek
0x0E Portuguese
Table 8: Definition of <language>
Notes:
The chosen language remains set even after an off/on sequence.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.33.2 Completion
Following the language switch the PT sends a Completion command:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command ECR causes the PT to make a connection to the TCS.
2.34.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 10 xx [06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 0F.
Using tag 0F an assignment-number can be given to the PT, which enables further sequence-control
during the call from PT to TCS.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.34.2 Data-Transmission:
For this purpose the PT makes an online-connection to the TCS. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
Note:
If the PT makes the connection to TCS via a communication module in the PT as opposed to a communica-
tion module connected to the ECR, the PT sends the Completion command before the update (depending on
implementation before or after the successful connection to TCS). This ensures that the ECR is not blocked
during the total time of the software-update.
2.34.3 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “master-
rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx 27<result-code> 0C<time> AA<date>
If the PT switches intermediately into Transparent-Mode then no Completion command is sent at the end
(see chapter Transparent-Mode (06 DD)).
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR can start the sequence once again from the
beginning the secure that software-update is successfully carried out.
With this command the ECR causes the PT to send a file (e.g. the merchant-journal) to the ECR.
2.35.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 11 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 2D (multiple, each with a subtag 1D and optional 1E).
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.35.2 Transmission
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 2D (multiple, each with tags 1C, 1D, and optional 1E, 1F00).
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.35.3 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “master-
rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx 27<result-code>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning.
With this command the ECR causes the PT to delete a file (e.g. the merchant-journal).
2.36.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 12 xx [06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 1D (several).
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.36.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx 27<result-code>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning.
The file will only be deleted if the ECR acknowledges the Completion with 80-00.
With this command the ECR provides manufacturer specific configuration information to the PT and may also
trigger a re-configuration procedure when applicable.
2.37.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 13 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 2D (multiple, each at least with a tag 1C containing the actual
configuration information (representation and meaning are manufacturer-specific)).
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.37.2 Completion
After applying the provided configuration the PT terminates the process via Completion whereupon the ECR
receives back the “master-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx 27<result-code>
ECR response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning.
Tax Free is the elimination of income tax liability on accumulated investment earnings. By issuing this com-
mand, the PT prints a cheque for tax refund through Global Refund for Non-EU-citizens. This cheque needs
to be filled out and signed by the merchant and the customer in order to be valid. Since this command needs
a printout according to the rules of Global Refund, the function can only be used on PTs fitted with a printer
and printing on the PT enabled.
2.38.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 0A xx [04<amount>]
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.38.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR causes the PT to send an overview about the stored transactions.
2.39.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 10 03 <password>
Data block:
<password>: See chapter Password.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.39.2 Status-Information
The PT responds with the Status-Information after End-Of-Day / Send Turnover Totals:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [27<result-code>] [<transaction-data>]
Data block:
<transaction-data>: See chapter Status-Information after End-Of-Day / Send Turnover Totals.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.39.3 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.40.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 18 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.40.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR causes the PT to print its system information to the print target defined in Regis-
tration (06 00).
2.41.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 1A 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.41.2 Receipt-Printout
If the PT function ECR-Receipt is activated (= setting in PT, that the ECR assumes the print-function), then
the PT transmits the receipt line-by-line to the ECR using „Print Line“ Commands (see chapter Print line (06
D1)). Alternatively the receipt printout is carried out using the „Print Text-Block“ Command (see chapter Print
line (06 D3)). Alternatively the PT prints the receipt on its own printer.
2.41.3 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR causes the PT to set or reset the terminal identifier. The command will only be
executed, if the turnover storage is empty e.g. after an end of day command.
2.42.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 1B xx <password>[29<terminal ID>]
Data block:
<password>: See chapter Password.
29<terminal ID: If present the content becomes the new terminal identifier.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.42.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR causes the PT load off eventually stored offline transactions to the host. It does
not imply an end of day command.
2.43.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 51 03 <password>
Data block:
<password>: See chapter Password.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.43.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR causes the PT start a self test and print it's system information to the print target
defined in Registration (06 00).
2.44.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 79 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.44.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command the ECR can change the merchant password required for some ZVT commands to the
PT (see chapter Password).
2.45.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 95 06 <old password> <new password>
Data block:
<old password>: 3 bytes, BCD. The old password.
<new password>: 3 bytes,BCD. The new password to be set.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.45.2 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “mas-
ter-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx 27<result-code>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning.
With this command the ECR causes the PT to make a connection to the Personalisation-System to start an
OPT-action.
2.46.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 20 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.46.2 Transaction
Following the response the PT begins with the transaction.
For this purpose the PT makes an online-connection to the PS. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
2.46.4 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ Commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out
using the „Print Text-Block“ Command (see chapter Print line (06 D3)).
2.46.5 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “master-
rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 0A 27<result-code> 0C<time> AA<date>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning to ensure that the OPT-action is successfully carried out.
With this command the ECR sets the point-in-time for the next OPT-Action in the PT.
2.47.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 21 0B <password> AA<date> 0C<time>
Data block:
<password>: See chapter Password.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.47.2 Completion
After setting the OPT Point-in-Time the PT sends a Completion command:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If the cannot set the OPT Point-in-Time (e.g. because Pre-Initialisation was not yet executed) the PT re-
sponds with command Abort instead of Completion.
With this command the ECR causes the PT to make a connection to the Personalisation-System to start an
OPT Pre-Initialisation.
2.48.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 22 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.48.2 Transaction:
Following the response the PT begins with the transaction.
For this purpose the PT makes an online-connection to the PS. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
2.48.4 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ Commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out
using the „Print Text-Block“ Command (see chapter Print line (06 D3)).
2.48.5 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “master-
rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 0A 27<result-code> 0C<time> AA<date>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning to ensure that the OPT-action is successfully carried out.
With this command the ECR can obtain the stored OPT-data from the PT.
2.49.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 23 03 <password>
Data block:
<password>: See chapter Password.
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.49.3 Completion
Following output of the OPT-Data the PT sends a Completion command:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If the PT has no stored OPT-Data then the PT responds with command Abort instead of Completion.
2.50.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 24 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.50.2 Transaction:
Following the response the PT begins with the transaction.
For this purpose the PT makes an online-connection to the PS. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
2.50.4 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ Commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out
using the „Print Text-Block“ Command (see chapter Print line (06 D3)).
2.50.5 Completion
Subsequently the PT terminates the process via Completion whereupon the ECR receives back the “master-
rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 0A 27<result-code>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E 01 <result-code>
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Note:
In error-case (i.e. <result-code> is not equal to ‘00’) the ECR starts the sequence again from the begin-
ning to ensure that the OPT-action is successfully carried out.
With this command the ECR switch the PT into Service-Mode. In Service-Mode the PT displays the configu-
ration-menu.
2.51.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 01 xx [<password>[03<service-byte>]]
Data block:
<password>: See chapter Password.
03<service-byte>: See Table 9: Definition of <service-byte>. If <service-byte> is sent then <password>
must also be sent.
Service-byte Definition
xxxx xxx1 The PT service-menu of the PT may not be displayed against the function-key on the PT.
xxxx xxx0 The PT service-menu of the PT may be displayed against the function-key on the PT.
Rest RFU
Table 9: Definition of <service-byte>
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.51.2 Service-Mode
Subsequently the PT shows the menu on its display. The operator can now execute different functions on
the PT. As long as the PT is in Service-Mode it is the master.
In Service-Mode the PT can send Dial-Up commands, Print-Line commands and Intermediate Status-
Information.
Caution:
If the PT does not send any command to the ECR within timeout T4 the ECR assumes that the PT no longer
functional and will not react to any further commands from the PT. To avoid this, the PT should periodically
send Intermediate Status-Information (where necessary with changed T4 value) to the ECR.
Note:
Following long-lasting events (e.g. software-update) the PT sends the Completion command independently
so that a service-technician does not have to remain at the PT until the end of the event.
2.51.4 Completion
To terminate the Service-Mode the PT sends a Completion command:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
The ending of the Service-Mode causes the PT to exit the Service-Menu and the ECR and PT set timeout T4
back to the default value.
Note:
If the PT makes the connection to TCS via a communication module in the PT as opposed to a communica-
tion module connected to the ECR, the PT sends the Completion command before entering the Service-
Mode. This ensures that the ECR is not blocked during the total time of the Service-Mode.
With this command the ECR can request the Status of the PT allow the PT to carry out time-controlled
events (e.g. OPT-actions or End-of-Day). To allow time-controlled events on the PT to be executed punctual-
ly the ECR should send Status-Enquiries as often as possible (every minute or more frequently).
2.52.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
05 01 xx [<password>[03<service-byte>]]
Data block:
<password>: See chapter Password.
03<service-byte>: SeeTable 10: Definition of <service-byte> Table 9: Definition of <service-byte>. If
<service-byte> is sent then <password> must also be sent.
Service-byte Definition
xxxx xxx1 The PT service-menu of the PT may not be displayed against the function-key on the PT.
xxxx xxx0 The PT service-menu of the PT may be displayed against the function-key on the PT.
xxxx xx1x Do NOT send SW-Version in Completion command
xxxx xx0x Do send SW-Version in Completion command, default if no service-byte sent
xxxx x0xx Do not send further status information in the completion (TLV-container).
xxxx x1xx Send further status information in the TLV-container of the completion.
All other RFU
Table 10: Definition of <service-byte>
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.52.2 Transaction:
If the PT does not wish to start any events it sends a Completion command, otherwise it sends other com-
mands (Dial-Up commands, Print-Line commands and Intermediate Status-Information).
For this purpose the PT makes an online-connection. This takes place – depending on configuration of the
PT and ECR – either over a communication module in the PT or over a communication module connected to
the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up (06 DA)).
Until the Completion command is sent the PT is the Master. If the PT switches intermediately into Transpar-
ent-Mode then no Completion command is sent at the end (see chapter Transparent-Mode(06 DD)).
2.52.4 Receipt-Printout
After the transaction the Receipt-Printout takes place. If the PT function ECR-Receipt is activated (= setting
in PT, that the ECR assumes the print-function), then the PT transmits the receipt line-by-line to the ECR
using „Print Line“ Commands (see chapter Print line (06 D1)). Alternatively the receipt printout is carried out
using the „Print Text-Block“ Command (see chapter Print line (06 D3)).
Caution:
If the PT does not send any command to the ECR within timeout T4 the ECR assumes that the PT no longer
functional and will not react to any further commands from the PT. To avoid this, the PT should periodically
send Intermediate Status-Information (where necessary with changed T4 value) to the ECR.
2.52.5 Completion
To terminate the Status-Enquiry the PT sends a Completion command:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx [<SW-version>] <terminal status-code> [06<TLV-container>]
Data block:
<SW-version>: LLLVAR, 7-bit ASCII with umlauts. The software-version of the PT, optional in depend-
ency with the service-byte of the calling commands from the ECR.
<terminal status-code>: 1 byte. See chapter Terminal Status Codes.
06<TLV-container>: Possible tags are 1F44, 1F54, 1F55, 1F56, 1F59, E4 (containing subtags 1F40,
1F41, 1F42, 1F43), E7 (containing subtags 1F57, 1F58).
The TLV-container is sent if the service-byte is set to xxxx x1xx.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Following termination of the Status-Enquiry the ECR and PT set timeout T4 back to the default setting.
The ECR can change the communication baud rate with this command if a serial connection is used.
2.53.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 40 01 <baudrate>
Data block:
<baudrate>: 1 byte. See Table 11: Definition of <baudrate>.
Baudrate Definition
0 9600 Baud
1 19200 Baud
2 RFU
3 RFU
4 RFU
5 RFU
6 57600 Baud
7 115200 Baud
Table 11: Definition of <baudrate>
2.53.2 Response
If the PT can change the baud rate it responds using the old baud rate:
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
Subsequently the baud rate is changed. The PT can accept commands in the new baud rate 2s after send-
ing the response. If ZVT over IP is used the PT can ignore the command respond with 80 00.
If the PT cannot change the baud rate it responds using the old baud rate with:
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 7D 00
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 FD 00
2.54.1 Start
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 09 xx <prepaid-card-ID> <payment-mode> 04<amount> [49<CC>]
[19<payment-type>] [3D<password>][2D<track 1 data>]
[23<track 2 data>] [24<track 3 data>][8A<card type>][06<TLV-
container>]
Data block:
<prepaid-card-ID>: 2 byte, BCD with leading zeros. Specifies the card type identifier of the network op-
erators for the prepaid-card to be charged.
<payment-mode>: 1 byte. See Table 12: Definition of <payment-mode>.
3D<password>: Mandatory for cash-payment, optional for card-payment.
06<TLV-container>: Possible tags are 41, 1F15.
For cards which cannot identified by the BIN, like CUP, the card type has to be sent with the command.
Therefor the BMP 8Aor TLV tag 41 is used.
Payment- Definition
mode
01 Top-up via card-payment
02 Top-up via cash-payment
03 Top-up via card-payment, card-payment was completed
Table 12: Definition of <payment-mode>
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CCRC APRC
06 1E xx 6F [49<CC>] <top-up amounts>
Data block:
6F: Error number for invalid top-up amount.
<top-up amounts>: Consists of one or several permissible top-up amount, each specified as
04<amount>.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
2.54.4 Transaction
Subsequently the PT begins with the transaction (top-up or cash-payment) or the transactions (card-payment
and top-up).
For this purpose the PT makes an online-connection to the host. This takes place – depending on configura-
tion of the PT and ECR – either over a communication module in the PT or over a communication module
connected to the ECR (see chapter Transmit Data via Dial-Up (06 D9) and chapter Receive Data via Dial-Up
(06 DA)).
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx 27<result-code> <transaction-data>
Data block:
<transaction-data>: See chapter Status-Information (04 0F).
The ECR response is carried out according to chapter Authorization (06 01).
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx 27<result-code><transaction-data>
Data block:
<transaction-data>: See chapter Status-Information (04 0F).
The ECR response is carried out according to chapter Authorization (06 01).
2.54.9 Receipt-Printout
Subsequenty the Receipt-Printout takes place, also if the authorisation failed. If the PT function ECR-
Receipt is activated (= setting in PT, that the ECR assumes the print-function), then the PT transmits the
receipt line-by-line to the ECR using „Print Line“ Commands (see chapter Print line (06 D1)). Alternatively the
receipt printout is carried out using the „Print Text-Block“ Command (see chapter Print line (06 D3)).
The Receipt-Printout should not be generated from data of the Status-Information by the ECR itself.
2.54.10 Completion
If card-payment and top-up were successful or for cash-payment the top-up was successful the PT termi-
nates the process via Completion whereupon the ECR receives back the “master-rights”:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F 00
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If the card-payment failed or if the top-up process failed for cash-payment the PT sends the command Abort
whereby the ECR receives back the “master-rights”:
PT ECR
APDU
Control field Length Data block
CCRC APRC
06 1E xx <result-code> [<CC>]
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
<CC>: The currency code of the PT is only sent with result-code ‘6F’. The PT only sends a currency
code to the ECR, if the ECR had also sent a currency code in its request.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Theoretically the card-payment can be successful but the top-up unsuccessful, which nevertheless results in
a Completion command and not an Abort. The negative-result of the top-up is then only indicated by the
corresponding contents of the Status-information.
For top-up via card-payment however the command Completion or Abort indicates the result of the top-up.
Recommendation:
Splitting of the two sequences in two separate processes – card-payment (command Authorisation) and top-
up via cash-payment (separate card-payment). This is also meaningful because the customer often not only
the Top-Up but also buys goods at the same time and therefore top-up amount and card-payment amount
are not identical.
If data from the ECR are to be printed on a printer integrated in, or connected to the PT, then the command
“Print Line” (06 D1) may be used in the reverse direction.
This command may only be sent from the ECR if the function is implemented in the PT.
If data from the ECR are to be printed on a printer integrated in, or connected to the PT, then the command
“Print Text-Block” (06 D3) may be used in the reverse direction.
This command may only be sent from the ECR if the function is implemented in the PT.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
08 02 01 <protocol-type>
Data-block:
<protocol-type>: 1 byte. Specifies the protocol to switch to. See Table 13: Definition of <protocol-type>.
Protocol- Definition
type
01 T=1
02 Serial IFSF
Table 13: Definition of <protocol-type>
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
This command can be used to calculate a message access code using DUKPT key stored in pinpad.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 E5 xx D3<key-identifier> 06<TLV-container>
Data-block:
06<TLV-container>: Possible tags are 1F32, 1F33.
If 1F32 is present this field contains the SMID used for PIN check. The PT shall verify if still the same
SMID is active in the pinpad. If 1F32 is not present a new SMID shall be created.
Data-block:
06<TLV-container>: Possible tags are 1F32, 1F34.
This command provides to the ECR a transparent channel to the card reader. It is possible to combine mulit-
ple APDUs in one command.
The request APDUs are processed as long the card reader returns response APDUs. In case of an excep-
tional situation (i.e. it does not make sense to continue te APDU processing) the ECR should stop the APDU
processing and return the response APDUs retrieved till now along with an error code.
To prevent communication timeout violations the ECR should distribute long running APDUs over several
“Send APDUs” commands or appropriately increase the timeout T3.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 C6 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 1F46.
Required tags are one or more 1F46 (request APDU).
PT-Response
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 1F16, 1F17, multiple 1F46 (response APDU corresponding to the
request APDU, same order as in the request), 1F47.
Note:
Since this command provides a transparent channel to the card the PT neither checks the responses
from the card nor stops the APDU processing even when a card command failed (in fact the PT does
make any assumptions about positive or negative responses from the card). Thus the ECR is responsi-
ble for bundling the request APDUs into reasonable portions that allow a sound failure processing with-
out messing up the card.
Note also the the PT may reject a command for PCI compliance reasons, e.g. a SELECT command for
an application identifier that is not contained on a whitelist.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 C5 00
Positive PT-Response
PT ECR
APDU
Control field Length Data block
CCRC APRC
80 00 00
Negative PT-Response
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 1E 00
This command is used for starting an authorization and additionally poll for functions cards (e.g. MIFARE). If
a functional card is presented at the reader, the return value of this command is giving information about it.
This command is using the same data blocks as the command Authorization (06 01). This command only
differs in command name and the PT response.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
06 E6 xx [04<amount>] [49<CC>] [19<payment-type>] [2D<track 1 data>]
[0E<expiry-date>] [22<card-number>] [23<track 2 data>]
[24<track 3 data>] [01<timeout>] [02<max. status infos>]
[05<pump no.>] [3A<CVV/CVC>] [3C<additional-data>]
[8A<card type>] [06<TLV-container>]
Data block:
The Data block elements that can be used are the same as described at the authorization command (06 01).
Please consult this chapter for further information.
06<TLV-container>: Possible tags are the same as in command Authorization (06 01) and additionally
1F5B.
If a non-payment card has been detected the PT responds with a specific Abort:
PT ECR
APDU
Control field Length Data block
CCRC APRC
06 1E xx <result-code> [06<TLV-container>]
Data block:
The possible result-codes are described in chapter Error-Messages.
If the return code is FF, specific information about the error could be found in the TLV tags 1F16 and
1F17.
If a non-payment card (e.g. a MIFARE card) has been detected, the result-code 7A is sent. Further in-
formation about the detected card is provided in the TLV container.
06<TLV-container>: Possible tags are 4C, 1F16, 1F17, 1F45, E6 (containing possible tags 1F12, 1F4C,
1F4D, 1F4F, 1F50).
In response to other commands not described in this specification, or not supported by the PT, the PT al-
ways reacts with an error-message. That means the PT must not support all the commands specified in this
document; the PT must however respond correctly to commands that are unknown to it.
ECR PT
APDU
Control field Length Data block
CLASS INSTR
xx xx xx xx
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 83 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [27<result-code>] [<transaction-data>] [06<TLV-container>]
Data block:
<transaction-data>: Consists of several fields, whereby each field is pre-fixed with a bitmap (e.g.
04<amount> 0B<trace-number> 49<CC>...). The individual data-fields have the following format. The bit-
maps are each optional depending on the payment-type. The order of the fields is arbitrary.
06<TLV-container>: Possible tags are 01, 0B, 0C, 13, 14, 15, 20, 21 (Pre-Authorisation), 22 (Authorisa-
tion), 2F, 41, 45, 46, 47, 4C, 4D, 60, 63 (Prepaid Top-Up), E1, 1F08, 1F09, 1F0A, 1F0B, 1F13, 1F14,
1F16, 1F17 (DCC) E2, 1F30 (EPurse).
Note:
The PT only sends a currency code to the ECR, if the ECR had also sent a currency code in its request.
For some transaction types e.g. GeldKarte or GiroGo the Status-Information can be repeated after the
delivery of goods has been confirmed containing more details on the transaction
Definition of transaction-data:
contents:
1) Maestro-cards (BMP8A = 46):
used-data max. 6 byte ASCII. The bitmap is filled with trailing zeros.
3) other cards:
used-data max. 8 byte ASCII. The bitmap is filled, where possible, with
trailing zeros.
49 <CC> 2 byte BCD packed. Value: 09 78 = EUR
Note: There may still exist old ECR implementations which rely on the order of BMPs given in
the table above.
Length Sub-field
3 LLLVAR, always: F1 F0 F0
100 payment-record according to specification Geldkarte
3.0
Length Sub-field
2 LLVAR
3 product-code according to goods-groups-table in PT,
BCD encoded with leading zeros
... ...
3 product-code according to goods-groups-table in PT,
BCD encoded with leading zeros
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 00 00
alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 9C 00
alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 yy xx xx
(any
value,
except-
ing 00
and 9C)
Note:
The responses 80-00-00 and 84-00-00 are positive acknowledgements of the ECR.
For vending-machines 80-00-00 and 84-00-00 mean that the issue of goods has succeeded.
The response 84-9C-00 implies that the PT the should repeat Status-Information after 2s.
A response 84-yy-xx-xx with ‚yy‘ not equal to ‚00‘ and not equal to ‚9C‘ implies that the issue of
goods has not succeeded. If issue of goods did not succeed the PT reverses the payment.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [27<result-code>] [<cardsdata>] [06<TLV-container>]
Data block:
The <result-code> is sent in error-case. Definition of <result-code> in chapter Error-Messages, length
1 byte.
The individual data-fields within <cardsdata> are marked via the ISO-bitmap position and have the
following formats. Each bitmap is optional and the order is arbitrary.
The field „06<TLV-container>“ is optional, the length is variable (see chapter TLV-container).
Possible tags in TLV-container: 21, 4C, 4D, 61, 62 (and subtags), E6, 1F0B, 1F14, 1F16, 1F17, 1F3F
Note:
- If the tracks have an even-length, no padding (e.g. „1F“ or „F0“) is allowed.
- Start- and End-sentinels are not sent.
- If masking of track data is enabled, the character "E" is used.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0F xx [27<result-code>] [<transaction-data>]
Data block:
The <result-code> is defined in chapter Error-Messages, length 1 byte.
<transaction-data> consists of several fields, whereby each field is prefixed with a bitmap (e.g.
04<amount>0B<trace-number>49<CC>...). The individual data-fields have the following formats.
Each bitmap is optional. The order of the fields is arbitrary.
Note:
The PT only sends a currency code (data-field 49) to the ECR, if the ECR had also sent a currency code
in its request.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 0F xx [27<result-code>] [0C<time>] [AA<date>] [19<status-byte>] [29<TID>]
[49<CC>] [06<TLV-container>]
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Commands which require Completion are explicitly noted within the command description.
If a command was not successfully terminated the PT sends this command to the ECR.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 1E xx <result-code> [06<TLV-container>]
Data block:
<result-code>: 1 byte. See chapter Error-Messages.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If the PT sends this command to the ECR, the ECR sets its system-time to the value sent in Data block.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 01 08 AA<date> 0C<time>
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
With this command a printer integrated in or attached to the ECR can be used to print a line from the trans-
ferred data. The text contains no CR LF. Empty lines are transferred as print-commands with an empty text-
field. The command is only sent from the PT if function ECR-receipt is active on the PT (see command Reg-
istration).
If implemented in the PT, this command can be used in the reverse direction to allow data from the ECR to
be printed by the PT’s printer.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 D1 xx <attribute> <text>
Data block:
<attribute>: Bit-field, 1 byte. With this field the PT can control text-formatting. See Table 14: Definition of
<attribute>.
<text> is the text to be printed.
If ‘FF’ is sent as attribute, <text> contains 1 byte with the number of the linefeeds.
If <text> is missing one linefeed is executed.
Attribute Definition
1000 0000 RFU
1xxx xxxx (not equal to 80h) this is the last line
1111 1111 Linefeed, count of feeds follows
01xx nnnn centred
0x1x nnnn double width
0xx1 nnnn double height
0000 nnnn normal text
Table 14: Definition of <attribute>
Notes:
nnnn = number of characters to indent from left (0-15).
Attribute „1xxx xxxx“ (not equal to 80) indicates also that a switch between customer-receipt and mer-
chant-receipt takes place, or vice-versa. It is required for ECRs
that first collect all print-lines in a buffer and then print them together on a page-printer
which use a printer with a cutter.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If no printer is connected to the ECR, or the printer is not ready, or the ECR cannot print for any other reason
it responds with:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 CC 00
With this command a printer integrated in or attached to the ECR can be made to print data from the PT.
In comparison to the command "Print Lines" the command "Print Text-Block" can send several lines simulta-
neously. Thereby the throughput is increased. The texts and attributes are transferred as a TLV-container.
The text contains no CR LF. Empty lines are created via the tag "text-lines" without further contents.
The command is only used by PT if the ECR requests this command via the list of permitted ZVT-commands
or if the PT is configured to use it, otherwise the PT uses the command "Print Lines".
If implemented in the PT, this command can be used in the reverse direction to allow data from the ECR to
be printed by the PT’s printer.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 D3 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 14, 25, 1F07, 1F37.
The last line of a receipt has to be followed by tag 09with contents 1xxx xxxx (not equal to 80), to al-
low the ECR to concatenate several blocks to a single receipt and separate receipts from each other.
The further sequence is comparable to that of command Print Line (06 D1).
With this command the ECR can display status-information about the state of the PT. The command is only
sent by the PT if the function for registration of the ECR was requested in the config-byte.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 FF xx <intermediate-status> [<timeout>] [06<TLV-container>]
Data block:
<intermediate-status>: 1 byte. See Table 15: Definition of <intermediate-status>.
<timeout>: 1 byte BCD, minutes. Sets the timeout T4. Altering timeout T4 is especially important for
lengthy actions on the PT (e.g. software-update).
06<TLV-container>: Possible tags are 24. If the <TLV-container> is sent, then the PT must also send
<timeout>.
value value 1)
hex. dec. Definition Bedeutung
00 0 PT is waiting for amount-confirmation BZT wartet auf Betragbestätigung
01 1 x Please watch PIN-Pad Bitte Anzeigen auf dem PIN-Pad beachten
02 2 x Please watch PIN-Pad Bitte Anzeigen auf dem PIN-Pad beachten
03 3 x Not accepted Vorgang nicht möglich
04 4 PT is waiting for response from FEP BZT wartet auf Antwort vom FEP
05 5 PT is sending auto-reversal BZT sendet Autostorno
06 6 PT is sending post-bookings BZT sendet Nachbuchungen
07 7 x Card not admitted Karte nicht zugelassen
08 8 x Card unknown / undefined Karte unbekannt / undefiniert
09 9 x Expired card Karte verfallen
0A 10 x Insert card Karte einstecken
0B 11 Please remove card! Bitte Karte entnehmen!
0C 12 x Card not readable Karte nicht lesbar
0D 13 x Processing error Vorgang abgebrochen
0E 14 x Please wait... Vorgang wird bearbeitet bitte warten...
value value 1)
hex. dec. Definition Bedeutung
0F 15 PT is commencing an automatic end-of- BZT leitet einen automatischen Kassen-
day batch abschluss ein
10 16 x Invalid card Karte ungültig
11 17 Balance display Guthabenanzeige
12 18 x System malfunction Systemfehler
13 19 x Payment not possible Zahlung nicht möglich
14 20 x Credit not sufficient Guthaben nicht ausreichend
15 21 x Incorrect PIN Geheimzahl falsch
16 22 Limit not sufficient Limit nicht ausreichend
17 23 x Please wait... Bitte warten...
18 24 x PIN try limit exceeded Geheimzahl zu oft falsch
19 25 x Card-data incorrect Kartendaten falsch
1A 26 Service-mode Servicemodus
1B 27 x Approved. Please fill-up Autorisierung erfolgt. Bitte tanken
1C 28 x Approved. Please take goods Zahlung erfolgt. Bitte Ware entnehmen
1D 29 x Declined Autorisierung nicht möglich
26 38 PT is waiting for input of the mobile- BZT wartet auf Eingabe der Mobilfunk-
number nummer
27 39 PT is waiting for repeat of mobile number BZT wartet auf Wiederholung der Mobil-
funknummer
28 40 Currency selection, please wait... Währungsauswahl, bitte warten...
29 41 Language selection, please wait... Sprachauswahl, bitte warten...
2A 42 For loading please insert card Zum Laden Karte einstecken
2B 43 Emergency transaction, please wait Offline-Notbetrieb, bitte warten
2C 44 Application selection, please wait Auswahl Debit/Kredit, bitte warten
41 65 Please watch PIN-Pad Bitte Anzeigen auf dem PIN-Pad beachten
Please remove card! Bitte Karte entnehmen!
42 66 Please watch PIN-Pad Bitte Anzeigen auf dem PIN-Pad beachten
Please remove card! Bitte Karte entnehmen!
43 67 x Not accepted Vorgang nicht möglich
Please remove card! Bitte Karte entnehmen!
44 68 PT is waiting for response from FEP BZT wartet auf Antwort vom FEP
Please remove card! Bitte Karte entnehmen!
45 69 PT is sending auto-reversal BZT sendet Autostorno
Please remove card! Bitte Karte entnehmen!
46 70 PT is sending post-booking BZT sendet Nachbuchungen
Please remove card! Bitte Karte entnehmen!
47 71 x Card not admitted Karte nicht zugelassen
Please remove card! Bitte Karte entnehmen!
48 72 x Card unknown / undefined Karte unbekannt / undefiniert
Please remove card! Bitte Karte entnehmen!
49 73 x Expired card Karte verfallen
Please remove card! Bitte Karte entnehmen!
4A 74
4B 75 Please remove card! Bitte Karte entnehmen!
4C 76 x Card not readable Karte nicht lesbar
Please remove card! Bitte Karte entnehmen!
value value 1)
hex. dec. Definition Bedeutung
4D 77 x Processing error Vorgang abgebrochen
Please remove card! Bitte Karte entnehmen!
4E 78 x Please wait Vorgang wird bearbeitet bitte warten...
Please remove card! Bitte Karte entnehmen!
4F 79 PT is commencing an automatic end-of- BZT leitet einen automatischen Kassen-
day batch abschluss ein
Please remove card! Bitte Karte entnehmen!
50 80 x Invalid card Karte ungültig
Please remove card! Bitte Karte entnehmen!
51 81 Balance display Guthabenanzeige
Please remove card! Bitte Karte entnehmen!
52 82 x System malfunction Systemfehler
Please remove card! Bitte Karte entnehmen!
53 83 x Payment not possible Zahlung nicht möglich
Please remove card! Bitte Karte entnehmen!
54 84 Credit not sufficient Guthaben nicht ausreichend
Please remove card! Bitte Karte entnehmen!
55 85 x Incorrect PIN Geheimzahl falsch
Please remove card! Bitte Karte entnehmen!
56 86 Limit not sufficient Limit nicht ausreichend
Please remove card! Bitte Karte entnehmen!
57 87 x Please wait... Bitte warten...
Please remove card! Bitte Karte entnehmen!
58 88 x PIN try limit exceeded Geheimzahl zu oft falsch
Please remove card! Bitte Karte entnehmen!
59 89 x Card-data incorrect Kartendaten falsch
Please remove card! Bitte Karte entnehmen!
5A 90 Service-mode Servicemodus
Please remove card! Bitte Karte entnehmen!
5B 91 x Approved. Please fill-up Autorisierung erfolgt. Bitte tanken
Please remove card! Bitte Karte entnehmen!
5C 92 x Approved. Please take goods Zahlung erfolgt. Bitte Ware entnehmen
Please remove card! Bitte Karte entnehmen!
5D 93 x Declined Autorisierung nicht möglich
Please remove card! Bitte Karte entnehmen!
66 102 PT is waiting for input of the mobil-number
BZT wartet auf Eingabe der Mobilfunk-
Please remove card! nummer
Bitte Karte entnehmen!
67 103 PT is waiting for repeat of the mobil- BZT wartet auf Wiederholung der Mobil-
number funknummer
Please remove card! Bitte Karte entnehmen!
68 104 PT has detected customer card insertion BZT hat Einstecken der Kundenkarte er-
kannt
69 105 Please select DCC Bitte DCC auswählen
C7 199 PT is waiting for input of the mileage BZT wartet auf Eingabe des Kilometer-
stands
C8 200 PT is waiting for cashier BZT wartet auf Kassierer
C9 201 PT is commencing an automatic diagnosis BZT leitet eine automatische Diagnose ein
value value 1)
hex. dec. Definition Bedeutung
CA 202 PT is commencing an automatic initialisa- BZT leitet eine automatische Initialisierung
tion ein
CB 203 Merchant-journal full Händlerjournal voll
CC 204 Debit advice not possible, PIN required Lastschrift nicht möglich, PIN notwendig
D2 210 Connecting dial-up DFÜ-Verbindung wird hergestellt
D3 211 Dial-up connection made DFÜ-Verbindung besteht
E0 224 PT is waiting for application-selection BZT wartet auf Anwendungsauswahl
E1 225 PT is waiting for language-selection BZT wartet auf Sprachauswahl
E2 226 PT requests to use the cleaning card BZT fordert auf, die Reinungskarte zu
benutzen
F1 241 Offline Offline
F2 242 Online Online
F3 243 Offline transaction Offline-Transaktion
1) the texts marked with x are of particular relevance for certification of unattended basis-terminals and
must displayed word-for-word on the customer-display.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
If the PT has received the master-rights from the ECR it can request with this command that the ECR makes
a dial-up connection, e.g to host or maintenence-system, for the PT. To be able to utilise this function the
ECR must be configured accordingly, since most ECRs do not provide dial-up support.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 D8 xx <dialing-data>
Data block:
<dialing-data>: Specifies the dialing parameters to be used, 7-bit ASCII encoded.
Structure of <dialing-data>:
Connection-type Parameter
modem and ISDN F <baud> : <target call number>
without user-data
<baud>: Desired baudrate between dial-up module and remote station (e.g. host, TCS); standard-values
= 9600 or 2400 Baud
<target call number>: Call number of the remote station
<user-data>: Routing information. Separated from the call number via “,”. The ECR has to decide wheth-
er the user-data are sent in the dialing-string or after the connect.
The data described above must be agreed from case-to-case with the network operator.
The ECR forwards the received data to the dial-up module and responds after the connect with:
ECR response:
ECR PT
APDU
Control field Length Data block
CLASS INSTR
80 00 00
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 DB 00
ECR response:
ECR PT
APDU
Control field Length Data block
CLASS INSTR
80 00 00
If the PT has received the master-rights from the ECR it can request with this command that the ECR trans-
mits data via a dial-up module on the ECR:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 D9 xx <dial-up data>
Data block:
<dial-up data> is the data to be transmitted.
The ECR forwards the received data to the dial-up module and responds after the connect with:
ECR response:
ECR PT
APDU
Control field Length Data block
CLASS INSTR
80 00 00
With this command the PT receives data via a dial-up module connected to the ECR:
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 DA 00
The ECR receives the data from the dial-up module and responds with:
ECR response:
ECR PT
APDU
Control field Length Data block
CLASS INSTR
80 00 xx <dial-up data>
Data block:
<dial-up data>: The data received from the dial-up module. Order FIFO – the first received byte is re-
layed first to the PT.
The ECR waits for approximately 0.5s for the reception of data. If no data is received after this timeout it
responds with 80-00-00.
This command serves to make transparent connection between PT and a third-party (e.g. Terminal-
Configuration-Server TCS) after the dial-up connection has been made.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 DD 00
ECR response:
ECR PT
APDU
Control field Length Data block
CLASS INSTR
80 00 00
All messages between the third-party and the PT are transmitted transparently further by the ECR. There-
fore no checking of the data takes place by the ECR (e.g. no ACK/NAK or 80-00-00).
The ECR ends the Transparent-Mode automatically if the connection between the dial-up module and the
third-party is terminated. There is no Completion command for the command Transparent-Mode.
Sequence – Remote-Maintenance:
1. Terminal-Supervisor calls the ECR.
2. The ECR relays data between Terminal-Supervisor and PT transparently.
3. The Terminal-Supervisor terminates the connection. The ECR must monitor the status the of the dial-up
module to recognize the hang-up. Then the ECR terminates the Transparent-Mode. Timeout T4 also
terminates the Transparent-Mode if no communication takes place between PT and TKS within the
timeout period.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0E xx [06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 2B.
Note:
This command may only be used if the ECR has noted during Registration (06 00) that it supports this com-
mand.
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 19.
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 00 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 19.
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 yy xx xx
(any
value,
except-
ing 00)
Note:
The responses 80-00 and 84-00 are positive acknowledgements from the ECR.
A response 84-yy with ‘yy’ not equal to ‘00’ implies that the Menu-Request was aborted with an error
(See chapter Error-Messages).
With this command the PT can send a blocked-list query to the ECR after reading the card. The ECR checks
the BLZ / account number / PAN or other relevant card parameter and returns the result to the terminal. De-
pending on the outcome the terminal either proceeds with the transaction or aborts. In any event there fol-
lows a Completion (06 0F) or an Abort (06 1E) from the PT to the ECR.
This command may only be sent by the PT to the ECR if the ECR listed it as a supported command in the
TLV container during registration.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
06 E4 xx <card data>
Data block:
<card data> contains numerous fields, whereby each field is prefixed by a bitmap (i.e 22<PAN /
EF_ID>0E<exp-date>…). The individual bitmaps are defined as follows, and are optional depending on
the payment-type. The order of fields is arbitrary.
Card-data definition:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 00
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 00 00
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 9C 00
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 yy xx xx
(any
value,
except-
ing 00
and 9C)
Note:
The responses 80-00-00 and 84-00-00 are positive acknowledgements from the ECR (card is not in the
blocked-list).
Response 84-9C-00 states that the PT should resend the blocked-list request after 2s.
Response 84-yy-xx-xx with ‘yy’ not equal to ‘00’ or ‘9C’ or ‘6E’ implies that an error occurred whilst
checking the blocked-list.
Response 84-6E-00 states that blocked-list request was completed successfully and the card is con-
tained in the blocked-list.
The PT sends an Input-Request to prompt for a string, a number or an amount at the ECR.
PT ECR
APDU
Control field Length Data block
CLASS INSTR
04 0D xx [06<TLV-container>]
Data block:
06<TLV-container>: Possible tags are 32.
Note:
Input-Requests are only sent by the PT, if the ECR has added this command to the list of permitted ZVT-
commands (tag 26) in Registration (06 00).
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
80 00 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 32 (containing 1F3A).
The ECR returns the result of input in tag 1F3A in the response. If the timeout for the input has ex-
pired without any input, tag 1F3A or the TLV container is not added to response.
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 00 xx 06<TLV-container>
Data block:
06<TLV-container>: Possible tags are 32 (containing 1F3A).
The ECR returns the result of input in tag 1F3A in the response. If the timeout for the input has ex-
pired without any input, tag 1F3A or the TLV container is not added to response.
Alternative:
ECR response:
ECR PT
APDU
Control field Length Data block
CCRC APRC
84 yy xx xx
(any
value,
except-
ing 00)
Note:
The responses 80-00 and 84-00 are positive acknowledgements from the ECR.
A response 84-yy with ‘yy’ not equal to ‘00’ implies that the Input-Request was aborted or an error
occurred (See chapter Error-Messages).
If the ECR assumes printing of payment-data it can receive the important information for receipt-printout in
two different ways:
1. Aquisition of the texts from the commands Print Line (06 D1) / Print Text-Block (06 D3) and their printing
details without re-formatting.
2. Aquisition of the texts from the command Status-Information (04 0F) and their printing details with the
preceding sorting and formatting.
The first method has the advantage that the programmer of the ECR does not need be concerned with the
contents of the receipt; the important details are always present and the formatting is correctly set. Thus it is
assured that the requirements of the ZKA or credit-card organisations or other partners are met. Additionally
the ECR is not liable to the ZKA.
The following table gives an overview of the most important data which must be included on a receipt.
payment-type print-texts
ELV (Track 3) name of the means-of-payment: ec direct-debit
signature line for customer
permitted advice-text from operator for direct-debit entry
card-sequence number from BMP ‚17‘
account-number and bank-code from the PAN from BMP ‚22‘
PoZ (obsolete) name of the means-of-payment: PoZ
signature line for customer
reference-number BMP ‚3B‘ (not available for reversal)
reference-parameter from BMP ‚BA‘ (not available for reversal)
There are locked-conditions during which the PT is temporarily out-of-order. These conditions are reflected
by the terminal-status. In this condition the PT is basically able to receive and respond to all PT commands.
However, all PT commands are responded to with the Abort command, with these exceptions:
Status-Request
Display Text
Display Text (old Version)
Display Text with Function-Key Input
Display Text with Function-Key input (old Version)
Display Text with numerical Input
Display Text with numerical input (old Version)
Activate Service-Mode
Software-Update
Registration
Log-Off
Read Card
Abort
Additionally commands which can deactivate the locked condition, (state can be read via the PT-command
„Status-Request“) are also processed.
The PT hat the possibility to execute time-controlled events independently. During this time the PT is tempo-
rarily out-of-order. In this case commands sent to the PT will not be responded to. After completion of the
event, cammonads are processed normally by the PT again. It is left up to the vending-machines or ECR to
decide how it reacts in this case. It is possible to discern when the PT is operational again by polling with the
command Status-Request. It must be noted that time-controlled events may last a considerable time period
(e.g. for software-update).
6 Additional Data
Depending on the software the ECR can send additional data commands Authorisation, Reversal etc.
6.1.1 Structure
Length Field
[byte]
3 Length of flowing data within BMP 3C, LLLVAR encoded
2 Driver-code, BCD packed, if the field driver-code is not used, default ‚00 00‘
3 Mileage, BCD packed, if the field mileage is not used, default ‚00 00 00‘
2 Error- and status-code, binary
8 Goods-data information #1
...
8 Goods-data information #n
RFU
6.3.1 Structure
Length Field
[byte]
3 Length of following data within BMP 3C, LLLVAR encoded
3 Mileage, BCD packed, if the field mileage is not used, default ‚00 00 00‘
2 Vehicle-number, BCD packed, if the field vehicle-number is not used, default ‚00 00‘
2 Driver-code, BCD packed, if the field driver-code is not used, default ‚00 00‘
3 Capture-type, binary encoded
20 Info, ASCII encoded
2 Filler, ASCII encoded
1 Number of the goods-data information, BCD packed, range 0 bis 15
12 Goods-data information #1
...
12 Goods-data information #n
6.3.2 Capture-Type
The contents are dependent on the network operator.
7 TLV-Container
Using the TLV-container variable data-elements can be transferred between ECR and PT. In contrast to
bitmaps the data-elements are transferred in a consistant format. Each element is pre-fixed with a tag (ID of
the data-element) and a length. The concatenation of tag + length + data-element is known a a data-object.
1. The ECR-interface is increasingly extended through new functions. The number of the possible bitmaps
is however limited to at most 256. Thus there is a resource-conflict. The flexible structure of the data-
objects allows (theoretically) any desired number of different data-objects to be defined.
2. For bitmaps there are different formats: bitmaps with fixed length, LL-Var and LLL-Var encoded. There-
fore the receiver must be able to identify each single bitmap to process it and to know where the next
bitmap in the data-flow begins. Through their uniform structure data-objects may be skipped or igored if
unknown to the receiver. This allows a certain downwards-compatibility for differing performance levels
bewteen transmitter and receiver is possible.
3. The uniform structure and the flexibility facilitate the development of new functions and allow further de-
velopment without creating unnecessarily long data-objects.
bitmap 06 (= pseudo-tag) + length-field (structure of the length-field according to chapter Length-Field, and
NOT LLL-Var!) + data-element (= list of data-objects).
Example:
06 + length + data-object
06 + length + data-object 1 + data-object 2 + ... + data-object n
7.3 Structure
tag + length
7.3.1 Tag-field
The tag-field is the identification of the following data-element. With it the receiver can associate the con-
tents.
In the tag is a class (bit 7 and 8), a type (bit 6) and a number (bit 1 bis 5) encode.
byte 1:
b8 b7 b6 b5 b4 b3 b2 b1 Definition
0 0 universal-class
0 1 application-class
1 0 context-specific class
1 1 private class
0 primitive data-object
1 constructed data-object
0 0 0 0 0 bis 1 1 1 1 0 tag-number
1 1 1 1 1 tag-number in next byte
Constructed Data-Object:
7.3.2 Length
byte 1:
b8 b7 b6 b5 b4 b3 b2 b1 Definition
0 value decimal 0 to 127 length (in bytes) of the following data-element
1 0 0 0 0 0 0 0 invalid value
1 0 0 0 0 0 0 1 one length-byte follows
1 0 0 0 0 0 1 0 two length-bytes follow:
nd
2 byte: high byte
rd
3 byte: low byte
1 value 3 to 127 RFU
If the length has value 0, the data-element is omitted. This is referred to as an empty data-object.
7.3.3 Data-Element
Format and contents of the data-elements are dependent on the particular tag.
Note:
The given lengths are the typical values for each field. However, the length of each data-object must always
be interpreted from the data-object since only this value is definitive.
7.4.1.1 Primitive
Tag Name see
01 reversal-ID section „Miscellaneous“
02 driver-number section „Fleet-card“
03 auto-number section „Fleet-card“
04 mileage section „Fleet-card“
05 goods-group section „Fleet-card“
06 restriction-code 1 section „Fleet-card“
07 text-lines section „Miscellaneous“
0808080 receipt-number section „Miscellaneous“
8
7.4.1.2 Constructed
Tag Name see
20 fleet-card container section „Fleet-card“
21 list of permitted goods-groups section „Fleet-card“
22 list of prohibited goods-groups section „Fleet-card“
23 list of open pre-authorisations section „Miscellaneous“
24 display-texts section „Miscellaneous“
25 print-texts section „Miscellaneous“
26 list of permitted ZVT-Commands section „Miscellaneous“
27 list of supported character-sets section „Miscellaneous“
28 list of supported languages section „Miscellaneous“
29 list of menus section „Menu“
2A list of menus section „Menu“
2B menu section „Menu“
2C menu-point section „Menu“
2D file section „Miscellaneous“
2E time-stamp section „Miscellaneous“
2F payment-type section „Miscellaneous“
30 card acceptance matching, container section „Miscellaneous“
31 amount information section „Miscellaneous“
32 input container section „Input“
7.4.2 Miscellaneous
Tag Data-element
The error-codes are application-specific. The definition must be taken from the relevant specifica-
tion.
The PT sends the extra result-code in the Status-Information to the ECR. The PT should however
still send the BMP27.
14 ISO-character-set; length variable
The PT sends this tag within the tags 27 2B, 32 and in the status-information and within tag 27 in
completion command for registration.
15 language-code; length 2 bytes; ASCII encoded (not null-terminated)
language-code according to ISO 639-1; e.g. DE = German; FR = French; EN = English; IT = Italian;
There is no difference between capital and small letters.
The PT sends this tag within the Tags 28 and 2B, in authorisation commands as optional language
preselection and in the status-information.
1A max. length the APDU; length variable; binary encoded (hi-byte sent before lo-byte)
During the Registration the ECR defines in tag 1A the maximum size of the APDU that the ECR
can process. The PT can send it owns max. size of APDU to be received in tag 1A in the Comple-
tion of the Registration.
Note:
During the implementation it must be observed that the data of the transport-protocols can be nota-
bly longer than the APDU (overhead of the transport-protocol: DLE, STX, DLE, ETX, CRC, CRC
and duplication of the ‘0x10’; see also PA00P016).
Each transmitter must observe that the APDU does not exceed the receive-buffer capacity of the
receiver.
1B diagnosis-type; length variable, binary encoded
0x01 merchant-journal
0x02 log-file the application
0x03 log-file of the ECR-protocol
0x04 log-file of the communication-module
0x05 log-file of the PIN-pad
Tag Data-element
0x06 reconciliation data (content is implementation dependent)
1E start-position; length variable; network byte order; this tag has two functions:
1.) for the request from the ECR: offset from which should be read/written
2.) for file-transfer: position within the file.
1F00 total-length of file network byte order. Should the file be so large that it cannot be transmitted in a
single tag, then this tag serves to inform the receiver, that further status-information may follow.
From the start-position (tag ‚1E‘) the receiver knows in which order the status-information belong
1F01 receipt-ID; length variable; binary encoded; this tag is used together with command „Repeat Re-
ceipt“:
If from_TA-Number is given in command Repeat Receipt the terminal prints all receipts stored in
the terminal starting at TA-number from_TA-number.
from_TA-Number can be linked with to_TA-Number.
If from_TA-Number and to_TA-Number are identical only one receipt will be printed for this TA-
number. For from_TA-Number= 0 and missing to_TA-Number all receipts are printed.
1F03 to_TA-number; length variable; binary encoded; used with tag ‚1F01‘ and tag ‚1F02‘.
1F04 receipt-parameter; length variable; bit-field; sent for the Registration or for a transaction:
Byte 0:
1xxx xxxx
positive customer-receipt required (0xxx xxxx = no customer-receipt); only relevant if the PT should
send print-lines or receipt-blocks and the transaction was success fully completed
x1xx xxxx
negative customer-receipt required (x0xx xxxx = kein customer-receipt); only relevant if the PT
should send print-lines or receipt-blocks and the transaction was not successfully completed
xx1x xxxx
positive merchant-receipt required (xx0x xxxx = kein merchant-receipt); only relevant if the PT
should send print-lines or receipt-blocks and the transaction was successfully completed
xxx1 xxxx
negative merchant-receipt required (xxx0 xxxx = kein merchant-receipt); only relevant if the PT
should send print-lines or receipt-blocks and the transaction was not successfully completed
xxxx 1xxx
customer-receipt should be sent before the merchant-receipt (xxxx 0xxx = merchant-receipt should
be sent before the customer-receipt) ; only relevant if the PT should send print-lines or receipt-
blocks
xxxx x1xx
print short receipt (payment-data excluded; no header/footer/advertising-text) (xxxx x0xx = print
Tag Data-element
normal receipt)
xxxx xx1x
do not print product-data (from BMP3C) on the receipt (xxxx xx0x = print normal receipt)
xxxx xxx1
use ECR as printer ( commands 06 D1/ 06 D3) instead of internal printer or if no printer available.
This enables printing of receipts with print commands only for the command the tag is issued with,
despite the print commands being disabled in general in the registration with MSB of the config
byte equal to 0. It does not influence the effect of the bits xxxx x11x in the config byte of the regis-
tration.
Byte 1:
1xxx xxxx enable sending of TLV-Tag E3 in command print text-block (06D3) within TLV-Tag 25
Further functions may be added in future, the bit-field can be extended from the right. The ECR
should set all unused bits to ‚0‘.
These parameters are only valid for optional receipts, i.e. via the payment-type used the PT can
override these guidelines (e.g. customer-receipt for ec-cash or error-receipt for prepaid top-up).
If tag 1F04 is not sent, the order of the receipts is dependent on the implementation in the PT.
1xxx xxxx The PT should send the card-data read during the Authorisation to the ECR
if these cannot be processed by the terminal, i.e card unknown/locked.
(0xxx xxxx = Terminal aborts in this case with an error). See also tag 1F08, 1F09,
1F0A.
x1xx xxxx Activate swipe-reader (x0xx xxxx = deactivate swipe-reader)
Further functions may be added in future, the bit-field can be extended from the right. The ECR
should set all unused bits to ‚0‘.
1F06 reservation-parameter; length variable; sent for pre-authorisation or book total:
0x01 pre-authorisation
0x02 reservation
0x03 extension of reservation
0x04 book total
0x05 booking of reservation
0x06 telephonic reservation
0x07 telephonic extension of reservation
1F07 receipt-type; length variable; sent by receipt-printout:
Tag Data-element
Note: if the track has an even length no padding (e.g. „1F“ or „F0“) may be used.
1F09 magnet-stripe data, track 2 of the magnet-stripe; length variable; optional; BCD packed including
special characters (A-F).
The PT can send the track-data in the Status-Information to the ECR, if the PT cannot process the
card-data itself (e.g. card unknown, card not permitted in PT).
See also tag 1F05.
Note: if the track has an even length no padding (e.g. „1F“ or „F0“) may be used.
1F0A magnet-stripe data, track 3 of the magnet-stripe; length variable; optional; BCD packed including
special characters (A-F).
The PT can send the track-data in the Status-Information to the ECR, if the PT cannot process the
acrd-data itself (e.g. card unknown, card not permitted in PT).
See also tag 1F05.
Note: if the track has an even length no padding (e.g. „1F“ or „F0“) may be used.
1F0D ECR data transported transparently from and to host
1F0E date. 4 byte, BCD-Format: YYYYMMDD
1F0F time. 3 byte, BCD-Format: HHMMSS
1F10 cardholder authentication:
0 offline
1 online
1F12 card-technology:
Tag Data-element
the ECR for reference purpose e.g. receipt printing in gas vending machines.
1F15 card reading control.
Variable length, bitfield, extension.
1xxx xx00 The PT should calculate with default algorithm and send the tag 1F14 in the
status information (04 0F) of the command Read Card and card payment com-
mands.
1xxx xx01 online algorithm
1xxx xx10 offline hash algorithm (SHA-256)
x1xx xxxx Contactless cards: The PT should read the unique ID (UID) from the card, pad it
with leading ‘00’ bytes to a length of 10 bytes, and return it in tag 4C in the sta-
tus information.
xx1x xxxx GeldKarte / girogo: The PT should read the remaining balance and return it in
tag 1F3F.
Further functions may be added in future, the bit-field can be extended to the right. The ECR
should set all unused bits to ‚0‘.
1F16 extended error code.
Variable length, binary. Contains PT manufacturer specific error code. Can be used if no reasona-
ble mapping to ZVT error codes is possible. Can be sent within status information (04 0F) or abort
frames (06 1E). This tag mainly serves logging or debug purposes.
1F17 extended error text.
Variable length, encoded in ZVT 8-bit character set. Contains the PT manufacturer specific plain
text related to the error code specified in tag 1F16. Can be used for the merchant receipt in case no
reasonable mapping to ZVT error codes is possible. In other cases the tag may serve logging or
debug purposes
1F18 card notification control
Controls behaviour of ZVT command Display Text with Function-Key Input 06 E1:
00 or missing: only function keys are recognized
01 card insertion terminates the command too
1F19 card acceptance, binary
0x00 accept
0x01 deny
1F1A PAN for card acceptance matching, BCD-packed, according to BMP 22 encoding
1F1D currency information; binary:
Tag Data-element
The ECR may send this tag in the command to the PT to specify the amount for the customer
cashback.
Please note:
BMP 04 (amount) must contain the sum of both, the payment amount and the cashback
amount.
The support of cashback depends on the card that is used for transaction and the configu-
ration/implementation of the PT. For this reason it is recommended for the ECR to use
command 04 0D (Input-Request) for amount inputs instead of usage of 1F25. If the ECR
sends 1F25 and cashback isn’t supported by PT or card, the PT may reject the ECR
command or ignore the tag. In second case the PT performes normal payment without
cashback, but uses the complete amount!
Tag Data-element
1F31 Encrypted PIN block, BCD-packed encoded
The PT may send this tag within the TLV container that is returned by command PIN-Verification
for Customer-Card (06 E3).
1F32 SMID value, BCD-packed encoded
If sent by the PT it specifies the SMID value used by command PIN-Verification for Customer-Card
(06 E3) or MAC calculation (06 E5). It is an optional parameter of the request of command MAC
calculation (06 E5).
1F33 Message data, binary
Contains a hash value (SHA-256, SHA-1) of the message or the message itself. For this data the
MAC will be calculated using the key specified by SMID (see 1F32.). The data shall be padded ac-
cording to EMV rules.
1F34 MAC value, binary
Specifies the calculated MAC.
1F35 ECR Identification, 4 bytes BCD encoded number to identify the ECR at PT with an 8 digit work-
station ID
1F36 Tip amount, BCD-packed encoded
The tag contains the tip amount for transactions with tip. The tag can be used as follows:
Byte 0:
Value Description
0x01 Positive receipt for an authorised transaction
(0x04 used for negative receipts)
0x02 If a positive receipt is printed (bit combined
with 0x01), this receipt contains a signature
field.
0x04 Negative receipt for an aborted or rejected
transaction
(0x01 used for positive receipts)
Tag Data-element
0x80 Printing of the receipt is mandatory and must
not be aborted by customer/retailer.
Further functions may be added in future, the bit-field can be extended and additional bytes can be
added. The ECR should set all unused bits to ‘0‘.
See also tag 1F07 containing information about the receipt type.
1F3B Transaction information (binary, variable length)
The PT sends this optional tag in command 040F (Status-Information) to the ECR to provide addi-
tional information about the transaction with following bit mask:
Byte 0:
0x01: tippable transaction, the ECR is allowed to send command 060C (Book tip) for this
transaction
Further functions may be added in future, the bit-field can be extended and additional bytes can be
added. The ECR should set all unused bits to ‘0‘.
1F3E Encrypted cardholder information, binary, variable length
General data field comprising encrypted data for transaction journal purposes. Since decryption
information (algorithm, keys) is not available on ECR side the content is fully transparent and can
only be used for post-processing by the host provider or within another secure environment.
1F3F Remaining balance
1F45 ATS, length variable, binary
1F46 Command and response APDU, length variable, binary
1F47 Card read error code, 1 byte
There is one error code for each command APDU.
Value Description
0x01 Contactless level 1 transmission error
0x02 Contactless level 1 protocol error
0x03 Contactless level 1 timeout
0x04 Contactless collision detected
0x05 Command not allowed due to whitelist check
0xFF Unknown card reader error, details are specified as extended errors in tags 1F16 and
1F17
1F4C Card type, 1 byte
Tag Data-element
The plaintext key. This tag and 1F5D are mutually exclusive. The actual format is out of scope of
this document.
1F60 Allowed card technologies, bit field, 1 byte
Specifies the card technologies the PT should accept for this command.
Exceptions:
- The commands "Status-Information", "Completion" and "Abort" may always be sent by the PT -
independent of whether in the list of allowed commands not.
- For ZVT-command "Intermediate-Status", the config-byte of the Registration must be evaluat-
ed. If the Intermediate-Status is allowed by the config-byte the Registration the PT may send
Tag Data-element
Intermediate-Status - independent of whether the command is in the list of allowed commands
or not.
- If via the config-byte of the Registration the receipt-printout over the ECR is demanded, the PT
should either send 06D1 or 06D3 to the ECR ( not valid if the ECR builds the receipt itself from
the status-information!). Which of the two commands (06D1 or 06D3) should be sent from PT
to the ECR is defined by the ECR in this list. Should information from the ECR be missing then
the PT uses 06D1 for downwards-compatibility, i.e. the ECR must explicitly request 06D3.
- All other commands should not be used by the PT if the ECR sends bitmap 06 in the Registra-
tion.
27 List of supported character-sets; length variable
The ECR sends the list of supported character sets in command “Registration” to the PT. The PT
responds in the Completion command of the Registration with the list of commonly (ECR + PT)
supported character sets.
Alternatively the tag can be used to configure a specific character set to the PT. The ECR sends a
single character-set (tag 14) in command “Registration” to the PT. If the PT supports the character
set, it is echoed in tag 27 in the Completion command. If the transmitted character set is not sup-
ported by the PT or more than one tag 14 was sent in the Registration, then no tag 27 is sent in the
Completion and the default character set CP437 is used by the PT.
If a character set is accepted by the PT it is then used for all print (06 D1, 06 D3) and display com-
mands (customer and merchant texts).
The ECR can then use command „Select Language“ to choose a suitable language.
See also tag 15.
2D file; length variable; consists of file -block (tag ‚1C‘), file-ID (tag ‚1D‘), start-position (tag ‚1E‘) and
total length of the file (tag ‚1F00‘)
Tag Data-element
unmasked digits are compared.
7.4.4 Fleet-cards
Byte 1
1xxx xxxx the PT should send „Application Label“ (tag 42) in the Status-Information
(for Read Card and (Pre-)Authorisation)
x1xx xxxx the PT should send „Application Preferred Name“ (tag 44) in the Status-Information
(for Read Card and (Pre-)Authorisation)
xx1x xxxx the PT should send tag 46 in the Status-Information
xxx1 xxxx the PT should send tag 47 in the Status-Information
Tag Data-element
xxxx xxx1 the PT should send tag 67 in the Status-Information
Byte 2
1xxx xxxx the PT should send „DC POS 2.4 product display“ (tag 4A) in the
Status-Information
If tags 66 and 67 are requested by the ECR, the PT may send tags 46 and 47 within tags 66 and
67, even if tags 46 and 47 were not specifically requested. The PT should ignore the configuration
bits for tag 46 and 47 in this case.
Affects tag 60 in the Status-Information for Read Card and (Pre-)Authorisation and not the BMP 8B.
Additionally the ECR can also pre-define the card-type-ID (tag 41) for command „Authorisation“
(e.g. after the application-selection on second customer-display).
If the ZVT card-type-ID is larger than decimal 255 then BMP 8A should be set to ‘FF’ and tag 41
used, providing the ZVT card-type-ID should be sent to the ECR. Alternatively tag 8A can be omit-
ted. The sending of the ZVT card-type-ID to the ECR is optional.
42 name of the application (= Application Label); length variable; ASCII encoded (not null-terminated);
see also tag 60.
43 application-ID (RID+PIX). length variable; binary encoded
See also tag 44.
Additionally the ECR can also pre-define the application -ID (tag 43) for command „Authorisation“
(e.g. after the application-selection on second customer-display).
44 application preferred name; length variable; ASCII encoded (not null-terminated); see also tag 60.
45 receipt-parameter, 4 byte BCD encoded
Tag Data-element
The PT sends the tag 46 in the Status-Information if configured in tag 40. The ECR should print the
receipt-DOL unchanged.
For new implementations only tag 66 should be evaluated.
47 EMV-print-data (merchant-receipt), length variable, ASCII-encoded (not null-terminated) = evaluat-
ed directly printable receipt-DOL for merchant-receipt
The PT sends the tag 47 in the Status-Information if configured in tag 40. The ECR should print the
receipt-DOL unchanged
For new implementations only tag 67 should be evaluated.
48 priority; length variable; hex-encoded. Priority is sen in tag 60 to deliver the priority of the different
applications (chip- and/or magnet-strip applications) for the application-selection.
49 network-provider card-type ID; length variable; binary coding; represents BMP 8C of the status
information. If the network-provider card-type-ID is larger than decimal 255 then BMP 8C should be
set to ‘FF’ and tag 41 used, providing the network-provider card-type-ID should be sent to the ECR.
Alternatively BMP 8C can be omitted. The sending of the network-provider card-type-ID to the ECR
is optional.
4A DC POS 2.4 product display; length variable; ASCII encoded (not null-terminated); contains the
product name to be displayed according to the rules of DC POS 2.4.
4B Issuer country code (EMV Tag ‚5F28’), 2 byte BCD encoded with leading 0
Additionally the ECR can also pre-define card-type-ID (tag 41) for command „Authorisation“ (e.g.
after the application-selection on second customer-display).
62 list of applications on chip. The list consists of one or several tag 60, which the PT sends in the
Status-Information of command „Read Card“ to the ECR.
Additionally the ECR can also pre-define application-ID (tag 43) for command „Authorisation“ (e.g.
after the application-selection on second customer-display).
64 receipt header. container with attributes and text-lines, order arbitrary (tag ‚09' and ‚07').
Note:
- attribute (tag ‚09') is optional
- attribute (tag ‚09') relates to all following text-lines until the next attribute.
- a further attribute replaces the previous one for following text-lines.
- each text-line is represented in its own line, i.e. no carriage return must be sent.
The PT sends tag 64 in the Status Information if configured in tag 40. The ECR should print the
receipt unchanged.
65 receipt advertising text. container with attributes and text-lines, order arbitrary (tag ‚09' and ‚07').
Note:
- attribute (tag ‚09') is optional
- attribute (tag ‚09') relates to all following text-lines until the next attribute.
- a further attribute replaces the previous one for following text-lines.
Tag Data-element
- each text-line is represented in its own line, i.e. no carriage return must be sent.
The PT sends tag 65 in the Status Information if configured in tag 40. The ECR should print the
receipt unchanged.
66 customer receipt data. container with arbitrary order of tags:
- “EMV print data (customer receipt)” (46)
- “print text transaction outcome” (68)
The PT sends tag 66 in the Status Information if configured in tag 40. The ECR should print the
receipt unchanged.
67 merchant receipt data. container with arbitrary order of tags:
- “EMV print data (merchant receipt)” (47)
- “print text transaction outcome” (68)
The PT sends tag 67 in the Status Information if configured in tag 40. The ECR should print the
receipt unchanged.
68 receipt text transaction outcome. container with attributes and text-lines, order arbitrary (tag ‚09'
and ‚07').
Note:
- attribute (tag ‚09') is optional
- attribute (tag ‚09') relates to all following text-lines until the next attribute.
- a further attribute replaces the previous one for following text-lines.
- each text-line is represented in its own line, i.e. no carriage return must be sent.
69 reference transaction container (e.g. timestamp of the orginal transaction for reversal, tag 2E).
6A invalid application
consists of the tags 41 or 43 and additionally (depending on configuration following command
„Registration“ see tag 40) the tags 42 and/or 44 and 48 (priority) and 4A product display
7.4.6 Menus
tag 17 is used to control the appearance of the menus. In connection with tag 18 the target-display
can also be controlled. It must be ensured during the implementation that the ECR always displays
the application-selection on the customer-display.
0x01 merchant-display
0x02 customer-display
further values RFU
The ECR sends this information for the Registration to the PT.
see also tag 16, 17.
2A list of menus which the ECR will not display and therefore must be displayed on the PT.
The ECR sends this information for the Registration to the PT.
see also tag 16, 17.
2B menu; contains the tags 14 (ISO character-set; optional), 15 (language-code; optional), 16 (me-
nutype), 17 (context) and 18 (target) and several tag 2C.
Menus can only be sent if the ECR had signaled in the Registration in tag 26 (= permitted ZVT-Commands)
that the ECR supports menus.
7.4.7 Prepaid
7.4.8 DCC
7.4.10 Input
see tag 32
1F39 Timeout (2 bytes, big endian, binary):
An optional timeout may specify the maximal time for the input in seconds. If the tag is missing, the
time for input is not limited.
see tag 32
1F3A Input result (variable length, ASCII):
The tag contains the result of the input and returned in the response 8000 for the input request.
For amount input (tag 1F38) the amount is returned as a numeric character string in smallest unit of
the used currency (tag 1F21). The ECR also has to consider the number of decimal places (tag
1F1E) for the result. Example: "100" for 1 Euro with 2 decimal places.
If the timeout (tag 1F39) for the input expires, result tag 1F3A (or complete TLV container) is not
sent in the response message.
see tag 32
1F3C Input
1F3D Alphanumeric data
1. Request:
24 (mandatory): Prompt text for user input, arbitrary list of text lines (tag '07')
1F38 (optional): Input mode
1F39 (optional): Timeout
14 (optional): ISO-character-set specifying encoding of prompt text (tag 24) and input result
text to be returned in tag 1F3A. If the tag is missing, the terminal uses encoding that was
configured with tag 27 in command 0600 (Registration).
1F21 (optional): ISO-currency code, for amount input only. If the tag is missing, 0x0978 for
EUR (€) is the default.
1F1E (optional): Number of decimals, for number and amount input only. If the tag is
missing, 2 decimal places for amount input or 0 decimal places for input a number is the
default.
1F3A (optional): initial value for the input dialog. If omitted an empty input dialog is used.
2. Response:
1F3A (optional): Input result. If the tag is missing, the timeout for the input has expired.
Input-Requests are only sent by the PT, if the ECR has added 040D to the list of permitted
ZVT-commands (tag 26) in command 0600 (Registration).
The terminal can send the VAS container in the status and completion message.
FF01 Coupon data. In combination with tag 1F65 the following use cases are possible:
7.4.12 Configuration
State Description
0 Ready
1 Initialization needed
2 No keys loaded
3 Fraud
Bit Description
1. Byte
b7 Lock of reconciliation with closure
b6 Initialization lock
b5 Diagnosis lock
b4 Service lock
b3 Out of order
b2 Printer lock
b1 Terminal start up needed
b0 Secure module changed
2. Byte
b7 Transaction log defective
b6 Card reader not found
b5 Card still inserted
b4 Secure link not ready
b3 Activation needed
b2 Low battery power
b1 Contactless reader not initialized
b0 MDB not ready
8 Error-Messages
Following error messages are possible:
9.1 Recovery-Actions:
The following table describes which actions are necessary to resolve the status from the PT.
1
To meet the PCI-DSS requirements, the bitmap 22 through 24 can be omitted instead of using
masking.
Value Definition
00 card output outwards (direction customer)
01 card output inwards
02 park card (not supported by all motor-readers)
D3 1 byte binary DUKPT key idenfierr
Value Definition
01 Swiss server
02 OASE
03 Oil company
E0 1 byte binary Minimal length of the input
E1 LL-Var Text2 line 1
E2 LL-Var Text2 line 2
E3 LL-Var Text2 line 3
E4 LL-Var Text2 line 4
E5 LL-Var Text2 line 5
E6 LL-Var Text2 line 6
E7 LL-Var Text2 line 7
E8 LL-Var Text2 line 8
E9 1 byte binary Maximal length of the input
EA 1 byte binary Echo the input
EB 8 byte binary MAC over text 1 and text 2
F0 1 byte binary Display-duration in seconds. ‘00’ means infinite. Default-value = ‘00’.
F1 LL-Var Text1 line 1
F2 LL-Var Text1 line 2
F3 LL-Var Text1 line 3
F4 LL-Var Text1 line 4
F5 LL-Var Text1 line 5
F6 LL-Var Text1 line 6
F7 LL-Var Text1 line 7
F8 LL-Var Text1 line 8
F9 1 byte binary Number of beep-tones, default-value = ‘00’
FA 1 byte binary Card reader activation. Defines whether the card-reader should be activated or de-
activated. Only an activated card-reader will draw-in the card or release the shutter.
Value Definition
00 Activate card reader
FF Deactivate card reader
FB 1 byte binary Confirmation the input with <OK> required
FC 1 byte binary Dialog-control
FD 1 byte binary Display device on which text should be shown. The default display-device type is the
terminal display.
The PT needn't support all bitmaps listed above; however the PT must react correctly. The PT should ignore
known, but not supported bitmaps and respond to unknown bitmaps with an error:
PT response:
PT ECR
APDU
Control field Length Data block
CCRC APRC
84 83 00
12 Summary of Commands
0F XX RFU for proprietary applications, the utilisation for particular cases should be clarified between man-
ufacturers
01 01 RFU
05 01 Status-Enquiry
05 FF RFU
06 00 Registration
06 01 Authorisation
06 02 Log-Off
06 03 Account Balance Request
06 04 Activate Card
06 09 Prepaid Top-Up
06 0A Tax Free
06 0B RFU
06 0C TIP
06 0F Completion
06 10 Send Turnover Totals
06 11 RFU
06 12 Print Turnover Receipts
06 18 Reset Terminal
06 1A Print System Configuration
06 1B Set/Reset Terminal-ID
06 1E Abort
06 20 Repeat Receipt
06 21 Telephonic Authorisation
06 22 Pre-Authorisation/Reservation
06 23 Partial-Reversal of a Pre-Authorisation/Booking of a Reservation
06 24 Book Total
06 25 Pre-Authorisation Reversal
06 30 Reversal
06 31 Refund
06 50 End-of-Day
06 51 Send offline Transactions
06 70 Diagnosis
06 79 Selftest
06 82 RFU
06 85 Display Text (only included for downwards-compatibility, for new implementations use 06 E0)
06 86 Display Text with Numerical Input (only included for downwards-compatibility, for new implementations
use 06 E2)
06 87 PIN-Verification for Customer-Card (only included for downwards-compatibility, for new implementa-
tions use 06 E3)
06 88 Display Text with Function-Key Input (only included for downwards-compatibility, for new implementa-
tions use 06 E1)
06 90 RFU
06 91 Set Date and Time in PT
06 93 Initialisation
06 95 Change Password
06 B0 Abort
06 C0 Read Card
06 C1 reserved
06 C2 reserved
06 C3 reserved
06 C4 reserved
06 C5 Close Card Session
06 C6 Send APDUs
06 C7 Open Card Session
06 CE RFU
06 D1 Print Line
06 D3 Print Text-Block
06 D4 RFU
06 D8 Dial-Up
06 D9 Transmit Data via Dial-Up
06 DA Receive Data via Dial-Up
06 DB Hang-Up
06 DD Transparent-Mode
06 E0 Display Text
06 E1 Display Text with Function-Key Input
06 E2 Display Text with Numerical Input
06 E3 PIN-Verification for Customer-Card
06 E4 Blocked-List Query to ECR
06 E5 MAC calculation
06 E6 Card poll with authorization
06 E8 reference number in BMP 60
06 E9 reference number in BMP 58
08 01 Activate Service-Mode
08 02 Switch Protocol
08 10 Software-Update
08 11 Read File
08 12 Delete File
08 13 Write File
08 20 Start OPT Action
08 21 Set OPT Point-in-Time
08 22 OPT-Pre-Initialisation
08 23 Output OPT-Data
08 24 OPT Out-of-Order
08 30 Select Language
08 40 Change Baudrate
08 50 Activate Card-Reader
0F CA ChipActivator
80 00 Positive Acknowledgement
84 00 Positive Acknowledgement
84 xx Negative Acknowledgement
84 9C Repeat Statusinfo
13 ZVT-Charactersets
.0 .1 .2 .3 .4 .5 .6 .7 .8 .9 .A .B .C .D .E .F
0. NUL ☺ ♣ ♠ ♦ ○ ♂ ♀
0 263A 263B 2665 2666 2663 2660 2022 25D8 25CB 25D9 2642 2640 266A 266B 263C
1. ► ◄
25BA 25C4 2195
‼
203C
¶
B6
§
A7
▬
25AC 21A8
↨
2191 2193 2192 2190
∟
221F 2194
▲
25B2
▼
25BC
3. 030 1
31
2
32
3
33
4
34
5
35
6
36
7
37
8
38
9
39
:
3A
;
3B
<
3C
=
3D
>
3E
?
3F
4. @
40
A
41
B
42
C
43
D
44
E
45
F
46
G
47
H
48
I
49
J
4A
K
4B
L
4C
M
4D
N
4E
O
4F
5. P
50
Q
51
R
52
S
53
T
54
U
55
V
56
W
57
X
58
Y
59
Z
5A
[
5B
\
5C
]
5D
^
5E
_
5F
6. `60 a
61
b
62
c
63
d
64
e
65
f
66
g
67
h
68
i
69
j
6A
k
6B
l
6C
m
6D
n
6E
o
6F
7. p q r s t u v w x y z { | } ~ ⌂
70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 2302
8. Ç
C7
ü
FC
é
E9
â
E2
ä
E4
à
E0
å
E5
ç
E7
ê
EA
ë
EB
è
E8
ï
EF
î
EE
ì
EC
Ä
C4
Å
C5
9. É æ Æ ô ö ò û ù ÿ Ö Ü ¢ £ ¥ ₧ ƒ
C9 E6 C6 F4 F6 F2 FB F9 FF D6 DC A2 A3 A5 20A7 192
A. áE1 í ó ú ñ Ñ ª º ¿ ⌐ ¬ ½ ¼ ¡ « »
ED F3 FA F1 D1 AA BA BF 2310 AC BD BC A1 AB BB
B. │ ┤ ┐
2591 2592 2593 2502 2524 2561 2562 2556 2555 2563 2551 2557 255D 255C 255B 2510
C. └
2514
┴
2534
┬
252C
├
251C
─
2500
┼
253C 255E 255F 255A 2554 2569 2566 2560 2550 256C 2567
D. ┘ ┌ █ ▄ ▌ ▀
2568 2564 2565 2559 2558 2552 2553 256B 256A 2518 250C 2588 2584 258C 2590 2580
E. α
3B1
ß
DF
Γ
393
π
3C0
Σ
3A3 3C3
µ
B5 3C4
Φ
3A6
Θ
398
Ω
3A9 3B4
∞
221E
φ
3C6 3B5
∩
2229
F. ≡
2261
±
B1
≥
2265
≤
2264 2320 2321
÷
F7
≈
2248
°
B0
∙
2219
·
B7
√ ⁿ
221A 207F
²
B2
■
25A0 A0
The hexadecimal number below the symbol denotes the unicode number.
This charset is valid for incoming commands with text displays.
14 References
PA00P016 ECR-Interface ZVT-Protocol – Transport-Protocol and Application-Protocol
PA00P017 Implications of TA7.0 / DC POS2.4 on the ECR-Interface Protocol
DCPOS25 Schnittstellenspezifikation für chipbasierte EMV-Debit/Credit-Anwendungen POS-Terminals
Version 2.5 07.04.2011
ISO 4217 http://www.iso.org/iso/home/standards/currency_codes.htm
15 Change-Control
The change-control for this documentation is assigned to CCV Deutschland GmbH. The current versions are
announced on http://www.terminalhersteller.de.