VTAP100-USB INSTALLATION GUIDE
PAGE 4
Example: Changes to
config.txt
to interact with particular NFC mobile passes
!VTAPconfig
VAS1MerchantID
VAS1KeySlot=2
; This entry will trigger full Apple VAS. When a corresponding pass is
; detected on an Apple iPhone, that pass will be read and decrypted using
; key file 2.
VAS1MerchantURL
; A website URL to be visited when a pass of type # is presented.
; Not currently supported by iOS for VAS-only transactions.
T1CollectorID=97598013
ST1KeySlot=4
ST1KeyVersion=10
; This entry will trigger a Smart Tap interaction. When a corresponding
; pass is detected on an Android phone, that pass will be read and
; decrypted using key file 4, at key version 10.
Note:
If a
VAS#KeySlot
or
ST#KeySlot
is omitted, or set to 0, then authentication (on
Google Pay Smart Tap only) and decryption (on Google Pay Smart Tap and Apple VAS) will not be
performed. In this case, Apple VAS data will be received by the VTAP100, the phone will register a
pass read, but that data will not be decrypted or output. However, Google Pay Smart Tap data will
be received and forwarded by the VTAP100, but only if the pass does not require authentication
by the terminal.
2.3 Check status in
BOOT.TXT
If you navigate to the VTAP100 in the computer's file system. It will appear as an attached mass
storage device and list the files contained, including the
BOOT.TXT
file.
Inspecting
BOOT.TXT
will give you essential information about your VTAP100 set up, which might
be helpful when troubleshooting.
Figure 2-1 Example BOOT.TXT file
You are most likely to need:
