MIGS Payment Client Installation Guide
Contents
1. 3 Read through and then press Next on the Introduction screen 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 10 of 36 4 Three installation options will be presented on the Choose installation options screen al o x w Dialect Solutions Payment Client 3 1 1 0 patel Choose Installation Options Please select the configuration of the Payment Client you wish to install More than one option may be selected Installation Options D Java O Sockets M COM InctallAnywhere byzero G Cancel Previous new Figure 4 Windows Payment Client 3 1 Installation Options Java select this option if you intend to use Java servlets with direct API calls to the Payment Client Sockets select this option if you intend to use Java servlets or Perl CGI with socket calls to the Payment Client COM select this option if you intend to use ASP COM with the Payment Client Note although multiple options may be selected please select the COM option only i e do not select Java or Sockets if you intend to use ASP COM Unlike Payment Client 3 0 where the Payment Client object is installed as a COM object via javareg exe and run inside the Microsoft VM Payment Client 3 1 installs a PCCOM dil file that connects to the Payment Client that off the SUN Java VM J2SE 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guid2. 17 InstallAnywhere Uninstaller About to uninstall QSI Payments Payment Client 3 0 This will completely remove all components installed by InstallAnywhere It will not remove files and folders created after the installation Cancel Figure 24 Windows Payment Client Uninstallation Confirmation 4 Once the uninstallation process is complete a summary screen will be displayed Press Quit to close the uninstallation program 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 35 of 36 InstallAnywhere Uninstaller Een att mi x Uninstall QSI Payments Payment Client 3 0 Uninstall Complete The following items could not be removed Unable to remove directory C QSIPayments P aymentClientilog Unable to remove directory C QS IPayments P aymentClienticontig Cancel Figure 25 Windows Payment Client Uninstallation Complete 5 As illustrated in the screenshot above certain files directories cannot be removed automatically C QSIPayments PaymentClient log C QSIPayments Paymentclient config These are configuration files and log files Backup the files by using the following command ren C QSIPayments PaymentClient PaymentclientBackup 6 Step 6 is for COM Installations only IMPORTANT if the Payment Client had been installed using the COM Support option for ASP COM check that the directory C WINNT java TrustLib PaymentClient has been r
3. see above screenshot needs to be enabled for the following screen to be displayed Other directories may also be visible depending on other applications existing on the IIS installation Directory browsing should be turned off in an production environment localhost Microsoft Internet Explorer ae _ 5 x File Edit View Favorites Tools Help I e s QOudas address http localhost x 60 localhost Thursday 30S 2 5P Thursday 3DS 2 5P MTS Thursday H 305 3P Thursday AMA CAPTURE Thursday AMA FINTRANS Thursday d AMA QUERYDR Thursday AMA REFUND Thursday EPS Thursday 5 MOTO Thursday MOTO MTS Thursday S5L fax Local intranet Figure 22 ASP version of Payment Client Sample Code Contents 3 Any of the available transaction types may now be used to test the ASP version of the Payment Client Sample Code 4 4 Java Samples gt Win32 Apache Jakarta Tomcat This example assumes that the Payment Client Sample Code will be deployed in the Tomcat Root Context on a new Tomcat installation on port 80 Please refer to Tomcat documentation if Virtual Hosts is required or deployment in a new context is required Please consult the Tomcat installation owner if the code is being deployed to an existing installation NOTE if Virtual Hosts or a new context is used change the value of FORM ACTION and the ReturnURL input field in the sample code 1 Determine the d
4. C Program FilesWJava j2re1 4 2_02 binijava exe Search For Others Choose Another Previous Figure 6 Windows Payment Client 3 1 Choose a Java Virtual Machine 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 12 of 36 7 Choose the installation folder at the Choose Install Folder screen For consistency it is recommended that the Payment Client should be installed in the default C Dialect directory Press Next to continue 8 Please select the appropriate proxy configuration at the Choose Proxy Configuration screen If you are unsure please contact your internal network support for information 9 The following sockets configuration screen will be displayed if sockets was selected in step 4 or if COM was selected and option 1 or 2 was selected in step 3 15 x YP Dialect Solutions Payment Client 3 1 1 0 Enter Sockets Configuration The following settings are required for a sockets installation The port number that the PCService will monitor Alist of valid IP addresses that requests will be accepted from separated by a space Ifthe PCService is to be installed as a NT Service the Service Name to use PCService Port 9050 Enter multiple IP Addresses separated by a space IP Addresses 127 0 0 1 M Install the Payment Client sockets listener as an NT Service Service Name Dialect PCService Port 9050 installAnywhe
5. Ensure all the settings are correct then press Install to continue 12 An Install Complete screen will be presented to confirm successful installation of the Payment Client Press Done to finish 13 The installation program will close NOTE The temporary directory created in Step I e g C temp MIGS_PC should be removed The installation package should be stored in a secure location 14 Test the payment client by using the Test Payment Client program Please refer to section 3 for help on Testing the Payment Client Installation 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 14 of 36 2 5 Unix Payment Client 3 0 Installation 1 Unzip all the files from the installation package into an empty unique temporary directory e g MIGS_PC 2 Open a shell and run the following commands cd MIGS_PC chmod u x paymentclient_30 bin _ paymentclient_30 bin NOTE the installation program requires a graphical display of at least 256 colours If a graphical display is not available please start the text mode installation via the command paymentclient_30 bin i console 3 The installation program will begin Read through and then press Next on the introduction screen 4 Choose the installation folder For consistency it is recommended that the Payment Client should be installed in the usr local OSITPayments directory Press Next to continue bd OSI Payments P
6. Testing the Unix Payment ClHCht ss esssseiassssstssssser otsisin antiasit 27 4 Payment Client Sample Code Installation ssssssesssrsssrsrrssrrsorenrrsrnrrnrsrnssrrsnrsrnnsrrrsnrsn nr rn en 28 4 1 Supported Programming LaNgUAZeCS ssssesrserssrsssrerrrsrrrsrerrrsrrrsrrsrrsrn rs rr rrnrsr ns sr rn rn rna 28 4 2 Installation Package Conventions s sssesssrsssrserserrrsrerrrsrrssrnrsnrsrnrssrrrrrsr ns ieaa ld nr sr r ren nen 28 4 3 ASP Samples Win32 Internet Information Services IIS ss sssesssrsrsesressrersrsnnsn 29 44 Java Samples Win32 Apache Jakarta TOMCat ssesssrsssersrersrsrersrrsnrsnnssrrsnrsnrr ren 30 4 4 1 Important Information Regarding Java Sources srssrrssrersrsrersrernrsnrssrrenrrsn en 31 4 4 2 Editing and Recompiling Java SOUICCS ssssserrssrsssrsrsrsrsrsrernnssrrsnrsnnssrrsnrennr ren 31 4 5 Java Socket Samples Win32 Apache Jakarta Tomcat ssssrsssesrsssressrensrsrnsnrent 32 4 5 1 Starting the Java Socket Listener ssiecctesckcschdsaciaessteccsdeseeesestate diaz sdsvdadasaadeanaras 32 4 5 2 Important Information Regarding Java Socket Sources s ssssessrsorssrsssrsnrssnrn 32 4 6 Perl Samples Win32 Apache HTTP SeCIVel ssssssssesssrsssressrsrresnrsrnrsnresrsnnssrrsnrrnrr ren 32 4 6 1 Important Information Regarding Perl Sources m ssesssrsssrersrsrersrernrsnrnssrnsnrsnnrs 33 4 6 2 Editing and Deploying Perl Sources ck concede eiecsacscesncdlinesastenianlaynedes 34 gt Payment Client
7. be supported please choose the option labelled COM Support Otherwise choose the Standard Installation Press Next to continue 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 8 of 36 NOTE for COM support the Payment Client 3 0 installation program registers the Payment Client object as a COM object with a utility javareg exe This allows the Payment Client to run inside the Microsoft VM 5 Choose the installation folder For consistency it is recommended that the Payment Client be installed in the C OQSTPayments directory Press Next to continue 6 A Choose Shortcut Folder selection screen will be displayed For consistency the default setting is recommended Press Next to continue 7 A Pre Installation Summary confirmation screen will be displayed Press Install to continue 8 An Install Complete screen will be presented to confirm successful installation of the program Press Done to finish 9 The installation program will close NOTE The temporary directory created in Step 1 e g C temp MIGS_PC should be removed The installation package should be stored in a secure location 10 Test the payment client by using the Test Payment Client program Please refer to section 3 for help on Testing the Payment Client Installation 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 9 of 36 2 4 Windows Pay
8. the PCService socket listener will accept incoming connects on For general installations on a single server the localhost should be able to connect to itself via the default port 9050 Enter multiple IP Addresses this is the list of IP addresses that will be allowed to connect to the PCService socket listener For general installations on a single server the machine connects to itself therefore the localhost IP of 127 0 0 1 will be sufficient 10 A screen will be displayed requesting you to Choose Link Location For consistency the default setting is recommended Press Next to continue 11 A Pre Installation Summary confirmation screen will be displayed Ensure all the settings are correct then press Install to continue 12 An Install Complete screen will be presented to confirm successful installation of the Payment Client Press Done to finish 13 The installation program will close NOTE the temporary directory created in Step 1 should be removed The installation package and encryption key files should be stored in a secure location 14 Test the Payment Client by using the Test Payment Client program Please refer to section 3 for help on Testing the Payment Client Installation 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 20 of 36 3 Testing the Payment Client Installation The Payment Client installation package contains a utility tha
9. the page address in the Address bar make sure that it is spelled correctly To check your connection settings click the Tools menu and then click Internet Options On the Connections tab click Settings The settings should match those provided by your local area network LAN administrator or Internet service provider ISP If your Network Administrator has enabled it Microsoft Windows can examine your network and automatically discover network connection settings If you would like Windows to try and discover them click a Detect Network Settings Some sites require 128 bit connection security Click the Help menu and then click About Internet Explorer to determine what strenath security you have installed If you are trying to reach a secure site make sure your Security settings can support it Click the Tools menu and i Internet Figure 19 Testing the Windows Payment Client SSL Return URL 6 Paste the URL to the Payment Client Diagnostics WINNT System32 cmd exe lease select a transaction type type 1 for type 2 for SSL lease enter a merchant id ESTTESAUDALUCYF he SSL test will be executed with the following data merchant id TESTTESAUDALUCYF session id session id purchase amount 160 locale id en_AU dr url esting creation of PaymentClient object OK Printing redirected messages from stdout ogging initilise starting EBUG XX0008 Loading property data C QSIPayments PaymentClien
10. 0 locale id en_AU dr url esting creation of PaymentClient object OK Printing redirected messages from stdout ogging initilise starting EBUG XX0008 Loading property data C QSIPayments PaymentClient conf ig con qg ipayments utility logging Logging properties Logging system initialising Log messages will temporarily display to standard out Logging system initialised Log messages will no longer appear on standard out End of message esting sending of MOTO digital order object OK hecking the results from the PaymentServer he MOTO test has been completed successfully QS1Payments PaymentClient gt _ Figure 15 Testing the Windows Payment Client MOTO Test Completed 5 A log of the test transaction will be stored in the following file C QsIPayments PaymentClient PaymentClientDiagnost1CSDDMMYYYYHHMMSS log or C Dialect Paymentclient bin PaymentclientDiagnost1CSDDMMYYYYHHMMSS log where DDMMYY Y YHHMMSS is the date and time of the test transaction 6 The MOTO test has been completely successfully if the following message can be found in the log file Checking the results from the PaymentServer OK The MOTO test has been completed successfully 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 23 of 36 3 1 2 Windows Payment Client SSL Test Prerequisites for the SSL test e SSL must be Enabled in Merchant Manager gt Glob
11. ANZ ANZ eGate MIGS Payment Client Installation Guide EGate User M Copyright Trademarks 2004 ANZ Banking Group Ltd The information contained in this manual is proprietary and confidential to MasterCard International Incorporated MasterCard and its members This material may not be duplicated published or disclosed in whole or in part without the prior written permission of MasterCard Trademark notices and symbols used in this manual reflect the registration status of MasterCard trademarks in the United States Please consult with the Customer Operations Services team or the MasterCard Law Department for the registration status of particular product program or service names outside the United States All third party product and service names are trademarks or registered trademarks of their respective owners Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 2 of 36 Table of Contents Tho Preface nnie nn ta sis sd kv sa Seu dels ann a a a a a a i aE 5 1 1 Wh Should Read This Cran es assault ipa te ac hh ke hat a a a se 5 X2 Related Doc MentS me vers sas stor se sr r r d r Sacer gode as ose cas oes asec 5 3 Software Versions COVERED sessioissa onata eA OA AEn R SEERIA AEREE no iiaea TE 5 1 4 Web Server Versions Covered ssessessseessssseesesststesesstsesssetsessestesesseseestsseesessesee 6 1 5 Other Software DependenCieS ssersssrssressrrsssrsrrssrrssrsrrrs
12. Java source files have been included in the directories corresponding to the transaction type e g MOTO Do not to leave these sources in their default directory otherwise they will be publicly downloadable The Java source files can be stored within the WEB INF classes directory itself 4 4 2 Editing and Recompiling Java Sources Java source files can be edited however once they are changed they must be recompiled using the Java Development Kit as specified in Section 1 5 Other Software Dependencies Compiled Java class files must be placed back into the WEB INF classes directory and Apache Jakarta Tomcat must be restarted to recognise the new class file In order to compile the Java source files add an entry into the system CLASSPATH On WindowsNT platforms this can be done via the command prompt set CLASSPATH CLASSPATH C QSTPayments PaymentClient classes Paym entClient jar The OSI PaymentClient class files would have been installed during the Payment 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 31 of 36 Client installation refer to Section 2 Payment Client Installation 4 5 Java Socket Samples Win32 Apache Jakarta Tomcat Installation of the Java Socket Samples is very similar to the Java Samples Please refer to Section 3 4 Win32 Apache Jakarta Tomcat 4 5 1 Starting the Java Socket Listener Before testing the Java Socket Samples socket listener must be s
13. T Card Number 51234567890 12346 Expiry Date 0504 a The program will display the following message Please enter a card number The card number should be entered with no spaces or hyphens b The program will display the following message Please enter the card expiry date MMYY NOTE the actual card expiry date could be in the format YYMM depending on the setup of the merchant 4 The Payment Client Diagnostics program will attempt to contact the Payment Server to carry out the test transaction NOTE depending on how the program was Started see section 3 1 the program will finish up and either close automatically or return to the cmd shell 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 22 of 36 A CAWINNT System32 cmd exe SNS lease select a transaction type type 1 for MOTO type 2 for SSL lease enter a merchant id ESTTESAUDALUCYF lease select a card ype shortCutKeyz for cardNamex cardNumberz cardExpiry r to enter another card type Z lease enter a card number 123456789612346 zene enter the card expiry date lt MMYY gt he following user data has been collected test type MOTO merchant id TESTTESAUDALUCYF card number 5123456789012346 card expiry 6564 he MOTO test will be executed with the following data merchant id TESTTESAUDALUCYF session id session id card number 5123456789012346 card expiry 6564 purchase amount 10
14. Uninstallauon ics isscc dass anina a a ai ai 35 5 1 Windows Payment Client UninstallatiOnN sssosssosssrsorssrrssrennrsrrrsresnrsrnnsrnrsnns gt 35 5 2 Unix Payment Client Uninstallation sssssesssrsserssrersrsrrrsrernrsrrssrnrsnrsrnnssrrsnnen rr nr en 36 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 3 of 36 Table of Figures Figure 1 Windows Payment Client 3 0 Installation Program eeceseeseeseeeteeeeeeteceaeeneeenee 8 Figure 2 Windows Payment Client 3 0 Installation Options sessssserseesresrsrerersernrrsrsrrnrene 8 Figure 3 Windows Payment Client 3 1 Installation Progr lm ssesssssrsrrsrrsrsrersesrsrerrrsrrn en 10 Figure 4 Windows Payment Client 3 1 Installation Options seessesessersessrsrerersrsrerrrsrrnrn 11 Figure 5 Windows Payment Client 3 1 COM Configuration sessessssersersrsrersrsesrerrrsrrnen 12 Figure 6 Windows Payment Client 3 1 Choose a Java Virtual Machine ssseseesossrrn0n 12 Figure 7 Windows Payment Client 3 1 Enter Sockets Configuration ssessersm0 13 Figure 8 Unix Payment Client 3 0 Installation FOIder sseseessssrsrrsrrrsrsrrsrrsrsrerrrrrrrrrnrrrrn ra 15 Figure 9 Unix Payment Client 3 0 Link Location ccccsssssccssstsonseresescessessessnasencsnsossensess 16 Figure 10 Unix Payment Client 3 0 Pre Installation SUmMary ssesssssrsrrsr
15. al Permissions e A Client Return URL must be specified in Merchant Administration gt Configuration Configuration Details Today s date 4 8 04 Merchant ID TESTTESAUDALUCYF Help CLICK HERE Merchant Merchant Name Lucy s Flower Shop Merchant ID TESTTESAUDALUCYF Internationalization Locale English United States Time Zone Australia Sydney SSL Client Return URL eg httos examnple corh http 127 0 0 1 SSLYASP_3party_DR asp DR DR Figure 16 Testing the Windows Payment Client Client Return URL for SSL Test The Client Return URL needs to be configured in Merchant Administration since no value can be provided in the Payment Client Diagnostics Once the test is complete the sample codes can be used and the Return URL can be sent with the digital order thus overriding the Merchant Administration setting To perform a SSL test start the Payment Client Diagnostics program as described in section 3 1 1 Enter the number 2 and press Enter to start the SSL test 2 The program will display the following message Please enter a merchant id Generally the user should use the TEST merchant ID This is the merchant ID prefixed with TEST 3 The user s default web browser will open and the server hosted card selection page will be displayed Click on a card logo to select that card 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 24 of 36 Z QSI Paym
16. ample assumes that the Payment Client Sample Code will be deployed in the DocumentRoot on a new Apache HTTP Server installation on port 80 Please refer to Apache documentation if Virtual Hosts are requied Please consult the Apache HTTP Server owner if code is being deployed on an existing installation NOTE if Virtual Hosts are used change the value of FORM ACTION and the ReturnURL input field in the sample code 1 Determine the directory of the Apache HTTP Server e g C apache_1 3 27 This will be referred to as APACHE_HOME 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 32 of 36 2 The contents of the sample code package should be extracted and placed a new APACHE_HOME MIGS_SC directory 3 Make a backup of the 4PACHE_HOME conf httpd conf file Open the file in a text editor and search for the following lines DocumentRoot The directory out of which you will serve your documents By default all requests are taken from this directory but symbolic links and aliases may be used to point to other locations DocumentRoot C apache_1 3 27 htdocs This should be changed to DocumentRoot The directory out of which you will serve your documents By default all requests are taken from this directory but symbolic links and aliases may be used to point to other locations DocumentRoot C apache_1 3 27 MIGS_SC Search for the following lines T
17. ayment Client 3 0 KX Choose Install Folder where would You Like to Install Vusr local Qs Pay ments Restore Default Folder Choose Cancel Previous Figure 8 Unix Payment Client 3 0 Installation Folder 5 A screen will be displayed allowing the user to choose a link directory This is the directory where symbolic links to the PaymentClientDiagnostics PCService and Uninstallation utilities will be created 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 15 of 36 K OSI Payments Payment Client 3 0 salaa Bay Zero AA H MA M ee Figure 9 Unix Payment Client 3 0 Link Location For consistency it is recommended that the default setting should be used This will create links in the directory Press Next to continue 6 A Pre Installation Summary confirmation screen will be displayed Press Install to continue K QSI Payments Payment Client 3 0 IstallA nere Hy Zerg S Figure 10 Unix Payment Client 3 0 Pre Installation Summary 7 An Install Complete screen will be presented to confirm successful installation of the program Press Done to finish 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 16 of 36 8 The installation program will close NOTE The temporary directory created in Step I e g MIGS_PC should be removed T
18. e April 2004 Page 11 of 36 5 IfCOM was selected a Select COM Configuration screen will be displayed VB Dialect Solutions Payment Client 3 1 1 0 Select COM Configuration Select the COM configuration you wish to install NOTE For performance reasons the recommended interface to use for the COM Objectis the COM Sockets interface Options 1 or 2 1 Use COM with an existing Payment Client PCService p Use COM and install a new Payment Client PCService 3 Use COM and install a Payment Client using Java JNI Option 1 Use this option to allow COM to connect to an existing Payment Client PCService that has already been installed on the local network The PCService may have to be configured to accept connections from this host InstallAnyw j Figure 5 Windows Payment Client 3 1 COM Configuration It is recommended that option 2 should be used Use COM and install a new Payment Client PCService Payment Client 3 1 installs a PCCOM dil file that connects to the PCService which runs off the SUN Java VM J2SE Press Next to continue 6 Select the correct SUN Java VM at the following screen Payment Client 3 1 should be used with J2SE 1 4 2 YB Dialect Solutions Payment Client 3 1 1 0 Choose a Java Virtual Machine The following Java Runtime Environments have been detected on this machine Please select a Java Runtime Environment 1 3 or 1 4 or IBM 1 3 to be used C j2sdk1 4 2_03 jreibinijava exe
19. emoved 5 2 Unix Payment Client Uninstallation The Uninstall Payment Client link that was created during the installation process can be used to start the uninstallation process 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 36 of 36
20. ent Client you wish to install More than one option may be selected Installation Options J Java i7 Sockets Cancel Previous Next Figure 11 Unix Payment Client 3 1 Installation Options Select the Java option if you intend to use Java servlets with direct API calls to the Payment Client Otherwise select the Sockets option if you intend to use sockets to connect to the Payment Client e g Java sockets or Perl CGI socket calls NOTE either option will allow direct Java API calls however the sockets option will install the PCService socket listener which opens a socket defaulting to port 9050 to listen for incoming requests 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 18 of 36 6 Select the correct SUN Java VM at the following screen Payment Client 3 1 should be used with J2SE 1 4 2 hd Dialect Solutions Payment Client 3 1 0 0 KX Choose a Java Virtual Machine The following Java Runtime Environments have been detected on this machine Please select a Java Runtime Environment 1 3 or 1 4 or IBM 1 3 to be used fusr bin j2sdk1 4 2_03 bin java Search For Others N Choose Another histallAnywhere by zero G Cancel Previous Next Figure 12 Unix Payment Client 3 1 Java Virtual Machine Selection 7 Choose the installation folder at the Choose Install Folder screen For c
21. ent Technologies Secure Payment Server Microsoft Internet Explorer Ol x Fie Edt view Favorites Tools Hep gt OO H 3 Address 2 iMvPVitsxc8pWajux 2nIs c4nicJvhyLNTSF3 eLhZ7 yLGw QLHQPvigrFDYrlOwySHDSY dZMMdkMylZ2UiOBa9k7PxInak6g__ amp o pt Y Go MasterCard Your details will be sentto and processed by The MasterCard Internet Gateway Service and will not be disclosed to the merchant Intemet Gateway Service TEST MODE Merchant name Lucy s Flower Shop f AC How would you like to pay he Pay securely using SSL by clicking on the card logo below Copyright 2003 H 1B internet 74 Figure 17 Testing the Windows Payment Client SSL 3 Party Card Select 4 The Card Details page will be displayed Enter a valid test card A full list of test cards can be found in Appendix 3 of the MIGS Payment Client Integration Guide Z QSI Payment Technologies Secure Payment Server Microsoft Internet Explorer provided by Mastercard inter 5 x File Edit View Favorites Tools Help Bak gt A A Reach Favorites History Er S MM E Address E https migs mtf mastercard com au ssl sessionid PAY 1060645105617263 MasterCard Your details will be sentto and processed by The MasterCard Internet Gateway Service and will not be _ disclosed to the merchant Internet Gateway Service TEST MODE Merchant name Lucy s Flowers p T J Paes N G E
22. entClient gt _ Figure 20 Testing the Windows Payment Client SSL Test Completed 7 A log of the test transaction will be stored in the following file C QsIPayments PaymentClient PaymentclientDiagnost1CSDDMMYYYYHHMMSS 10g or c Dialect Paymentclient bin PaymentclientDiagnost1TCSDDMMYYYYHHMMSS 10g 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 26 of 36 where DDMMYY Y YHHMMSS is the date and time of the test transaction 8 The SSL test has been completely successfully if the following message can be found in the log file Checking the results from the PaymentServer OK The SSL test has been completed successfully 3 2 Testing the Unix Payment Client The Payment Client Diagnostics can be accessed via the Test_Payment_Client link that was created during the installation process The procedure for testing the Unix Payment Client is similar to the procedure for testing the Windows Payment Client 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 27 of 36 4 Payment Client Sample Code Installation The Payment Client Sample Code will only be distributed to authorised systems integrators via an authorised Payment Client consultant These packages contain bank specific customisations and MUST NOT BE REDISTRIBUTED to any other parties Please contact a Payment Client representative for the Payment Client Sample Code packa
23. esrsrernesrsrrrrrnrrn ra 16 Figure 11 Unix Payment Client 3 1 Installation Options sssssesssssrsressesrerersrsrerrerrsrerresrrr rn nen 18 Figure 12 Unix Payment Client 3 1 Java Virtual Machine Selection sesssessessesrsrsnnn 19 Figure 13 Unix Payment Client 3 1 Sockets ConfiguratiOn ssessessrsrrsrssrsrersrrrsnrsnrerr ra 20 Figure 14 Testing the Windows Payment Client Payment Client DiagnostiCcs 21 Figure 15 Testing the Windows Payment Client MOTO Test Completed s 23 Figure 16 Testing the Windows Payment Client Client Return URL for SSL Test 24 Figure 17 Testing the Windows Payment Client SSL 3 Party Card Select 25 Figure 18 Testing the Windows Payment Client SSL 3 Party Card Details 25 Figure 19 Testing the Windows Payment Client SSL Return URL ssssssssesressesesrersrsrrnnn 26 Figure 20 Testing the Windows Payment Client SSL Test Completed s sss 26 Figure 21 ASP version of Payment Client Sample Code IIS Directory cece 29 Figure 22 ASP version of Payment Client Sample Code COntentS s sssessmrrsss 30 Figure 23 Java Sockets version of Payment Client Sample Code Listener 32 Figure 24 Windows Payment Client Uninstallation Confirmation ssseesrerssrsns 35 Figure 25 Windows Payment Client Uninstallatio
24. for fully or partially refunding a transaction via the original transaction number returned with all authorisation purchase transactions e EPS External Payment Selection sample code Similar to the SSL Server Hosted sample code however the card type is sent in the digital order and thus bypasses the card type 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 28 of 36 e MOTO e MOTO MTS SSL selection screen on the Payment Server Merchant Hosted payments sample code Card details are captured by the merchant s systems which communicates with the Payment Server for authorisation Similar to the above with merchant transaction sources Server Hosted payments sample code Cardholder is redirected to the Payment Server to enter their card details reducing the risk of cardholder information being stolen from the merchant s systems Communication is done via redirection of the cardholder s browser to the server hosted pages NOTE depending on the transaction types supported by your merchant profile a subset of the sample codes may be provided 4 3 ASP Samples gt Win32 Internet Information Services IIS 1 The contents of the sample code package should be extracted and placed in the ZZS wwwroot directory This directory may be different for different IIS installations however the default value is C Inetpub wwwroot The following screenshot shows the default value in t
25. ge 4 1 Supported Programming Languages The Payment Client Sample Code will contain sample code in various different programming languages The Payment Client Sample Code may be provided in any combination of the following languages e ASP COM e Java e Java Sockets e Perl 4 2 Installation Package Conventions The Payment Client Sample Code installation package generally contains the following directories containing sample code for different transactions e 3DS 2 5P 3D Secure authentication and payment sample code Merchant hosted model where the merchant collects the card details and sends this through in the digital order e 3DS 2 5P MTS Similar to the above with merchant transaction sources e 3DS 3P 3D Secure authentication and payment sample code Server hosted model where cardholder enters their card details on the Payment Server reducing the risk of cardholder information being stolen from the merchant s systems e AMA CAPTURE Advanced Merchant Administration command for performing captures after a previous authorisation request This is the second step of a two step authorisation then capture payment model e AMA FINTRANS Command for performing transaction lookup via the original transaction number returned with all authorisation purchase transactions e AMA QUERYDR Command for transaction lookup via the MerchTxnRef which is supplied by the merchant with each digital order e AMA REFUND Command
26. he IIS administration Default IIS Web Site Properties Directory Security 21x HTTP Headers Custom Errors Server Extensions Home Directory Web Site Performance ISAPI Filters When connecting to this resource the content should come from A directory located on this computer CA share located on another computer A redirection to a URL Documents Vv Directory browsing a ne Local Path 4 C Inetpub wwwroot Browse MV Log visits v Head IV Index this resource T Write Application Settings Application name Default Application lt Default IIS Web Site gt Scripts only yv Application Protection Medium Pooled t Starting point Execute Permissions Remove Configuration Unload Cancel Apply Help Figure 21 ASP version of Payment Client Sample Code IIS Directory 2004 ANZ Banking Group Ltd MIGS Payment Client Installation Guide April 2004 Version 1 2 Page 29 of 36 NOTE for security purposes ensure that Script source access is O unchecked and Execute Permissions is set to Scripts Only M Check the Directory Browsing box if you would like to see the files displayed like Figure 22 2 Test to ensure that the sample code has been placed in the correct directory by pointing the internet browser to the following URL http Nocalhost A listing similar to the following will be displayed NOTE Directory browsing
27. he installation package should be stored in a secure location 9 Test the payment client by using the Test Payment Client program Please refer to section 3 for help on Testing the Payment Client Installation 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 17 of 36 2 6 Unix Payment Client 3 1 Installation 1 Unzip all the files from the installation package into an empty unique temporary directory e g MIGS_PC 2 The encryption keys qsi 3 and qsi 4 may have been distributed separately from the Payment Client zip file Please ensure that these are copied to the temporary directory alongside the other installation files otherwise installation will fail 3 Open a shell and run the following commands cd MIGS_PC or your temporary directory from step 1 chmod u x paymentclient_3_1_1_0 bin paymentclient_3_1_1_0 bin NOTE the installation program requires a graphical display of at least 256 colours If a graphical display is not available please start the text mode installation via the command paymentcliTent_3_1_1_0 bin 7 console 4 The installation program will begin Read through and then press Next on the Introduction screen 5 Two installation options will be presented on the Choose Installation Options screen EJ Dialect Solutions Payment Client 3 1 0 0 KX Choose Installation Options Please select the configuration of the Paym
28. his should be changed to whatever you set DocumentRoot to lt Directory C apache_1 3 27 htdocs gt This should be changed to This should be changed to whatever you set DocumentRoot to lt Directory C apache_1 3 27 MIGS_SC gt Search for the following lines ScriptAlias cgi bin C apache_1 3 27 cgi bin This should be changed to ScriptAlias cgi bin C apache_1 3 27 MIGS_SC cgi bin Search for the following line lt Directory C apache_1 3 27 cgi bin gt This should be changed to lt Directory C apache_1 3 27 MIGS_SC cgi bin gt 4 Start the Apache HTTP Server 5 Test to ensure the setup is correct by pointing the internet browser to the URL http Nocalhost The sample code will be listed 6 Start the Java Socket Listener Please refer to Section 3 5 1 Starting the Java Socket Listener 7 Any of the available transaction types may now be used to test the Perl version of the Payment Client Sample Code 4 6 1 Important Information Regarding Perl Sources The Perl source files cgi have been included in the directories corresponding to the transaction type e g MOTO It is a good idea not to leave these sources in their default directory otherwise they will be publicly downloadable Remove these and leave all cgi files in the cgi bin directory Also note that depending on the Apache HTTP Server and Perl setup the first line of all the cgi files may need to be changed The first
29. ient Sample Code ASP COM Java Java Sockets Perl 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 5 of 36 1 4 Web Server Versions Covered Due to the multitude of web server implementations and platforms this document will not attempt to cover all versions but will instead illustrate various examples Web Server Version Reference URL Apache HTTP Server 1 3 27 http httpd apache org Apache Jakarta Tomcat 4 1 18 http jakarta apache org Microsoft IIS Internet Information Services 5 0 http www microsoft com tis 1 5 Other Software Dependencies Software Version Reference URL Java Runtime Environment to run samples OR Java Development Kit for compilation SUN J2SE 1 3 1 http 4ava sun com j2se 1 3 OR SUN J2SE 1 4 2 http java sun com j2se 1 4 2 OR Perl needed for Perl samples only 5 http www perl com NOTE Payment Client 3 0 should be used with SUN Java 1 3 1 while Payment Client 3 1 should be used with SUN Java 1 4 2 1 6 Revision History Version Date Author History Draft 0 01 18 Mar 2003 Thomson Document creation 1 01 06 Aug 2003 Thomson Document updated 1 2 06 Apr 2004 Thomson Document updated 1 7 Where to Get Help For assistance with Payment Client integration please contact your support organisation s help desk Con
30. irectory for the Tomcat installation e g C jakarta tomcat 4 1 18 This will be referred to as TOMCAT HOME 2 The contents of the sample code package should be extracted and placed in a new 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 30 of 36 TOMCAT HOME webapps MIGS_SC directory 3 Make a backup of the TOMCAT_HOME conf server xml file Open the file in a text editor and search for the following lines lt Tomcat Root Context gt lt lt Context path docBase ROOT debug 0 gt gt Notice that by default these lines are commented out Change these lines to the following example lt Tomcat Root Context gt lt Context path docBase MIGS_SC debug 0 gt 4 Start the Jakarta Tomcat web server 5 Test to ensure the setup is correct by pointing the internet browser to the URL http Nocalhost The sample code directories should be listed NOTE the WEB INF directory is a special directory containing the compiled Java class files It is hidden from the internet browser 6 The OSI properties file may need to be copied into Jakarta Tomcat This can be done by copying the following file From C WINNT java trustlib QSLproperties To TOMCAT_HOME bin QSL properties 7 Any of the available transaction types may now be used to test the Java version of the Payment Client Sample Code 4 4 1 Important Information Regarding Java Sources The
31. line of the samples may have been 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 33 of 36 defaulted to C Perl bin per l This will need to be changed to the location of an existing Perl interpreter 4 6 2 Editing and Deploying Perl Sources As mentioned above cgi sources have been left in their corresponding directories for reference only Changed cgi files must be placed back in the cgi bin directory to function correctly 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 34 of 36 5 Payment Client Uninstallation 5 1 Windows Payment Client Uninstallation To uninstall the Windows Payment Client the following steps need to be followed 1 Step 1 is for COM Installations only IMPORTANT if the Payment Client had been installed using the COM Support option for ASP COM temporarily stop the IIS web server prior to uninstalling the Payment Client NOTE the web server will be down and must be restarted after completing the uninstallation process Please contact the web server owner for correct procedures 2 Use the following shortcut to start the uninstallation process Start Menu gt Programs gt QSIPayments gt PaymentClient gt Uninstall Payment Client 3 A confirmation screen will be displayed Click on the Uninstall button to begin the uninstallation process 215 x Uninstall QSI Payments Payment Client 3 0
32. ment Client 3 1 Installation Please ensure that SUN J2SE 1 4 2 is installed prior to the installation of Payment Client 3 1 1 Unzip all the files from the installation package into a unique temporary directory e g C temp MIGS_PC 2 Open the temporary directory e g C temp MIGS_PC and verify that the following files are available CardNumbers profile preset test card for diagnostics tests and test merchant IDs paymentclient_3 1 1 0 exe Payment Client 3 1 installation program qsi 3 qsi 4 encryption keys linked to the specific merchant ID s serverurl properties URL setting for accessing the Payment Server truststore properties encryption truststore settings NOTE the encryption keys qsi 3 and qsi 4 may have been distributed separately from the Payment Client zip file Please ensure that these are copied to the temporary directory alongside the other installation files otherwise installation will fail SI C temp MIGS_PC RE O x File Edit View Favorites Tools Help Ea Back gt HA fa A search U4 Folders EBdistory as 0 x A Ez Address 9 c ItempiMIGS Pc x eo a a e FB CardNumbe paymentclient JPC 3 1 1 qsi 3 qsi 4 serverurlpr truststore 3 1 1 0 exe J 7 objectis 2 78 MB E My Computer Figure 3 Windows Payment Client 3 1 Installation Program Double click on the file named paymentclient_3 1 1 0 exe to start the installation program
33. n Complete sssssrsresrssrsresersrsnrrnrsrrnra 36 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 4 of 36 1 Preface This Payment Client Installation Guide outlines the installation process for the MIGS Payment Client The purpose of this document is to provide an overview of the following Payment Client installation tasks 1 Installing the Payment Client 2 Setting up the Payment Client Sample Code 1 1 Who Should Read This Guide This guide is specifically aimed at business analysts and systems integrators who intend to integrate the Payment Client into merchant applications and personnel who will be involved with the integration and support processes The purpose of this document is to provide an overview of the installation process The reader is expected to be familiar with configuring their respective operating systems and web servers 1 2 Related Documents This document must be read in conjunction with various other documents which describes the Payment Client technical details as well as business logic surrounding transaction processing Document Name Revision Provider MIGS Payment Client Reference Manual 2 3 MasterCard International MIGS Payment Client Integration Guide 2 3 MasterCard International 1 3 Software Versions Covered Software Version Payment Server 2 2 Payment Client 3 0 and 3 1 Payment Cl
34. n transactions Therefore it is imperative that this file is kept in a secure location 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 7 of 36 2 3 Windows Payment Client 3 0 Installation 1 Unzip all the files from the installation package into a unique temporary directory e g C temp MIGS_PC 2 Open the temporary directory e g C temp MIGS_PC and double click on the file named paymentclient_3 0 exe to start the installation program as illustrated in the following screenshot amp C temp MIGS_PC File Edit View Favorites Tools Help Back Za Search yFolders history p LPM Address C temp MIGsS_PC qsi 3 qsi 4 serverurl pr 6 objects 2 00 MB My Computer Figure 1 Windows Payment Client 3 0 Installation Program 3 Read through and then press Next on the Introduction screen 4 Two installation options will be presented on the Features screen E QSI Payments Payment Client 3 0 i Choose Product Features i Standard Installation Installs the QS Payments Payment Client 3 0 This option is recommended for most users COM Support Installs the Payment Client 3 0 with wrappers for operation via COM Install this feature if you intend to interface with the Payment Client via Common Object Model See SE Previous i Figure 2 Windows Payment Client 3 0 Installation Options If ASP COM is to
35. nter your card details 4 MasterCard You have chosen MasterCard as your method of payment Please enter your card details into the form below and click pay to complete your purchase Card Number l l E E a i Security Code i The 3 digits after the card number on the signature panel of your card Purchase Amount AUD 1 00 Pay y si Sa H 18 le internet Expiry Date i month year Figure 18 Testing the Windows Payment Client SSL 3 Party Card Details 5 A Processing page will be displayed followed by a Results page NOTE Depending on the Client Return URL specified in section 3 1 2 and whether the sample code has been installed a further Receipt Page or an Error Page will be displayed Either one is acceptable for the SSL test as long as the URL contains the encoded receipt Copy the URL from the browser 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 25 of 36 32 Cannot find server Microsoft Internet Explorer provided by MasterCard International Eie Edit View Favorites Tools Help la The page cannot be displayed The page you are looking for is currently unavailable The Web site might be experiencing technical difficulties or you may need to adjust your browser settings copy this encoded receipt URL Please try the following Click the 2 Refresh button or try again later If you typed
36. onsistency it is recommended that the Payment Client should be installed in the default usr local Dialect directory Press Next to continue NOTE installation to the usr local Dialect directory may require administrative privileges If you do not have administrative access to your system you may install the Payment Client in your home directory however the user that owns the web server process or the PCService process must be able to access the Payment Client and log directories 8 Please select the appropriate proxy configuration at the Choose Proxy Configuration screen If you are unsure please contact your internal network support for information 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 19 of 36 9 The following sockets configuration screen will be displayed if sockets was selected in step 5 fv Dialect Solutions Payment Client 3 1 0 0 X Enter Sockets Configuration The following settings are required for a sockets installation The port number that the PCService will monitor Alist of valid IP addresses that requests will be accepted from separated by a space PCService Part 9050 Enter multiple IP Addresses separated by a space IP Addresses 127 0 0 1 InstallAnywhere by zero G Cancel Previous Next a Figure 13 Unix Payment Client 3 1 Sockets Configuration PCService Port this is the TCP IP port on which
37. re by Zero G Cancel Previous Net Figure 7 Windows Payment Client 3 1 Enter Sockets Configuration PCService Port this is the TCP IP port on which the PCService socket listener will accept incoming connects on For general installations on a single server the localhost should be able to connect to itself via the default port 9050 Enter multiple IP Addresses this is the list of IP addresses that will be allowed to connect to the PCService socket listener For general installations on a single server the machine connects to itself therefore the localhost IP of 127 0 0 1 will be sufficient Install the Payment Client sockets listener as an NT Service if this option is checked the PCService socket listener will be started automatically each time the machine is started This option is recommended as it will allow the machine to run the PCService socket listener without the need for a user to be logged onto the system however this option will require administrative privileges on the system Service Name the NT Service name only applicable where the option above is checked 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 13 of 36 10 A screen will be displayed requesting you to Choose the Shortcut Folder For consistency the default setting is recommended Press Next to continue 11 A Pre Installation Summary confirmation screen will be displayed
38. rrrrrenrrsrrsrrerrr sr rr rr rr nr rr nr rr enn nn 6 1 60 R vision History 33 c3u5 chats sedd ersds basar ss res dess ssd lens tad St Saleh etn NN Dre NS NESS MANNEN rs Vr SKANNA 6 LT Where to Get Help ordrin a i eder AA rdr A Ada E dade neon iene 6 2 Payment Client InstallatiOM ss ssessissnssbasbrisisetonsaades bd ssnsd ease EEEE RAESTE 7 2 1 Supported Platf rlli8 25 issssisssdssssusdss tres tres seen ie cas eee Nn RE des a awit ARENAN 7 22 INSt lla tiori P CKADE sssessbesst es tereves se vasrdnean uactona er det a ga ees a a aie o a aS 7 2 3 Windows Payment Client 3 0 Installation sessssssssssrsrsrsrersrrsnrsnrrsrnrsnrsnnssrrsnrennr ren 8 24 Windows Payment Client 3 1 Installation s ssssssssssssrsssrsrrrsrrsnrsrnssrrsnrsnrssrrsnnennr ren 10 2 5 Unix Payment Client 3 0 InstallatiOn ssssssessssseessrersrsnnssrrsnrsnnrsrrsnrsnrnsrrrrnr caveats 15 2 6 Unix Payment Client 3 1 Install tiOn ssesssessssserssressrsrnserrnsnrsnrrsrrsnrenrnsrrernr es 18 3 Testing the Payment Client Installation ssessssessessrsssrsrrssrrsnrsnnrsrrnsrrerrnrsrnrsnrerrrsr ns rnrennna 21 3 1 Testing the Windows Payment Client sseessesssrsrrrssrrsrssrnssrernrsrrnssrrsrnrsrnssrrrrrsr ns nr rn nn 21 3 1 1 Windows Payment Client MOTO TeStosssmssssosssrrsssrersrsrnesrernrssrrsnrsnrrsrrsrrsrnnsnr rn 22 3 1 2 Windows Payment Client SSL TeSt ssssssssssrrssrersrsressrersrsrnssrrsrrsrnrsrrrsnrenrr ren 24 3 2
39. sNPaymentClientNQSI properties looking for C NWINNT Java TrustLib sI properties ound QSIRoot entry in C WINNT Java TrustLib QSI properties C QSIPayments Pay entClient End of message lease select a transaction type type 1 for MOTO type 2 for SSL Figure 14 Testing the Windows Payment Client Payment Client Diagnostics Depending on the merchant s setup they may do MOTO and or SSL transaction mode tests Merchants should consult with their bank to determine their transaction mode 2004 ANZ Banking Group Ltd Version 1 2 MIGS Payment Client Installation Guide April 2004 Page 21 of 36 3 1 1 Windows Payment Client MOTO Test Prerequisites for the MOTO test e MOTO must be Enabled in Merchant Manager gt Global Permissions To perform a MOTO test start the Payment Client Diagnostics program as described in section 3 1 1 Enter the number and press Enter to start the MOTO test 2 The program will display the following message Please enter a merchant id Generally the user should use the TEST merchant ID This is the merchant ID prefixed with TEST 3 The program will display the following message Please select a card or to enter another card type Z Type Z and press Enter to specify a test card A full list of test cards can be found in Appendix 3 of the MIGS Payment Client Integration Guide As a quick reference the following card can be used for any merchant IDs prefixed with TES
40. t conf ig con q ipayments utility logging Logging properties Logging system initialising LOg messages will temporarily display to standard out Logging system initialised Log messages will no longer appear on standard out End of message esting creation of SSL digital order object OK oaded a brower with the digital order lease perform SSL transaction hen the transaction is completed please copy the browser address here ttp 127 8 8 1 SSL ASP_3part y_DR asp DR Y dr d HRidaucuC8oUe jJAYkKLS3 7PXKE2 uCLA SZDUGrD8 wrhjCok114xBDf 3XT lmunyDP kK1gB1tiACkhid FUQOUtG4GPF96YPzno zQigyOKGlg hiCiMk PHS5S6nGZ8n 7 26KTJ44f CS gALyhp0egqFJD2qyPDGD hbpwft 3F6BeWRy yUtNpG3xcUNEok KR4FLewrk rC3f cNS jxUf Rf whOb6U32r 11 hxW u yu3 f UxWMt DpikbKRTxivM nphc Kk1DWtdl S IUuyy AFFDJ8WkkPwNuT dhHk91bQ 5 FulS 46m 1 wmyudpnA85us lgf NHcZ02 i4qAqIcIsdSput ISFFHb1iv5S in6 dhd SczCwn LpO0Gt8c8gA 2DsogakGykJu yI yKMdpoFf 2UWNx3 COQUoBF3 buywJLI jLuS lzu3wn N8 dhScbhYJyN8L52k4uu696 LbzQUyFMW2 LY2ULZIMAmkT rYf xT cEO6J 15t 4gKDabGI julxWk4Fk x4 rhcUZCDSSLrSc jX Bf JPwL9L1wZ6ca5f OduEHPF XSH jB1 1CLsg63t8 qCOHM4 pHJeQR8 LHAHUKR Ad Ke LsBkhGIitgBZFJU zmLO983mkp2kkUs but R66UbUT2 j8T pEisqMhj J9RSTcQefi12WuHKulDi8s3BD CFroJSed g Hsp 3BKt2 jGT btzmmzMav8 bF1 Zf KoZI OSUS i3MsEvptmLUrqy2xdgavu_ ecrypting digital receipt OK hecking the results from the PaymentServer OK he SSL test has been completed successfully QSIPayments Paym
41. t will allow the systems integrator to test the functionality of the Payment Client and connectivity with the Payment Server 3 1 Testing the Windows Payment Client The Payment Client Diagnostics can be accessed by following the menu Start Menu gt Programs gt QSIPayments gt PaymentClient gt Test Payment Client OR Start Menu gt Programs gt Dialect gt PaymentC ient gt Test Payment Client Alternatively Payment Client Diagnostics can be started by running the following commands in a cmd shell C cd C QSIPayments Paymentclient PaymentClTentDiagnostics exe or ce cd C Dialect Paymentclient bin PaymentClientDiagnostics exe Fl test Payment Client SI Payments Inc ayment Client 3 8 Diagnostics ate stamp 11 68 2663 at 10 46 64 lasspath C QSIPayments PaymentClient c lasses 5C QSIPayments PaymentClient cla ses PaymentClient jar C WINNT Java Trust Libs C NQS I Payments PaymentClient lax j rjciNdevNjdki 3 1_87N Njre libN ii8n jar c deu jdk1 3 1_ jre lib jaws jar c de N gjdk1 3 1_ jre lib rt jarjc deuy jdki 3 1_ jre lib sunrsasign jar Printing redirected messages from stdout EBUG XX 6066 Loading profile data C QSIPayments PaymentClient conf ig CardNu bers profile EBUG XX 666 Loading property data C QSIPayments PaymentClient conf ig setup properties End of message Printing redirected messages from stderr looking for C NQSIPayment
42. tact details will be supplied upon service sign up 2004 ANZ Banking Group Ltd MIGS Payment Client Installation Guide April 2004 Version 1 2 Page 6 of 36 2 Payment Client Installation The Payment Client will only be distributed to authorised systems integrators via an authorised consultant Please contact a Payment Client representative for the Payment Client software 2 1 Supported Platforms The following platforms are supported by Payment Client e Windows NT4 SP6 All sample code versions e Windows 2000 SP2 or later All sample code versions e Windows XP ASP COM sample code supported in Payment Client 3 1 only e Solaris 8 ASP COM sample code not supported e Red Hat Linux 7 x 8 x ASP COM sample code not supported 2 2 Installation Package NOTE Either the Windows Payment Client or the Unix Payment Client will be provided depending on the operating system of the target machine Either the Payment Client 3 0 OR the Payment Client 3 1 will be provided depending on your intended deployment Java version Installation packages are compressed using the zip format and requires a zip decompression program to extract the files from the package Please contact internal IT support if the program has not been installed IMPORTANT it is the responsibility of the bank and the merchant to keep this installation file in a secure place These files contain bank and merchant specific encryption keys used i
43. tarted On WindowsNT platforms this can be done via the command prompt set CLASSPA TH CLASSPATH C WINNT java trustlib java PaymentClient PCService The following screenshot is an example of a successfully started listener SCA WINNTYSystem32 4cmd exe java PaymentClient PCService C N gt java PaymentClient PCService looking for C QSI properties looking for C NWINNINjavastrustlibsQSI properties found QSIRoot entry in C WINNT java trust Lib QSI properties C NQSIPaymentsN PaymentClient Logging initilise startin DEBUG XX0000 Loading property data C QSIPayments PaymentClient conf ig com qsipayments utility 1 ogging Logging properties Logging system initialising Log messages will temporarily display to standard out Logging system initialised Log messages will no longer appear on standard out Payment Client listener up on port 9656 PCHandler Thread has started PCHandler Thread 1 has started Figure 23 Java Sockets version of Payment Client Sample Code Listener 4 5 2 Important Information Regarding Java Socket Sources The Java Socket source files have been included in the directories corresponding to the transaction type e g MOTO It is a good idea not to leave these sources in their default directory otherwise they will be publicly downloadable The Java Socket source files can be stored within the WEB INF classes directory itself 4 6 Perl Samples Win32 Apache HTTP Server This ex
Download Pdf Manuals
Related Search