VTS Userguide
VTS Userguide
User’s Guide
The Visa Confidential label signifies that the information in this document is confidential and proprietary to Visa and is in-
tended for use only by Visa Clients subject to the confidentiality restrictions in Visa's Operating Regulations, non-Client Third
Party Processors that have an executed and valid Exhibit K on file with Visa, and other third parties that have a current non-
disclosure agreement (NDA) with Visa that covers disclosure of the information contained herein.
This document is protected by copyright restricting its use, copying, distribution, and decompilation. No part of this document
may be reproduced in any form by any means without prior written authorization of Visa.
Visa, VisaNET, and Visa USA are trademarks or registered trademarks of Visa, Inc. in the U.S. and other countries, and are
used under license by Visa, Inc.
All other product names mentioned herein are the trademarks of their respective owners.
THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE
PERIODICALLY ADDED TO THE INFORMATION HEREIN: THESE CHANGES WILL BE INCORPORATED IN NEW EDI-
TIONS OF THE PUBLICATION. VISA, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.
If you have technical questions or questions regarding a Visa service or capability, contact your Visa representative. If you
have comments or questions about this document, send them to TCS@visa.com.
Contents
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Field 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
Field 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
Network ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
Literal . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–2
Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
Installing Software for the GemCore Keyboard USB Pro Cherry . . . . . 9–13
Installing the Driver for the GemCore Keyboard USB Pro Cherry . . . . 9–13
Editing SMC Message: To edit the SMC messages please click the
SMC Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
Index
Visa Test System – V.I.P. (VTS-V.I.P.) application performs testing of certification scripts. It
provides functionality to streamline the certification process.
Audience
The Visa Test System – V.I.P. User’s Guide is intended for users who:
●
Install the hardware, communications subsystem, and applications software.
●
Conduct testing of VisaNet Integrated Payment (V.I.P.) certification scripts.
This guide assumes that users have some experience with the pre-certification testing
process and with using the Windows interface.
Related Documents
The publications listed in this section provide more information about Visa systems and
about additional services not covered in this manual.
● Card Technology Standards
●
Deluxe ISO8583 Interface Specifications
●
PIN and Security Requirements
● VAP Interface Specifications: V.I.P. Processing
● Visa Smart Debit/Visa Smart Credit System Technical
●
V.I.P. System BASE I Technical Specifications and the V.I.P. System suite of technical
specifications manuals
● V.I.P. System Services
●
EMV2000 Guidelines: www.emvco.com
● VCMS Testing and Certification Guide—V.I.P. System Member Version
Overview of VTS-V.I.P.
VisaNet Certification Management Service (VCMS) provides members and their
processors with a dedicated environment for testing their systems and completing
certification with Visa. The service offers a convenient and reliable way of testing system
integrity before connecting to VisaNet in a production environment.
VCMS closely mirrors the current VisaNet Integrated Payment (V.I.P.) System (including
Single Message System [SMS] and BASE I) and clearing and settlement (BASE II)
production environments. VCMS also supports many of the production applications in
BASE I, BASE II, and SMS.
VCMS V.I.P. allows online testing of member systems both for BASE I and for SMS.
VCMS clearing and settlement allows online testing of member clearing and settlement
interfaces.
Members need to certify that their host is capable of handling the new or changed V.I.P.
formats correctly. Members use a software application to simulate the processing of
messages between their host and the V.I.P. System.
Members used to use the DOS-based VisaNet Test System application to perform the
scenarios necessary to complete testing and certification; next, Visa developed VTS2000,
a Windows-based software application which used a standard Windows interface.
VTS2000 was discontinued in October of 2005.
VTS-V.I.P. is a Windows-based software application using a standard Windows interface
which can be connected to your test host or to the VisaNet Access Point (VAP) to execute
production similar V.I.P. testing. This tool has been in production since 2001.
VTS-V.I.P. supports end-to-end testing by performing the role of an acquirer or an issuer,
depending on the role of the member’s host system.
VTS-V.I.P. Features
VTS-V.I.P. provides these features:
An easy-to-navigate application—VTS-V.I.P. implements a Windows standard interface
which is familiar and easy to use. Screens include more information to help you to
complete testing.
An up-to-date platform—VTS-V.I.P. runs on Windows XP and Windows Vista and is not
dependent on an unsupported operating system.
IMPORTANT
The Windows NT 4.0 operating system is not supported, effective 30
November 2005. See IML #4204.
The Windows 2000 operating system is not supported, effective 30
April 2010.
NOTE: Any references to Windows XP in this document refer to both the Home and
Professional editions. Any references to Windows Vista in this document refer to
the 32 bit version.
An expanded variables function—With the Variables Manager, you can create your
own variables, as well as use or edit variables supplied by Visa. The Variables function
enables you to change a variable once and have this change reflected in all tests that use
the variable. VTS-V.I.P. improves variables management by grouping them by function.
New editing features—VTS-V.I.P. includes a cursor place indicator to help you locate
your position when you are editing a field or subfield. This is especially helpful when you
are editing large literal fields where the position of data is critical.
Matching at a subfield level—VTS-V.I.P. provides matching at the subfield level.
The ability to run cases in parallel—With VTS-V.I.P., you can run several test cases at
the same time. This saves testing time.
The ability to resume running a test—This feature allows you to pause test execution to
correct message errors as they occur and then resume testing at that point, rather than
beginning again.
The ability to pair and depair station IDs with Extended Access Server/Visa
Message Gateway (EAS/Visa MG)—VTS-V.I.P. allows you to pair and depair station IDs
easily using a new menu option or toolbar icon called EAS/Visa MG.
A raw message viewer—VTS-V.I.P. provides an option to save raw messages in a
separate file and view them while the Communications Handler is not running.
Support for new chip card readers—VTS-V.I.P. supports two EMV Level 1-compliant
chip card readers. These chip card readers allow a complete online chip card processing
flow, including support for issuer authentication and issuer scripts.
Contactless—VTS-V.I.P. provides support for using the ViVOpay 4000/5000 contactless
card reader using MSD standard.
Magstripe—VTS-V.I.P. provides support for using the Magtek for magstripe card readers.
Contact, Contactless, Magstripe—VTS-V.I.P. provides support for using the Equinox
device for these three types of card reading.
Multiple Instances—VTS-V.I.P. provides the ability to view and run both issuer and
acquirer stations simultaneously on one machine.
Better Productivity—Automated Log Comparison enables users, developers, QA
analysts, regional certifiers, and members to have better productivity.
Support for Deluxe (ISO 0, 2, 4, A, C, and 8)—VTS-V.I.P. provides the Deluxe
Knowledgebase and variables.
You can use VTS-V.I.P. for authoring, editing, and testing functions. You can build your
own tests, as well as run or modify any tests supplied by Visa.
When you run a test, VTS-V.I.P.:
● Builds incoming and outgoing messages.
● Analyzes incoming and outgoing messages by comparing input fields to expected
results.
● Logs test run results, including errors and discrepancies.
In addition, VTS-V.I.P. enables you to edit or create any component of the test system,
from a database that contains one or more tests to a subfield within a message. The
editing tools let you perform common editing functions such as copying, cutting, pasting,
and deleting text.
VTS-V.I.P. uses information from the Knowledgebase to determine which fields you can
include in messages and what their values should be. These values are based on the
V.I.P. definition database. See V.I.P. System BASE I Technical Specifications and the
V.I.P. System SMS technical specifications manuals for more information on V.I.P. fields.
For information on other message formats, see the following:
When you run the tests, VTS-V.I.P. sends and receives the messages over the
communications lines using the Communications Handler. As soon as these messages
are sent or received, VTS-V.I.P. logs them. You can use this log to evaluate the test
results.
Figure 1–1 shows the major VTS-V.I.P. components.
Communications
Knowledgebase Handler
Test Handler
Log Server
Variable Manager
Log File Log Viewer
ATM or POS
Request
Response
Acquirer
Host
Response Request
= Role being
tested
= Role of VTS-
V.I.P.
ATM or POS
Device
Response Request
Acquirer
Host
Response Request
Request Request
Response Response
Acquirer VisaNet Issuer VAP
VAP Interchange
Center (VIC)
Response Request
Issuer
= Role of VTS-V.I.P. Host
Request
Response
ATM or POS
Acquirer
Device
Host
Response Request
Acquirer
VAP
Response Request
Request Request
= Role being
Response Response
tested
VisaNet Issuer VAP Issuer
= Role of VTS- Interchange Host
V.I.P. Center (VIC)
Response Request
Request
= Role being
tested Response
● VisaNet Loopback—Routes messages to and from VTS-V.I.P. and the member host
through the VAP and VCMS test systems. VisaNet Loopback mode provides a
simulation of a complete V.I.P. processing cycle.
● None—Routes messages to and from the member's host either to another member's
host or to a Visa certification lab. Because VTS-V.I.P. is not in the routing path for this
loopback mode, it prevents test execution until the loopback mode is changed to
either Local Loopback or VisaNet Loopback.
Request
Response Request
Request
Response
VCMS
VAP VIC
Serial Test Port
= Role being
tested
= Role of VTS-
V.I.P.
Issuer
Host
Request
Response Request
Request
Response
VCMS
VAP VIC
Test Port
Response Request
= Role being
tested
= Role of VTS-
V.I.P.
Issuer
Host
Online Certification
As soon as you have completed offline testing and VCMS VisaNet Loopback testing, you
can perform online certification testing. You do not use VTS-V.I.P. in this configuration.
Your host computer runs tests through a VAP that is connected to the Visa VCMS V.I.P.
System, as shown in Figure 1–8 and Figure 1–9.
Request
Response Request
Request Request
= Role being
tested Response Response
VCMS Visa
VAP VIC Certification
Office
= Role being
tested
Limitations of VTS-V.I.P.
VTS-V.I.P. does not simulate all of the functionality of the V.I.P. System. The following
limitations apply when offline testing:
●
In VCMS VisaNet Loopback mode, VTS-V.I.P. does not download data defined in the
core V.I.P. globals for its processing.
● VTS-V.I.P. does not calculate fees for multicurrency processing.
● VTS-V.I.P. does not perform the following edits:
VTS-V.I.P. Support
If you have a problem, first call your Visa representative for help. If your Visa
representative cannot solve your problem, please ask them to contact Inovant Global
Support Services.
Inovant Global Support Services will escalate your issue to VTS-V.I.P. Development using
all of the information you have provided to your Visa representative. Remember to include
a phone number where you can be reached in case Inovant Customer Support or VTS-
V.I.P. Development needs to call you back to troubleshoot your problem. Inovant
Customer Support is available 24 hours per day, seven days per week.
For troubleshooting, VTS-V.I.P. Development asks for the following information:
● The version of VTS-V.I.P. you are using.
●
The type of operating system.
●
The steps needed to re-create your problem.
See Table 2–2 for protocol requirements and Chapter 3, Setting Up the
Communications Handler for more information on choosing a protocol.
● If an anti-virus application is running on your personal computer, disable it before
attempting to install VTS-V.I.P. Do not allow any anti-virus software to run in the
background. (However, be sure to enable it after you install VTS-V.I.P.)
● If you have difficulty installing the VTS-V.I.P. software, contact your Visa
representative.
System Requirements
VTS-V.I.P. should be installed on a computer running Windows XP or Windows Vista.
Table 2–1 provides the minimum and recommended system requirements.
Computer Pentium III, 550 MHz or higher Pentium III, 700 MHz or higher
Operating system One of the following is required: One of the following is required:
● Windows XP ● Windows XP
● Windows Vista (32 bit) ● Windows Vista (32 bit)
● Windows 7 (64 Bit) ● Windows 7 (64 Bit)
Table 2–2 provides the communications protocols supported in VTS-V.I.P. and their
requirements.
TCP/IP LAN Computer should be able to ping the VAP and vice-versa.
X
Installing VTS-V.I.P.
The VTS-V.I.P. application contains utilities that work together to create, edit and run tests,
and create logs and printouts of the results. VTS-V.I.P. includes the following components:
● Main VTS-V.I.P. application (referred to as Test Handler)
● Communications Handler
● Variables Manager
● Knowledgebase
● Log Comparison
● Log Server
●
Log Viewer
●
Raw Message Viewer
● Uninstall Utility
● User’s Guide
●
Help
When you install VTS-V.I.P., you also install the Visa-provided V.I.P. Knowledgebase. This
knowledgebase contains predefined templates according to product and service. You use
these messages to build your tests. (A separate installation is required for other
knowledgebases, such as Deluxe.)
Installing the VTS-V.I.P. software makes the following changes to your system:
● Adds entries to your registry file.
● VTS3.ini and VTS3default.ini file.
● For multiple instances VTS-V.I.P. (0), (1), (2).ini files.
● Installs Microsoft Data Access Components (MDAC) 2.8 or later, if not already
installed.
To install VTS-V.I.P.:
1. Insert the VTS-V.I.P. CD-ROM into the CD-ROM drive or download the VTS-V.I.P.
installation files from VOL as appropriate.
2. Double-click the setup.exe file.
The default is set to install all files.
3. Follow the screen prompts to complete the installation, or download for VOL.
NOTE: After VTS-VIP v33.0 installation on WinXP, please replace the file
"C:\Program Files\Vts3\Appl\WinSCard.dll" with the existing file
"C:\Windows\System32\WinSCard.dll" in your workstation.
Starting VTS-V.I.P.
You can start all of the VTS-V.I.P. components, except the uninstall utility, from inside the
application. In addition, you can start some of the utilities from the Programs menu.
To start VTS-V.I.P.:
1. Click the Start button on the taskbar, point to Programs, and then click Visa Test
System Suite of Tools.
2. Click the Visa Test System icon or any of the icons to start that corresponding utility.
NOTE: You can also right-click any utility to create a shortcut for your desktop.
When you start the first VTS utility there is approximately a 15-second delay, due to
initiation of the Log Server. When you start subsequent VTS utilities, there will be no delay
as long as the Log Server is running. The Log Server runs in the background and the Log
Server icon remains in the taskbar.
Navigating VTS-V.I.P.
You can navigate through VTS-V.I.P. by clicking buttons or by selecting items from the
menus. Scroll bars allow you to view data that might not fit on your screen. Also, you can
adjust the size of many of the windows to fit your needs.
If a button or menu selection appears in dim print, this indicates that the function or option
is not available and is probably not applicable to your current activity.
The main VTS-V.I.P. window is divided into the Test Area on the left and the
Knowledgebase on the right. The Log Window displays current messages at the bottom of
this main window. You can also hide the Log Window.
For optimal viewing with multiple instances, resize the windows to view the instances side
by side, rather than layering instances horizontally. This way, you can view the Log
Window in both instances.
NOTE: As you resize the window and it becomes narrower, some of the features on the
toolbar are not visible. You may select any of these features by using menu
options (File, Edit, View, Tools, Help).
VTS-V.I.P. includes a toolbar with buttons for quick access to commonly performed tasks.
There is also a status bar and indicator showing whether the communications line is up or
down.
Figure 2–3 illustrates the parts of the main VTS-V.I.P. window.
Toolbar
Log Window
Status Bar
You can control whether to display the status bar or main toolbar by using the View menu.
2. The view option you select appears in the main VTS-V.I.P. window.
You can control whether to show or hide the Log Window in Preferences. The view option
will take effect after you restart VTS-V.I.P.
Viewing Preferences
In Preferences, you can view the version number, installation directories, and internal
message template IDs.
The Installed Version box shows the version number of VTS-V.I.P. that is installed on
your computer. This value is for display only.
2. Click OK to close the Preferences dialog box.
On the Directories tab, you can view the installation directories.
Viewing Directories
Follow these steps to view directories.
This tab shows the directories where VTS-V.I.P. was installed. These values are for
display only.
2. Click OK to close the Preferences dialog box.
Viewing Signons
You can view the internal message template IDs VTS-V.I.P. uses for credit and debit sign-
on and sign-off messages.
This tab shows the business paths for BASE I and SMS sign-on and sign-off 0800
messages used when connected to the VCMS VAP. These values are for Visa internal
use only.
2. Click OK to close the Preferences dialog box.
This tab shows the file indicator for the types of files to rotate and the frequency of
scheduled rotation. These values can be adjusted as desired to avoid overfilling your
hard disk.
2. Check the File Rotation box to adjust file rotation parameters.
3. Adjust the files and options as needed.
4. Click Apply to apply any new settings.
5. OK to close the Preferences dialog box.
The other tabs in Preferences are described in the chapters and sections listed below.
Variables groups are designated for each case. Therefore, if a test is made up of
several cases, you could designate different variables groups for each. (See Chapter
5, Using Variables.)
6. Modify messages in the test at the field or subfield level with the Message Editor and
Field Editor. (See Chapter 6, Modifying a Test.)
7. Run the test. (See Chapter 7, Running a Test.)
8. Examine the test results with the Log Viewer after the test has been run. (See Chapter
8, Obtaining Test Results.)
To open the Help system, click the Help toolbar button (pictured at left), or, on the Help
menu, click Help Topics.
You can browse the expandable table of contents on the left-hand side of the screen.
Click the Contents tab and click any topic to display it on the right-hand side. Each
Contents entry has an icon that describes the type of topic it is linked to as shown in
Table 2–3.
You can also search through Index entries. Click the Index tab, then type a word to
perform a search. When you find an Index entry that interests you, click to display the
topic or list of topics associated with it. Topics are often indexed under more than one
entry.
Also, you can use the search feature to locate every occurrence of a word or phrase in the
Help system. Click the Search tab, type the word, and click List Topics. When you find a
topic description of interest, click it to display the topic.
In addition, in many dialog boxes you can click the Help button or Help menu to access a
context-sensitive Help topic. Context-sensitive Help provides information about the
purpose of the dialog box, how to complete it, and related topics.
Uninstalling VTS-V.I.P.
You can uninstall VTS-V.I.P. from the Programs menu.
To uninstall VTS-V.I.P.:
1. Click the Start button on the taskbar, point to Programs, and then click Visa Test
System Suite of Tools.
2. Click the Uninstall Visa Test System icon, and the VTS-V.I.P. application will be
removed from the system.
Toolbar
Status
Indicators
Raw Messages
Log
The Log shows communications line messages that provide information about the status
and activity of the Communications Handler. It also shows the severity of the error
message (Informational, Warning, or Fatal).
Choosing a Protocol
The Communications Handler supports the following host interface protocols:
● TCP/IP LAN
● TCP/IP SLIP (direct or modem)
Set your protocol in the Communications Handler on the General tab. (This procedure is
described later in this chapter in “Setting Your Protocol in the Communications Handler.”)
NOTE: Effective November 2005, SNA LU0, X.25, BSC 3270, and BSC 2780 are not
supported.
4. Select whether VTS-V.I.P. will play the Client or Server role. (Typically, VTS-V.I.P. acts
as the Client and the remote host system acts as the Server.)
NOTE: VMLH (B2 B3 Hex) is for development use only.
5. Type the IP Address of the computer on which VTS-V.I.P. is running.
To determine the IP address of the computer, open a DOS window by clicking the
Start button on the taskbar, and clicking Run. Type Command in the dialog box. In
the DOS window, type IPCONFIG.
NOTE: If you click the TCP/IP tab, and then select Server, the Communications Handler
autodetects the VTS IP address; you do not have to find it using IPCONFIG. You
can do this on both the issuer PC and the acquirer PC by entering the
corresponding HOST IP address.
For multiple instances, the client Host IP Address and Port data should be used
for the server VTS IP Address and Port.
For a TCP/IP LAN connection, if you use an incorrect local IP address or a virtual
IP address used in the TCP/IP SLIP connection, you can establish the
connection with the remote host, but cannot change the VCMS loopback mode.
6. If VTS-V.I.P. is acting as the Client:
– Type the IP Address of the remote host system.
– Type the 4-digit Port number where the remote host system is listening.
If VTS-V.I.P. is acting as the Server:
– Type a 4-digit Port number. This can be any value from 1024 through 32767, as
long as this port number is not used by another server application on your
computer.
7. Under Link Protocol, click LAN.
8. Click Apply to save the settings, and click OK to close the dialog box.
6
— 20
8
6
1 2 3 4 5 6 7 8 20 20 —
8
7 — 7
3. Insert the other end of the 9- to 25-pin connector into the null modem.
4. Insert one end of the 25-pin cable into the null modem and the other end into the host
or VAP. If you are connecting to a VAP, use communications port 2.
Configuring RAS
You need to configure Microsoft Remote Access Service (RAS) if you are connecting
through a TCP/IP SLIP connection.
NOTE: Your system administrator should have already installed your Remote Access
Service (RAS).
Windows XP includes support for Unimodem modems. If you attempt to use a device with
RAS that is not supported by Unimodem, you may need to configure RAS to use the
Modem.inf file (instead of using Unimodem) to retrieve initialization information for the
devices you add.
When you install VTS-V.I.P., it sets the EnableUnimodem=0 to allow RAS to add the direct
connect serial cable (Dial-Up Networking Serial Cable between 2 PCs). The VTS-V.I.P.
installation also updates your Modem.inf file to add the lines for Dial-up Networking
Serial Cable between 2 PCs.
You need to set up your computer to use this entry. Follow the appropriate section
depending on whether you have a Windows XP operating system.
10. Choose the port (COM1 or COM2) that will have the serial cable to the VAP, click
Next, and click Finish.
Follow the next section to set up your RAS Phone Book file.
2. Click Client. (You cannot set the Communications Handler as the server because
Windows XP and Windows Vista workstations do not support a TCP/IP SLIP dial-in
connection.)
NOTE: VMLH (B2 B3 Hex) is for Development use only.
3. Type a virtual IP address specified by the VAP or remote host. This IP address should
be within the same subnet as the IP address of the VAP or remote host.
4. Type the IP Address of the remote host system.
5. Type the 4-digit Port number where the remote host system is listening.
6. Under Link Protocol, click SLIP, and click Direct.
7. In the Port list, select the communications port where you have attached the serial
cable to the null modem.
8. Click Apply to save the settings, and click OK to close the dialog box.
2. Click Client. (You cannot set the Communications Handler as the server because
Windows XP and Windows Vista workstations do not support a TCP/IP SLIP dial-in
connection.)
NOTE: VMLH (B2 B3 Hex) is for Development use only.
3. Type a virtual IP address specified by the VAP or remote host. This IP address should
be within the same subnet as the IP address of the VAP or remote host.
4. Type the IP Address of the remote host system.
5. Type the 4-digit Port number where the remote host system is listening.
6. Under Link Protocol, click SLIP, and click Modem.
7. Type the phone number of the modem for the VAP.
8. In the Port list, select the communications port where you have attached the serial
cable to the dial-up modem.
9. In the Baud Rate list, select 9600 bps or higher if appropriate.
10. Click the Enable compression check box to enable data compression.
11. Click Apply to save the settings, and click OK to close the dialog box.
2. On the Tools menu, click Protocol Options. The Settings dialog box appears.
Case names within each test and message names within each case must be unique.
When you open a saved test in VTS-V.I.P., the cases and messages appear, as shown in
Figure 4–2.
Case
Messages
Each message contains fields that contain data or references to data. You can edit these
fields to change data or references. A field may or may not have subfields.
NOTE: The properties at the test level are global and, once selected, override the case-
level properties.
Using Knowledgebases
Knowledgebases are Visa-supplied databases designed to assist you in the testing
process. The Knowledgebases contain preset possible message definitions.
These preset definitions in the Knowledgebase are provided so that you can avoid
specifying all required values yourself. Each prototype definition already includes fields
that are optional, conditional, or mandatory for the specific function, and the Message
Type Indicator (MTI). The definition also contains default values for each field in the
request and response and the validation rules used for each field.
When you create a test, you associate a Knowledgebase with it. Then you can select a
message or group of messages from the Knowledgebase, and drag it (or them) to the test
case.
Figure 4–3 shows the format of the Knowledgebase.
Creating a Test
This section describes how to create a new test and add cases and messages to it.
2. Click to select the type of Knowledgebase that you want to associate with the test.
The type can be V.I.P. or Deluxe.
3. Click OK.
NOTE: To name the test, on the File menu, click Save As.
This creates a test which appears in the left pane of the window and contains one
empty test case. On the right pane, the Knowledgebase displays a tree with the
current available messages
4. In the right pane, click to expand the Knowledgebase tree to open the Incoming
Request or Outgoing Request folder of the service desired.
5. Drag a single message or pair of messages to the case in the left pane to add new
messages to test Case 1.
NOTE: You can also drag a folder and add all the messages in that folder to the test case
at the same time.
6. Click the Save toolbar button, or on the File menu, click Save.
If you designate a variables group at the test level (in the Test Properties dialog box),
VTS-V.I.P. also updates all case properties. However, after this test-level update, you can
designate a variables group for individual cases (in the Case Properties dialog box).
For more information on designating a variables group, see “Designating a Variables
Group for the Test Case” in Chapter 5, Using Variables.
For information about match probability, see “Using Match Probability” in Chapter 7,
Running a Test.
2. Select a test file and click Open. The test opens in the left pane.
3. If you modify the test, use Save As to save it in your User_Test_Scripts folder.
NOTE: To change the name of a case, double-click or right-click the case name, or click
Properties under the case name in the main VTS-V.I.P. window.
3. On the Tools menu, click Export Case(s) To Text File. The Save As dialog box
appears.
4. Type a file name.
EXAMPLE
Field 123 can be added to an authorization request for AVS
processing, but it cannot be included in reversals.
When you select a test configuration setting, VTS-V.I.P. generates default field values for
the fields affected by the setting; however, you can override these defaults by editing the
message and specifying literal values for any of the fields.
Table 4–1 provides a brief description of each configuration setting.
Bypass VCMS Stations Bypasses the station pairing VCMS establishes between the
member host and VTS-V.I.P. in VisaNet Loopback mode. If
selected, VTS-V.I.P. does not insert station IDs into header fields
5 and 6.
Field 55 ● Field 55 is an ISO field used for transmitting chip data in Tag
Length Value (TLV) format. Field 55 can be used for chip
transactions. Field 55 contains a drop-down menu with the
following options: VIS_F55, CCD_EMV_F55, GEN_EMV_F55,
VIS_F55_2.
●
If set to Yes, field 55 is present in the message, if appropriate.
● If set to No, field 55 is omitted from the message.
VTS-V.I.P. provides context-sensitive Help in the status bar for the Test Configuration
dialog box. As you point to a test configuration setting, the status bar indicates which
fields it affects.
For more information about field usage and valid values, refer to the V.I.P. System BASE I
Technical Specifications document and the V.I.P. System SMS technical specifications
manuals. For more information about individual services, refer to V.I.P. System Services.
The following sections provide more information on each configuration setting.
3rd Bitmap
3rd Bitmap Expanded and 3rd Bitmap Fields each have two options: yes and no.
When 3rd Bitmap Expanded is set to Yes, the Expanded Format of the 3rd bitmap chip
fields is present in the message. Selecting Yes results in F134E and F140 being used
instead of F134/F135 and F139.
If No is selected, F134/F135 and F139 (nonexpanded) are used (instead of F134E and
F140).
This configuration setting is used in conjunction with the 3rd Bitmap Fields configuration
setting. That is, 3rd Bitmap Fields are set to Yes when 3rd Bitmap Expanded is set to Yes.
If 3rd Bitmap Fields is set to Yes, 3rd bitmap chip fields are present in the message, if
appropriate. One of three chip card types or flags (VIS_3RD, CCD_EMV_3RD, and
GEN_EMV_3RD) can be selected from the drop-down menu. Please refer to related
documentation (that is, VIS 1.4.0 Technical Reference, EMVCo manuals, and the like) for
card type definitions.
If set to No, chip fields are omitted from the message.
Custom Payment Service (CPS) adds field 62 and subfields to appropriate messages.
CPS transactions qualify for a different interchange rate.
Field 55
Field 55 is an ISO field used for transmitting chip data in Tag Length Value (TLV) format.
Field 55 can be used for chip transactions. Field 55 contains a drop-down menu with the
following options: VIS_F55, CCD_EMV_F55, GEN_EMV_F55,VIS_F55_2.
If this field is set to yes, it is present in the message, if appropriate. If it is set to no, it is
omitted from the message.
Field 59
Field 59 is a national-use field that identifies an intra-country geographical location. For
instance, it is used in the U.S. and Canada to include the state code or province code, and
sometimes the ZIP or postal code.
Field 62 Bitmap
Field 62 can be formatted in bitmap or fixed format.
If the Field 62 Bitmap configuration setting is set to Yes, field 62 appears in bitmap format,
whenever it is present in a message. If it is set to No, field 62 appears in fixed format.
See V.I.P. System BASE I Technical Specifications and the V.I.P. System SMS technical
specifications manuals for details on field 62.
Field 118
Field 118—Intra-Country Data is a national-use field that contains information unique to
the processing of Visa messages by members in a given country.
If you set the Field 118 configuration setting to Yes, you can specify Japan, Korea, or
another country.
Message Format
The Message Format configuration setting determines whether messages are in BASE I
or V.I.P. message format. V.I.P. format requires fields 19 and 25 in response messages,
but BASE I does not.
Multicurrency Service
The Multicurrency Service configuration setting in VTS-V.I.P. simulates main parts of the
Multicurrency component of the V.I.P. System. VTS-V.I.P. emulates this functionality so
that you can test your member host’s software by processing Multicurrency Service fields.
It consists of the conversion of transaction amounts and currency codes of outgoing
messages if the Multicurrency configuration setting is set to Yes. To calculate a value for
field 6, VTS-V.I.P. multiplies the value in field 4 by the Billing Rate issuer variable.
Network ID
Field 63.1 contains Network ID that specifies the network to be used for transmission of
the message and determines the program rules that apply to the transaction.
●
If user selects VISA_NID0002 then the value of F 63.1 would be 0002.
● If user selects INLK_NID0003 then the value of F 63.1 would be 0003.
● If user selects VISA_NID0004 then the value of F 63.1 would be 0004.
●
If user selects CIRRUS_NID0006 then the value of F 63.1 would be 0006.
● If user selects MASTERCARD_NID0007 then the value of F 63.1 would be 0007.
● If user selects STAR_NID0008 then the value of F 63.1 would be 0008.
● If user selects PLUS_NID0009 then the value of F 63.1 would be 0009.
● If user selects STAR_NID0010 then the value of F 63.1 would be 0010.
●
If user selects STAR_NID0011 then the value of F 63.1 would be 0011.
Name represents the common name used for the service and Flag represents an
internal description of the flag. In some cases, the Flag column includes a drop-down
list.
For instance, if you set the AVS configuration setting to Yes, you can also specify AVS
or IAVS.
2. Double-click the Y/N column to select whether the field is set to Yes or No. (By
default, all services are set to No.)
3. Click OK to save your selections.
VTS-V.I.P. changes the fields and messages and the main VTS-V.I.P. window appears.
To insert a delay:
1. Select a message in the main VTS-V.I.P. window.
2. Click the Insert Delay toolbar button, or on the File menu, click New and then click
Delay.
VTS-V.I.P. inserts a Delay icon before the test and the Delay dialog box appears.
3. Type the length of the delay in the Hours, Minutes or Seconds boxes.
4. Click the Save toolbar button, or on the File menu, click Save.
Message Format
Variables Groups
Within the acquirer, card, issuer, and system group folders, you can maintain one or
several groups of variables. When you install VTS-V.I.P., you receive one default group in
each folder.
The default variables groups are marked default and cannot be deleted. However, once
you create other groups, you can designate a different one as the default group.
In the user-defined folder, you maintain only one group of variables. When you install
VTS-V.I.P., this group is empty.
You can edit variables in any group, and add or delete variables in the user-defined group.
In addition, you can make a copy of any group, using the save as feature, to create a new
group with a new name.
NOTE: For an open test, any changes to variables will not appear in the test cases until
you close and reopen the test.
Acquirer Variables
Acquirer variables relate to acquirer identification and processing. Table 5–1 lists the
primary fields where the values are used. However, values may be used in other fields.
F042 CARD ACCEPTOR Card Acceptor Identification Code - Field CARD ACCEPTOR
CODE 42
F130/F55 TERM CAP PROF Terminal Capability Profile - Field 130 - 204000
Tag 9F33 (Chip)
F131/F55 TERM VERI RESULTS Terminal Verification Results - Field 131 - 8000100000
Tag 95 (Chip)
F133/F55 TERM SER NUM Terminal Serial Number - Field 133 - Tag 99999999
9F1E (Chip)
F146/F55 TERM TXN DATE Terminal Transaction Date - Field 146 - 010101
Tag 9A (Chip)
F149/F55 CRYPT CASHBACK AMT Cryptogram Cashback Amount - Field 149 000000000000
- Tag 9F03 (Chip)
NOTE: * These fields contain a drop-down menu from which to select a value. The value
indicated is an example.
Card Variables
Card variables relate to a credit or debit card. Table 5–2 lists the primary fields where the
values are used. However, values may be used in other fields.
F045.04 CARD HOLDER NAME Track1 Card Holder Name - Field CARD HOLDER NAME
45.4
F134/F55 GENERIC EMV APPL DATA Generic EMV Issuer Application 22112233445566778899
Data - Field 134 - Tag 9F10 (Chip/ AABBCCDDEEFFFFEE
GENERIC Format) DDCCBBAA9988776655
4433221100
F134/F55 VISA DISCRE DATA Visa Discretionary Data - Field 134 - 010A03A0B0000000000
Tag 9F10 (Chip) 00
F134/F55 VISA DISCRA DATA CCD Visa Discretionary Data - Field 134 - A400000000000000000
Tag 9F10 (Chip/CCD Format) 00000000000
F135/F55 ISS DISCRE DATA Issuer Discretionary Data - Field 135 N/A
- Tag 9F10 (Chip)
F135/F55 ISS DISCRE DATA CCD Issuer Discretionary Data - Field 135 00000000000000000000
- Tag 9F10 (Chip/CCD Format) 0000000000
F152/F55 SECONDARY PIN DATA Secondary PIN Data - Field 152 - 1234
Tag C0 (Chip)
Issuer Variables
Issuer variables relate to issuer identification and processing. Table 5–3 lists the primary
fields where the values are used. However, values may be used in other fields.
F139.02/F55 CARD STATUS UPDATE Cryptogram CSU - Field 139.02 or Field 00860000
140.02 - Tag 91 (Chip)
NOTE: * These fields contain a drop-down menu from which to select a value. The value
indicated is an example.
System Variables
System variables are not specifically related only to an issuer, acquirer, or a credit or debit
card. Table 5–4 lists the primary fields where the values are used. However, values may
be used in other fields.
NOTE: * These fields contain a drop-down menu from which to select a value. The value
indicated is an example.
User-Defined Variables
Initially, when you first install VTS-V.I.P., the user-defined group of variables is empty. You
can create these variables, and use them in any message in a test.
The database for the message format you select appears. The following example
shows the V.I.P. Variables Database.
You can resize or relocate the main Variables Manager window by using the mouse to
drag the window corner. The window will open to this same position each time you
open the Variables Manager.
3. Click the plus symbol (+) next to the any of the group folders, for instance Acquirer
Groups, to expand and display the groups in that folder.
See the next sections “Creating a New Variables Group” or “Modifying a Variable.”
3. Type a new name for your variables group and click OK. Your new group appears.
See the next section for instructions on editing variables in your new group.
Modifying a Variable
This section describes how to edit the value of an existing variable. However, to edit a
user-defined variable, see the “Modifying a User-Defined Variable” section.
As you edit a variable, VTS-V.I.P. validates its minimum length, maximum length, and
validation type (numeric, alphanumeric, alphanumeric/special, or hexadecimal format).
The property of each variable has been created in advance to be used in specific fields,
which have predetermined data types and lengths. For instance, a variable created for
country code only allows a length of three digits and numeric data.
When editing variables, you cannot navigate to other windows. This is necessary for key-
by-key validation of input.
You can copy and paste data from Microsoft Word or Excel.
To edit a variable:
1. Open a variable group.
2. Enter detailed information about the variables group in the Group Description box.
NOTE: To change the name of a variables group (Group Name), use the Save As feature
on the File menu. If you no longer need the old group, simply delete it.
3. Double-click the variable in the Value column to edit it.
VTS-V.I.P. displays the variable’s minimum length, maximum length, and validation
type (AN, ANS, N, or HEX) at the bottom of the screen for your reference.
As you enter new data, each character is immediately validated. For example, if the
validation type is HEX, only the characters 0-9 and A-F are accepted. Also, no more
than the maximum length number of characters is accepted and the Enter key is not
recognized unless the minimum number of characters is present. To cancel editing
and restore the original value, press ESC.
When you are finished editing, press Enter or the TAB key.
4. Click the Save toolbar button, or on the File menu, click Save to keep your changes.
5. To close the message format database, click the Close Database toolbar button, or
on the File menu, click Close.
3. VTS-V.I.P. prompts you to save changes. The CA Bank variables group displays
Default next to the group name.
NOTE: The variables group set as the default cannot be deleted. You must first select a
different group as the default in order to delete a variables group.
The issuer variables group is now associated with the specified card group.
2. Click the Add Variable toolbar button, or on the User menu, click Add Variable.
3. Click the Edit Variable Properties toolbar button, or on the User menu, click Edit
Variable Properties.
NOTE: You can also double-click the Value column to edit the variable. When you are
finished editing, press Enter or the Tab key.
4. The Field Editor window appears. Under Population Method, click Variable.
5. Under Population Source, in the Variable Name box, select Variable from the drop-
down list.
The validation type and length of the variable must match the format and length
defined for the field or subfield in order to be displayed in the Population Source.
6. Click OK to save your changes and return to the Message Editor.
7. Click OK to close the Message Editor and return to the main VTS-V.I.P. window.
To delete a variable:
1. Open the user-defined variables group.
2. Double-click a cell in the Value column to select the variable you want to delete.
3. Click the Delete toolbar button, or on the File menu, click Delete.
3. Under Variable Groups to Use, click a drop-down list to change the associated
variables group, or click Default to use the variables group set as the default.
Click Random or Sequential to specify that VTS-V.I.P. either applies a random
variables group or the next group in sequence.
a. Under Card, when you select a card group, VTS-V.I.P. uses the associated issuer
group.
See the “Processing Cards Offline” section in Chapter 9 for information about
using a chip card reader.
b. Under Issuer, by default, All is selected.
If you click the button next to the Issuer drop-down list and select an issuer, under
Card only cards linked to that issuer will be available in the card drop-down list.
4. Click OK.
NOTE: If you add a new variables group (using Variables Manager), use the Refresh
button (shown) to view the newly added group in the Acquirer, Card, Issuer, or
System drop-down lists.
The main use of the Message and Field Editors is to logically construct a value for a
current field. A field is defined with a value or a reference that points to or generates a
value. You can change the value of a field, remove it from a message, specify where VTS-
V.I.P. can find its value, or construct a subfield value for some fields.
NOTE: You can right-click a message to quickly edit it in the Message Editor, view it in
hexadecimal format, copy, rename, or delete it.
In editable fields in the Message or Field Editor, you can right-click to copy, paste,
or delete content.
Population Methods
Fields and subfields include references that describe the source of the data, such as
literal data or whether a field is system-generated. The population methods determine
how VTS-V.I.P. generates a value for the field. Depending on the population method
selected, the value can be entered by you, copied from another message, or generated
by VTS-V.I.P.
The population methods include:
● Literal
● Field in Earlier Message
● Field in Previous Message
● Field in Current Message
● Variable
● Valid Value
● System Generated
● Subfield Level
Literal
Selecting this option tells VTS-V.I.P. that you are providing data in alphanumeric, decimal,
or hexadecimal format. You can type the value for that field or subfield manually.
Specify hexadecimal format by selecting the Hex check box. Checking this option allows
you to put in literal hexadecimal data for a field. Hexadecimal format bypasses all edit
rules and can be used to send data that is normally not allowed. Hexadecimal characters
are 1–9 and A–F.
You can copy only from an earlier or previous message within the same test case.
Previous refers to the message immediately before the current message. If VTS-V.I.P.
cannot find the field to be copied from an earlier message, it generates a valid value to
meet the field validation.
Variable
Selecting this function lets you provide a name and a pointer to variables. VTS-V.I.P. only
permits use of the variable if the validation type and length of the variable matches the
format and length defined for the field or subfield.
Valid Value
For an incoming message, Valid Value means that VTS-V.I.P. allows any valid value and
checks the content for validity.
Valid values are values that meet the edit criteria, but do not necessarily represent
specific codes or values used by V.I.P. For example, a valid value for field 32 is a random
numeric value that does not represent a real Acquirer Institution Identification Code. If a
random value is not sufficient for your testing, you must substitute a valid literal value in
the field.
System Generated
For an outgoing message, System Generated means that VTS-V.I.P. generates a value for
you. However, you cannot populate some fields with system-generated values.
<BlueUL>Table 6–1 lists the fields for which System Generated is allowed for outgoing
messages.
NOTE: The accuracy of the data values can be guaranteed only for those fields listed in
<BlueUL>Table 6–1.
Field ID Name
H1 Header Length
Field ID Name
15 Date, Settlement
16 Date, Conversion
73 Date, Action
Subfield Level
Selecting this population method allows you to edit subfields. Only fields that contain
subfields have this option available.
Field Properties
Field properties describe the attributes of the data. For instance, properties might include
exact matching on a field or only matching whether the field is present. You can view or
edit the field properties in either the Message Editor or the Field Editor.
Match Field
Selecting this property designates a field as a match criteria field.
Once you select matching, you can further specify whether to match a field’s Exact Value,
Field Presence, or Field Absence in the Field Editor. When matches occur, VTS-V.I.P.
evaluates all the values in the record for acceptable field edits and expected results of the
test.
Exact Value means this field is a match field, and the data from the incoming field should
exactly match the expected data.
EXAMPLE
In field 2 you expect a particular account number so you set field 2 for
Exact Value matching. Field 2 of the incoming message must contain
the expected account number for VTS-V.I.P. to accept a match on the
incoming message.
Field Presence and Field Absence simply mean that the selected field must be present or
absent in the incoming message in order for VTS-V.I.P. to accept the incoming message
as a match.
If a matching field does not match during a run, you are notified. You can terminate the
test run or continue even though there is a “No Match.”
Matching on a Valid Value field means that the field must be present in the message, no
matter what the value is. Matching on an omitted field indicates the field must be absent in
the incoming message.
NOTE: If no Match Fields are defined in the message, the message always matches
each incoming message. No mismatch occurs.
Validate Field
If selected, VTS-V.I.P. checks the content of this field for validity.
You can use Validate to perform exception testing by entering invalid data for the field.
Omit Field
Checking this option tells VTS-V.I.P. to omit a field from a test message.
Editing a Message
Use the Message Editor to edit a field or subfield. The Message Editor displays your
changes in bold.
3. You can change the name of the message by typing a new name in the Msg box, if
desired. You can enter up to 255 alphanumeric characters.
4. In the Case box, the Message Editor shows the name of the Case.
To change the name of a case, double-click or right-click the case name, or click
Properties under the case name in the main VTS-V.I.P. window.
In the upper right-hand corner the Message Editor shows the direction and Message
Type Indicator (MTI) of the selected message.
The Field No., Name, and MOC columns are unavailable for editing. The MOC field
shows the necessity of the field and is either Mandatory, Optional or Conditional. See
V.I.P. System BASE I Technical Specifications and the V.I.P. System SMS technical
specifications manuals for more information.
5. Double-click the Match column to select whether the field is set to Yes or No.
6. Double-click the Validate column to select whether the field is set to Yes or No.
7. Double-click the Omit column to select whether the field is set to Yes or No. If set to
Yes, VTS-V.I.P. omits this field from the test message.
8. If the Value column contains data, you can edit it directly or modify it in the Field
Editor. See the “Editing a Field” section for instructions on how to set the Population
Method to Literal.
9. To add a particular usage or change an existing usage for a particular field, right click
on the selected field and select "Add Usage" option from the menu. Select the
required usage from the "Choose Usage" dialog. If the field doesn't have any usage,
the "Add Usage" menu is disabled.
10. Under Display Options, click one of the following in the Show list:
All Fields—Displays all fields.
Business Case Defined—Displays only fields defined in the business function of the
Knowledgebase.
Fields Set for Matching—Displays only fields that contain a Yes in the Match
column.
Fields With Values—Displays only fields containing data (fields that contain a No in
the Omit column).
11. Click Show Headers And Bitmaps to display header fields and bitmaps at the
beginning of the field list.
You can use the following buttons in the Message Editor:
Click OK to save your changes in message content and return to the main VTS-V.I.P.
window.
Click Cancel to return to the main VTS-V.I.P. window without saving any changes.
Click Previous or Next to page forward or backward through the messages in all
cases.
Click Field Editor to edit the field in more detail. See the “Editing a Field” section for
more information.
Click Add Field to add a field from another message. See the “Adding a Field” section
for more information.
Click Print to print the contents of the message. See the “Printing Message Content”
section for more information.
Editing a Field
Use the Field Editor to access all possible options for a field and to quickly pull information
from other messages. The Field Editor shows some of the information from the Message
Editor and the Match, Validate, and Omit fields can be edited in either the Message Editor
or Field Editor.
The Field Editor displays your changes in bold.
The Field Editor shows the field ID, name, type, format, minimum length, and
maximum length of the selected message.
5. If the Population Method is set to Literal, you can enter the Value. The Position box
shows the position of your cursor in the Value box.
6. Under Population Method, click one of the following:
Literal—The data you are providing is in alphanumeric, alphanumeric/special
characters (commas, slashes, and dashes), numeric, or hexadecimal format.
Earlier Msg in this Case—VTS-V.I.P. populates the field with a field from an earlier
message in the same test case. Under Population Source, you can specify which field
in the Msg Name list.
Field in Previous Msg—VTS-V.I.P. populates the field from the previous message in
the same test case.
Field in Current Msg—VTS-V.I.P. populates the field with a field in the current
message. Under Population Source, you can specify which field in the Msg Name list.
Variable—VTS-V.I.P. uses a specified variable.
Valid Value—For incoming messages, VTS-V.I.P. checks the content for validity.
System Generated—For outgoing messages, VTS-V.I.P. generates a value.
Subfield Level—Choose if the field is a subfield.
7. If you copy from a field in an earlier, previous, or current message, click If Present to
populate this message field only if that field is present in that message.
8. Under Properties:
a. Click Match to specify the field for matching when you are running test cases.
If you click Match, select Exact Value, Field Presence or Field Absence from
the drop-down list.
b. Click Validate to have VTS-V.I.P. validate this field.
c. Click Omit to remove this field from the test message.
9. Under Population Source:
a. If the Population Method is set to Variable, this box is named Variable Name.
Select a variable from the drop-down list.
b. If the Population Method is set to copy from a field in an earlier, previous, or
current message, this box is named Msg Name. Select a message from the drop-
down list.
c. If the Population Method is set to copy from a field in an earlier, previous, or
current message, also select Field ID.
Click OK to save your changes and return to the Message Editor.
Click Cancel to return to the Message Editor without saving any changes.
Click Default to restore the default values. VTS-V.I.P. sets the values as defined in the
Knowledgebase.
2. Click Print.
Adding a Field
You can add or remove a field using this feature.
The Bitmap Editor shows the bit number and description of the selected field.
5. Double-click the On/Off column to set the field to On or Off.
6. Click OK to save your selections. VTS-V.I.P. converts your selections into a
hexadecimal string and places it in the Value box of the Field Editor and Message
Editor.
Click Cancel to return to the Field Editor without saving any changes. The
hexadecimal string value for the field remains unchanged.
4. Click Close.
You may have to change the test configuration setting so the appropriate fields are
present in the message. See “About Test Configuration” in
Chapter 4, Creating a Test, for more information.
6. In the Tag box, type a value or select one from the drop-down list.
7. In the Value box, type any value. You can choose between Hex and Text modes for
some fields, such as F123.3.
8. Click OK to save your selections. The TLV Editor automatically calculates the length
and formats the data into the appropriate TLV format. The result is displayed in the
Value field of the Field Editor.
Click Cancel to return to the Field Editor without saving any changes.
Test 1
Outgoing 0100 Request Msg 1 Outgoing 0100 Request Msg 1 Outgoing 0200 Request Msg 1
Incoming 0110 Response Msg 2 Incoming 0110 Response Msg 2 Outgoing 0200 Request Msg 2
Outgoing 0400 Request Msg 3
Incoming 0410 Response Msg 4
If no cases or messages were selected, VTS-V.I.P. would process all the messages in Test
1 in the following order:
2. Under Log ISO Messages, click Yes to log messages sent or received during test
execution in the main log file.
3. Under Run Control, click one of the following:
– 0 - Continuous Loop—VTS-V.I.P. will run all tests continuously.
– 1 - Repeat—VTS-V.I.P. will repeat all tests the number of times you specify. Also
type how many times you want to repeat the test in the Repeat text box.
– 2 - Run for Time—VTS-V.I.P. will run all tests for the amount of time you specify.
Also type values in the hour and minute boxes.
4. Under Stop On Error, click Yes to specify that VTS-V.I.P. stop running all tests when it
detects an error.
VTS-V.I.P. categorizes messages into Informational, Warning, and Fatal depending on
the severity of the error. If you select Stop On Error, during test execution VTS-V.I.P.
ignores Information and Warning messages and only stops on Fatal messages.
5. In the Wait For Start Line box, type an amount of time in milliseconds that VTS-V.I.P.
should try to start the communications line. If VTS-V.I.P. cannot start the line in this
time limit, it notifies you.
6. In the Wait For Stop Line box, type an amount of time in milliseconds that VTS-V.I.P.
should try to stop the communications line. If it cannot stop the line in this time limit, it
notifies you and brings the line to a forced stop.
7. In the Transaction Number box, type a value for VTS-V.I.P. to use for Field 11—
System Trace Audit Number and Field 37—Retrieval Reference Number. This
number is used to match messages in a transaction set. VTS-V.I.P. also increments
this number each time it sends an outgoing message.
8. Click OK.
Executing a Test
When you execute a test in VTS-V.I.P., it automatically starts the Communications
Handler, if it is not already running, and processes your test message. See Chapter 3 for
more information on the Communications Handler.
Before executing a test, you can choose any combination of cases or messages or both
to execute by pressing the SHIFT key or CTRL key while selecting cases and messages.
Use CTRL+A to select all messages.
When VTS-V.I.P. determines that an incoming message is unmatched, it asks whether you
want to continue running the test.
As VTS-V.I.P. runs your test, it opens a dialog box so you can see statistics during your
test run. You can also specify run control options and run the test again.
To execute a test:
1. Open a test and select a test case or cases.
2. Click the Execute Test toolbar button, or on the File menu, click Execute Test.
3. The Communications Handler starts, if it is not already running. Once the line is up,
the Test Execution dialog box appears.
The Test Execution dialog box shows the following statistics while the test runs:
●
Selected Cases—Shows the number of cases you have selected.
● Selected Msgs—Shows the number of messages you have selected.
●
Sent Total —Shows how many messages VTS-V.I.P. has sent.
●
Received Total—Shows how many messages VTS-V.I.P. has received.
● Received Unmatched—Shows how many unmatched messages VTS-V.I.P. has
received.
● Received Rejects—Shows how many rejected messages VTS-V.I.P. has received.
● Elapsed Loops—Indicates the number of times VTS-V.I.P. has run the test.
● Elapsed Time—Indicates how long the test has been running.
● Current Message—Shows the name of the incoming or outgoing message that VTS-
V.I.P. is processing.
● In Progress/Stopped—Displays a flashing “In Progress” while the test is executing
and shows the percentage of the test that has been completed. When the test has
stopped, displays “Stopped” and shows the percentage of the test completed before
VTS-V.I.P. stopped.
You can use the following buttons in the Test Execution dialog box:
Click Stop to terminate the current run.
Click Pause to temporarily stop test execution to correct message errors as they
occur.
Once the test has run, click Return to return to the main VTS-V.I.P. window.
You can also specify run control options and run the test again.
4. Click to select the duration of the test run as Continuous Loop, Repeat, or Run For
a specified amount of time.
5. Select the number of times to repeat the test or the amount of time to run it, and type
a value or click the arrows to select a value.
6. Click Log ISO to log messages in the main log.
7. Click Stop On Error to stop running the test when VTS-V.I.P. detects a Fatal error
message. It does not stop if it detects Informational or Warning error messages.
8. Click Continue On Mismatch to keep running the test when the incoming message
doesn’t match the expected result.
Case 1 Case 2
Field 39 = 00 Field 39 = 05
About Keys
The data contained in certain fields in a financial transaction message must be protected
against unauthorized access. An example of such data is the personal identification
number (PIN) of the cardholder. To provide security, such fields are encrypted using the
Data Encryption Standard (DES) algorithm. To encrypt data using DES, an encryption key
is required. The key is either an 8-byte (single DES) or a 16-byte (triple DES) binary value
that is normally expressed as 16 or 32 hexadecimal digits, respectively. The DES
algorithm accepts the clear (unencrypted) data item along with the key as input and
produces an encrypted data item and key as output. The DES algorithm will also accept
an encrypted data item and key as input and produce the clear data item as output. Thus,
provided that both the sender and receiver have the same key, sensitive data can
successfully be transmitted in a financial transaction.
In VTS-V.I.P., several different keys are maintained and used for encryption and
decryption. The so-called working keys, WK_1 or WK_2, are used to secure the
cardholder’s PIN. Through the Dynamic Key Exchange (DKE) Service, it is possible for a
new working key to be sent to an acquirer or issuer in an online message. Because this
new working key must itself be secure, it is encrypted using a key known as the Zone
Control Master Key (ZCMK). A Visa chip card message also contains encrypted fields
Field Description
Field Description
To enter keys:
1. On the View menu, click Preferences. The Preferences dialog box appears. Click the
Keys tab.
5. Click OK.
Also, you can use Export in the Log Viewer to save selected messages or the entire log
file as a text file or Microsoft Word file. To save only selected messages, press the CTRL
key to select the messages and then click Export.
You can also use the Log Comparison feature to accomplish this. See Chapter 11,
Automated Log Comparison for more information.
Drag the scroll bar on the right-hand side to view messages within the page. A page
contains about 150 log messages.
In Preferences, you set which types of messages to display in the Log Viewer. To
further narrow this selection, change the Log Viewer Options.
2. On the View menu, click Options. The Options dialog box appears.
3. Select the check boxes of the type of messages you want to display and click OK.
4. Customize your layout by selecting the column headings in the Column area.
You can use the following navigation buttons to move through the messages:
Click Next Page to go to the next page of the log.
5. Double-click a log entry to review details. The System Message dialog box appears.
6. Once you review the details, click OK to close the dialog box.
7. If you double-click an ISO log entry, the corresponding Incoming Message or
Outgoing Message dialog box appears in a format similar to the Message Editor.
If you selected Validate in the Message Editor for a field, the Incoming Message
dialog box displays any invalid values in red. To only display these invalid values,
select the Show Errors Only check box.
8. In the Incoming Message log window, select F55 Tag ID Matching if you need to
match the tag IDs in Field 55.
9. Once you review the details, click Close.
10. If you double-click the bitmap (BMP) fields (identifiable by pink icon) in an ISO log
entry, the corresponding Bitmap Settings dialog box appears. You can see which
fields are present (labeled “on”) in the message.
Printing Messages
You can print the contents of the messages in the Log Viewer or Raw Message Viewer.
To print messages:
1. Open the Log Viewer or Raw Message Viewer.
2. On the File menu, click Print.
Deleting Messages
You can delete all messages in the Log Viewer or Raw Message Viewer, or choose
particular messages based on date. In the Log Viewer, you can also delete multiple
messages by pressing the CTRL key while selecting the messages.
To delete messages:
1. Open the Log Viewer or Raw Message Viewer.
2. On the File menu, click Delete.
The Delete Log dialog box appears. (This example shows the Delete Log dialog box
in the Log Viewer.)
3. Choose to delete selected messages (in Log Viewer), all messages, or a range of
messages. You can only select a date that falls between the dates of the oldest and
newest log message.
4. Click OK.
Chip Card Reader Model EMV Level 1 Supports Supported in Supported in Supported in
Compliant Issuer Scripts Windows XP Windows Vista Windows 7
GemPC Twin
X X X X X
NOTE: The EMV Level 1-compliant chip card readers supported by VTS-V.I.P. have
been tested against Acquirer Device Validation (ADV) Tool Kit chip cards. Chip
cards not included in the ADV Tool Kit may not work as desired.
VTS-V.I.P. reads the Application Identifier (AID) from the chip card and checks its validity
against the values listed in Table 9–2.
A0000000032020 VPay
A0000000031010 Visa
A0000000032010 Electron
A0000000033010 Interlink
A0000000038010 PLUS
A0000000039010 Loyalty
A0000000041010 MasterCard
A0000000043060 Maestro
Issuer Authentication
Using a EMV Level 1-compliant chip card reader with VTS-V.I.P. enables you to validate
that you can support issuer authentication. In issuer authentication, the chip card confirms
that it is communicating with the valid issuer of the card.
VTS-V.I.P. acting as the acquirer generates a message to the issuer. The issuer receives
the authorization message and responds with a message containing the ARPC and
ARPC Response Code in field 139. VTS-V.I.P. receives the information, parses the ARPC
and ARPC Response Code, and forwards this data (via the EXTERNAL AUTHENTICATE
command) to the card where it is validated.
VTS-V.I.P. acting as the issuer generates the ARPC and ARPC Response Code and
sends them to the acquirer in the response message.
Issuer Scripts
Using a EMV Level 1-compliant chip card reader with VTS-V.I.P. also enables you to
validate that you can support issuer scripts. Issuer scripts are commands that allow the
issuer to change information on the chip card after the card has been issued. For
example, the issuer can rewrite or update a counter on the card to provide more restricted
usage. Issuer scripts are sent to the VSDC card in the response message.
When VTS-V.I.P. is acting as the issuer, it will send issuer scripts to the acquirer in the
response message (fields 55 and 142). This tests the acquirer’s ability to correctly accept
issuer script data in response messages and forward this information to the terminal.
VTS-V.I.P. supports the generation of only two issuer scripts, PUT DATA and UPDATE
RECORD.
When VTS-V.I.P. is acting as the acquirer it will receive the script in the response
message, act as the terminal to parse the issuer script data from fields 55 and 142 and
build issuer script commands, and send issuer script commands to the card via the card
reader. VTS-V.I.P. acting as the acquirer will accept any valid script from the issuer.
Table 9–3 shows the chip card fields, the source of the data, and which variable VTS-V.I.P.
uses.
Table 9–3: Source and Variables Used for Chip Card Fields (1 of 3)
Field 23—Card Sequence Number Chip card CARD SEQ NUM, Card Group
Field 130/F55 Tag 9F33—Terminal Terminal TERM CAP PROF, Acquirer Group
Capability Profile
Field 133/F55 Tag 9F1E—Terminal Terminal TERM SER NUM, Acquirer Group
Serial Number
Field 134.1/F55 Tag 9F10—Derivation Chip card VISA DISCRE DATA, Card Group
Key Index
Field 134.2/F55 Tag 9F10— Chip card VISA DISCRE DATA, Card Group
Cryptogram Version
Field 134.3/F55 Tag 9F10—Card Chip card VISA DISCRE DATA, Card Group
Verification Results (CVR)
Field 135/F55 Tag 9F10—Issuer Chip card ISS DISCRE DATA, Card Group
Discretionary Data
Table 9–3: Source and Variables Used for Chip Card Fields (2 of 3)
Field 137/F55 Tag 9F26—Application Chip card APPL TXN CNTR, Card Group
Transaction Counter
Field 138/F55 Tag 82—Application Chip card APPL INTRCHG PROF, Card
Interchange Profile Group
Field 146/F55 Tag 9A—Terminal Terminal TERM TXN DATE, Acquirer Group
Transaction Date
Table 9–3: Source and Variables Used for Chip Card Fields (3 of 3)
F55.21 Tag 9F6E – Form Factor Chip Card FORM FACTOR, Card Group
Indicator
User Interface
Due to a structure change in the format of Issuer Authentication Data (that is, F140 and
Tag 91 of F55) for VIS type of cards with CVN 18, there are a couple of setting changes in
the field editor to distinguish between a VIS type of cards between CVN 10/14 and CVN
18.
The CVN 10/14 cards still carry a fixed length of 10 bytes (8 bytes ARPC + 2 bytes Auth.
Response Code) of Issuer Authentication Data on F140 and Tag 91 of F55. However, the
CVN 18 cards have 4 bytes ARPC, 4 bytes CSU, and an optional 1-8 bytes of Proprietary
Authentication Data (PAD).
The following image shows the current field setting for VIS cards with CVN 10/14, which is
used in the current release (that is, prior to version 20). Note that F140.1 or F55.17.3
(ARPC) is at the top field level (no subfield).
The following image shows Field Editor setting/display on F140 for VIS cards with CVN
10/14.
The following image shows Field Editor setting/display on Tag 91 of F55 for VIS cards with
CVN 10/14.
The screen snapshot below is the current field setting for VIS cards with CVN 18. Note
that F140.1 or F55.17.3 (ARPC) is set at the subfield (has 2 subfields) level. These
subfields (see screen snapshot) contains ARPC VIS (4 bytes) and CSU (4 bytes).
NOTE: F140.3 or F55.17.5 (PAD) are being omitted since this is an optional field. If this
PAD subfield is un-omitted, F140.2 or F55.17.4 (ARPC RC) should be omitted.
Forget to omit or un-omit these subfields will result an incorrect length which will
be rejected by VCMS.
Currently, only F55.17.3 that can be set at subfield level which contains ARPC
VIS and CSU.
Field Editor setting/display on F140 for VIS cards with CVN 18:
Field Editor setting/display on Tag 91 of F55 for VIS cards with CVN 18:
Installing the Driver for the GemCore Keyboard USB Pro Cherry
You can install the driver from the Cherry Web site or from the VTS-V.I.P. CD.
To install the GemCore Keyboard USB Pro Cherry driver from the Web site:
1. Type the following in the address bar of your browser window, and press Enter:
http://www.cherrycorp.com/english/advanced-line/keyboard-smart-card-
home-banking-smartboard-g83-6733.htm
NOTE: The Cherry Web site may change from the screen shot shown here.
2. Drag the scroll box to view the bottom of the page and click Download software. The
Cherry Support Download dialog box appears.
3. In the product list, click SmartBoard, G83-6733 (if not already selected).
4. In the Operating System list, click Windows XP.
5. Click Next. The Software/Manual Download dialog box appears.
To install the GemCore Keyboard USB Pro Cherry driver from the CD:
1. Go to C:\Program Files\Vts3\Appl\Smart Card Driver.
2. Double-click SmartBoard_G83-6733.exe.
3. Follow the prompts to install the driver.
For more information, you can visit the manufacturer web sites.
● For the Castles EZPROX:
http://www.castech.com.tw/en/in-products-
03.aspx?id=P_00000039&cid=C_00000010&pname=EZPROX&cname=Contactless
+Reader
● For the Magtek:
http://www.magtek.com/support/software/programming_tools/drivers/
usb_hid_swipe.asp
For your convenience, VTS-V.I.P. has all of the above setup files included in the install
program and is available at the following directory:
C:\Program Files\Vts3\Appl\Magtek
2. Select the subfolders based on the Operating System installed in your workstation.
3. Right-click MTHIDSR.inf, the setup file, and run Install.
This install will take a fraction of a second.
4. For Windows XP Double-click MTHIDCFG.exe.
For Windows Vista right click MTHIDCFG.exe and run as administrator.
5. Select the lowest available COM port from the HID Swipe Reader List box (in this
case COM5).
6. Click OK.
4. Click Finish.
c. Choose the VivoTech 5000 Visa TTQ parameters you want, then click OK.
The L5000 series, like all Equinox customer-activated terminals, seamlessly integrates
with the vast majority of electronic cash registers used by large-scale retailers throughout
the U.S. This terminal offers modular Contactless Reader, Signature Capture, PIN entry
etc. The NFC reader also works with Google Wallet, ISIS and so forth.
To verify successful installation, please attach the Equinox terminal to the system. A
new registry entry "\Device\thcdcacm0" should be listed under
"HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM".
2. FPE Interface Driver Installation
The Equinox Forms Processing Engine (FPE) Server is an in-proc COM server that
communicates to the Equinox Serial Server or Equinox TCP/IP Server and provides
API to drive Equinox Multi-Lane terminals. This driver is required to enable
communication between the terminal and the VTS application.
Install the Equinox FPE Interface driver from the VTS Install directory path. For ex:
"C:\Program Files (x86)\Vts3\Appl\Equinox\FPE Interface\ FPEInterfaceSetup.EXE".
3. Sentinel Driver Installation
This driver provides licensing encryption for applications that use Sentinel Keys.
Install the Sentinel System driver from the VTS Install directory path. For ex:
"C:\Program Files (x86)\Vts3\Appl\Equinox\Sentinel System Driver\Sentinel System
Driver.EXE".
2. Open an acquirer variables group and modify the variables to be sent to the card.
3. Open a card variables group.
4. Select a card reader from the Card Reader Attached drop down menu. VTS-V.I.P.
supports contactless, chip card, and magstripe.
5. Click Read Card. The Select Acquirer Group dialog box appears.
6. Select the acquirer group you previously modified. VTS-V.I.P. uses the variables in
this group as terminal input data.
7. This step is for chip cards only. If the card has multiple applications, the Select ICC
Application dialog box appears.
8. Select which card application to use. VTS-V.I.P. reads the card and inserts the data in
the card variables group.
9. On the File menu, click Save As to save the card data in a new variables group.
10. On the File menu, click Exit to close the Variables Manager.
This procedure describes how to designate a variables group for a test case. You can also
designate a variables group for an entire test (in the Test Properties dialog box), which will
designate it for all cases in that test. For more information, see the “Designating a
Variables Group for the Test Case” section in Chapter 5, Using Variables.
4. Click OK to save your selections. VTS-V.I.P. adds the card fields to the message and
the main VTS-V.I.P. window appears.
5. Check that you have defined the VSDC_MDK keys for properly encrypting and
decrypting the ARQC and ARPC. See Chapter 7, Running a Test, for more
information on entering keys.
6. Click Properties under the case name. The Case Properties dialog box appears on
the right-hand side of the screen.
7. Under Variable Groups to Use, select the card variables group used to save the card
values from the drop-down list.
Next, run the test as described in “Executing a Test” in Chapter 7. When you run the test,
VTS-V.I.P. uses the values in this card variables group which are saved from the card.
4. Click OK to save your selections. VTS-V.I.P. adds the card fields to the message and
the main VTS-V.I.P. window appears.
5. Click Properties under the case name. The Case Properties dialog box appears on
the right-hand side of the screen.
7. Click OK.
Next, run the test as described in the “Executing a Test” section in Chapter 7. When you
run the test, VTS-V.I.P. attempts to connect to the card reader. If successful, all test case
properties are saved.
When you import a test, you can select which components to import, depending on which
were included in the export file.
Exporting Files
The following section describes how to create an export file. You must first open the test
you want to export, otherwise the export menu is unavailable.
When you create an export file, it automatically contains the test configuration database.
– ISO Log—If you select this option in Preferences, Test Execution tab, VTS-V.I.P.
logs the ISO messages sent or received during test execution. If selected, VTS-
V.I.P. saves this file with the same name as the test.
– Variables Database—This is the Variables Manager database associated
with the test.
4. Type the name of the file in the Export File box, or click Browse to select the export
file name and path.
5. Click OK. VTS-V.I.P. creates the export file. When finished, an Export Complete
message appears.
Importing Files
The following section describes how to import a file. The test should already be saved
using the Export feature in VTS-V.I.P.
2. Click Browse to select the exported file in the Archive (.zip) File Name box.
3. When you identify and select the file, VTS-V.I.P. shows which components exist in the
exported file by automatically selecting those check boxes. If you do not want to
include a component, clear the check box.
4. Click OK.
5. A message box asks if you want to save changes. Click Yes.
6. The Save As dialog appears. Select a location for your file and click Save. VTS-V.I.P.
imports the file.
Introduction . . . . . . . . . . . . . . . . . . . . . . . .11–1
Introduction
Automated Log Comparison provides a very fast and accurate means of detecting
differences in test results, giving users, developers, QA analysts, regional certifiers, and
members better productivity. Testing efforts are simplified by providing an automated
comparison of member logs run prior to and after member host changes are introduced.
To exclude fields:
1. From the Tools menu, select Options.
3. In the Exclude area, click to select the fields you want to exclude from the log
comparison. Enter the location where you want the file saved.
4. Click Apply and then click OK to close the Options dialog.
Once you have selected the fields you want excluded, you are ready to compare log files.
2. The log comparison function executes. When finished, a Log Comparison Completed
message appears.
Acquirer Host
VCMS Loopback
Response Request
Request
Response
If you plan to test VTS-V.I.P. with the VisaNet Certification Management Service (VCMS),
it offers the following loopback modes:
● Local Loopback—Routes messages to and from the member host using the VTS-
V.I.P. test port connection to the VAP without a connection to the VCMS test system.
Local Loopback uses communications interfaces that are identical to those used for
online VCMS testing.
●
VisaNet Loopback—Routes messages to and from VTS-V.I.P. and the member host
through the VAP and VCMS test systems. VisaNet Loopback mode provides a
simulation of a complete V.I.P. processing cycle.
●
None—Routes messages to and from the member's host to either another member's
host, or a Visa certification lab. Because VTS-V.I.P. is not in the routing path for this
loopback mode, it prohibits test execution until the loopback mode is changed to
either Local Loopback or VisaNet Loopback.
For Windows XP or Windows Vista, the member line uses TCP/IP.
The test port line from VTS-V.I.P. to the VAP uses the TCP/IP protocol, and the VCMS line
connected to the VAP uses the IP protocol. These VCMS testing protocols are shown in
Figure 12–2.
VCMS
VIC
CR Message Processing
Whenever a connection to a VAP goes to Up status, the VAP sends a Connection Report
(CR) message. This CR message contains information regarding the station IDs identified
in the VAP configuration.
Using the station IDs, VCMS establishes station pairing between the member host and
VTS-V.I.P. This is further explained in the “Station Pairing” section.
When logging into VCMS, you can choose whether to pair two credit stations for BASE I
testing or to pair a MIS and CAS station for SMS testing.
If you select the credit station ID for VTS-V.I.P., it automatically inserts a credit station ID
for the member host. If you select a CAS station ID for VTS-V.I.P., it automatically inserts a
MIS station ID for the member host.
You can override these automatic selections by editing the partner station ID.
Station Pairing
This section describes how the V.I.P. System matches and routes messages to their
proper destinations, and how VTS-V.I.P. accomplishes this through station pairing.
The V.I.P. System compares information in key data fields to match messages within a
transaction. These messages include the original request, original response, and any
subsequent messages. For instance, the Retrieval Reference Number (Field 37) is a key
data element for matching a message to others within a given transaction set. The
reference number must be the same for all messages in the set.
As well as matching messages, the V.I.P. System routes requests to their proper
destination. Usually V.I.P. routes requests based on the account number in the message.
The issuer associates each issuer BIN (a range of card numbers for a specific card
program, such as Visa Classic) with a specific issuer processing center.
In some cases, V.I.P. uses data other than the account number to determine message
routing. Also, issuers can control which processing center receives requests for their
cardholders by designating multiple processing centers and specifying the types of
transactions that should be routed to each processing center.
A single processing center can have any number of physical network stations, based on
volume and business needs. Network stations send a sign-on message (0800) to V.I.P. to
notify it when they are available to send and receive messages.
In the test environment, messages cannot be matched and routed in this manner; instead,
VCMS establishes station pairing between the member host and VTS-V.I.P. so traffic from
one station always goes to the other station.
Just as network stations notify V.I.P. that they are available by sending a sign-on
message, a network station has to sign on and sign off when connecting to and
disconnecting from VCMS.
When switching to VisaNet Loopback mode, VTS-V.I.P. sends a sign-on message (0800)
that contains the station IDs of the member host and VTS-V.I.P. It inserts the station IDs
into Header Field 5—Destination Station ID and Header Field 6—Source Station ID. Once
VCMS receives this 0800 message, it pairs together the two network stations and routes
subsequent messages according to that pairing.
Table 12–1 shows how this loopback query works depending on which mode you select in
VTS-V.I.P. and the current loopback mode of the VAP.
Current Loopback Mode Desired Loopback Mode How Loopback Query Works
IMPORTANT
It is strongly recommended that you always exit in Local Mode to
avoid having to manually set the mode on the VAP.
2. In the CR Msg Timeout box, type the amount of time VTS-V.I.P. will wait for a CR
(Connection Report) message to be sent from the VAP. Once this time limit is
exceeded, it automatically stops and restarts the line in order to “force” the VAP to
send a CR message. If the VAP still does not send a CR message, you will receive an
error message.
3. VTS-V.I.P. inserts a default value into the IPC Timeout box. The Inter-Process Call
(IPC) is used by the name pipes between the Communications Handler and VTS-V.I.P.
to delay sending or receiving messages. You only need to change this value because
of the speed of the hardware on which VTS-V.I.P. is installed.
4. In the SignOn/Off Reply Timeout box, type the amount of time VTS-V.I.P. should wait
for an 0810 response to the 0800 sign-on request sent as a result of the VCMS logon
process.
5. In the Wait For VIC box, type the amount of time to wait for the line from the VAP to
the VIC to brought up.
6. In the Start/Stop Line Timeout box, type the amount of time to start or stop the line to
the VAP.
7. In the Loopback Mode Timeout box, type the amount of time to query or change the
loopback mode on the VAP.
8. Click OK.
Logging On to VCMS
This section describes how to log on to VCMS.
IMPORTANT
It is strongly recommended that you always exit in Local Mode to
avoid having to manually set the mode on the VAP.
1. Click the Login to VCMS toolbar button, or on the Tools menu, click VCMS Login.
2. VTS-V.I.P. sends a remote shell command to query the loopback mode status. In the
Loopback Mode box, it displays None, Local, or VisaNet.
Click Query if VTS-V.I.P. does not automatically query the loopback mode.
To change the loopback mode, by clicking None, Local or VisaNet, see Table 12–1
for a description of what VTS-V.I.P. will do, based on the current loopback mode.
3. Under Stations IDs, the VTS-V.I.P. drop-down list displays the three VTS-V.I.P. station
IDs as defined by the VAP. Select one.
4. After you select a station ID, VTS-V.I.P. automatically selects the corresponding
member host’s station ID, which appears in the Member Host drop-down list.
5. If you want to change any station IDs, click Edit. The Edit Partner Station ID dialog
box appears.
Visa Test System and Member Host station IDs that need to be paired can be added here.
Clicking OK will save any changes made in this dialog box.
To pair two station IDs, users can click the Pair button. Then the paired station IDs are
displayed in the Station Paired box. The paired station can be depaired by selecting the
pair and clicking Depair.
Users may also choose either Automatic Depair on Exit, or Prompt for Depairing on Exit. If
users select Prompt for Depairing on Exit, the Depair confirmation box appears, as shown
in the following figure. The Close button is provided to exit the EAS dialog box.
When your connection is up, the Communication Handler SMC menu and tool bars
will be enabled in the VTS tool.
Setting up Stunnel
Stunnel is a third-party open source application that you can use to encrypt your TCP
communications. You will find the application for download, as well as all Stunnel
documentation, at http://www.stunnel.org/ or http://www.openssl.org/.
Editing SMC Message: To edit the SMC messages please click the SMC
Edit menu
Edit LogOn Msg Edit Logon Message is used to modify the following
fields :
1. TransCodeIdentifier
2. MessageIndicators
3. OriginatorID
4. TransmissionDateAndTime
5. UserID
6. UserPassword
7. ResponseCode
Edit logoff Msg Edit Logoff Message is used to modify the following
fields :
1. TransCodeIdentifier
2. MessageIndicators
3. OriginatorID
4. TransmissionDateAndTime
5. ResponseCode
Edit HeartBeat Msg Edit HeartBeat Message is used to modify the following
fields :
1. TransCodeIdentifier
2. MessageIndicators
3. OriginatorID
4. TransmissionDateAndTime
5. ResponseCode
Edit Shutdown Msg Edit Shutdown Message is used to modify the following
fields :
1. TransCodeIdentifier
2. MessageIndicators
3. OriginatorID
4. TransmissionDateAndTime
5. ResponseCode
6. ShutdownTimeout
2. Click toolbar button Add Fields or on the edit menu, click Message AddFields.
NOTE: When you select any message, Add Fields button will be enabled.
3. The Select Fields dialog box appears with all ISO fields as shown in Figure 14–3.
4. After retrieving all data, the Select Fields dialog box appears with all not omitted ISO
fields of messages as shown in Figure 15–3.
10. Click the Yes button to open the script (excel) file or No to close.
This script (excel) file contains following transaction details:
●
Case #: Case number
● MTI: MTI of the Case
● Test Description: Description of the message
● Selected Fields (From 'Select Fields' dialog): Field value of the outgoing message.
● Comments
I M
importing a test, 10–3 magstripe card reader, 9–1, 9–17, 9–19
Incoming Message dialog box, 8–5 main
informational messages, 8–2 toolbar, 2–6
inserting a message delay, 4–20 window display, 2–5
installing match probability, 7–7
chip card reader software, 9–12 matching fields, 6–5
prerequisites, 2–1 Matching on a Valid Value, 6–5
VTS-V.I.P., 2–4 Message Editor
Intra-Country Data (field 118), 4–16 populating fields, 6–2
invalid values, 8–5 using, 6–5
ISO messages, 8–2 message format
issuer authentication, 9–4 hexadecimal, 6–14
issuer scripts, 9–5 other, 1–3
test configuration setting, 4–11, 4–16
K Message Type Indicator (MTI), 4–3
keys messages
description of, 7–8 Connection Report (CR), 12–3
setting, 7–11 deleting, 6–10
Knowledgebase deleting from Log Viewer, 8–10
description of, 2–3, 4–3 deleting from Raw Message Viewer, 8–10
display, 2–5, 4–3 editing, 6–5
Endpoint Session (ES), 12–5
L
Heart Beat, 12–5
limitations inserting a delay, 4–20
of VTS-V.I.P., 1–13 overview, 8–1
literal data, 6–2 printing, 6–10
Local Loopback mode printing from Log Viewer, 8–10
changing, 12–5 printing from Raw Message Viewer, 8–10
defined, 1–9, 12–2 processing order, 7–1
log comparison, automated, 11–1 saving as a Word document, 8–3
Log Server icon, 2–5 sources, 8–2
Log Viewer Time Broadcast (TB), 12–5
deleting messages, 8–10 Time Query (TQ), 12–5
displaying invalid values, 8–5 values for outgoing, 6–3
printing, 8–10 Microsoft Smart Card Manager components, verifying,
setting filters, 8–2 9–13, 9–16
toolbar, 8–2 modem
using, 8–2 dial-up, 3–10
viewing bitmap, 8–6 null, 3–6
logging on to VisaNet Certification Management Service modem eliminator
(VCMS), 12–8 configuring, 3–13
loopback mode recommended settings, 3–14
changing, 12–5 sample settings, 3–14
defined, 1–9, 12–2 modifying
none, 1–10, 12–2 messages, 6–5
user-defined variables, 5–21
variables, 5–14
multicurrency processing, 1–13
Multicurrency Service, 4–11, 4–16
Dynamic Key Exchange (DKE) Service, 7–9 saving as a Word document, 4–7
Full Authorization Service, 4–11, 4–16 setting preferences, 7–3
Multicurrency Service, 4–11, 4–16 structure, 4–1
National Net Settlement Service, 4–11, 4–16 using a user-defined variable, 5–23
special account numbers, 4–11, 4–17 validation code, 1–5
VisaNet Certification Management Service (VCMS), Visa-supplied, 4–7
1–1, 12–1 test configuration
setting 3rd Bitmap Expanded, 4–9
default variables group, 5–16 3rd Bitmap Fields, 4–9
Log Viewer filters, 8–2 Address Verification Service (AVS), 4–9
match probability, 7–7 bypass VCMS stations, 4–9
RAS phone book, 3–8 Card Verification Value (CVV) Service, 4–10
test execution preferences, 7–3 changing, 4–19
variables group for a test case, 5–24 Currency Precision Service, 4–10
variables group for an entire test, 4–5 Custom Payment Service (CPS), 4–10
VCMS logon preferences, 12–6 description of, 4–8
working keys, 7–11 field 118, 4–11
signons, viewing, 2–11 field 55, 4–10
sorting columns in Variables Manager, 5–2 field 59, 4–10
sources of messages, 8–2 field 62, 4–10
special account numbers, 4–11, 4–17 Full Authorization Service, 4–11
starting VTS-V.I.P., 2–4 message format setting, 4–11
station pairing, 12–4 Multicurrency Service, 4–11
steps to using VTS-V.I.P., 2–13 National Net Settlement Service, 4–11
subfields Network ID, 4–12
editing, 6–4 special account numbers, 4–11
support, for VTS-V.I.P., 1–13 Test Execution dialog box, 7–5
supported chip card readers, 9–2 Test Properties dialog box
system adding a test description, 4–6
changes, 2–4 setting match probability, 7–7
components, 1–4, 2–3 test properties, editing, 4–5
messages, 8–2 testing
requirements, 2–2 basic steps, 2–13
System Generated, 6–3 environments, 1–1
offline, with direct connection, 1–5
T
offline, with VAP, 1–8
TCP/IP online certification, 1–11
direct protocols, 3–5 online, with VCMS, 1–9 to 12–2
LAN protocols, 3–3 Time Broadcast (TB) message, 12–5
modem protocols, 3–10 Time Query (TQ) message, 12–5
protocols, overview, 3–3 TLV Editor, 6–15
test toolbar
case, adding, 4–7 in main window, 2–6
creating, 4–3 Log Viewer, 8–2
description, adding, 4–5 Variables Manager, 5–11
export file, 10–2 Transaction ID, 1–5
import file, 10–3
processing order of messages, 7–1
resume running, 1–2, 7–2, 7–4
running, 7–4