THE INSTALLATION MEDIA AND THE INFORMATION FURNISHED HEREIN BY VISA ARE CONFIDENTIAL, AND

ARE DISTRIBUTED TO VISA MEMBERS, THEIR MERCHANTS, AND AGENTS FOR THEIR EXCLUSIVE USE IN
PARTICIPATING IN VISA SPONSORED PROGRAMS, AND SHALL NOT BE DUPLICATED, PUBLISHED, OR
DISCLOSED IN WHOLE OR IN PART, OR USED FOR OTHER PURPOSES, WITHOUT PRIOR WRITTEN
PERMISSION FROM VISA.

COPYRIGHT (C) VISA INC. 1992 - 2017 ALL RIGHTS RESERVED

NOTE: A user must have administrative rights on the target PC in order to install the PC Edit Package for
Windows.

This readme file contains these sections:

SECTION 1 What's New

SECTION 2 Important Considerations
SECTION 3 Complete/Verify the Install
SECTION 4 Corrections to the Users Guide
SECTION 5 Required Software Third-Party Vendors

SECTION 1. What's New

1.1. This release contains the following enhancements
1.1.1. April 2017 Business Release

RTN Description
Visa Claims Resolution will replace the existing exception processing/dispute resolution process at
RTN 820157 Visa. This portion of the VCR project is to update the chargeback, representment and associated
VCR Enhancement CC#3 reversal messages in VisaNet to support the transfer of liability for the Visa Claims Resolution
process
RTN 822577
Global B2B Virtual Visa will introduce a new Global B2B Virtual Payments Program with a unique interchange rate for
Payments Program wholesale, invoice based spend that utilize virtual accounts
Product ID
RTN 820313 The Visa Multinational Merchant Acceptance Program (VMMAP) is intended to enable select,
Visa Multinational enrolled acquirers to transact and qualify for domestic, regional and inter-regional processing
Merchant Acceptance based solely on merchant/issuer jurisdiction. This is basically extending the International Airline
Program CC #12 Program (IAP) to other merchant categories but only for select, enrolled acquirers.
RTN 820521 The Payment Account Reference (PAR) value is to allow clients, primarily merchants/acquirers to
PAR Capture and Clearing replace the PAN with the PAR for the purposes of storing and other internal merchant/acquirer
CC#01 processes
As part of The Visa Rules rewrite and in response to a broader merchant market issue, Visa needs
to expand the T&E special authorization procedures to allow additional merchants the capability of
RTN 821427 utilizing incremental and estimated authorization processing. The expansion will include rental
Expand Incremented merchants whose business has an unknown final purchase amount (such as truck rental, motor
Authorization home rentals, bike rentals, and equipment rental) and entertainment merchants who can use
incremental processing to offer new innovative payment options to their customers (such as
amusement parks, bars, campgrounds, and restaurants).
Issuers are not currently getting token requestor ID (TRID) in the clearing and settlement data. As
number of token requestors is increasing rapidly, issuers are having difficulties with reporting and
RTN 820521
billing of the token transactions (by token requestor) processed and they are not able to link
Visa Token Vault (VTV)
original auth transactions with clearing and settlement data. Issuers would like Visa to populate
Backlog VBAK092
token requestor ID in clearing and settlement data that helps them in reporting token transactions
(by token requestor) processed correctly.
 This change will implement modifications to domestic AFTs for US only transactions.

1. Allow BAI = BI for AFT original and reversal for US domestic Visa cards with MCC =
RTN 821459 6012 only. AFTs sent with BAI = BI and MCC <> 6012 should be rejected by Edit
CC#3&6 Visa Message Set Package process. (CC#3)
Enhancements
2. Allow BAI = AA, PP, BI, TU and WT for AFT original and reversal for US domestic Visa
cards. AFTs sent with any other BAI should be rejected by Edit Package process.
(CC#6)
Visa Direct is a global service that allows cross border and domestic money transfers to a Visa
debit, credit, or reloadable prepaid card account utilizing the push payment capability of the Visa
payment system. Either AFT or OCTs can be used to move the money between accounts. This
project addresses OCTs only.
RTN 822117
Ph#2 Validate OCT For Phase 1 (October 2016), changes were implemented worldwide to mandate that OCT
Originator Approval (PIF) originators complete the PIF and its associated attestations. OCT originators that have not
completed the PIF and submitted it to Visa will not be allowed to send OCTs BII.

For Phase 2 an edit will be implemented to check for valid Business Application ID (BAI) values
and obsolete BAI code will be cleaned up
This RTN enables the growth of Visa Direct in Canada beyond its current focus on money transfer.

RTN 822545 Support new use cases, and interchange structural changes in support of Canada domestic
Visa Direct CANADA original credit and account funding pricing. Additional improvements in support of domestic
processing of original credit and account funding transactions will further accelerate customer
adoption of Visa Direct.
Dynamic Currency Conversion (DCC) is an optional Non-Visa service offered by merchants at the
point of sale. This service involves offering the cardholder the option to pay for goods or services in
their own billing currency or in the merchants own local currency. DCC occurs when the merchant
performs currency conversion locally and submits the transaction in the Cardholders billing
currency. The merchant must be registered to perform currency conversion.

For the initial implementation (Phase 1) for this project a new Dynamic Currency Conversion
(DCC) Indicator instituted Worldwide for BASE II and SMS originated transactions. This was
implemented on April 15, 2011.

For the second implementation (Phase 2) for this RTN, the DCC Indicator was allowed on
exception items, Chargebacks and Representments. Edit Package started to reject transactions
RTN 822196 that are submitted with invalid values in the DCC Indicator field. This was implemented on October
Dynamic Currency 15, 2011.
Conversion Indicator
(EU17326) The VE Region was not participating, however there was no systematic blocking to prevent them
from receiving the DCC Indicator value.

Dynamic Currency Conversion occurs when the transaction amount is converted from merchants
pricing currency to the cardholder billing currency prior to submission of the transaction for
authorization.

Visa Europe supports DCC at POS and ATM. VE Acquirers are required to register with Visa
Europe and complete a certification process prior to performing DCC services. This project will
mandate that
VE acquirers set the DCC indicator on transactions where DCC is performed. This indicator will be
used to assess a new DCC fee payable by acquirer to issuer. The fee will be applicable to all intra-
VE ATM transactions.

1.1.2. Important Notes

Edit Package endpoints using Windows XP or Windows Server 2003 must upgrade to a supported operating
system. Effective with the April 2016 Business Enhancements Release, Edit Package will not operate using the
mentioned OS. Section 1 of Edit Package Operations Guide contains the list of supported OS.
 1.1.3. New features and enhancements

ALM Areas of Effective

ALM Description Description of Enhancement Incident ID
ID Impact Immediately
185 Edit Package User Code has been added to automate this process
Interface hangs and will
PC INC000004903633 Immediate
not start after a read error
of the applMiscInfo.xml file
77 Data Entry Source Amount Modified code to disable selecting Error
168 being increased by 100% Message tree view entries PC
INC000002827292
and values from one Data Immediate
INC000004916681
transaction being copied Entry
to another
187 Fix TIU-027 - Outgoing Added code to where the Update About Log is
Edit Run window will not being called to catch all exceptions and write the
PBI000000101551
display because of an exception information to the OPERLOG.TXT file PC Immediate
INC000004022820
exception in the update for further research
About Log process
188 Operator ID Setup window Modified code to not allow last ID with option to
is allowing all Operator perform Operator ID Setup to be saved with the
IDs to be defined with option turned off, at least one is required PC Immediate
option to perform Operator
ID Setup to be disabled
189 Run mode / File mode Modified message to a more understandable
mismatch message not version indicating that the run mode for EP does PC Immediate
clear not match the run code of the file being added
190 Starting the Edit Package Modified the message to say that the Edit
UI can display a Socket Package Service needs to be started and then
Exception message and it try starting the Edit Package UI again PC Immediate
is unclear what the issue
is and how to resolve it
185 Client experiencing slow Code was modified to allow the response
response issues when message to be recognized in a more timely
PC Immediate
starting Edit Package UI manner
or switching Bins
191 Client was trying to create Updated code to display Folder xxx not found,
a Secure EA and getting a so clients does not think it is a dataset not found
message that dataset not issue PC Immediate
found when it should have
said folder not found
192 EP Support getting emails Updated the Table Update RC=6 message to be
asking for guidance when more meaningful
PC INC000004917968 Immediate
Table Update generates
RC=6 Message
193 DEX File Transfer stops Modified code to close file reader
working with file in use by PC INC000005045121 Immediate
another process error
194 Collect Batch utility will not Added code to show users what file contains
start due to WTF files that bad data and give them the option to rename it
PC Immediate
contain bad data to filename. BAD and continue processing or
stop processing
195 Batch Facility was not Code was added to use the future date from
using future date from data entry release selection for creating list of PC
data entry release tables available for extract / report processing Batch Immediate
selection for list of tables for Batch Facility Facility
for extracts / reports
196 FTPS Tool for EA File Integrated TIU-028 into April 2017 BER
PC Immediate
Transfer (TIU-028)

SECTION 2. Important Considerations

2.1. Directory naming convention restrictions
 Directory names cannot contain embedded spaces for any directory used in the EP environment. This is because
EP directory names are passed in command line parameters, and spaces are delimiters. Additionally the length of
the Directory name and the files in it cannot exceed 64 characters.
2.2. Additional documentation
Features of the PC Edit Package for Windows are documented in the User's Guide, Online Help and this README
file.
2.3. Multi-user configuration
Multi-user configuration requires specific install procedures found in Appendix C of the Windows Users Guide.
2.4. Network delay
If the Processor BIN data directory is on a network drive and not a local hard-drive, the user should expect longer
run times for incoming and outgoing processing. For fastest processing, put all data directories on the local PC in
the case of a single user.
2.5. EPWIN400.exe.config
This control file contains several user defined parameters. Some of the parameters in this file can be changed
through the Settings Menu Item on the Main Edit Package Window. These parameters are defined in Appendix A of
the User's Guide.
2.6. PCEP Windows help
The Edit Package Online Help has not been updated for Version 4.00. The latest documentation can be found in the
Users Guide.
The Edit Package help file contains links to the BASE II Clearing manuals that are in PDF format. The links to the
PDF manuals will work only if the PC on which Edit Package is installed also has Microsoft Windows Scripting Host
(WSH) installed. If WSH is not installed, the manuals can be viewed by navigating to the EP40 folder on the local PC
and double clicking the desired PDF file. WSH is bundled with all versions of Windows supported by the Edit
Package as well as all versions of Internet Explorer version 3 or greater.
2.7. PCEP Windows and incompatible software
When using mouse enhancement software from TV4Studios, the EPNG Menu bar would not respond to the mouse
clicks. Please do not use MImpPRO.EXE with EP40.
2.8. Supported Windows Operating Systems
PCEP 4.00.xxxx is supported on desktop OS versions only, not on server OS versions.
Running the PC Edit Package for Windows version 4.00.xxxx on unsupported operating systems may give
unpredictable results. For further details on the supported operating systems, pls. refer to Section 1.1.1. Supported
Platforms and Operating Systems of Edit Package Release 4 Operations Guide.

SECTION 3. Complete/Verify the Install

Verify that the following files exist in each of your BIN folders - \EP40\C999999 (where 999999 is the BIN number):

temp.opts.txt

Verify that the following files exist in each of your BIN workspace folders - \EP40\C999999\WORKSPACE (where
999999 is the BIN number):

DEXSFILE.INF
ep.history
ep.history.bkupa
ep.history.bkupb
PERM.ENV.OPTS.TXT
TEMP.ENV.OPTS.TXT
 PERM.TABLE.OVERRIDES.TXT
TEMP.TABLE.OVERRIDES.TXT

If any of the above files are not present in the BIN folders, copy these files from the \EP40\ folder to each of your
BIN folders.

To verify a successful installation, sign on to the PC Edit Package. From the Menu, click on Help and then click on
About the PC Edit Package: The about.log report should show the following information:

In the middle of the report:

Edit Package 4.0 Service installed successfully

--------

Current Edit Package Information

EPWIN400 Version - 4.0.17.0 - Date - 3/9/2017 10:24:54 AM

BPBatch Version - 4.0.17.0 - Date - 3/9/2017 10:24:50 AM
EPZOS Version - 4.0.17.1 - Date - 4/6/2017 1:17:36 PM
EPTBLUPD Version - 4.0.12.0 - Date - 12/2/2016 8:17:42 AM
EPTBLSPT Version - 4.0.10.1 - Date - 12/2/2016 8:17:50 AM

If this message is not displayed, there may be a problem with the install. Copy the epinst.log.txt file from your install
folder before contacting Visa for support.

SECTION 4. Corrections to the Users Guide

None

SECTION 5. Required Software Third-Party Vendors

5.1. Direct Exchange file transfer
Requires the Xygate Software CD for the Key, License and Executable.

The Xygate/FE application will need to be acquired in order to utilize Direct Exchange. Contact your VISA member
representative. Instructions for setting up Direct Exchange are defined in Section 5 of Appendix A.

5.2. National Language support (NLS)

Provides conversion between EBCDIC and ASCII for Merchant Name and/or Merchant Location for:

1 KANJI (Japanese Double Byte) - Merchant Name

2 HANGUL (South Korean Double Byte) - Merchant Name/Location

Microsoft Host Integration Server 2010 is required to be able to utilize the double-byte character Set (DBCS) feature.
Once the Host Integration Server 2010 software is installed, the user will be able to perform both Kanji and South
Korean DCBS conversions.

If Host Integration Server is not installed and draft transactions that include TCR 2 records for Japan (country code
JP) or South Korea (country code KR) are processed in an Incoming or Outgoing run it will fail with a return code of
16 with a message that NLS conversion failed

5.3 Adobe Reader

The BASE II Clearing manuals are installed from the CD in PDF format. Adobe Reader is required to read the
manuals.
FTPS Client
A secure FTPS client that supports a scripting interface and complies with RFC 4217 must be selected in order to
implement secure file transfers. Other software may be required by the FTPS vendor.

For EA File Transfers a FTPS Tool created and supported by Visa can be used. The software can be found in the
EP40\FTPS_TOOL\EPFTPSClient-0.2 folder, the following are instructions on how to use the tool

1. If you have not already done so create a Secure EA Interface (Chapter 11.8.1 of the BASE II Clearing
PC Edit Package for Windows (Release 4.0) User's Guide), the FTP ExecuNon Path must be set to the
folder to EP40\FTPS_TOOL\EPFTPSClient-0.2
2. Update the FILETRANSFER.TXT le in the EP40\WORKSPACE folder, nd the [FTPS-JCL] secNon and
update the set CP line and the java line to call the FTPS UNlity les

[FTPS-JCL]
*the string " >goftp.log 2>&1" is required or EP will think the file transfer failed
set CP=<FTPexePath>\EPFTPSClient.jar;<FTPexePath>\commons-cli-1.3.1.jar;<FTPexePath>\commons-net-3.5.jar;<FTPexePath>\log4j-1.2.17.jar
java -cp %CP% com.visa.eas.ftpsclient.EPFTPSClient -f FTPS_Script.txt -u <username> -p <password> >goftp.log 2>&1

3. FTPS requires that VICA4 CerNcates be used, if you do not have them you will need to create a
VHELP incident to request them.
4. The FTPS also requires that JAVA 1.8 be installed on the PC.

End of Version 4.00.0017 Readme