Dot Origin VTAP Series Quick setup guide

Integration Guide -
Serial Integration Guide
Firmware from v2.2.2.1
VTAP50 and VTAP100
Revised November 2023 v1.01

If you need help to set up or use your VTAP reader, beyond what is contained in this
Integration Guide, then please contact our support team.
Email: [email protected]
Download the latest documentation and firmware from https://vtapnfc.com
Telephone UK and Europe: [phone]
Telephone North America and Latin America: [phone]
If you have any feedback on setting up or using your VTAP reader or this documentation,
then please contact our support team. The product is constantly being reviewed and
improved and we value feedback about your experience.
Copyright 2023 Dot Origin Ltd. All rights reserved.
No part of this Integration Guide may be published or reproduced without the written
permission of Dot Origin Ltd except for personal use. This Integration Guide relates to correct
use of the VTAP reader only. No liability can be accepted under any circumstances relating to
the operation of the user’s own PC, network or infrastructure.
Dot Origin Ltd
Unit 7, Coopers Place Business Park, Combe Lane, Wormley
Godalming GU8 5SZ United Kingdom
[phone]

Contents
1 Integrating VTAP with other systems 1
1.1 Basic - keyboard emulation and mass storage 1
1.2 Advanced - USB COM, serial RS232 or RS485 communications 2
2 Choice of interface 3
2.1 Interfaces to receive data from the VTAP reader 5
2.2 Interfaces to send commands or transfer files (firmware, config or
keys) to the VTAP reader 5
2.3 Available interfaces on the VTAP models 6
3 Receiving pass payload from a VTAP reader 7
3.1 Send pass payload over a serial RS232 or TTLinterface 8
3.2 Send pass payload over a serial RS485 interface 12
4 Sending commands to a VTAP reader 14
4.1 Data request commands 15
4.2 Dynamic commands 17
4.3 Remote management commands 20
5 Use an interface in passive mode 21
6 Transfer files over a command interface 23
7 About this Integration Guide 25
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE I
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 1
1  Integrating VTAP with other systems
The VTAP reader is designed to be flexible, with many different ways that it can interface to
other systems, to accommodate a wide range of requirements. It is important to choose the
most suitable interface(s) when integrating a VTAP reader with other systems.
Interfaces available on the VTAP reader
lUSB keyboard emulation and mass storage
lUSB COM port
lSerial RS232 interface
(VTAP50-OEM and VTAP100-OEM option)
lSerial RS485 interface (VTAP100-PAC-485-CC only)
lSerial TTL/3.3V logic interface (VTAP50-OEM option)
lWiegand interface (VTAP100-PAC-W only).
Note: The Wiegand interface is specific to Access Control applications and discussed in
other VTAP Application Notes on that topic.
The tables in Section 2  Choice of interface will help you understand the pros and cons of
choosing one or more of these interface options.
The following sections explain the difference between a basic use of the VTAP reader
USB interface, assumed in the VTAP Configuration Guide, and the more advanced use of a
VTAP reader involving one or more serial interfaces.
1.1 Basic - keyboard emulation and mass storage
A simple point-of-sale or kiosk application, with a small number of VTAP readers on one site,
is likely to use USB keyboard emulation and mass storage options. The VTAP Configuration
Guide deals with the essential functions of a VTAP reader for this situation.
lDetecting a reader is present;
lReading data from the VTAP reader;
lChanging configuration file settings for reading passes, cards or tags, and providing the
configured user feedback;
VTAP MOBILE WALLET READERS

lLoading any necessary private ECC or application key files;
lUpgrading VTAP reader firmware.
The standard mass storage drive of the VTAP allows most of these functions to be performed
by third-party software integration or development, using standard file write functions, under
most combinations of programming language and operating system.
1.2 Advanced - USB COM, serial RS232 or RS485
communications
If more advanced functionality is required, the USB keyboard emulation and mass storage
drive are not always suitable, or may not be the best choice. You should consider which of
the VTAP interfaces best suits each function.
It may be that your integration requires more advanced functionality, such as:
l'Background' pass reading - the pass payload is received by an application running on an
operating system in the background, rather than the application in focus on that PC (with
the cursor correctly positioned to receive the keyboard input);
lDynamically changing configuration, either to suit different transaction types or switching
to card emulation mode and back (for detail refer to VTAP Application Notes on
VTAP NFC Tag Emulation).
All of the functions, both basic and advanced, can be reduced to three broad types:
lReceiving data from the VTAP reader - pass payload, card or tag data;
lSending commands to the VTAP reader- for dynamic configuration, to control
LED/buzzer, or request data or current settings;
lTransfer files - either firmware or configuration files.
After considering your choice(s) of interface, this Integration Guide will look at the best
approach for each of these types of action one by one.
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 2
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 3
2  Choice of interface
The tables in sections 2.1 to 2.3 present all of the interface options and their pros and cons.
The first option in each table is the most basic configuration scenario, where pass payload or
tag data is sent from a single VTAP reader to the attached PC over a USB keyboard emulation
interface. Copying a firmware file to the VTAP mass storage drive is an easy way to update
firmware in this situation, if required.
Sending commands or remote transfer of files to the VTAP reader will require at least one of
the USB ComPort, RS232 serial, RS485 serial or TTL serial interfaces. These are called the
VTAP 'Command Interface(s)'.
Three common implementations are:
1. One of the serial ports is used for sending commands and file transfer, while pass payload
is sent over USB keyboard emulation;
2. The USB ComPort is used for sending commands and file transfer, with pass payload sent
over a serial RS232 interface;
3. Pass payload, sending commands and file transfer all use a single type of serial port, in
passive mode. (If you are using command-response actions and receiving routine data on
the same interface, choose passive mode to avoid the risk of pass reads interrupting other
actions.)
VTAP MOBILE WALLET READERS

Active or passive interface
The USB or serial communication interfaces, can be described as being in either
active or passive mode.
Active mode means that pass payload or card data read by the VTAP reader will be
sent immediately over the interface in use, whenever it is read. Active mode
allows simultaneous bi-directional communication, such as continuous reception of
any incoming data from the reader and sending any commands. (Active mode is not
therefore suitable for RS485 where communications are half-duplex.)
Passive mode means that the VTAP reader will only send data in response to a
command (query), listed in the VTAP Commands Reference Guide. Passive mode is
useful if your system or application polls for data to process, rather than reacting to
data which could arrive at any time. It ensures that data received can always be
treated as a response to the last command sent. Passive mode allows
uni-directional communication only, and so is recommended for the RS485
interface as that is half-duplex. It can also be used, on any of the full-duplex
interfaces on your VTAP reader (USB COM, serial RS232, TTL serial), if required for
your application.
Your preference is likely to be driven by your existing systems, and in-house technical
expertise.
If you need pinouts and hardware connection information please refer to the Installation
Guide for your VTAP reader (available on https://vtapnfc.com).
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 4
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 5
2.1 Interfaces to receive data from the VTAP reader
 USB keyboard emulation USB ComPort and Serial
(RS232, RS485, TTL/3.3V logic)
Read
mode
Active Active/Passive
Command-
response
No Yes
Pros •Very simple set up
•Easily understood by non-technical staff
•No third-party software integration or
development required
•Can read pass/card data without the receiving
application being in focus on an operating system
•Commands can be sent to request data, read or
change settings
•Dynamic configuration changes possible
•Can be integrated in existing custom
software/script
Cons •Requires the receiving application to be open
and in focus for every pass read (cannot be in the
background). The cursor must be in the correct
position to receive keyboard input.
•As keyboard responses differ between UK/US
and Apple keyboards some characters may
change with operating system keyboard language
settings, requiring a special keyboard map (see
KBmap setting).
•Equipment reboot needed to initiate USB
ComPort
2.2 Interfaces to send commands or transfer files
(firmware, config or keys) to the VTAP reader
 USB mass storage emulation USB ComPort and Serial
(RS232, RS485, TTL/3.3V logic)
Pros •Very simple set up
•Easily understood by non-technical staff
•USB connection on most PCs
•Updating firmware requires simple copy/paste
operation
•Config.txt file (and LED.ini file on VTAP50) can
be opened and edited simply in a text editor such
as Notepad
•Serial connections widely used in industry
•Remote file transfer can be done easily using
Zmodem, without the operating system file
manager
•More suitable for scenarios with multiple VTAP
readers connected
•RS485 ideal for long cable run (up to 1200m)
Cons •File transfer can be done locally over USB
connection
•Detecting addition or removal of mass storage
not always reliable on Windows - difficulties for
automating file transfer
•May be file caching issues where a deleted file is
only detected by the operating system on
reboot/remount
•RS232 is only suited to short cable runs (up
to 15m)
•RS485 is half-duplex, which means
communication is in only one direction at a time.
VTAP MOBILE WALLET READERS

2.3 Available interfaces on the VTAP models
The table below illustrates available interfaces on all the VTAP models
VTAP model Keyboard
wedge/
barcode
emulation
USB
ComPort
TTL
Serial
Serial
RS232
Serial
RS485
Bluetooth
keyboard
VTAP50-OEM Available Available Available Available - -
VTAP100-OEM Available Available - Available - -
VTAP100-USB-CC Available Available - - - -
VTAP100-PAC-485-CC Available Available - Available Available -
VTAP100-PAC-W Available Available - Available - -
VTAP100-PRO
(Coming soon)
Available Available - Available - Available
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 6
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 7
3  Receiving pass payload from a VTAP reader
Receiving pass payload (and card data) and sending it over one (or more) of its interfaces is
core functionality for a VTAP reader. You should decide which interface(s) will receive this
data, and whether that data should be sent automatically whenever a pass or card is read
(active mode) or whether another system is responsible for polling the reader on a regular
basis to request data (passive mode).
Although there is no restriction on the type of system that can be connected over the
interface you choose, there may be electrical safety measures to be observed in the hardware,
such as using rated power settings for the interface and the VTAP reader, grounding on both
sides, and cable shielding. You must ensure the commands used by the connected system
respect warnings or cautions that appear in this Integration Guide or the VTAP Commands
Reference Guide. (The next section discusses the commands to use if you want to poll for
data.)
The key advantage of choosing any option other than USB keyboard emulation, is that the
data can be read in the background and does not rely on a system cursor being present in an
entry box. It can also avoid the need for complex keyboard input handling code, or setting the
keyboard input language.
The configuration settings to send pass payload over USB keyboard emulation or send pass
payload over a virtual COM port are included in the VTAP Configuration Guide.
The settings to use other interfaces all follow the same basic pattern as those for keyboard
emulation, where <interface>Mode enables or disables the interface.
Most of the same settings are then used, with the appropriate KB, ComPort, Serial, or
Serial2 prefix, to determine which data to read, from which passes, cards or tags. There are
then a few extra settings specific to each interface. Refer to the VTAP Commands Reference
Guide for the specific settings to use with different interfaces.
This Integration Guide discusses the integration and operational aspects of using the serial
interfaces, including RS232 and RS485. It includes using the VTAP interfaces for sending
commands, which may be required for your integration and custom software development.
VTAP MOBILE WALLET READERS

3.1 Send pass payload over a serial RS232 or TTLinterface
The VTAP reader will, by default, send pass payload or a command response to the connected
system (such as a PC) over any serial RS232 or TTL interface.
Physical RS232 or TTLconnector
The RS232 interface is available on the captive USB/RS232 connector on
VTAP100-OEM and VTAP50-OEM. The TTL serial interface is only available on
VTAP50-OEM on the 12-pin expansion connector (if fitted). Refer to the Installation
Guide for your VTAP reader for wiring serial RS232 and TTL interfaces.
Note: RS232 and TTL serial present as different physical interfaces but use the same
UART, so only one of these interfaces should be used at a time, if both are available.
The VTAP reader can communicate in either Active or passive interface mode over a serial
RS232 interface. The settings in this section assume active mode, as this is the default. See
Use an interface in passive mode for additional settings and considerations if you need to
use passive mode.
The following list describes optional settings. You may need to use some of them to suit your
VTAP reader application:
lThe RS232 interface is enabled by default. (It can be disabled by setting SerialMode=0 if
required.) The default serial port settings are 9600 baud rate, no parity, 8 data bits and 1
stop bit, but this can be changed to match your system, in config.txt, using
SerialSettings and defining the parameters in the sequence = <baud rate>,
<parity>, <data bits>, <stop bits>, such as
SerialSettings=115200,n,8,1.
lUse the setting SerialSource in config.txt to restrict the types of data to be passed
through the serial RS232 interface, if needed. The default value is A1, which allows every
mobile pass or card/tag read, all commands and interface messages.
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 8
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 9
SerialSource values
You restrict the types of data passed through the serial RS232 interface by setting a
hex value for SerialSource in config.txt. The most common values are:
oA1 (default) allows every mobile pass, card/tag read, all commands and interface
messages;
o83 for all mobile pass, card/tag reads, all commands and interface messages;
o80 for mobile pass reads only.
The values come from a bitwise combination of the following hexadecimal values:
SECTION 1 SECTION 2
BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1 BIT 0
0x80 0x40 0x20 0x10 0x80 0x40 0x20 0x10
Mobile
wallet
pass
- - - - - Command
interface
message
Card/Tag
UID
So, for example setting SerialSource=83 (hex) will send only NFC mobile pass data to
the serial interface because 80 corresponds to choosing 1000 0011 in the table
above.
lYou could add extra prefix or postfix characters (up to 16 characters) to the data being sent,
using SerialPrefix or SerialPostfix settings.
VTAP MOBILE WALLET READERS

SerialPrefix and SerialPostfix syntax
oURL encoding of ASCII characters is supported.
oUse $t command to return the pass type as 0, 2, 4, 5, a, g, together with the
payload, where:
0 = MIFARE Classic
2 = NFC Forum type 2 / MIFARE Ultralight / NTAG
4 = NFC Forum type 4 / DESFire
5 = NFC Forum type 5 / I-CODE
a = Apple VAS pass
g = Google Smart Tap pass
o$n will add VAS merchant ID / Smart Tap collector ID index (1 to 6) and the
keyslot number used (1 to 6). For cards/tags $n will return no value --.
Example: Using prefix and postfix on Serial RS232 interface
for pass and card/tag payload
SerialPrefix=%0a%0d
SerialPostfix=%20Type:$t,Slot:$n
This will result in Google pass output:
(New line)
3|F6I53ZaPv2Ys2PAb|Muhammad Faraz|Dot Type:G,Slot:16
or NFC Type-2 card output:
(New line)
0473816A831E80 Type:2,Slot:--
lSerialPass... settings allow you to extract only a part of the full pass payload, if
preferred. Refer to VTAP Commands Reference Guide for more about these settings.
lA start-up message is set up on the VTAP reader, which defaults to
"VTAP100/<firmware version>\r". Change this using the setting SerialStartup in
config.txt.
After changing these Serial... settings in config.txt and saving it (if something other
than default behaviour is required), you can start reading pass payloads over the serial RS232
interface, in either active or passive mode.
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 10
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 11
You can continue to modify or add any of the Serial... settings by sending them as a
command over the serial RS232 interface. This is useful if you need to change a setting value
on a VTAP reader which is not accessible over USB. Section 5 details how to Use an interface
in passive mode, and important factors to bear in mind when using this approach.
VTAP MOBILE WALLET READERS

3.2 Send pass payload over a serial RS485 interface
RS485 is a half-duplex interface, so the VTAP reader must be set to passive mode to enable
uni-directional communication only.
In passive mode the VTAP reader connected over RS485 becomes subordinate to a system,
such as a PC, which is the master. The PC (master) sends a command (query) to the VTAP
reader and waits for a response. The PC can send a serial command to the VTAP reader such
as ?r to retrieve the last pass payload, or ?t to retrieve the type of the last pass read. The
VTAP reader only responds to incoming commands.
Physical RS485connector
The RS485 interface is only available on the VTAP100-PAC-485-CC. Refer to the
Installation Guide for your VTAP reader for advice on wiring a serial RS485 interface.
The following list describes optional settings. You may need to use some of them to suit your
VTAP reader application:
lThe Serial2 RS485 interface is enabled by default. (It can be disabled by setting
Serial2Mode=0 and/or Serial2RS485=0 to disable the Serial2 interface and RS485
transmission driver respectively, if required.) The default serial2 port settings are 9600
baud rate, no parity, 8 data bits and 1 stop bit, but this can be changed to match your
system in config.txt, using Serial2Settings and defining the parameters in the
sequence = <baud rate>, <parity>, <data bits>, <stop bits>, such as
Serial2Settings=115200,n,8,1.
lUse the setting Serial2Source in config.txt to restrict the types of data to be passed
through the serial2 RS485 interface, if needed. The default value is A1, which allows every
mobile pass, card or tag read, all commands and interface messages. This setting works in
the same way as SerialSource for RS232. Refer to SerialSource values in the previous
section for more, if it needs to be changed to suit your application.
lYou could add extra prefix or postfix characters (up to 16 characters) to the data being sent,
using Serial2Prefix or Serial2Postfix settings. This setting works in the same way
as Serial2Source for RS232. Refer to SerialPrefix and SerialPostfix syntax in the
previous section for more, if this is needed for your application.
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 12
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 13
Example: Using prefix and postfix on Serial2 RS485 interface
for pass and card/tag payload
Serial2Prefix=UID:
Serial2Postfix=%20Type:$t,Slot:$n
This will result in Google pass output:
UID:3|F6I53ZaPv2Ys2PAb|Muhammad Faraz|Dot Type:G,Slot:16
or MIFARE Classic card output:
UID:0473816A831E80 Type:4,Slot:--
lSerial2Pass... settings allow you to extract only a part of the full pass payload, if
preferred. Refer to VTAP Commands Reference Guide for more about these settings.
lA start-up message is set up on the VTAP reader, which defaults to
"VTAP100/<firmware version>\r". Change this using the setting Serial2Startup in
config.txt.
After changing the Serial2... settings in config.txt and saving it (if something other
than default behaviour is required), you can start sending commands (queries) over the serial2
RS485 interface, to receive pass payloads in response.
To set up the VTAP for passive mode and start sending different commands and receive
responses, follow the instructions in the section Use an interface in passive mode.
You can then modify or add any of the Serial2... settings by sending them as a command
over the serial RS485 interface. This is useful if you need to change a setting value on a VTAP
reader which is not accessible over USB.
VTAP MOBILE WALLET READERS

4  Sending commands to a VTAP reader
You can send VTAP commands to perform various operations including:
lData requests, such as a command to retrieve the last pass or card/tag payload from the
VTAP reader.
lRemote management commands, to set any of the VTAP settings in the main configuration
(config.txt), or retrieve any of the files stored on the VTAP reader, such as
config.txt or boot.txt.
lDynamic configuration commands, to perform operations not saved in config.txt like
enabling/disabling the NFC field to save power, or perform integration tasks, such as
consuming newly loaded keys.
Any serial port (USB ComPort, RS232, or RS485 serial port) can be a Command Interface, if
your VTAP reader hardware permits.
You can send the commands to the VTAP through any terminal emulator such as TeraTerm or
PuTTY, or your own custom software.
By default, with CommandInterfaces=7, sending commands is enabled on all available
serial interfaces of the VTAP reader. You can change this value to restrict which interfaces
can be used to send commands: CommandInterfaces=1 for USB ComPort only, =2 for
Serial RS232, and =4 for Serial2 RS485. You add these values together to enable commands
on multiple interfaces.
You might use the Command Interface on one communications port to control and configure
the VTAP reader in passive mode, while receiving pass and tag data on a different port in
active mode.
If you use the Command Interface on any serial port that is also set to receive pass or tag data,
we recommend you enable passive mode. This avoids potential for confusion between
command responses and pass or tag data. When a serial interface is set to use passive mode,
your application will need to poll the VTAP reader (by sending an ?r command) to retrieve
pass or tag data. This makes half-duplex operation possible (for example when using RS485).
When developing your own software, use the data request commands to pull data from the
VTAP reader, dynamic commands to make changes in VTAP reader behaviour to suit your
system and connected hardware, and use remote management commands to modify
config.txt if a setting is to be permanently changed in the VTAP reader.
The following sections discuss the use of different types of commands, during integration or
operation, over the ComPort, RS232 or RS485 interfaces. The full list of possible commands is
provided in the VTAP Commands Reference Guide.
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 14
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 15
4.1 Data request commands
These can be used to retrieve data (a Get operation) from the VTAP reader. Some of the most
common data request commands are listed below. The full list of possible commands is
provided in the VTAP Commands Reference Guide.
lUse ?r when in passive mode to request the NFC pass or card/tag payload last read. (This
command must be sent within the payload retention time set by InvalidDataCacheMS,
which is 3000ms by default).
lUse the ?type command to request the type of the NFC pass last read, along with VAS
merchant ID/ ST Collector ID and ECC key slot. For cards/tags ?t is more suitable. This
command is also used in passive mode only.
Example:Send type? command
within 3000ms after a successful Google pass read
?type
This will result in a VTAP response, such as:
G16
This shows the pass type is G for Google, the Collector ID is 1 and ECC key slot used
is 6.
Note: Always use ?type to extract the pass type when in passive mode. In passive mode,
you cannot set a prefix/postfix for your payload to output the payload using ?r with $t$n
set as prefix/postfix.
lUsing the %<setting> command to request the current value of any setting that is
included in config.txt. This command can be used in both active and passive mode.
Example:Send %PassLED to get the value for
the LED response pattern set for a successful pass read
%PassLED
This will result in a VTAP response such as:
PassLED=00FF00,100,50,2
VTAP MOBILE WALLET READERS

lSend a ?b command to retrieve boot information from your VTAP reader, as contained in
boot.txt. This includes model, serial number, hardware and firmware version, connected
expansion (if any), and ECC key slots used.
lUse the ?temp command to retrieve the internal temperature (in Celsius) of the VTAP
reader .
Example:Send %temp to check the internal temperature
of the VTAP reader
?temp
This will result in a VTAP response such as:
40.41C
SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 16
VTAP MOBILE WALLET READERS

SERIAL INTEGRATION GUIDE © DOT ORIGIN PAGE 17
4.2 Dynamic commands
These commands are used to make dynamic changes in VTAP reader behaviour. They are not
saved in the config.txt, so they can be used to make frequent changes in the VTAP reader
settings without degrading the flash memory. There are a wide range of dynamic commands,
some of the most common are listed below. The full list of possible commands is provided in
the VTAP Commands Reference Guide.
lChange the current mode of the VTAP reader to active or passive, using ?a and ?p
respectively.
lPower cycle the VTAP reader using ?reboot. (An alternative to saving reboot in a
command.txt file).
lLock the VTAP reader configuration with a password using ?l (for example ?l
APa55w0rd) and unlock with ?u (for example ?u APa55w0rd).
lConsume any newly added keys into secure storage, from the file system on your VTAP
reader, using ?keyload
lEnable or disable card emulation mode using ?cardmode (for example ?cardmode 1 to
enable card emulation mode), and set the card emulation data using ?card
<type><:lang>,<data> (for example ?card text,Hello world). For more details
refer to VTAP Application Notes on NFC tag emulation.
lSend a message from one VTAP reader interface to another, such as from RS232
(Serial) to RS485 (Serial2), or from RS485 (Serial2) to USB COM (ComPort). This can be
done using the >interface:type:message command. This feature could be used
when integrating the VTAP reader into your custom software or script development
including actions such as:
oTrigger an operation on another connected device (through the chosen interface) when
your VTAP reader reads an appropriate pass.
oSend a particular message based on the <type> of pass, card or tag read by the VTAP
reader, where your application requires different operation according to the type of pass,
card or tag.
oCopy the pass payload to another interface when in passive mode, since using ?r on any
interface will remove the cached payload from the VTAP reader.
oSend an emulated NFC pass or card UID, during testing, to see if the device connected
on a particular interface reacts as required.
VTAP MOBILE WALLET READERS