![IDTECH Vivopay Neo 2 Скачать руководство пользователя страница 70](http://html.mh-extra.com/html/idtech/vivopay-neo-2/vivopay-neo-2_developers-manual_618786070.webp)
NEO 2 Interface Developer’s Guide
Copyright © 2019, International Technologies & Systems Corporation. All rights reserved.
70
created by individual payment associations and reader manufacturers for specific functions.
Proprietary TLVs must be handled in a manner that isolates them from other proprietary TLVs.
For a complete listing of all ID TECH proprietary tags and their meanings, you should consult
the document P/N 80000503-001,
ID TECH TLV Tag Reference Guide.pdf
ViVOpay proprietary TLVs can be present with standard TLVs without encapsulation when the
command is processed exclusively by ViVOpay firmware or software. If the TLVs will be
processed by other devices, ViVOpay proprietary TLVs must be encapsulated to prevent
conflicts with proprietary TLVs from other organizations.
ViVOPay TLV Group Tag FFEE01 is used to encapsulate ViVOpay proprietary TLVs.
Example
The following example is for an encapsulated "Terminal Capabilities – CVM Required" TLV.
The TLV string “FFEE0106DF29030101” is broken down as follows:
FFEE01
ViVOpay TLV Group Tag
06
Length of all encapsulated TLVs
DF29
Tag Terminal Capabilities – CVM Required – ViVOpay Proprietary
03
Length of Transaction CVM
00 01 00
Value: Actual Transaction CVM
4.2.
Card Application Proprietary Tag List (FF69 or FFEE69)
Some applications may require list of defined proprietary tags that may be returned in Data
Object Lists (DOLs). To accomplish this, the reader allows each user-defined Group (except
Group 0) to define a list of proprietary tags that can be inserted into the tag database. The
maximum size of this list is 32 bytes. The new tag used for encapsulating the proprietary tag
list is FF69 (or FFEE69).
A tag in this list may be configured in one of two ways:
•
Constant Value:
the TLV contains a non-zero length and a value. The reader will not
modify this value, but it can be provided when requested (as in a DOL).
•
Updateable:
the TLV contains a length of zero and no value. The tag is then “defined”
but has no value, so it may be updated during the transaction. At the end of a
transaction, the reader will send any updated proprietary tags back in the activate
response frame.
4.3.
Configuration Tag Tables