Payment Client

(1)

Payment Client 3.2.0.0

Deployment Guide

Version 1.0

(2)

Unless otherwise expressly agreed in writing, the information contained in this document is subject to change without notice and TNS assumes no responsibility for any alteration to, or any error or other deficiency, in this document.

All intellectual property rights in the Document and in all extracts and things derived from any part of the Document are owned by TNS and will be assigned to TNS on their creation. You will protect all the intellectual property rights relating to the Document in a manner that is equal to the protection you provide your own intellectual property. You will notify TNS immediately, and in writing where you become aware of a breach of TNS' intellectual property rights in relation to the Document.

The names “TNS”, any product names of TNS including “Dialect” and “QSI Payments” and all similar words are trademarks of TNS and you must not use that name or any similar name.

TNS may at its sole discretion terminate the rights granted in this document with immediate effect by notifying you in writing and you will thereupon return (or destroy and certify that destruction to TNS) all copies and extracts of the Document in your possession or control.

TNS does not warrant the accuracy or completeness of the Document or its content or its usefulness to you or your merchant cardholders. To the extent permitted by law, all conditions and warranties implied by law (whether as to fitness for any particular purpose or otherwise) are excluded. Where the exclusion is not effective, TNS limits its liability to $100 or the resupply of the Document (at TNS' option). Data used in examples and sample data files are intended to be fictional and any resemblance to real persons or companies is entirely coincidental.

TNS does not indemnify you or any third party in relation to the content or any use of the content as contemplated in these terms and conditions.

Mention of any product not owned by TNS does not constitute an endorsement of that product. This document is governed by the laws of New South Wales, Australia and is intended to be legally binding.

(3)

Preface

Welcome to TNS

TNS Payment Technologies Pty Ltd. ("TNS") is the global communications company that enables payments, money or voices to move around the world. Our secure network is used by leading retailers, banks/processors, telecommunications companies and the financial markets - enabling the world to transact.

TNS’ Merchant Payment Gateway solution offers a complete range of services that enable merchants to accept payments over the Internet and from other card-not-present channels. This includes any payment application where the cardholder is not present at the point-of-sale, such as call centres, IVRs, and recurring billing systems. As part of the TNS Global Payment Gateway range of solutions, our services enable merchants to authorize and settle multi-regional card transactions securely, reliably and cost-effectively. Today, our Merchant Payment Gateway solution represents the platform of choice for over 15,000 merchants, two major global card schemes, and 70+ banks worldwide. In addition, the solution utilizes the resilient, state-of-the-art TNS global network that transports billions of transactions each year.

For more information on how TNS can help you with your payment processing needs, visit our website at http://www.tnsi.com http://www.tnsi.com

About Payment Client

Payment Client does real-time online payment processing with a variety of transaction modes to provide merchants and enterprises with an affordable Internet based payment system.Payment Client supports payment from the web, Call Centres, and Interactive Voice Response systems; in fact Payment Client supports any merchant application that requires processing for credit cards in “Card Present” and “Card Not Present” transactions.

(8)

Windows 2000 (SP4), Windows XP (SP3), Windows Server 2003, Windows Server 2008

RHEL3, RHEL4, RHEL5

Solaris 8, Solaris 9 (Sparc), Solaris 10 (Intel and Sparc)

MAC OSX v10.4, MAC OSX v10.5

Payment Client Documentation Set

This document, Payment Client Deployment Guide, provides an overview of Payment Client, and contains instructions on installation and management tasks.

For detailed information about integrating Payment Client with a merchant application, you will need to consult the following additional documents:

Payment Client Integration Guide describes how to integrate Payment Clientinto your architecture and environment.

Payment Client Reference Guide provides detailed reference information on the Payment Client API.

Audience

The Payment Client documentation set is designed for developers deploying the Payment Client in a suitable environment. It is assumed that you have at least the following:

Intermediate level of technical knowledge, for example, IT graduate with 2-3 years experience.

Familiarity with operating systems and basic system administration tasks for example, installing software and services and configuring the web server.

Familiarity with the web environments for client-server applications.

Ability to configure and debug development and deployment environments.

(9)

Payment Client 3.2.0.0 Deployment Guide 9

About this Document

The Payment Client Deployment Guide is part of the Payment Client documentation set. It contains information on how to install, configure, and manage Payment Client. In addition, this guide contains conceptual information that you should read before you attempt to install the product.

The organisation of this guide is summarised below:

Payment Client Overview on page 11 describes how e-payments work.

Integrating Payment Client on page 15 helps you to select the most suitable integration model and interface for your environment.

Before You Start on page 21 describes how to prepare to install Payment Client.

Installing Payment Client on page 27 describes how to install Payment Client.

Testing Payment Client on page 47 describes how to test Payment Client, PCService and the environment.

Upgrading from Earlier Versions on page 53 describes how to upgrade your previous installation of Payment Client.

Managing Payment Client on page 77 describes how to fine tune Payment Client to suit your requirements, if necessary.

Uninstall Payment Client on page 85 describes how to uninstall your new Payment Client using the uninstaller and manually.

Glossary on page 87 provides a list of commonly used terms in this document with their meanings.

Appendix A on page 93 describes how to configure Payment Client for your environment using the property files.

Appendix B on page 103 describes how merchant-hosted payments work.

Appendix C on page 105 describes how TNS-hosted payments work.

This symbol, when it appears in this manual, warns you of a potential problem. If the problem occurs, you may need to stop and get assistance.

The Light Bulb symbol, when it appears in this User Guide, indicates additional information that is supplementary to the main text.

(10)

If you need help integrating Payment Clientin your merchant application, please contact your Technical Support group.

The information in this document is accurate at the time of publication; however, there may be inaccuracies when applying this document to the Payment Clientin use. For further information, please contact your Technical Support group.

(11)

11 Payment Client 3.2.0.0 Deployment Guide

C

H A P T E R

2

Payment Client Overview

This section is an overview of electronic payments or e-payments and how they are processed by Payment Client.

You must be familiar with this information and understand the core concepts before attempting to install or update Payment Client.

What are e-payments?

e-payments are secure real time payments that transfer funds (via the Internet) between a consumer and the merchant’s financial institutions. This is represented in the following diagram:

(12)

An end-to-end e-payment solution is made up of the following components:

The Merchant application is a business application running on the merchant’s system that uses Payment Client to process payments.

The Integration module is a communication bridge between the merchant application and Payment Client.

Payment Client provides secure communication between the merchant application and the Payment Server. Payment Client can be integrated with a number of systems including merchant applications, Interactive Voice Response (IVR) systems, and integrated ERPs

Payment Server processes merchant transaction requests in real time by sending messages to the payment provider and Payment Client.

The Payment Provider (also called the “acquirer, “acquiring bank” or “merchant bank”) enables the merchant’s facility to accept payments online. It is where the merchant maintains their business banking account and deposits payments.

How e-payments Transfer Funds

e-payments transfer funds via the following steps:

1 The cardholder purchases goods/services from the merchant (for example, in person, via the Internet, over the phone).

2 The merchant application sends a Payment Clientrequest (via the Payment Server) to the merchant’s payment provider.

3 The merchant’s payment provider directs the request to the cardholder’s bank.

4 The cardholder’s bank debits the cardholder’s account and transfers the funds to the merchant’s account.

About e-payment Information Flows

This section describes how information is transferred between the merchant application and the Payment Server.

The Merchant Application

To process a payment, the merchant application must send the required information to the Payment Server. The merchant application uses the Payment Clientto send this information to the Payment Server using two messages:

Transaction Request is sent by the Payment Client to the Payment Server to provide transaction information.

Transaction Response is sent from the Payment Server to the Payment Client to indicate the outcome of the transaction (that is, successful or otherwise).

A Transaction is the combination of a Transaction Request and a Transaction Response. For each customer purchase or order, merchants may issue several transactions.

(13)

Payment Client 3.2.0.0 Deployment Guide 13

The Payment Client

To securely communicate transaction information between the merchant application and the Payment Server, Payment Client:

Formats, encrypts and digitally signs a Transaction Request from the merchant application; and

Sends the Transaction Request to the Payment Server

Receives the Transaction Response, decrypts it and processes the results.

The Payment Server

To complete the transaction the Payment Server:

Processes the Transaction Request

Transfers funds from the cardholder's account to the merchant's Payment Provider account and

(14)

(15)

15 Payment Client 3.2.0.0 Deployment Guide

C

H A P T E R

3

Integrating Payment Client

Payment Client can be used in a variety of different environments and offers a number of different integration options. You must select the most appropriate options for your environment before you begin to deploy Payment Client.

To determine the best way to integrate e-payments in your merchant application, you need to

understand the areas where you can choose different options, and the advantages and disadvantages of each.

This section provides basic information on how to enable your merchant application to process e-payments.

Note: It is important that you choose the relevant options before starting the installation, as the installation prompts you for related information.

How to Select an Integration Model on page 15 answers this question:

Who will manage the payment process (that is, the merchant or the Payment Server)?

How to Select an Interface on page 15 answers this question:

How will your merchant application communicate with the Payment Client?

To identify the best options for your environment, you must understand how e-payments work, as well as the advantages and disadvantages for each option.

How to Select an Integration Model

The integration model determines who manages the payment process. Two integration models are discussed in this section. It describes how to select an integration model for communicating with the Payment Server. It can be either:

2-Party payments is where the cardholder interacts with the merchant application only and the merchant must collect the required information (for example, credit card number, expiry date, etc). This is also called merchant-managed or direct method payments. For more information, see

(16)

Use the following guidelines to select an integration model, depending on your application, preferred communication method, security needs, and future plans.

When to use 2-Party Payments

Consider using 2-Party Payments if:

You are willing to collect card details and manage the associated security and privacy issues. (VISA AIS, MasterCard SDP and so forth).

You are integrating an application with the Payment Client (for example, web, call centre, billing application, Interactive Voice Response (IVR) system) that does not use 3-D Secure

authentication (for example, Verified by Visa™ and MasterCard SecureCode™). For more information see Payment Authentication.

You do not want the cardholder's browser to be redirected away from your web site to the Payment Server for payment processing.

You do not want to display Payment Provider-branded pages in the payment flow.

When to use 3-Party Payments

Consider using 3-Party Payments if:

You are integrating a web browser-based application only. Call centres, IVRs and other applications cannot use this transaction mode.

You want to, either now or in the future, increase security by using 3-D Secure authentication (for example, Verified by Visa™ and MasterCard SecureCode™).

It is acceptable to have the cardholder's browser redirected away from your web site to the Payment Server.

You want the Payment Provider to collect and manage the cardholder’s card details and to manage the associated security and privacy issues.

It is acceptable to display Payment Provider-branded pages in the payment flow.

Note: If you require branding to be consistent throughout a transaction, you can collect card details and include them into the Transaction Request. However the higher risk and responsibility of collecting card details remains the same as in a 2-Party transaction.

(17)

Payment Client 3.2.0.0 Deployment Guide 17

When to combine 3-Party and 2-Party Payments

Consider using both 2-Party and 3-Party if any of the following are true:

You want to use a combination of 3-Party for Web and 2-Party for call centre/IVR/other applications.

You have a web application in which you want to perform some form of repeat payment, as in a subscription, where you want to take advantage of 3-D Secure authentication for the first payment and then use 2-Party payment transactions for each subsequent installment payment. (You must capture and store the card details to do this).

You are willing to use 3-Party transactions for payments and are also using other transactions like refunds and queries, which are all 2-Party mode transactions.

Note 1: If you are collecting card details and want to implement 3-D Secure authentication, you only need to perform 3-Party transactions for those transactions that require 3-D Secure authentication like MasterCard and Visa. Other transactions that don't use 3-D Secure authentication such as Bankcard and American Express can be performed using 2-Party transactions as they don't support

Authentication.

Note 2: Advanced Merchant Administration functions such as captures, refunds, voids and queries all use the 2-Party style of transaction, so if you need to use any of these transaction types through the Payment Client, you will also need to install the Payment Client with the 2-Party options installed. These operations, captures, refunds, voids and queries carry no higher risk than 3-Party as you do not need to pass in cardholder card information to carry out these transaction types.

(18)

How to Select an Interface

In addition to the integration model, you must select the most appropriate interface to access Payment Client from your merchant application using one or more of the following interfaces:

Java interface communicates directly with the Payment Client using native Java calls from the merchant application running in the same Java Virtual Machine (JVM). This method can be used on any operating system that supports Java, however only one Payment Client can be installed in the same JVM using this interface.

TCP/IP Sockets allows a merchant application to communicate to a Payment Client located on the same machine, or on any other machine on the same local secured network via a Payment Client TCP/IP sockets listener (called PCService). More than one Payment Client can be installed using this method. Any programming language that supports TCP/IP Sockets can use this

interface.

Note: In a situation where the system administrator is unable or unwilling to install a Java Runtime Environment (JRE) on an application machine to run the Payment Client, the ideal solution is to install Payment Client on a separate machine with a JVM and communicate via sockets.

COM (Microsoft Windows only) is a variant of the Java installation for Microsoft based programs. It provides a separate component to communicate with the Payment Client via a DLL using:

Sockets-based installation in which the DLL connects to the PCService using TCP/IP sockets to pass socket requests and responses. The DLL communicates with a PCService installed on the local machine (or on a separate machine on the local secured network). More than one Payment Client can be installed in the same JVM using this method.

If the DLL is communicating with a PCService operating on a separate machine, it does not require a Java Runtime Environment to be present on its own machine for the DLL to operate.

Java-based installation that uses a Java Virtual Machine (JVM) and instantiates the Payment Client in the JVM. This allows commands to be passed from the DLL to the Payment Client via JNI. Only one Payment Client can be installed in the same JVM using this interface. The DLL and Payment Client must be installed in the same machine.

Selection Guidelines for Interfaces

This section describes how you should select the best interface for your environment.

(19)

Payment Client 3.2.0.0 Deployment Guide 19

Use the Java interface

Use the Java interface if the following describes your environment:

The operating system supports Java.

The application that is to be integrated with Payment Client is either Java based or able to support Java objects.

Payment Client must be locally installed on the same host as the application to be integrated with the Payment Client.

Only one Payment Client is to be installed.

Multiple merchant profiles can be accommodated on the same Payment Client in the following manner

They are all on the same Payment Server AND

Your Payment Service Provider has configured all profiles to use the same Payment Client (as designated by a single PaymentClientID).

Use the Sockets interface

This interface provides the most generic interface across most programming environments. Use the sockets interface if the following describes your environment:

The application that is to be integrated with Payment Client supports TCP Sockets based communication.

You want flexibility of installation and operation.

A centrally located shared Payment Client is required for multiple applications and/or hosts for ease of management and deployment.

(20)

Use the COM interface if the following describes your environment:

The Microsoft based application that is to be integrated is not able to support TCP/IP Sockets.

The COM.dll is being installed on a Microsoft Operating System. Use COM with Sockets

Use the COM interface with sockets if the following describes your environment:

You want flexibility of installation and operation.

A COM object is provided to abstract TCP sockets communications.

The COM Object can access a Payment Client installed with the sockets interface via a secured local network. The Payment Client with the sockets interface can be installed on the same host or on a centrally located host.

You need to install multiple Payment Clients, now or at some future date. Multiple Payment Clients can use the single COM installation by connecting to different TNS Payment Client.

Use COM

Use COM with Java JNI

Use the COM interface with Java JNI if the following describes your environment:

You cannot or do not wish to use the COM with Sockets interface.

The Payment Client must be locally installed on the same host as the application to be integrated with.

Only one Payment Client is to be installed. Multiple merchant profiles can be accommodated on the same Payment Client as long as they are all on the same Payment Server and your Payment Service Provider has configured all merchant profiles to use the Payment Client that is being installed, as designated by the same PaymentClientID.

The operating system supports Java.

(21)

21 Payment Client 3.2.0.0 Deployment Guide

C

H A P T E R

4

Before You Start

Before you install Payment Client you should ensure that:

Payment Client supports the environment in which the installation will take place

You understand the software that will be installed with Payment Client

You have considered the integration strategy you are going to adopt once Payment Client has been installed

Prerequisites

To install Payment Client you need:

Java Runtime Environment (JRE) installed on your server

Administrator or root privileges, allocated by your System Administrator

Valid Merchant ID issued by the payment provider

Java Runtime Environment (JRE) Requirements

Payment Client requires at least JRE V1.3.0 with Java Secure Sockets Extensions (JSSE). The supported Java versions are Sun Microsystems Inc JRE versions 1.3.x+.

Note: Payment Client v3.2 is not compatible with any version of Java older than Sun Microsystems Inc, Java JRE 1.3.0 or the Microsoft Virtual Machine.

JSSE is part of the standard installation for Sun Microsystems Inc JRE 1.4+. It is an optional installable download for JRE 1.3.x from the Sun Microsystems Inc Java Website (see http://java.sun.com/products/archive/jsse).

For more information on Java or to download the JRE, see http://www.java.sun.com.

(22)

Supported Platforms

Payment Client 3.2 is supported on the following platforms:

Microsoft Windows XP (SP3)

Microsoft Windows 2000 (SP4)

Microsoft Windows Server 2003 (SP2)

Microsoft Windows Server 2008 (SP2)

Solaris 8, Solaris 9 (Sparc), Solaris 10 (Intel and Sparc)

Red Hat Linux RHEL 3

Mac OSX v10.4, OSX v10.5

Included Software

Payment Client ships with the following third party cryptographic libraries:

Bouncy Castle Crypto APIs

Bouncy Castle - Clean Room Java Cryptography Extensions (JCE)

Note: JCE is only required when running Payment Client in a 1.3.x Java Runtime Environment without a JCE.

Payment Client 3.2 also ships with the following libraries:

Library Source commons-lang-2.4.jar http://jakarta.apache.org/commons/ commons-logging-1.1.1.jar http://jakarta.apache.org/commons/ commons-httpclient-2.0.2.jar http://jakarta.apache.org/commons/ commons-io-1.0.jar http://jakarta.apache.org/commons/ log4j.jar http://logging.apache.org/log4j/ jakarta-regexp-1.5.jar http://jakarta.apache.org/regexp

(23)

Payment Client 3.2.0.0 Deployment Guide 23

Connection Details

As part of the installation process you will need to specify details of the client-server connections you will need to make in order to process transactions. For this purpose you should determine the host IP addresses and port numbers of all payment servers with which Payment Client will potentially connect. Instructions for using this information are provided in Installing Payment Client on page 27.

Information Required for a Java Interface

Use the table to enter the details prior to installation. At installation, refer to this table to enter the correct options for your interface.

Item Details

Location of a compatible JVM (java.exe) Installation Directory

The directory where Payment Client will be installed.

Windows default

C:\Program Files\Transaction Network Services\PaymentClient-3.2.0.0

Unix/Linux default /opt/Transaction Network Services/PaymentClient-3.2.0.0

Proxy Configurations _None _SOCKS4 _{SOCKS5 HTTP NTLM}

Proxy Details not required for “None" Proxy Address Proxy Port Username (Optional)

Password (Optional) (not required for SOCKS4)

Domain (Optional) (only required for NTLM)

(24)

Item Details

Location of a compatible JVM (java.exe) Installation Directory

Windows default

Proxy Configurations _None _SOCKS

4 SOCKS 5 HTTP NTLM Proxy Details not required for “None" Proxy Address Proxy Port Username (Optional) Password (Optional) (not required for SOCKS4) Domain (Optional) (only required for NTLM) Sockets

Configuration

Payment Client Service Port IP Address/es

Install as Windows Service (Windows only)

NO YES

Windows Service Name

Location of folder for shortcuts icons

(25)

Payment Client 3.2.0.0 Deployment Guide 25

Information Required for a COM JNI Interface

Note:This is only available on a Windows operating system.

Item Details

Location of a compatible JVM (java.exe) Location of JVM.dll

Installation Directory

Windows default

Proxy Configurations _None _SOCKS 4 SOCKS 5 HTTP NTLM Proxy Details Not required for “None” Proxy Address Proxy Port Username (Optional) Password (Optional) (not required for SOCKS4) Domain (Optional) (only required for NTLM) Location of folder for shortcut icons

(26)

(27)

27 Payment Client 3.2.0.0 Deployment Guide

C

H A P T E R

5

Installing Payment Client

This section describes how to perform a fresh installation of Payment Client 3.2. If you already have an earlier version of Payment Client, see Upgrading from Earlier Versions on page 53.

Before installing Payment Client, ensure that you have familiarised yourself with the topics discussed in Before You Start on page 21.

(28)

Ensure Windows Compatibility

If you are installing Payment Client under Windows 2003 and Windows XP some additional

requirements must be considered. If you are not installing the Payment Client under Windows 2003 or Windows XP, you can skip this section.

Run the Installer in Compatibility Mode

You must ensure that you run the Payment Client installer in Windows 2000 compatibility mode if you require access to COM. To allow the installation of the Payment Client under Windows 2003 Server or Windows XP:

1 Extract the Payment Client bundle that has been provided by your Payment Service Provider to a temporary directory.

2 Right click on the paymentclient_3.2.0.0.exe and select Properties from the menu.

(29)

Payment Client 3.2.0.0 Deployment Guide 29

3 Click the Compatibility tab.

4 Select Run this program in compatibility mode for check box. 5 From the drop-down list select Windows 2000.

6 Click the [Apply] button. 7 Click [OK].

8 Proceed with the installation as detailed.

Exclude the Payment Client from Windows DEP

New security features in Windows 2003 Service Pack 1+ and Windows XP Service Pack 2+ are incompatible with the Payment Client installer, and will cause errors in Payment Client installation.

To avoid these errors, when installing the Payment Client under these Service Packs, you must exclude the client installer from Windows Data Execution Prevention (DEP). To exclude the installer from being affected by DEP:

(30)

1 Right click on My Computer and select Properties from the pop-up menu. The System Properties dialog box displays.

2 Click the Advanced tab.

3 In the Performance group, click Settings. The Performance Options dialog box displays. 4 Click the Data Execution Prevention tab.

5 Click Turn on DEP for all programs and services except those I select:. 6 Click Add… to add the Payment Client to the list of excluded programs. 7 Navigate to the Payment Client installer file paymentclient_3.2.0.0.exe. 8 Select paymentclient_3.2.0.0.exe and click OK.

9 Click OK to close the Performance Options dialog box. 10 Click OK to close the System Properties dialog box.

(31)

Payment Client 3.2.0.0 Deployment Guide 31

Install a Single Payment Client

The steps for a single installation are:

1 Install the Java Runtime Environment (JRE) and Java Secure Sockets Extensions (JSSE). For more information, see Java Runtime Environment (JRE) Requirements on page 21.

2 Obtain the Payment Client software by downloading the software or extracting the software from email as required.

3 Ensure you have all the pre-installation information. See Before You Start on page 21. 4 Extract the files from the distribution to a temporary directory.

5 Start the installer:

Windows users – click the install file paymentclient_[version].exe (for example, ./paymentclient_3_2_0_0.exe) or execute the install file via a command prompt.

UNIX/Linux users – run paymentclient_[version].bin (for example, paymentclient_ 3_2_0_0.bin) or execute the install file via a command prompt.

For GUI installations, the InstallAnywhere installation wrapper requires a colour depth of at least 256 colours; otherwise the installation will fail. On Unix if you cannot run the installer in a GUI, use the text-based version in the console window using –i console option. For example, ./paymentclient_3_2_0_0.bin –i console

6 Follow the prompts and enter the relevant information as required to install the Payment Client. Assuming you have all the pre-installation information (see Before You Start on page 21), installation time on Windows or UNIX/Linux is approximately 5 minutes.

7 The following sections detail step by step examples. If required you can always run the installer again to install a different interface. For a

Step by Step COM Installation (see Step by Step COM Installation on page 32).

Step by Step Installation for a Java Interface (see Step by Step Installation for a Java Interface

on page 45).

Step by Step Installation for a Sockets Interface (see Step by Step Installation for a Sockets Interface on page 46).

(32)

Step by Step COM Installation

The COM option only displays on Microsoft Windows operating systems. There are three different types of COM installations.

Use COM with an existing Payment Client PCService.

This is the preferred option if a Payment Client sockets listener (PCService) is installed. You may have to configure PCService to accept connections from this host. You can add or remove hosts post-install by editing PCService.properties file.

Use COM and install a new Payment Client PCService.

Use this option if a PCService is not installed, or a new PCService is required. If other hosts will also connect to this PCService then it will have to be configured to accept connections from those hosts, which you can do later during the install. You can add or remove hosts post-install by editing the PCService.properties file.

Use COM and install a Payment Client using Java JNI

This option does not require PCService to be installed. It is suitable for installations where Payment Client is only required to process a small number of transactions. With this option the COM Object uses JNI to create and connect to a Java Virtual Machine that will instantiate and run the Java Payment Client. The Java Virtual Machine will be recreated each time a COM object is used.

1 After Payment Client installation starts, the Introduction displays. Read the instructions and click Next.

2 In Choose Install Folder, in Where would you like to install? enter the location on your hard drive where Payment Client is to be installed with all its associated files.

You can click Restore Default Folder to set the location to "C:\Program Files\Transaction Network Services" or Choose to navigate to a required location. Click Next.

3 In Choose An Installation Type, select No if you are installing Payment Client as a fresh installation. Select Yes if you wish to reuse the configuration parameters from a previous

installation of Payment Client. For example, you may want to reuse the parameters configured for Payment Client 3.1.1.1. If you wish to upgrade from your previous installation, skip this section and refer to Upgrading from Earlier Versions on page 53.

4 In Choose Installation Options, select COM. Click Next.

(33)

(34)

Follow Steps 1 to 4 on Step by Step COM Installation on page 32.

1 In Select COM Configuration, select Use COM with an existing Payment Client PCService, and click Next.

(35)

Payment Client 3.2.0.0 Deployment Guide 35

2 In COM Configuration – existing PCService, enter the IP address of the machine hosting Payment Client PCService and the Port that the service is running on. Click Next.

(36)

(37)

4 After Payment Client has been configured, the Pre-Installation Summary displays. If correct, click Install. If not, click Previous and correct your selections.

Installing the Transaction Network Services Payment Client 3.2.0.0 displays, followed by the Please Wait message.

5 If the installation is successful, the Install Complete message displays. Click Done to exit the installer and begin testing your newly installed Payment Client. For more details, see Testing Payment Client on page 47.

(38)

Follow Steps 1 to 4 on Step by Step COM Installation on page 32.

Then follow these steps:

1 In Select COM Configuration, select Use COM and install a new Payment Client PCService, and click Next.

(39)

Payment Client 3.2.0.0 Deployment Guide 39

2 In Choose a Java Virtual Machine the installer determines the Java Virtual Machines installed on the host. The default path to the Java Virtual Machine is shown, ensure that it is correct and that the java.exe file is in the location shown. Click Next.

(40)

being installed on requires a proxy to connect to the Internet, select the type of proxy used from SOCKS4, SOCKS5, HTTP, or NTLM. Click Next.

If you selected None, go to Step 5.

4 On Enter Proxy Data, enter information on the proxy that you wish to connect to. This information can be updated after installation. Click Next.

(41)

Payment Client 3.2.0.0 Deployment Guide 41

5 In Enter Sockets Configuration, specify the configuration of Payment Client PCService and click Next.

(42)

listen on for incoming connections. Enter multiple IP Addresses, separated by a

space.

Payment Client PCService accepts connections only from hosts specified in the IP addresses. For multiple IP addresses, you must separate each IP address with a space. You may add or remove hosts after you install Payment Client by editing the PCService.properties file.

For more information on configuring Payment Client and PCService, see Appendix A - Configuration Syntax on page 93. Install Payment Client sockets listener as a

Windows Service.

This option is only available to Microsoft Windows Operating Systems, for example, Microsoft Windows 2000, or XP. If selected, Payment Client PCService will be installed as a service that will start automatically, when a machine is starting or restarted. The service is installed with the name specified in the Service Name field.

6 In Choose Shortcut Folder, select where you want to install shortcut icons to Payment Client. Click Next.

7 After Payment Client has been configured, the Pre-Installation Summary displays. If correct, click Install. If not, click Previous to correct your selections.

Installing Transaction Network Services Payment Client 3.2.0.0 displays, followed by the Please Wait message.

8 If the installation is successful, the Install Complete message displays. Click Done to exit the installer and begin testing your newly installed Payment Client. For more details, see Testing Payment Client on page 47.

If you get an error message, see Error Codes on page 102.

(43)

Payment Client 3.2.0.0 Deployment Guide 43

Use COM and Install a Payment Client using Java JNI

Follow Steps 1 to 4 in Step by Step COM Installation on page 32.

1 In Select COM Configuration, select Use COM and install a Payment Client using Java JNI and click Next.

(44)

JNI technology to create a Java Runtime Environment to communicate with Payment Client from the COM object. The default jvm.dll for the machine displays. Click Next.

Follow Steps 6 to 8 of Use COM and install a new Payment Client PCService on page 38.

(45)

Payment Client 3.2.0.0 Deployment Guide 45

Step by Step Installation for a Java Interface

Use the steps below to install Payment Client using a Java interface.

1 After Payment Client installation starts, the Introduction displays. Read the instructions and click Next.

2 In Choose Installation Options, select Java. Click Next. (See Choose Installation Options in

Step by Step COM Installation on page 32.)

3 In Choose a Java Virtual Machine the installer determines the Java Virtual Machines installed on the host. The default path to the Java Virtual Machine is shown, ensure that it is correct and that the java.exe file is in the location shown. Click Search for Others or Choose Another to browse to and select another java.exe file if necessary. Click Next.

(46)

Step by Step Installation for a Sockets Interface

See Install Multiple Payment Clients on page 46.

Install Multiple Payment Clients

If you need to process payments between multiple payment providers (for example, an ISP), you must install multiple Payment Clients and select the sockets installation option.

Note: Each Payment Client can only communicate with a single Payment Server.

The steps to install multiple Payment Clients are:

1 Run the Installer for each Payment Client. 2 Select the Sockets installation option.

3 Specify a different installation directory and port for each Payment Client. Note that if installing the Payment Client as a Windows Service (available for Microsoft Windows based installations only), the entry in the Services list will reflect the latest PCService installed only.

4 If installing the COM Interface, the default COM object will use the latest Payment Client installed. 5 Test each installation using the procedure outlined in Testing Payment Client on page 47.

Step by Step Installation for Multiple Payment Clients

Do the following for each Payment Client:

1 After Payment Client Installation starts, the Introduction displays. Read the instructions and click Next.

2 In Choose Installation Options, select Sockets. Click Next. (See Step 2, Choose Installation Options in Step by Step COM Installation on page 32.)

3 In Choose a Java Virtual Machine the installer determines the JVMs installed on the host. Ensure that the default path to the JVM as displayed is correct. Click Next. (See Step 2, Choose Java Virtual Machine in Use COM and install a new Payment Client PCService on page 38.) 4 On Choose Proxy Configuration, either select None, or, if the network that Payment Client is being installed on requires a proxy to connect to the Internet, select the type of proxy used from SOCKS4, SOCKS5, HTTP, or NTLM. Click Next. If you selected None, go to Step 7.

5 On Enter Proxy Data, enter the Proxy Address and Proxy Port of the proxy that you wish to connect to. This information can be updated after installation. You can also optionally enter Username and Password. (See Step 4, Enter Proxy Data in Use COM with an existing Payment Client PCService on page 34.)

6 Ensure you enter a different port for every instance of Payment Client. Click Next.

7 Follow Steps 5 to 8 of Use COM and install a new Payment Client PCService on page 38.

(47)

47 Payment Client 3.2.0.0 Deployment Guide

C

H A P T E R

6

Testing Payment Client

After installing your new Payment Client, you should test the installation to confirm that Payment Client is working correctly and can perform transactions with the Payment Server. To do this you should:

1 Use the Diagnostic Tool (see Use the Diagnostic Tool on page 47)

2 Test the Sockets Interface (see Test the Sockets Interface on page 50) (applicable to Sockets interface only)

3 Use the PCCOM Tool (see Use the PCCOM Tool on page 51) (applicable to COM interface only) 4 Run the Example Code (see Run the Example Code on page 52)

Use the Diagnostic Tool

This section describes how to test Payment Client using the diagnostic tool. These tests ensure that Payment Client itself is working correctly by instantiating itself in its native Java environment.

Note: You must run a successful test transaction to ensure the test data is correct. If you cannot run a successful test transaction, do NOT continue the test process.

The steps for testing Payment Client with the diagnostic tool are:

1 Obtain the prerequisites for the diagnostic tool.

2 Configure the diagnostic tool, (only required for TNS-hosted payments.) 3 Run the diagnostic tool and check the results.

Obtain the Prerequisites for the Diagnostic Tool

(48)

To configure the diagnostic tool for TNS hosted payments, you must enter a Client Return URL where the Payment Server will send the DR.

Client Return URL information

You can enter the Client Return URL in Payment Server Merchant Administration via Merchant Setup » Merchant Configuration. The URL must be a valid format with DR=${DR} appended as a URL-encoded variable. For example, you can set the Client Return URL using any of the following valid examples:

http://localhost?DR=${DR} http://127.0.0.1?DR=${DR} https://localhost?DR=${DR}

http://www.somehost.com/web/script.cgi?DR=${DR}

For more information on configuring this setting, see the Merchant Administration User Guide.

Run the Diagnostic Tool

You can now run the Diagnostic Tool and check the results.

To run the diagnostic tool:

On Windows:

Go to Start menu > All Programs > Transaction Network Services > PaymentClient-3.2.0.0, and click Test Payment Client; or

Run the PaymentClientDiagnostics.exe file in the \bin\ directory of Payment Client installation directory.

On Linux:

Run the PaymentClientDiagnostics.exe file in the /bin/ directory of Payment Client installation directory

You must have write access to Transaction Network Services/PaymentClient-3.2.0.0/bin directory.

Note: You can terminate the test at any time using Ctrl-C.

The diagnostic tool runs different tests depending on whether you select Merchant-hosted or TNS-hosted payments.

You can check the results of the diagnostic tool by viewing the log file. The diagnostic tool logs the results to the file with the format PaymentClientDiagnosticsddmmYYYYmmhhss.log in the

Transaction Network Services/PaymentClient-3.2.0.0/bin directory.

The following sections demonstrate the diagnostic tool for Merchant-hosted and TNS-hosted payments.

(49)

Payment Client 3.2.0.0 Deployment Guide 49

Example for Merchant Hosted payments

Run the diagnostic tool.

1 Select test type. Type 1 (MOTO) or 3 (MOTO including currency) and click Enter. 2 Enter merchant ID. Enter the test merchant ID for the transaction.

The test merchant ID should be provided to you by the Payment Server Provider.

3 Enter currency. Enter a valid currency configured for the merchant. This prompt appears if you choose test type 3 (MOTO including currency)

4 Enter session ID. Enter a unique session ID for the transaction.

5 Select or enter card information. Select the card number from the list displayed. To enter another card, type Z and manually enter the card number.

6 Enter card expiry date in YYMM format (Optional). This step is only required if you manually entered a card number in step 5.

7 Perform test. The diagnostic tool performs the test and reports whether the test was successful or failed.

For example, if you run the test using the following information:

test type: MOTO merchant id: m001

currency: session id: 1

card number: 5123456789012346 card expiry: 0305

The diagnostic tool displays the following output:

merchant id: m001 currency: session id: 1 card number: 5123456789012346 card expiry: 0305 purchase amount: 100 locale id: en_AU

dr url:Testing creation of PaymentClient object ... OK Testing sending of MOTO digital order object ... OK Checking the results from the PaymentServer ... OK

(50)

session id: 1

card number: 5123456789012346 card expiry: 0305

purchase amount: 100 locale id: en_AU

dr url:Testing creation of PaymentClient object ... OK Testing sending of MOTO digital order object ... OK Checking the results from the PaymentServer ... OK

Example for TNS-hosted payments

Run the diagnostic tool.

1 Select test type. Enter 2 (SSL) or 4 (SSL including currency) and click Enter. 2 Enter merchant ID. Enter the test merchant ID for the transaction.

The test merchant ID should be provided to you by the Payment Server Provider.

3 Enter currency. Enter a valid currency configured for the merchant. This prompt appears if you choose test type 4 (SSL including currency).

4 Enter session ID. Enter a unique session ID for the transaction.

5 Perform test transaction. The diagnostic tool opens a web browser window for you to perform a test transaction. If a browser window is not opened, the diagnostic tool prompts you to copy and paste the Digital Order URL into a new browser window.

6 Copy browser address. When the transaction completes, the diagnostic tool displays a broken URL page. Copy the URL from the Address bar of the browser and paste it into the diagnostic tool. If cannot locate the DigitalReceipt text from the browser, fail the test by entering “Z”.

7 Review test result. The diagnostic tool reports whether the test was successful or failed.

Fix Communication Errors

Merchant-hosted transactions that cannot pass through the firewall display an error message similar to:

E5231:QSI.util.tls.TLSException: Error getting TLS connection to paymentserver.anybank.com.test:443

In this situation, check your network and firewall connectivity. For more information, see Test Connectivity on page 81.

Test the Sockets Interface

Use the PCService to test communications with Payment Client. A manual test ensures that PCService on Payment Client is correct and working.

Note: If you installed multiple Payment Clients, you must test each Payment Client.

(51)

Test PCService

To test the sockets:

1 Start PCService for the Payment Client.

For more information, see Configure PCService on page 96. 2 Open a connection.

Telnet to Payment Client port by typing telnet 127.0.0.1 9050 (where 9050 is the PCService port). A telnet session opens if successful; otherwise the message: Could not open a

connection to host ... displays. 3 Check that PCService is running

Run an "echo" command by typing 1,test. The response should be 1,echo:test 4 Check the connection

Run a "getDigitalOrder" command by typing 2,1,<test Merchant ID>,100,en,

For example, type:

2,1,test123456,100,en,

If the test result is a success, the response will be 1,https://<url>/pay?DO=<encrypted digital order>. If the test fails, you will get 0,0. For more details on these commands, see Payment Client Reference Guide.

5 Close the connection by typing 99,

This confirms the Payment Client communications are working.

If you cannot complete the connection, PCService has not been started or Payment Client is not installed or configured correctly.

Use the PCCOM Test Tool

This section describes how to test your COM object using the PCCOM test tool. This test ensures that COM object itself is working correctly (Windows only).

(52)

Run the Example Code

Payment Client ships with example code that demonstrates how to use it in different merchant

application environments, in a variety of languages. Running the appropriate example code allows you to test the environment that the merchant’s application is running in.

The example code demonstrates the integration code you need to write for your merchant application. For more information, see the relevant code examples.

(53)

53 Payment Client 3.2.0.0 Deployment Guide

C

H A P T E R

7

Upgrading from Earlier Versions

Payment Client 3.2 and the earlier versions of Payment Client can both co-exist and run on the same system without interfering with each other's processes.

To upgrade from an earlier Payment Client version, perform the following steps:

1 Prepare for your upgrade

This section describes the considerations you need to be aware of before upgrading to your new Payment Client. For more details, see Prepare for Your Upgrade on page 54.

2 Install the new version of Payment Client as an upgrade

Select "Re-use configuration from a previous installation of Payment Client" during installation. For more details, see Upgrade Your Existing Payment Client on page 58.

3 Test the installation of the new Payment Client See Testing Payment Client on page 47.

4 Update Your Application Integration to use the new Payment Client See Update Your Application Integration on page 62.

(54)

Prepare for Your Upgrade

Depending on the options you selected when you installed your existing Payment Client, you will currently be using one of the following configurations:

Java Interface

Sockets Interface

COM Interface (Windows only)

1. Use COM with an Existing Payment Client PCService 2. Use COM and Install a new Payment Client PCService 3. Use COM and Install a Payment Client using Java JNI

When you install the new version of Payment Client as an upgrade, you will need to know the location of the setup.properties file of your existing Payment Client. This file resides in the config directory of your existing installation.

Each of the aforementioned configurations have their installation components installed on a single machine except COM option 1 (Use COM with an Existing Payment Client PCService). In the case of COM option 1, typically you will have installed your existing Payment Client and PCService on a machine that is remote from your payment application and your existing COM object. It is this remote machine that will contain the setup.properties file of your existing Payment Client. Hence, your upgrade will need to be performed on the remote machine rather than the machine that hosts your payment application. It's not necessary to perform an upgrade on your COM object with COM Option 1.

The following sections illustrate the typical states for each of the configurations both before and after the installation of your new Payment Client as an upgrade. When you have reached the After state following the upgrade, you will be in a position to test your new Payment Client. As mentioned, your payment application will still be able to run with your previous version of Payment Client.

Before refers to a typical state that you are currently in.

After refers to a typical state where you have installed your new Payment Client as an upgrade.

(55)

Java Interface

(56)

Use COM with an Existing Payment Client PCService

(57)

Use COM and Install a new Payment Client PCService

(58)

Upgrade Your Existing Payment Client

As described in the previous section, Prepare for Your Upgrade on page 54, you are currently in the Before state. To move to the After state, you will need to install your new Payment Client as an upgrade.

To upgrade from your existing version:

1 Run the Payment Client installer. After Payment Client installation starts, the Introduction displays. Read the instructions and click Next.

2 In Choose Install Folder, enter the location on your hard drive where your new Payment Client is to be installed with all its associated files.

You can click Restore Default Folder to set the location to "C:\Program Files\Transaction Network Services" or Choose to navigate to a required location. Click Next.

(59)

Payment Client 3.2.0.0 Deployment Guide 59

3 In Choose An Installation Type, select Yes to reuse the configuration parameters from your previous installation of Payment Client.

(60)

C:\Dialect\PaymentClient\config.

The installation will use this information to locate the "setup.properties" file from your previous installation.

(61)

5 If your installation uses the Sockets interface, the Enter Sockets Configuration screen displays. Specify the configuration of Payment Client PCService and click Next.

The port number of the new PCService defaults to the port number of the previous PCService incremented by 1. However, if this is not suitable you may select another port for the PCService to monitor. Note that you should NOT select the port number being monitored by the previous installation; otherwise the new PCService will fail to start.

6 In Choose Shortcut Folder, select where you want to install shortcut icons to Payment Client. Click Next.

7 After Payment Client has been configured, the Pre-Installation Summary displays. If correct, click Install. If not, click Previous and return to Step 3.

Installing Transaction Network Services Payment Client 3.2.0.0 displays, followed by the Please Wait message.

(62)

Update Your Application Integration

As mentioned previously, before continuing you must first test your upgrade. See Testing Payment Client on page 47.

The integration of your new Payment Client for your production environment varies based on the interfaces you are currently using. The following sections illustrate the typical states for each of these interfaces both before and after updating your application integration.

Java Interface on page 63

Sockets Interface on page 64

COM Interface on page 66

Before refers to a typical state where you have successfully installed and tested the new Payment Client on your machine.

After refers to a typical state where you have updated your application integration to use your new Payment Client.

(63)

Payment Client 3.2.0.0 Deployment Guide 63

Java Interface

Note: Before integrating the new Payment Client with your payment application, test the Payment Client. See Use the Diagnostic Tool on page 47.

If you are currently using the Java interface:

1 Stop your payment application.

2 Change the java classpath of your payment application to include the path of your new Payment Client classes instead of the earlier version. For example, if the java classpath was set to

C:\Dialect\PaymentClient\classes, change it to C:\Program Files\Transaction Network Services\PaymentClient-3.2.0.0\classes

(64)

Note: Before integrating the new Payment Client with your payment application, test your new PCService. See Test the Sockets Interface on page 50.

If you are currently using the Sockets interface:

1 Stop the new PCService installed using the new Payment Client. If you've registered PCService as a Windows Service, see Starting and Stopping Payment Client on page 77.

2 Modify the port number in C:\Program Files\Transaction Network Services\PaymentClient-3.2.0.0\config\PCService.properties to use the port number used by the earlier version of Payment Client.

For example, PCService.properties file might have the following configuration where the new Payment Client connects to PCService using port 9051.

port=9051

# Comment out the line above and uncomment the next line

# to use the same port number as the previous installation (if any) # port=9050

To switch your new Payment Client to use port 9050, comment "port=9051" and uncomment

"port=9050" as follows.

#port=9051

# Comment out the line above and uncomment the next line

# to use the same port number as the previous installation (if any) port=9050

4 Stop the old PCService used by the earlier version of Payment Client. 5 Start the new PCService.

6 Start your payment application.

(65)

(66)

The integration steps for a COM-based installation differ with the COM option you are currently using.

The three COM options are:

Use COM with an Existing Payment Client PCService

The upgrade for this COM option includes a new Payment Client and a new PCService. You will continue to use your old COM object.

Use COM and Install a new Payment Client PCService

The upgrade for this COM option includes a new Payment Client, a new PCService, and a new COM object.

Use COM and Install a Payment Client using Java JNI

The upgrade for this COM option includes a new Payment Client and a new COM object.

Note: Before integrating the new Payment Client with your payment application, test your new COM object with PCCOM tool, PCService with telnet, and Payment Client with the Diagnostic tool. For more details, see Testing Payment Client on page 47.

Use COM with an Existing Payment Client PCService

For this COM option, we assume that your payment application and COM object reside on Machine A, and your Payment Client and PCService reside on Machine B (see diagram below).

2 On Machine A, modify the port number in bin\ PCCOM.ini (for example,

C:\Dialect\PaymentClient\bin\PCCOM.ini) to match the port number configured for the new Payment Client PCService on Machine B. In the socketport section of PCCOM.ini file, modify the value for the field "socketport" to match the port number of the new PCService. For example,

socketport=9051

Note: To retrieve the port number of the new PCService, go to <new Payment Client Installation directory>\config\PCService.properties on Machine B. The value for the field "port" in this file must match the value of "socketport" in <old Payment Client Installation directory>\bin\PCCOM.ini on Machine A.

(67)

(68)

Use COM and Install a new Payment Client PCService

During installation on your production machine, you may have chosen not to register your new PCCOM.dll due to outage issues. This would have allowed you to test the new COM object using the PCCOM test tool. See Use the PCCOM Test Tool on page 51.

To update your application integration for the new Payment Client, you must now register your new PCCOM.dll. This will automatically unregister your old COM object.

2 Double-click RegisterCOM.cmd in the bin directory of the new Payment Client installation. For example, C:\Program Files\Transaction Network Services\PaymentClient-3.2.0.0\bin\RegisterCOM.cmd

Note: Ensure that you start your new PCService before registering PCCOM.dll. If not, the registration will fail.

(69)

Payment Client 3.2.0.0 Deployment Guide 69

(70)

Use COM and Install a Payment Client using Java JNI

During installation on your production machine, you may have chosen not to register your new PCCOM.dll due to outage issues. This would have allowed you to test the new COM object using the PCCOM test tool. See Use the PCCOM Test Tool on page 51.

To update your application integration for the new Payment Client, you must now register your new PCCOM.dll. This will automatically unregister your old COM object.

2 Double-click RegisterCOM.cmd in the bin directory of the new Payment Client installation. For example, C:\Program Files\Transaction Network Services\PaymentClient-3.2.0.0\bin\RegisterCOM.cmd

(71)

Payment Client 3.2.0.0 Deployment Guide 71

Roll Back Your Application Integration

There may be occasions where you may decide to roll back your application integration to use your previous installation of Payment Client. Additionally, you will need to follow the roll back instructions before you uninstall your new Payment Client to ensure that your previous Payment Cl

Payment Client

Payment Client 3.2.0.0

Contents

Contents v

7 Payment Client 3.2.0.0 Deployment Guide

Preface

About Payment Client

 RHEL3, RHEL4, RHEL5

Payment Client Documentation Set

Audience

Payment Client 3.2.0.0 Deployment Guide 9

About this Document

This symbol, when it appears in this manual, warns you of a potential problem. If the problem occurs, you may need to stop and get assistance.

Payment Client Overview

How e-payments Transfer Funds

About e-payment Information Flows

Payment Client 3.2.0.0 Deployment Guide 13

The Payment Client

The Payment Server

15 Payment Client 3.2.0.0 Deployment Guide

Integrating Payment Client

How to Select an Integration Model

When to use 3-Party Payments

Payment Client 3.2.0.0 Deployment Guide 17

When to combine 3-Party and 2-Party Payments

How to Select an Interface

Selection Guidelines for Interfaces

Payment Client 3.2.0.0 Deployment Guide 19

Use the Java interface

Use the Sockets interface

21 Payment Client 3.2.0.0 Deployment Guide

Before You Start

Prerequisites

Supported Platforms

Included Software

Payment Client 3.2.0.0 Deployment Guide 23

Connection Details

Item Details

Item Details

NO YES

Information Required for a COM JNI Interface

Note:This is only available on a Windows operating system.

27 Payment Client 3.2.0.0 Deployment Guide

Installing Payment Client

Run the Installer in Compatibility Mode

Payment Client 3.2.0.0 Deployment Guide 29

Exclude the Payment Client from Windows DEP

Payment Client 3.2.0.0 Deployment Guide 31

Install a Single Payment Client

Step by Step COM Installation

Payment Client 3.2.0.0 Deployment Guide 35

Payment Client 3.2.0.0 Deployment Guide 39

Payment Client 3.2.0.0 Deployment Guide 41

Windows Service.

Payment Client 3.2.0.0 Deployment Guide 43

Use COM and Install a Payment Client using Java JNI

Payment Client 3.2.0.0 Deployment Guide 45

Step by Step Installation for a Java Interface

Step by Step Installation for a Sockets Interface

Note: Each Payment Client can only communicate with a single Payment Server.

Step by Step Installation for Multiple Payment Clients

47 Payment Client 3.2.0.0 Deployment Guide

Testing Payment Client

Use the Diagnostic Tool

1 Obtain the prerequisites for the diagnostic tool.

Obtain the Prerequisites for the Diagnostic Tool

Run the Diagnostic Tool

Note: You can terminate the test at any time using Ctrl-C.

Payment Client 3.2.0.0 Deployment Guide 49

Example for Merchant Hosted payments

1 Select test type. Type 1 (MOTO) or 3 (MOTO including currency) and click Enter. 2 Enter merchant ID. Enter the test merchant ID for the transaction.

Example for TNS-hosted payments

1 Select test type. Enter 2 (SSL) or 4 (SSL including currency) and click Enter. 2 Enter merchant ID. Enter the test merchant ID for the transaction.

7 Review test result. The diagnostic tool reports whether the test was successful or failed.

Fix Communication Errors

Note: If you installed multiple Payment Clients, you must test each Payment Client.

Test PCService

1 Start PCService for the Payment Client.

Use the PCCOM Test Tool

53 Payment Client 3.2.0.0 Deployment Guide

RHEL3, RHEL4, RHEL5