oracle i payment

8/9/2019 Oracle i Payment

1/76

For Professional Use Only

Currently only available in English.

A usage Professional Uniquement

Disponible en Anglais uniquement pour l'instant.

Oracle iPaymentBack-End PaymentServlet Installation

Guide


2/76

2006 PayPal Inc. All rights reserved. PayPal, the PayPal logo, Payflow, and Payflow Pro are registeredtrademarks of PayPal Inc. Other trademarks and brands are the property of their respective owners.

The information in this document belongs to PayPal Inc. It may not be used, reproduced or disclosedwithout the written approval of PayPal Inc.

PayPal (Europe) Ltd. is authorised and regulated by the Financial Services Authority in the UnitedKingdom as an electronic money institution. PayPal FSA Register Number: 226056.

Notice of Non-Liability

PayPal Inc. is providing the information in this document to you AS-IS with all faults. PayPal Inc. makesno warranties of any kind (whether express, implied or statutory) with respect to the informationcontained herein. PayPal Inc. assumes no liability for damages (whether direct or indirect), caused byerrors or omissions, or resulting from the use of this document or the information contained in thisdocument or resulting from the application or use of the product or service described herein. PayPal Inc.reserves the right to make changes to any information herein without further notice.

PayPal Inc. does not guarantee that the features described in this document will be announced or madeavailable to anyone in the future.

Oracle iPayment Servlet Installation Guide

200033


3/76

Oracle iPayment Servlet Installation Guide iii

Contents

Chapter 1 Int roduct ion . . . . . . . . . . . . . . . . . . . . . . . . . 1

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PayPal Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Oracle iPayment Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

How to Contact Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Ins tal l ing and Conf igur ing on Windows . . . . . . . . . . . 5

Manually Installing the PayPal BEP Servlet on Windows . . . . . . . . . . . . . . . . . . . 5

Uninstalling the BEP Servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3 Ins tal l ing and Conf igur ing on Non-Windows Plat forms . . .13

Manually Installing the PayPal BEP Servlet on Non-Windows Platforms . . . . . . . . . . 13

Uninstalling the BEP Servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4 Regis ter ing and Test ing . . . . . . . . . . . . . . . . . . .21

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Registering the BEP Servlet in iPayment . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Testing the Installation Using the Oracle iPayment User Interface . . . . . . . . . . . . . 27

Testing the Installation Using PayPals Sample Store . . . . . . . . . . . . . . . . . . . . 32

Processing Live Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 5 Bu i ld ing Your Own Web Si te . . . . . . . . . . . . . . . . 37

Appen dix A Tran sac t ion Decl ine or Er ror RESULTs an d RESPMSGs . . 39

Appen dix B Mapping PayPal Param et er s to iPaymen t Param et er s . . . . 45

Parameters Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45


4/76

Contents

iv Oracle iPayment Servlet Installation Guide

Appen dix C Troubles hoot ing . . . . . . . . . . . . . . . . . . . . . . . 63

Enabling Debug Log File Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Before Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Appen dix D Manual ly Un instal l ing the PayPal BEP Serv let . . . . . . . 65

Appen dix E En crypt ing Your Datab as e Us er Password . . . . . . . . . 69

Ind ex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71


5/76

Oracle iPayment Servlet Installation Guide 1

1 Introduct ion

This guide provides information on installing and configuring the PayPal Back-end Payment

System (BEP) servlet for use with Oracle iPayment.

Intended Au dience

This guide is for merchants and administrators who are implementing the Oracle iPayment

module with Oracle Applications and the PayPal BEP servlet.

You should have knowledge of the following essentials:

Java language

Web servers, servlets, and their configuration

How to configure Java servlets with Apache Web server. In particular, you should know

where to find Apache and JServ configuration files for the Apache Web server. For more

information, see the Apache documentation available at the following location:

http://www.apache.org.

Oracle Applications (merchants version)

Oracle iPayment

NOTE

: In this guide,yourefers to the merchant or administrator.This guide assumes that you are familiar with the documents listed in Related Documents on

page 3.

Overview

Oracle iPayment is an electronic payment processing solution designed for application

developers, system integrators, and enterprises that need to payment enable new or existing

Internet or client/server e-commerce applications.

PayPal Payment Services Payflow Pro is a real-time Secure Socket Layer (SSL) paymentsystem supporting credit card transactions using pure Java libraries. Payflow Pro supports all

iPayment core operations. It also supports the following additional operations through the

iPayments extensibility API:

Fraud Protection services

Purchase cards, Level 2 and 3

Buyer Authentication
http://www.apache.org./http://www.apache.org./


6/76

Introduction

Overview1

2 Oracle iPayment Servlet Installation Guide

The BEP servlet integrates Payflow Pro with Oracle iPayment to manage online payment

processing.

FI GURE1 .1 BEP servlet integration

Oracle iPayment uses the BEP servlet to perform secure online transaction processing for

Internet merchants. Merchant administrators perform iPayment administration using browser-

based administration pages.

Prerequisites

The following are prerequisites to using the BEP servlet:

Oracle Applications must be installed.

Oracle iPayment must be installed with responsibility, menu, security roles, andpermissions. See the Oracle documentation for details.

You must create an Administration User for Oracle iPayment. See the Oracle

documentation for details.

PayPal has tested with Oracle Applications 11.5.9 and 11.5.10 on AIX 5.2 and Windows.

iStore (or anyiPayment

core operation)

OrderManagement

AdministrativeInterface

Order Capture

AccountsReceivable

JavaAPIs

iPaymentengine

ECapp.

ECservlet

Extensibility

HTTP(S)Adapter

BEP

APIs

VeriSignServlet


7/76


Introduction

Related Documents1

Related Docum ents

The following documents support information found in this guide. You should read these

documents before using this guide.

PayPal Docum ents

Payflow Pro Developers Guide

Payflow Pro Fraud Protection Services Users Guide

Oracle iPayment Documents

Oracle iPayment Concepts and Procedures Release 11i

Oracle iPayment Implementation Guide Release 11i

How to Contact Customer Support

For problems with transaction processing or your connection to PayPal, contact Payflow

Support [email protected].

For a list of tasks that you need to complete before contacting Customer Support, see Before

Contacting Customer Support on page 63.
http://../PayflowPro/TitlePayflowPro_Guide.pdfhttp://../PayflowPro_FPS/PFP/Title_PayflowPro_FPS_Guide.pdfhttp://../PayflowPro_FPS/PFP/Title_PayflowPro_FPS_Guide.pdfhttp://../PayflowPro/TitlePayflowPro_Guide.pdf


8/76

Introduction

How to Contact Customer Support1



9/76


2 Instal l ing and Confi gur ing onWindowsThis chapter guides you through installing and configuring the PayPal Payment Services

servlet for use with Oracle iPayment on Windows.

The PayPal BEP servlet is not configured as a part of Oracle Applications Rapid Installation

process. Follow the appropriate procedures in this section to install it. PayPal BEP servlet

installation on Windows uses the directory references described in Table 2.1.

Manually Instal l i ng t he PayPal BEP Servl et on Wind ows

NOTE: Before you install or uninstall the PayPal integration, be sure that the Oracle database

instance is up and running. You should be able to log into the database by using

SQLPlus, as follows:

C:\> sqlplus /@ is the database user ID

is the database password

is the database instance ID

The following procedure explains how to manually install the PayPal BEP Servlet. If you are

using PayPal BEP Servlet version 3.1, follow the guidelines in Manually Uninstalling the

PayPal BEP Servlet on page 65before installing the current servlet version.

TABLE2 .1 BEP Servlet path and directory no tation

Notation Description

%VERISIGN_TOP% Represents the PayPal directory into which the pf pro_i payment . zi p

file is unzipped, as shown in Figure 2.1.

If, for example, you unzipped pfpro_i payment . zi pintoD: \ oracl e\ , %VERISIGN_TOP% would representD: \ oracl e\ ver i si gn, the top-level directory in the directorystructure.

%ORACLE_TOP% Represents the top-level Oracle directory for Oracle Apps, for example,

D: \ oracl e\ vi sora.

%APPL_TOP% Represents the top-level application directory for Oracle Apps, for

example D: \ oracl e\ vi sappl .

%COMN_TOP% Represents the top-level Oracle Apps common directory, for example,

D: \ oracl e\ vi scomn.

%JAVA_HOME% Java home directory of your JDK, for example, C: \ j 2sdk1. 4. 2


10/76

Installing and Configuring on Windows

Manually Installing the PayPal BEP Servlet on Windows2


Step 1 Unzip the pfpro_ipayment file

Unzip the pf pro_i payment . zi pfile to a local directory. The file unzips into the directorystructure shown in Figure 2.1. The directory contains all files required to configure iPayment

to use the PayPal BEP.

FI GURE2 .1 pfpro_ipayment directory struc ture

TABLE2 .2 pfpro_ipayment directory contents

Directory or File Contents / Description

certsdirectory f 7389f d. 0(digital certificate)

cl assesdirectory Contains the following directories:

com directory - Contains ver i si gn\ i Payment \ *. cl ass

(Classes required by the PayPal objects. The class files arein the veri si gn\ i Payment subdirectories such asbi zcompand buyerauth.)

i byextenddirectory - ContainsTxnCust omi zer_vps. cl ass(PayPal requires iPaymentextensibility. These classes should be accessible to

iPayment)

docsdirectory Contains Oracl ei Payment . pdf

l i bdirectory Contains Ver i si gn. j ar

sampl est oredirectory Contains files for PayPal sample store:

Er ror . j sp- Error page for Sample Store i PaymentSampl eStore. j sp- Main page for Sample

Store

Veri Si gnLogo. J PG- logo to be displayed on SampleStore


11/76


12/76




5. Copy the following directory from the %VERISIGN_TOP%\ payf l owpro\ i payment directory into the %ORACLE_TOP%\ 8. 0. 6 di rectory:

certsdirectory

Step 4 Download Xerces XML Parser

1. Download the Xerces-J 2.7.1 package (XML parser) called Xerces- J - bi n. 2. 7. 1. zi pfrom Apaches archive download Web site at http://archive.apache.org/dist/xml/xerces-j/

2. Extract the following files from this package and place them in the%APPL_TOP%\ i by\ 11. 5. 0\ l i bdirectory:

xercesI mpl . j ar

xml -api s. j ar

Step 5 Configure Java Secure Sockets Extension (JSSE)

NOTE: Step 5 is not required if you are using JDK 1.4.x or higher. Oracle iPayment 11.5.10

and higher use JDK 1.4.x. To find out which version of the JDK you have, use the

following command: java -version

To configure the JSSE, use the following procedure:

1. Download the JSSE from the following location:

http://java.sun.com/products/jsse/index-103.html

2. Place the following JSSE jar files into the

%ORACLE_TOP%\ i AS\ Apache\ j dk\ j re\ l i b\ ext directory:

j cer t . j ar j net . j ar

j sse. j ar

Step 6 Modify vpsipayment.properties

Table 2-3 shows the entries in the vpsi payment . propert i esfile. You are going to modifythese entries to reflect your current environment, as described below:

1. Edit the properties in the

%ORACLE_TOP%\ 8. 0. 6\ ver i si gn\ vpsi payment . proper t i esfile as indicated inTable 2.3. If no default value is shown in the table for a parameter, the parameter is empty.

NOTE: Be sure that you do not add spaces, extra characters, or carriage returns at the end of

any of the lines in the vpsi payment . propert i esfile.

2. Important:Replace the value of the dbpwd entry in your version of the

vpsi payment . propert i esfile with your encrypted database user password. For
http://archive.apache.org/dist/xml/xerces-j/http://java.sun.com/products/jsse/index-103.htmlhttp://archive.apache.org/dist/xml/xerces-j/http://java.sun.com/products/jsse/index-103.html


13/76




instructions on how to encrypt your password, see Appendix E, Encrypting Your Database

User Password.

Step 7 Modify zone.properties

1. Modify the zone.properties located in a directory such as:%ORACLE_TOP%\ i AS\ Apache\ J serv\ et c

2. Insert the contents of the Windows section from the%VERI SI GN_TOP%\ ver i si gn\payf l owpro\ i payment \ zone. propert i es. ver i si

TABLE2 .3 vpsipayment.properties parameters to be modified

Name Default Value Description

hostname test-payflow.verisign.com HPayPalost name

For live transactions, use payflow.verisign.com

For test transactions, use test-payflow.verisign.com

port 443 Payflow Pro server port number

timeout 30 Transaction timeout value sent to the Payflow Pro server

certs /mv1/oracle/demoora/8.0.6/certs Digital certificates folder containing the certificate file,

f y3d89f d. 0

proxyHost Proxy server address. Use the proxy parameters for

servers behind a firewall. Your network administrator can

provide the values. Leave blank if you are not using a

proxy.

proxyPort 0 Proxy server port. Leave the 0 if you are not using a proxy.

proxyUser Proxy server logon ID. Leave blank if you are not using a

proxy.

proxyPwd Proxy server logon password. Leave blank if you are not

using a proxy.

baurl test-buyerauth.verisign.com URL for Buyer Authentication server

termurl http://machine.yourdomain.com:8000/servlets/oramipp_ Payee2VPS

Merchant URL for Buyer Authentication. The format is:http://:/servlets/oramipp_Payee2VPS

dburl jdbc:oracle:thin:@machine.yourdom

ain.com:1521:DEMO

JDBC database connection URL for the Oracle Apps

instance. The format is:

jdbc:oracle:thin:@::

NOTE: is your database listener port number,

not your Apache Web server port.

dbuid apps Database user ID

dbpwd apps Database user password (encrypted)


14/76




gnfile between the Begin Customizations and End Customizations tags of yourzone. proper t i esfile.

If the Begin and End tags are not present, then insert the contents of the Windows section

from the

%VERI SI GN_TOP%\ ver i si gn\payf l owpro\ i payment \ zone. propert i es. ver i signfile to the end of your zone. propert i esfile.

NOTE: If you have Oracles autoconfig utility turned on, then you must enclose the

statements from the

%VERISIGN_TOP%\ ver i si gn\ payf l owpro\ i payment \ zone. propert i es.ver i si gnfile in between the #Begin Customizations and #EndCustomizations tags.

3. In the newly inserted statements in your zone. proper t i esfile, replace%ORACLE_TOP%and %APPL_TOP%with the appropriate values for your environment.

Step 8 Modify the jserv.properties file

1. Modify the jserv.properties located in a directory such as:

%ORACLE_TOP%\ i AS\ Apache\ J serv\ et c

2. Insert the contents of the Windows section from the

%VERISIGN_TOP%\ ver i si gn\ payf l owpro\ i payment \ j serv. proper t i es. ver i si gnfile between the Begin Customizations and End Customizations tags of yourj serv. proper t i esfile.

If the Begin and End tags are not present, then insert the contents of the Windows section

from the

%VERISIGN_TOP%\ ver i si gn\ payf l owpro\ i payment \ j serv. proper t i es. ver i si gnfile to the end of yourj serv. proper t i esfile.


statements from the

%VERISIGN_TOP%\ ver i si gn\ payf l owpro\ i payment \ j serv. proper t i es. ver i si gnfile in between the #Begin Customizations and #EndCustomizations tags.

3. In the newly inserted statements in yourj serv. proper t i esfile, replace%ORACLE_TOP%and %APPL_TOP%with the appropriate values for your environment.

4. If the following lines are present in yourj serv. proper t i esfile, remove Oracles SSL

implementation by commenting out the following two lines:

wrapper. cl asspath=%ORACLE_TOP%\ i AS\ j l i b\ j avax- ssl - 1_1. j arwrapper. cl asspath=%ORACLE_TOP%\ i AS\ j l i b\ j avax- ssl - 1_2. j ar

5. Add the JSSE provider as described below.


15/76


16/76


Uninstalling the BEP Servlet2


Uninst al l ing t he BEP Servl et

To uninstall the BEP servlet, undo the steps in Manually Installing the PayPal BEP Servlet on

Windowsstarting onpage 5. In substep 2 of Create the database tables on page 11, run theVRSN_Drop_Table.sql script from the sql prompt instead of running the

VRSN_Create_Table.sql script.


17/76


3 Instal l ing and Confi gur ing onNon-Windows Platfor msThis chapter guides you through installing and configuring the PayPal Payment Services

(VPS) servlet for use with Oracle iPayment on non-Windows platforms.

The PayPal BEP servlet is not configured as a part of Oracle Applications Rapid Installation

process. Follow the appropriate procedures in this section to install it. PayPal BEP servlet

installation on non-Windows platforms uses the directory references described in Table 3.1.

Manually Instal l i ng t he PayPal BEP Servlet on Non-Wind ows

Platforms

NOTE: Before you install or uninstall the PayPal integration, be sure that the Oracle database

instance is up and running. You should be able to log into the database by using

SQLPlus, as follows:

$ sqlplus /@ is the database user ID

is the database password

is the database instance ID

The following procedure explains how to manually install the PayPal BEP Servlet. If you are

using PayPal BEP Servlet version 3.1, follow the guidelines in Manually Uninstalling the

PayPal BEP Servlet on page 65before installing the current servlet version.

TABLE3 .1 BEP Servlet path and directory no tation

Notation Description

$VERISIGN_TOP Represents the PayPal directory into which the pf pro_i payment . zi p

file is unzipped, as shown in Figure 3.1.

If, for example, you unzipped pfpro_i payment . zi pinto/ mv2/ oracl e/ , $VERISIGN_TOPwould represent/ mv2/ oracl e/ ver i si gn, the top-level directory in the directorystructure.

$ORACLE_TOP Represents the top-level Oracle directory for Oracle Apps, for example,

/ mv2/ oracl e/ vi sora.

$APPL_TOP Represents the top-level application directory for Oracle Apps, for

example / mv2/ oracl e/vi sappl .

$COMN_TOP Represents the top-level Oracle Apps common directory, for example,

/ mv2/ oracl e/ vi scomn.

$JAVA_HOME Java home directory of your JDK, for example, / usr / j 2sdk1. 3. 1


18/76

Installing and Configuring on Non-Windows Platforms

Manually Installing the PayPal BEP Servlet on Non-Windows Platforms3


Step 1 Unzip the pfpro_ipayment file

Unzip the pf pro_i payment . zi pfile to a local directory. The file unzips into the directorystructure shown in Figure 3.1. The directory contains all files required to configure iPayment

to use the PayPal BEP.

FI GURE3 .1 pfpro_ipayment directory struc ture



certsdirectory f7389fd.0 (digital certificate)

cl assesdirectory Contains the following directories:

comdirectory - Contains ver i si gn\ i Payment \ *. cl ass(Classes required by the PayPal objects. The class files are inthe verisign\iPayment subdirectories such as bi zcompandbuyerauth.)

i byextenddirectory - ContainsTxnCust omi zer_vps. cl ass(PayPal requires iPaymentextensibility. These classes should be accessible to iPayment)

docsdirectory Contains Oracl ei Payment. pdf

l i bdirectory Contains Veri si gn. j ar

ver i si gndirectory Contains the following files:

par am. xml

vpsi payment . propert i es-(vpsi payment . propert i esis the key propert yfile to

be used by PayPals integration of the Oracle iPayment

servlet.)


19/76




Step 2 Stop the Oracle Apache serverStop the Oracle Apache Server by using the following command:

sh $COMN_TOP/ admi n/ scr i pts/ _/ adapcct l . sh stop

for example:

sh / mv2/ oracl e/ demo2comn/admi n/ scr i pts/ DEMO2_ai x2/ adapcct l . sh st op

Step 3 Copy PayPal fi les

1. Copy the following directories from the $VERISIGN_TOP/ payf l owpro/ i payment/ cl assesdirectory into the $ORACLE_TOP/ i AS/ Apache/ J serv/ servl et sdirectory:

comdirectory i byextenddirectory

2. Copy the following files from the $VERISIGN_TOP/ payf l owpro/ i payment / ver i si gndirectory into the $ORACLE_TOP/ 8. 0. 6/ ver i si gn directory:

param. xml

vpsi payment . propert i es

3. Copy the following files from $VERISIGN_TOP/ payf l owpro/ i payment / sampl est oredirectory into $COMN_TOP/ html directory:

Ver i Si gnLogo. j pg

Err or. j sp

i PaymentSampl eStore. j sp

4. Copy the following file from the $VERISIGN_TOP/ payf l owpro/ i payment / l i bdirectory into the $APPL_TOP/ i by/ 11. 5. 0/ l i bdirectory:

Ver i si gn. j ar

sampl est oredirectory Contains files for PayPal sample store:

Err or. j sp- Error page for Sample Store i PaymentSampl eStore. j sp- Main page for Sample Store

Veri Si gnLogo. J PG- logo to be displayed on Sample Store

Rel easeNotes. t xt Contains release notes

sql directory Contains the following sql files:

VRSN_Create_Tabl e. sql - SQL script to create thePayPal-specific tables in the Oracle Apps database

VRSN_Drop_Tabl e. sql - SQL script to drop the PayPal-specific tables from the Oracle Apps database




20/76




5. Copy the following directory from the $VERISIGN_TOP/ payf l owpro/ i payment directory into the $ORACLE_TOP/ 8. 0. 6directory:

certsdirectory

Step 4 Download Xerces XML Parser

1. Download the Xerces-J 2.7.1 package (XML parser) called Xerces- J -bi n. 2. 7. 1. t ar . gzfrom Apaches archive download Web site athttp://archive.apache.org/dist/xml/xerces-j/

2. Extract the following files from this package and place them in the

$APPL_TOP/ i by/ 11. 5. 0/ l i bdirectory:

xercesI mpl . j ar

xml -api s. j ar

Step 5 Configure Java Secure Sockets Extension (JSSE)

NOTE: Step 5 is not required if you are using JDK 1.4.x or higher. To find out which version of

the JDK you have, use the following command: java -version

To configure the JSSE, use the following procedure:

1. Download the JSSE from the following location:

http://java.sun.com/products/jsse/index-103.html

2. Place the following JSSE jar files into the

$ORACLE_TOP/ i AS/ Apache/ j dk/ j re/ l i b/ ext directory:

j cer t . j ar j net . j ar

j sse. j ar

Step 6 Modify vpsipayment.properties

Table 2-3 shows the entries in the vpsi payment . propert i esfile that you are going tomodify to reflect your current environment.

TABLE3 .3 vpsipayment.properties parameters to be modified


hostname test-payflow.verisign.com Host name

For live transactions, use payflow.verisign.com

For test transactions, use test-payflow.verisign.com

port 443 Payflow Pro server port number

timeout 30 Transaction timeout value sent to the Payflow Pro

server
http://archive.apache.org/dist/xml/xerces-j/http://java.sun.com/products/jsse/index-103.htmlhttp://archive.apache.org/dist/xml/xerces-j/http://archive.apache.org/dist/xml/xerces-j/http://java.sun.com/products/jsse/index-103.html


21/76




1. Edit the properties in the$ORACLE_TOP/ 8. 0. 6/ ver i si gn/ vpsi payment . proper t i esfile as indicated inTable 3.3. If no default value is shown in the table for a parameter, the parameter is empty.

NOTE: Be sure that you do not add spaces, extra characters, or carriage returns at the end of

any of the lines in the vpsi payment . propert i esfile.

2. Replace the value of the dbpwd entry in your version of the vpsi payment . propert i esfile with your encrypted database user password. For instructions on how to encrypt your

password, see Appendix E, Encrypting Your Database User Password.

Step 7 Modify zone.properties

1. Modify the zone.properties located in a directory such as:

$ORACLE_TOP/ i AS/ Apache/ J serv/et c

certs /mv1/oracle/demoora/8.0.6/certs Digital certificates folder containing the certificate

file, f y3d89f d. 0proxyHost Proxy server address. Use the proxy parameters for

servers behind a firewall. Your network

administrator can provide the values. Leave blank if

you are not using a proxy.

proxyPort 0 Proxy server port. Leave the 0 if you are not using a

proxy.

proxyUser Proxy server logon ID. Leave blank if you are not

using a proxy.

proxyPwd Proxy server logon password. Leave blank if you are

not using a proxy.

baurl test-buyerauth.verisign.com URL for PayPal Buyer Authentication server

termurl http://machine.yourdomain.com:8000

/servlets/oramipp_ Payee2VPS

Merchant URL for Buyer Authentication. The

format is:

http://:/servlets/oramipp_Payee

2VPS

dburl jdbc:oracle:thin:@machine.yourdoma

in.com:1521:DEMO

JDBC database connection URL for the Oracle Apps

instance. The format is:

jdbc:oracle:thin:@::

NOTE: is your database listener portnumber, not your Apache Web server port.

dbuid apps Database user ID

dbpwd apps Database user password (encrypted)

TABLE3 .3 vpsipayment.properties parameters to be modified (Continued)



22/76




2. Insert the contents of the non-Windows platforms section from the$VERISIGN_TOP/ ver i si gn/ payf l owpro/ i payment / zone. proper t i es. ver i si gnfile between the Begin Customizations and End Customizations tags of your

zone. proper t i esfile.

If the Begin and End tags are not present, then insert the contents of the non-Windows

platforms section from the

$VERISIGN_TOP/ ver i si gn/ payf l owpro/ i payment / zone. proper t i es. ver i si gnfile to the end of your zone. proper t i esfile.


statements from the

$VERISIGN_TOP/ ver i si gn/ payf l owpro/ i payment / zone. proper t i es. ver i si gnfile in between the #Begin Customizations and #End Customizationstags.

3. In the newly inserted statements in your zone. proper t i esfile, replace $ORACLE_TOP

and $APPL_TOPwith the appropriate values for your environment.

Step 8 Modify the jserv.properties and java.security files

1. Modify the jserv.properties located in a directory such as:$ORACLE_TOP/ i AS/ Apache/ J serv/et c

2. Insert the contents of the non-Windows platforms section from the$VERISIGN_TOP/ ver i si gn/ payf l owpro/ i payment / j serv. proper t i es. ver i si gnfile between the Begin Customizations and End Customizations tags of your

j serv. proper t i esfile.

If the Begin and End tags are not present, then insert the contents of the non-Windowsplatforms section from the

$VERISIGN_TOP/ ver i si gn/ payf l owpro/ i payment / j serv. proper t i es. ver i si gnfile to the end of yourj serv. propert i esfile.


statements from the

%VERISIGN_TOP%\ ver i si gn\ payf l owpro\ i payment \ j serv. proper t i es. ver i si gnfile in between the #Begin Customizations and #EndCustomizations tags.

3. In the newly inserted statements in yourj serv. proper t i esfile, replace $ORACLE_TOPand $APPL_TOP with the appropriate values for your environment.

4. If the following lines are present in yourj serv. proper t i esfile, remove Oracles SSLimplementation by commenting out the following two lines:

wrapper . cl asspath=$ORACLE_TOP/ i AS/ j l i b/ j avax- ssl - 1_1. j arwrapper . cl asspath=$ORACLE_TOP/ i AS/ j l i b/ j avax- ssl - 1_2. j ar

5. Add the JSSE provider as described below.


23/76




NOTE: This substep is not required if you are using JDK 1.4.x or higher. Oracle iPayment

11.5.10 and higher use JDK 1.4.x. To find out which version of the JDK you have,

use the following command: java -version

Add the JSSE provider to yourj ava. secur i tyfile in the

$ORACLE_TOP/ i AS/ Apache/ j dk/ j re/ l i b/ secur i t yand$JAVA_HOME/ j re/ l i b/ secur i tydirectories as follows:

Increment the provider number to the next higher number. If, for example, the following

two provider strings currently are present, the provider string you insert would be

security.provider.4=secur i ty. provi der . 2=com. sun. net . ssl . i nt ernal . ssl . Provi dersecur i t y. provi der. 3=com. sun. crypto. provi der. SunJ CE

NOTE: If $ORACLE_TOP/ i AS/ Apache/ j dk/ j re/ l i b/ secur i ty/ j ava. secur i t ydoes not point to the default JDK version set in the class path, then this change also

needs to be made to thej ava. secur i tyfile associated with the default JDK at$JAVA_HOME/ j re/ l i b/ secur i ty.

Step 9 Create the database tables

To create the database tables:

1. Log in to the Oracle database using sqlplus.

sql pl us $dbui d/ $dbpwd@

(for example, sqlplus apps/apps@DEMO)

2. Run the Create Table sql script from the sql prompt.

@$VERI SI GN_TOP/ payf l owpro/ i payment / sql / VRSN_Create_Tabl e. sql

Be sure to replace $VERISIGN_TOP with its appropriate value.

3. Verify that the following three tables are created in the APPS schema:

4. To verify that all tables were created, run the following commands:

desc VRSN_EXTEND_DATA

desc VRSN_BUYERAUTH

desc VRSN_EXTEND_LI NEI TEM_DATA

The above commands should display the table structure for the table created.

Step 10 Start the Oracle Apache serverStart the Oracle Apache Server by using the following command:

sh $COMN_TOP/ admi n/ scr i pts/ _/ adapcct l . sh st art

for example:

sh / mv2/ oracl e/ demo2comn/admi n/ scr i pt s/ DEMO2_ai x2/ adapcct l . sh st art


24/76


Uninstalling the BEP Servlet3


Step 11 Register the BEP Servlet in iPayment

For detailed instructions on registering the BEP servlet, see Chapter 4, Registering and

Testing.

Uninst al l ing t he BEP Servl et

To uninstall the BEP servlet, undo the steps in Manually Installing the PayPal BEP Servlet on

Non-Windows Platforms on page 13. In substep 2 of Create the database tables on

page 19, run the VRSN_Drop_Table.sql script from the sql prompt instead of running the

VRSN_Create_Table.sql script.


25/76


4 Registering and Test ing

Once you have successfully installed the PayPal Payment Services servlet, you are ready to

register and test it. This chapter guides you through registering and testing the servlet. It also

provides instructions for processing live transactions.

Before You Begin

Before you register and test the BEP Servlet, you must create an iPayment user. Refer to

Oracles iPayment documentation for details.

Regis tering the BEP Servlet in iPayment

In this procedure, you register the BEP servlet, register a payee, and then configure routing

rules. Refer to Oracles iPayment documentation for details.

Step 1 Register the BEP servlet

1. Log in (as an administrative user) to the iPayment administration site athttp://:/OA_HTML/jtflogin.jsp.

Replace host_nameandportwith your server information.

FI GURE4 .1 iPayment administration s ite


26/76

Registering and Testing

Registering the BEP Servlet in iPayment4


2. The Payment Systemspage appears, displaying the Payment Systemtab.

FI GURE4 .2 Payment systems page

3. Click Createto generate the PayPal payment system.

The Create Payment Systempage appears.

FI GURE4 .3 Create payment system page

4. In this page, enter the following values:

IMPORTANT:For suffix, be sure to enter the following value in all lowercase

letters: vps

Name Enter PayPal.

Suffix Enter vps.

NOTE: For suffix, you mustenter vps in all lowercase letters.

Payment System Type Select Gateway.


27/76




5. Click Create. The Payment Systemspage reappears with the PayPal payment system addedto it.

FI GURE4 .4 Payment systems page with PayPal added

Step 2 Register the Payee

1. Click the Payee tab. The Payees and Risk Managementpage appears.

FI GURE4 .5 Payees and risk management page

2. Click Create. The Create Payeepage appears.

User Name Enter any value (not used by BEP servlet).

User Password Enter any value (not used by BEP servlet).

Base URL http://:/servlet. The host on which the

PayPal servlet is to be installed, and any active port. Forexample:

http://www.merchant.com:8000/servlet

For Oracle On Demand installations, the URL would be:

http://www.merchant.com:8000/servlets

Administration URL Enter any value (not used by BEP servlet).

Purchase Card Select this checkbox.

Credit Card Select this checkbox.

NLS Language Preferred Leave empty.

NLS Language Optional Leave empty.


28/76




FI GURE4 .6 Create payee page

3. Enter the following values:

4. On the Create Payeepage, indicate the icon to be clicked for PayPal under PaymentSystem Identifier > Payment System.

The Payment System Identifierspage appears.

5. Select the first radio button under Defaultand arrange the data that you used whenregistering for the PayFlow Pro account (and described in the table below) in the following

format.

:::

For example, tjohnson:mypassword:tjohnson:PayPal.

Payee Name Enter the payee name. This value is Unique, is case

sensitive, and can be any value. For example, tjohnson.

Payee Identifier iPayment uses this payee identifier to identify a particular

payee. You cannot modify this identifier after saving it. It

is unique, is case sensitive, and can be any value. For

example: vps.(This is not related to Suffix vps used for Payment

system).

Status Select Active.

Purchase Card

Credit Card

Select Purchase Card and Credit Card.

Merchant Category Code Leave this field empty.


29/76


30/76




2. Click Create. The Create Routing Rulepage appears.

FI GURE4 .9 Routing rule

3. Enter the following values, and click Add Rule Condition.

TheAdd Rule Conditionscreen shown in Figure 4.10appears.

TABLE4 .1

Rule Name Enter PurchaseCardPayment.

Rule Priority Select 2.

Status Active.

Payment Instrument Type Select Purchase Card.

Payee Select the payee name, for example, tjohnson.

The value selected here must be the same value that was

entered for Payee Name in Step 3 onpage 24.

When all enabled conditions below

are met route to

Select PayPal.

Payment System Identifier Enter in the format:

:::

For example, tjohnson:mypassword:tjohnson:PayPal


31/76



Testing the Installation Using the Oracle iPayment User Interface4

FI GURE4 . 1 0 Adding ru le condit ions

4. In the Condition Namefield, enter a name, for example, Amount.

5. Select the radio button next to Amount, select an operation from the Operationlist, andfill in the required value.

6. Click Add Rule Condition. The Create Routing Rulepage reappears.

NOTE: You can only add one rule condition at a time, so you must click Add Rule Conditionand complete theAdd Rule Conditionscreen for each new rule condition you add.

7. Click Create.

8. Repeat these procedures to create and configure the routing rules for credit cards, using theappropriate values for credit card payments.

Testi ng t he Inst al lat ion Usin g th e Oracle iPayment User

Interface

NOTE: Oracle iPayment does not support the following transaction types:

- Void (V) For Authorizations only

- Fraud filter (U). See Payflow Pro Fraud Protection Services Users Guidefor details.

- Recurring Billing (R): See the Payflow Pro Recurring Billing Service Users Guide

for details.

Step 1 Test the servlet configuration with iPaymentNOTE: For testing parameters, see Payflow Pro Developers Guide.

1. On the Operationtab, click New Operation. TheAuthorization Detailspage appears.
http://../PayflowPro_FPS/PFP/Title_PayflowPro_FPS_Guide.pdfhttp://../Recurring_Billing_PayflowPro/PFP/Title_RecurringBilling_Guide.pdfhttp://../PayflowPro/TitlePayflowPro_Guide.pdfhttp://../PayflowPro/TitlePayflowPro_Guide.pdfhttp://../Recurring_Billing_PayflowPro/PFP/Title_RecurringBilling_Guide.pdfhttp://../PayflowPro_FPS/PFP/Title_PayflowPro_FPS_Guide.pdf


32/76




FI GURE4 . 1 1 Au thor izati on detail s page


3. Click Next. The secondAuthorization Detailspage appears.

TABLE4 .2

Payee Select payee name, for example tjohnson

(vps).

Tangible ID/Order ID Enter any number, for example, 123.

Amount Enter any non-zero number, for example, 55.

Currency Select US dollar.

Payment instrument type Select credit card.


33/76




FI GURE4 . 1 2 Second authorization details page

4. Enter values for the following fields:

5. Click Next. TheAuthorization Summarypage appears.

6. Verify the values, and click Submit.

TABLE4 .3

Authorization Type Select Authorization Only.

Card number Enter credit card number, for example, 4111111111111111.

Expiration Date Select the date, for example, 3/2010.

Card type Select the card type, for example, Visa.


34/76




FI GURE4 . 1 3 Au thor izat ion summary

iPayment processes the test transactions by calling the VPS BEP servlet, and the

Authorization Resultspage appears on the Operationtab. If the transaction is not approved,

review your configuration and retry.

FI GURE4 . 1 4 Au thor izati on resul ts

Step 2 Verify operation of the Extensibility APIs

It is important to test extensibility functionality because all follow-on transactions (for

example, Capture, Void, and Return) make use of iPayments extensibility APIs. To test

extensibility, you perform a follow-on Capturetransaction for a previously authorized

transaction, as follows:


35/76




1. On the Operationtab, click the Follow-on Operation subtab. The Search Transactionspage appears.

FI GURE4 . 1 5 Search transactions page


3. Click Goto retrieve the authorized record.

TheMatching Transactionspage appears.

FI GURE4 . 1 6 Matching transactions

4. To capture the transaction, click the Capturelink for the record.

5. TheCapture Detailspage appears. Verify the capture details and click Submit.

TABLE4 .4

Payee Select the payee with the (vps) in parentheses.

Tangible ID/Order ID Use the value that you used in the previous

Authorization transaction.

Transaction Status Select Authorized.


36/76


Testing the Installation Using PayPals Sample Store4


FI GURE4 . 1 7 Capture details page

The Capture Resultspage appears. A successful capture transaction indicates that

extensibility is working properly. If the transaction is not successful, review your

configuration and retry.

FI GURE4 . 1 8

Capture result s page

Testi ng t he Inst al lat ion Usin g PayPals Sampl e Stor e

NOTE: PayPals Sample Store is for demonstration purposes only and should not be used in a

production environment.

To submit an order using the Sample Store follow the steps below:

1. Open the URL to Sample Store in Internet Explorer. The URL would be of the form shownhere, where the port number is 8000 by default:

http://:/OA_HTML/iPaymentSampleStore.jsp

2. On the order form, enter the appropriate data and the suitable transaction type. Leave theORDER NUMBERfield empty for primary transactions such as Authorization Only,AuthCapture, and Credit (independent).

3. Click Submit Transactionat the bottom of the form.


37/76



Testing the Installation Using PayPals Sample Store4

FI GURE4 . 1 9 iPayment Purchase

4. If Buyer Authentication Required was set to YES, an intermediate page appears for BuyerAuthentication. If the account number is enrolled for Buyer Authentication, enter the

password. Then click Submit.

FI GURE4 . 2 0 Buyer Authentication

5. The order is submitted to the PayPal Payment Gateway. Then a results page appears,indicating the actual request sent and response received from the Payment Gateway.


38/76


Processing Live Transactions4


FI GURE4 . 2 1 Results page

FI GURE4 . 2 2 Purchase order follow-on t ransaction

6. To do a follow-on transaction, click on the order number link (Tangible ID value) on theresults page. Then, on the order form, click Get Order Details.

7. Choose the appropriate follow-on transaction; then click Submit Transaction. A resultspage appears that is similar to the one shown in Figure 4.21.

Processing Liv e Transact ions

To process live transactions, change test-payflow.verisign.com to payflow.verisign.comin theappropriate file:

Windows: %ORACLE_TOP%\ 8. 0. 6\ ver i si gn\ vpsi payment . proper t i es

Non-Windows: $ORACLE_TOP/ 8. 0. 6 / ver i si gn/ vpsi payment . proper t i es

NOTE: You must use DNS resolution for transaction processing. In its effort to achieve high

availability, PayPal retains the right to change the IP address of PayFlow hosts without


39/76




notice. PayPal cannot be held responsible for any outages that result from your not

using DNS.


40/76





41/76


5 Bui ldi ng Your Own Web Site

To build your own Web site, follow these guidelines:

Insert the PayPal-specific parameters into the VRSN_EXTEND_DATA and the

VRSN_EXTEND_LINEITEM_DATA tables. See Appendix B, Mapping PayPal

Parameters to iPayment Parameters,for a mapping of these parameters to the database

table name and column name in that table. The values of these parameters are picked up by

the preTxn method in theTxnCust omi zer_vps. j avaclass, which is part of theiPayment Extensibility API.

Use the respective iPayment APIs to call the relevant transactions. Refer to Oracles

iPayment documentation for details.


42/76

Building Your Own Web Site5



43/76


A Transacti on Decli ne or Erro rRESULTs and RESPMSGsOapfVendErrCode maps to RESULT.

OapfVendErrMsg maps to RESPMSG.

A value greater than zero indicates a decline or error. Exact wording of the RESPMSG may

vary. Sometimes a colon appears after the initial RESPMSG followed by more detailed

information.

TABLEA .1 Payflow t ransaction RESULT values and RESPMSG text

RESULT RESPMSG and Explanation

0 Approved

1 User authentication failed.Error is caused by one or more of the following:

Invalid Processor information entered. Contact merchant bank to verify.

"Allowed IP Address" security feature implemented. The transaction is coming

from an unknown IP address. See PayPal Manager online help for details on how to

use Manager to update the allowed IP addresses.

You are using a test (not active) account to submit a transaction to the live PayPal

servers. Change the URL from test-payflow.paypal.com to payflow.paypal.com.

2 Invalid tender type.Your merchant bank account does not support the followingcredit card type that was submitted.

3 Invalid transaction type.Transaction type is not appropriate for this transaction. For

example, you cannot credit an authorization-only transaction.

4 Invalid amount format. Use the format: #####.## Do not include currencysymbols or commas.

5 Invalid merchant information.Processor does not recognize your merchant account

information. Contact your bank account acquirer to resolve this problem.

6 Invalid or unsupported currency code

7 Field format error.Invalid information entered. See RESPMSG.

8 Not a transaction server

9 Too many parameters or invalid stream

10 Too many line items

11 Client time-out waiting for response

12 Declined.Check the credit card number, expiration date, and transaction information to

make sure they were entered correctly. If this does not resolve the problem, have the

customer call their card issuing bank to resolve.


44/76


45/76


Transaction Decline or Error RESULTs and RESPMSGsA

103 Error reading response from host

104 Timeout waiting for processor response.Try your transaction again.

105 Credit error.Make sure you have not already credited this transaction, or that thistransaction ID is for a creditable transaction. (For example, you cannot credit an

authorization.)

106 Host not available

107 Duplicate suppression time-out

108 Void error.See RESPMSG. Make sure the transaction ID entered has not already beenvoided. If not, then look at the Transaction Detail screen for this transaction to see if it

has settled. (The Batch field is set to a number greater than zero if the transaction has

been settled). If the transaction has already settled, your only recourse is a reversal(credit a payment or submit a payment for a credit).

109 Time-out waiting for host response

111 Capture error.Either an attempt to capture a transaction that is not an authorization

transaction type, or an attempt to capture an authorization transaction that has already

been captured.

112 Failed AVS check. Address and ZIP code do not match. An authorization may stillexist on the cardholders account.

113 Merchant sale total will exceed the sales cap with current transaction. ACHtransactions only.

114 Card Security Code (CSC) Mismatch.An authorization may still exist on the

cardholders account.

115 System busy, try again later

116 VPS Internal error. Failed to lock terminal number

117 Failed merchant rule check.One or more of the following three failures occurred:

An attempt was made to submit a transaction that failed to meet the security settings

specified on the PayPal Manager Security Settingspage. If the transaction exceeded the

Maximum Amount security setting, then no values are returned for AVS or CSC.

AVS validation failed. The AVS return value should appear in the RESPMSG.

CSC validation failed. The CSC return value should appear in the RESPMSG.

118 Invalid keywords found in string fields

122 Merchant sale total will exceed the credit cap with current transaction. ACHtransactions only.

125 Fraud Protection Services Filter Declined by filters

TABLEA .1 Payflow t ransaction RESULT values and RESPMSG text (Continued)



46/76



126 Fraud Protection Services Filter Flagged for review by filters

Important Note:Result code 126 indicates that a transaction triggered a fraud filter.This is not an error, but a notice that the transaction is in a review status. The

transaction has been authorized but requires you to review and to manually accept the

transaction before it will be allowed to settle.

Result code 126 is intended to give you an idea of the kind of transaction that is

considered suspicious to enable you to evaluate whether you can benefit from using the

Fraud Protection Services.

To eliminate result 126, turn the filters off.

For more information, see the Fraud Protection Services documentation for your

payments solution. It is available on the PayPal Manager Documentation page.

127 Fraud Protection Services Filter Not processed by filters

128 Fraud Protection Services Filter Declined by merchant after being flagged forreview by filters

131 Version 1 Payflow Pro SDK client no longer supported.Upgrade to the most recentversion of the Payflow Pro client.

150 Issuing bank timed out

151 Issuing bank unavailable

1000 Generic host error.This is a generic message returned by your credit card processor.The RESPMSG will contain more information describing the error.

1001 Buyer Authentication Service unavailable

1002 Buyer Authentication Service Transaction timeout

1003 Buyer Authentication Service Invalid client version

1004 Buyer Authentication Service Invalid timeout value




1014 Buyer Authentication Service Merchant is not enrolled for Buyer

Authentication Service (3-D Secure).

1016 Buyer Authentication Service 3-D Secure error response received.Instead ofreceiving a PARes response to a Validate Authentication transaction, an error response

was received.

1017 Buyer Authentication Service 3-D Secure error response is invalid.An errorresponse is received and the response is not well formed for a Validate Authentication

transaction.




47/76



1021 Buyer Authentication Service Invalid card type

1022 Buyer Authentication Service Invalid or missing currency code

1023 Buyer Authentication Service merchant status for 3D secure is invalid

1041 Buyer Authentication Service Validate Authentication failed: missing orinvalid PARES

1042 Buyer Authentication Service Validate Authentication failed: PARES format isinvalid

1043 Buyer Authentication Service Validate Authentication failed: Cannot findsuccessful Verify Enrollment

1044 Buyer Authentication Service Validate Authentication failed: Signaturevalidation failed for PARES

1045 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid amount in PARES

1046 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid acquirer in PARES

1047 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid Merchant ID in PARES

1048 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid card number in PARES

1049 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid currency code in PARES

1050 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid XID in PARES

1051 Buyer Authentication Service Validate Authentication failed: Mismatched orinvalid order date in PARES

1052 Buyer Authentication Service Validate Authentication failed: This PARES wasalready validated for a previous Validate Authentication transaction




48/76




49/76


B Mapp ing PayPal Parameters toiPayment Parameters

Parameters Mappi ng

TABLEB .1 Parameters mapping

PF Pro Parameter

Database -

TableName.ColumnName

Oapf Parameter

Name Oapf Parameter Name

ABA VRSN_EXTEND_DATA.ABA OapfABA Cardholder's ABA

Number

ACCT IBY_CREDITCARD.CCNUM

BER

OapfPmtInstrID Cardholder's Account

Number

ACCTTYPE VRSN_EXTEND_DATA.

ACCTTYPE

OapfAcctType Cardholder's Account

Type

ACSURL NA NA ACS Url for Buyer

Authentication. Value

returned only if

AUTHENTICATION_S

TATUS=E.

ADDLMSGS VRSN_EXTEND_DATA.

ADDLMSGS

OapfAddlMsgs Additional error message

that indicates that the

merchant used a featurethat is disabled.

ALTTAXAMT VRSN_EXTEND_DATA.

ALTTAXAMT

OapfAltTaxAmt Alternative Tax Amount

AMT IBY_TRXN_SUMMARIES_A

LL.

AMOUNT

OapfPrice Order Amount

AUTHCODE IBY_TRXN_CORE.AUTHCO

DE

OapfAuthCode Authorization Code for

use in Voice

Authorization

AUTHENTICATION_ID

VRSN_EXTEND_DATA.AUTHENTICATION_ID

OapfAuthentication_Id Unique identifier forVerify Enrolment request

in Buyer Authentication.


50/76

Mapping PayPal Parameters to iPayment Parameters

Parameters MappingB


AUTHENTICATION_STATUS

VRSN_EXTEND_DATA.AUTHENTICATION_STATU

S

OapfAuthentication_Status

Status for BuyerAuthentication:

E: Card Enrolled.

O: Card Not Enroled.

X: Unable to determine.

I: Verify Enrolment

request failed.

AUTHTYPE VRSN_EXTEND_DATA.

AUTHTYPE

OapfAuthType The type of authorization

received from the payer.

Defaults to CCD for B2B

format accounts.

Defaults to PPD(standard customer

authorization method) for

B2C format accounts.

You can specify the

following values for B2C

format accounts:

TEL: Debit authorization

obtained by telephone.

POP: Point of Purchase

check entry for a single

entry debit.

ARC: AccountsReceivables check entry

for a single entry debit.

RCK: Re-presented

check entry for a single

entry debit.

WEB: The customer

authorized the payment

over the Internet.

AVSADDR VRSN_EXTEND_DATA.AVS

ADDR

OapfAVSAddr AVS Address Match (Y,

N, X)

AVSZIP VRSN_EXTEND_DATA.AVS

ZIP

OapfAVSZip AVS Zip Match (Y, N, X)

BILLTOPHONE2 VRSN_EXTEND_DATA.

BILLTOPHONE2

OapfBillToPhone2 Alternative Phone

Number

For The Billing Contact

BILLTOSTREET2 VRSN_EXTEND_DATA.

BILLTOSTREET2

OapfBillToStreet2 Extended Billing Address


PF Pro Parameter

Database -


Oapf Parameter



51/76



Parameters MappingB

BROWSERCOUNTRYCODE

VRSN_EXTEND_DATA.BROWSERCOUNTRYCODE

OapfBrowserCountryCode

Browser Country Code

BROWSERTIME VRSN_EXTEND_DATA.

BROWSERTIME

OapfBrowserTime Browser Time

BROWSERUSER

AGENT

VRSN_EXTEND_DATA.

BROWSERUSERAGENT

OapfBrowserUserAgent Browser User Agent

CARDSECURE VRSN_EXTEND_DATA.

CARDSECURE

OapfCardSecure CAVV Validity.

(Y=valid, N=Not Valid,

X=Cannot Determine)

CARRIER VRSN_EXTEND_DATA.CAR

RIER

OapfCarrier Shipment Carrier

CAVV VRSN_EXTEND_DATA.CAV

V

OapfCAVV Cardholder

Authentication

Verification Value. The

value generated by card

issuing bank to prove that

the cardholder has been

authenticated with a

particular transaction.

CHECKNUM Not Supported Not Supported

CHECKTYPE Not Supported Not Supported

CHKNUM VRSN_EXTEND_DATA.CHK

NUM

OapfChkNum Account Holder's Next

Available Check Number

CHKTYPE VRSN_EXTEND_DATA.CHK

TYPE

OapfChkType Check Type (P=Personal,

C=Company)

CITY HZ_LOCATIONS.CITY OapfCity Billing City

COMMCARD VRSN_EXTEND_DATA.

COMMCARD

OapfCommCard Commercial Card Type

(P=Purchase,

C=Corporate,

B=Business,

U=Unknown-default,

N=None)

COMMENT1 VRSN_EXTEND_DATA.

COMMENT1

OapfComment1 Comment

COMMENT2 VRSN_EXTEND_DATA.

COMMENT2

OapfComment2 Comment

COMPANYNAME VRSN_EXTEND_DATA.

COMPANYNAME

OapfCompanyName Cardholders company


PF Pro Parameter

Database -


Oapf Parameter



52/76


Parameters MappingB


CORPNAME VRSN_EXTEND_DATA.CORPNAME

OapfCorpName Corporation's Name

CORPPURCHDESC VRSN_EXTEND_DATA.

CORPPURCHDESC

OapfCorpPurchDesc Description of Corporate

Purchase

COUNTRY HZ_LOCATIONS.COUNTRY OapfCntry Billing Country Code

COUNTRYCODE VRSN_EXTEND_DATA.

COUNTRYCODE

OapfCountryCode Destination Country

Code

CURRENCY This is not saved into database.

It is required for BuyerAuth

only.

NA Currency (840=US$)

CUSTAGE VRSN_EXTEND_DATA.CUS

TAGE

OapfCustAge Customer's Age (0-150)

CUSTCODE VRSN_EXTEND_DATA.

CUSTCODE

OapfCustCode Customer Code

CUSTID VRSN_EXTEND_DATA.CUS

TID

OapfCustId Merchant Web sites Id

for the Customer

CUSTIP VRSN_EXTEND_DATA.CUS

TIP

OapfCustIP Customer's IP Address

CUSTMAXAGE VRSN_EXTEND_DATA.

CUSTMAXAGE

OapfCustMaxAge Customer's Maximum

Age

CUSTMINAGE VRSN_EXTEND_DATA.

CUSTMINAGE

OapfCustMinAge Customer's Minimum

Age

CUSTREF VRSN_EXTEND_DATA.CUS

TREF

OapfCustRef Customer Reference

Number

CUSTTM VRSN_EXTEND_DATA.CUS

TTM

OapfCustTm Customer's Local Time

(hhmmss)

CUSTVATREGNUM VRSN_EXTEND_DATA.

CUSTVATREGNUM

OapfCustVatRegNum VAT Registration

Number

CVV2 VRSN_EXTEND_DATA.CVV

2

OapfCVV2 Card Security Code

(CSC)


PF Pro Parameter

Database -


Oapf Parameter



53/76



Parameters MappingB

CVV2MATCH VRSN_EXTEND_DATA.CVV2MATCH

OapfCVV2Result CSC Match(Y=The submitted value

matches the data on file

for the card,

N=The submitted value

does not match the data

on file for the card,

X=The cardholders bank

does not support this

service)

DESC VRSN_EXTEND_DATA.DES

CR

OapfDesc Description

DESC1 VRSN_EXTEND_DATA.DES

C1

OapfDesc1 Description of Goods

and/or Services


C2


and/or Services


C3


and/or Services


C4


and/or Services

DISCOUNT VRSN_EXTEND_DATA.

DISCOUNT

OapfDiscount Discount Amount

DL VRSN_EXTEND_DATA.DL OapfDL Driver's License Number

(Xx=State Code,

Nnnnnnnn - DL Number)

DOB VRSN_EXTEND_DATA.DOB OapfDOB Date Of Birth

(mmddyyyy)

DUTYAMT VRSN_EXTEND_DATA.DUT

YAMT

oapfdutyamt Duty Amount /Import

Tax


PF Pro Parameter

Database -


Oapf Parameter



54/76


55/76



Parameters MappingB

FIRSTNAME VRSN_EXTEND_DATA.FIRSTNAME

OapfFirstName Customer's First Name

FORGOTPWD VRSN_EXTEND_DATA.

FORGOTPWD

OapfForgotPwd Forgot Password (Y/N)

FPS_POSTXMLDATA VRSN_EXTEND_DATA.

FPS_POSTXMLDATA

OapfFPS_PostXmlData Itemized list of responses

for triggered filters as an

xml.

FPS_PREXMLDATA VRSN_EXTEND_DATA.

FPS_PREXMLDATA

OapfFPS_PreXmlData Itemized list of responses

for triggered filters as an

xml.

FREIGHTAMT VRSN_EXTEND_DATA.

FREIGHTAMTOapfFreightAmt Freight Amount

GIFTCARDTYPE VRSN_EXTEND_DATA.

GIFTCARDTYPE

OapfGiftCardType Gift Card Type (B, A, G,

H, C, W, S or U)

GIFTMSG VRSN_EXTEND_DATA.GIFT

MSG

OapfGiftMsg Gift Message

HANDLINGAMT VRSN_EXTEND_DATA.

HANDLINGAMT

OapfHandlingAmt Handling Amount

HOMEPHONE VRSN_EXTEND_DATA.

HOMEPHONE

OapfHomePhone Customer's Home Phone

HOSTADDRESS NA NA PayPals host name.

For live transactions, use

payflow.verisign.com

For testing purposes use

test-

payflow.verisign.com

HOSTCODE VRSN_EXTEND_DATA.

HOSTCODE

OapfHostCode Response code returned

by the Processor.

HOSTPORT NA NA Use port 443

IAVS VRSN_EXTEND_DATA.IAVS OapfIAVS Indicates whether AVS

response is international(Y), US (N), or cannot be

determined (X). Client

version 3.06 or later is

required.

INVNUM VRSN_EXTEND_DATA.INV

NUM

OapfInvNum Invoice Number


PF Pro Parameter

Database -


Oapf Parameter



56/76


Parameters MappingB


INVOICEDATE VRSN_EXTEND_DATA.INVOICEDATE

OapfInvoiceDate Invoice Date(yyyymmdd)

L_AMTn VRSN_EXTEND_LINEITEM

_DATA.L_AMT

OapfL_Amt Item Amount

L_BILLEDUOMn VRSN_EXTEND_LINEITEM

_DATA.L_BILLEDUOM

OapfL_BilledUOM Not used currently by the

Payment Gateway

L_CATALOGNUMn VRSN_EXTEND_LINEITEM

_DATA

.L_CATALOGNUM

OapfL_CatalogNum Supplier Catalog Number

L_CATEGORYn VRSN_EXTEND_LINEITEM

_DATA.L_CATEGORY

OapfL_Category Item Category

L_COMMCODEn VRSN_EXTEND_LINEITEM

_DATA.

L_COMMCODE

OapfL_CommCode Item Commodity Code

L_COSTCENTER

NUMn

VRSN_EXTEND_LINEITEM

_DATA.

L_COSTCENTERNUM

apfL_CostCenterNum Cost Center Number

L_COSTn VRSN_EXTEND_LINEITEM

_DATA.

L_COST

OapfL_Cost Item Cost

L_DESCn VRSN_EXTEND_LINEITEM_DATA.

L_DESC

OapfL_Desc Item Description

L_DISCOUNTn VRSN_EXTEND_LINEITEM

_DATA.

L_DISCOUNT

OapfL_Discount Item Discount

L_FREIGHTAMTn VRSN_EXTEND_LINEITEM

_DATA.

L_FREIGHTAMT

OapfL_FreightAmt Item Freight Amount

L_FREIGHTUOMn VRSN_EXTEND_LINEITEM

_DATA

L_FREIGHTUOM

OapfL_FreightUOM Not used currently by the

Payment Gateway

L_HANDLINGAMTn VRSN_EXTEND_LINEITEM

_DATA.

L_HANDLINGAMT

OapfL_HandlingAmt Item Handling Amount

L_HANDLINGUOMn VRSN_EXTEND_LINEITEM

_DATA.

L_HANDLINGUOM

OapfL_HandingUOM Not used currently by the

Payment Gateway


PF Pro Parameter

Database -


Oapf Parameter



57/76



Parameters MappingB

L_MANUFACTURERn

VRSN_EXTEND_LINEITEM_DATA.

L_MANUFACTURER

OapfL_Manufacturer Item Pickup City

L_PICKUPCITYn VRSN_EXTEND_LINEITEM

_DATA.L_PICKUPCITY

OapfL_PickupCity Item Pickup Country

L_PICKUPCOUNTRY

n

VRSN_EXTEND_LINEITEM

_DATA.

L_PICKUPCOUNTRY

OapfL_PickupCountry Item Pickup State

L_PICKUPSTATEn VRSN_EXTEND_LINEITEM

_DATA.

L_PICKUPSTATE

OapfL_PickupState Item Pickup Country

L_PICKUPSTREETn VRSN_EXTEND_LINEITEM

_DATA.

L_PICKUPSTREET

OapfL_PickupStreet Item Pickup Street

L_PICKUPZIPn VRSN_EXTEND_LINEITEM

_DATA.

L_PICKUPZIP

OapfL_PickupZip Item Pickup Zip

L_PRODCODEn VRSN_EXTEND_LINEITEM

_DATA.

L_PRODCODE

OapfL_ProdCode Item Product Code

L_QTYn VRSN_EXTEND_LINEITEM

_DATA.

L_QTY

OapfL_Qty Item Quantity Ordered

L_SKUn VRSN_EXTEND_LINEITEM

_DATA.

L_SKU

OapfL_SKU Item SKU Number

L_TAXAMTn VRSN_EXTEND_LINEITEM

_DATA.

L_TAXAMT

OapfL_TaxAmt Item Tax Amount

L_TAXRATEn VRSN_EXTEND_LINEITEM

_DATA.

L_TAXRATE

OapfL_TaxRate Item Tax Rate

L_TAXTYPEn VRSN_EXTEND_LINEITEM

_DATA.

L_TAXTYPE

OapfL_TaxType Tax Type Applied

L_TRACKINGNUMn VRSN_EXTEND_LINEITEM

_DATA.

L_TRACKINGNUM

OapfL_TrackingNum Item Tracking Number


PF Pro Parameter

Database -


Oapf Parameter



58/76


Parameters MappingB


L_TYPEn VRSN_EXTEND_LINEITEM_DATA.

L_TYPE

OapfL_Type Item Type

L_UNSPSCCODEn VRSN_EXTEND_LINEITEM

_DATA.L_UNSPSCCODE

OapfL_UnspscCode Item UNSPC Code

L_UOM VRSN_EXTEND_LINEITEM

_DATA.

L_UOM

OapfL_UOM Item Unit of

Measurement

L_UPCn VRSN_EXTEND_LINEITEM

_DATA.

L_UPC

OapfL_UPC Item Universal Product

Code

L_WEIGHTUOMn VRSN_EXTEND_LINEITEM

_DATA.

L_WEIGHTUOM

OapfL_WeightUOM Not used currently by the

Payment Gateway

LASTNAME VRSN_EXTEND_DATA.LAS

TNAME

OapfLastName Customer's Last Name

LOCALTAXAMT VRSN_EXTEND_DATA.

LOCALTAXAMT

OapfLocalTaxAmt Local Tax Amount


PF Pro Parameter

Database -


Oapf Parameter



59/76



Parameters MappingB

MD NA NA The Merchant Data field:Merchant state data that

must be returned to the

merchant. This field is

used to accommodate the

different ways merchant

systems handle session

state. If the merchant

system can associate the

final post with the

original shopping session

without any further

assistance, the MD field

may be empty. If the

merchant system does not

maintain state for a given

shopping session, the MD

can carry whatever data

the merchant needs to

continue the session.

Since the content of this

field varies by merchant

implementation, the ACS

must preserve it

unchanged and without

assumptions about itscontent.

The MD field must

contain only ASCII

characters in the range

0x20 to 0x7E.

If other data is needed,

then the field must be

Base64-encoded. The

size of the field (after

Base64 encoding, if

applicable) is limited to

1024 bytes.If MD includes

confidential data (such as

the PAN), then it must be

encrypted.

MERCHDESCR VRSN_EXTEND_DATA.

MERCHDESCR

OapfMerchDescr Merchant Description


PF Pro Parameter

Database -


Oapf Parameter



60/76


61/76



Parameters MappingB

PARMLIST NA NA The ParmList is the list ofparameters that specify

the payment information

for the transaction. The

quotation marks at the

beginning and end are

required. In the example,

the ParmList is:

TRXTYPE=S&TENDE

R=C&PARTNER=PayPa

l&VENDOR=Super

Merchant&USER=Super

Merchant&PWD=x1y2z3&ACCT=55555555

55554444&EXPDATE=0

308&AMT=123.00

PARTNER VRSN_EXTEND_DATA.

VSGNPARTNER

In the preTxn method of

TxnCustomizer_vps. If

all of PARTNER, PWD,

USER, and VENDOR

are present then they are

arranged into the format

of OapfStoreId and put

into OapfExternalStoreId

field. These aremandatory for Buyer

Authentication.

Partner Name

PASSWORDGIVEN VRSN_EXTEND_DATA.

PASSWORDGIVEN

OapfPasswordGiven Password Given (Y/N)

PHONE Not Supported Not Supported NA

PHONENUM VRSN_EXTEND_DATA.

PHONENUM

OapfPhone Account Holder's

Telephone Number

PNREF IBY_TRXN_CORE.

REFERENCECODE

OapfRefcode Reference Number for

the current transaction

PONUM VRSN_EXTEND_DATA.PON

UM

OapfPONum Purchase Order Number

POSTFPSMSG VRSN_EXTEND_DATA.

POSTFPSMSG

OapfPostFPSMsg Post FPS Message

PREFPSMSG VRSN_EXTEND_DATA.

PREFPSMSG

OapfPreFPSMsg Pre FPS Message


PF Pro Parameter

Database -


Oapf Parameter



62/76


Parameters MappingB


PRENOTE VRSN_EXTEND_DATA.PRENOTE

OapfPreNote Prenote (Y/N)

PREVIOUSCUST VRSN_EXTEND_DATA.

PREVIOUSCUST

OapfPreviousCust Previous Customer (Y/N)

PROCAVS VRSN_EXTEND_DATA.PRO

CAVS

OapfProcAVS AVS (Address

Verification Service)

response from the

Processor.

PROCCARDSECURE VRSN_EXTEND_DATA.

PROCCARDSECURE

OapfProcCardSecure VPAS/SPA response

from the Processor.

PROCCVV2 VRSN_EXTEND_DATA.PROCCVV2

OapfProcCVV2 CVV2 (BuyerAuthentication) response

from the Processor.

PROXYADDRESS NA NA Proxy server address. Use

the PROXY parameters

for servers behind a

firewall.

PROXYLOGON NA NA Proxy server logon ID

PROXYPASSWORD NA NA Proxy server logon

password

PROXYPORT NA NA Proxy server portPUR_DESC VRSN_EXTEND_DATA.PUR

_DESC

OapfPur_Desc Purchase Description

PWD VRSN_EXTEND_DATA.

VSGNPASSWORD




USER, and VENDOR





field. These are

mandatory for Buyer

Authentication.

Merchant's Password.

RECURRING VRSN_EXTEND_DATA.

RECURRING

OapfRecurring Recurring Account (Y/N)

REGLOYALTY VRSN_EXTEND_DATA.

REGLOYALTY

OapfRegLoyalty Registered For Loyalty

program (Y/N)


PF Pro Parameter

Database -


Oapf Parameter



63/76



Parameters MappingB

REGPROMO VRSN_EXTEND_DATA.REGPROMO

OapfRegPromo Registered ForPromotions (Y/N)

REQNAME VRSN_EXTEND_DATA.REQ

NAME

OapfReqName

RESPMSG VRSN_EXTEND_DATA.RES

PMSG

OapfRespMsg Response Message

RESPTEXT VRSN_EXTEND_DATA.RES

PTEXT

OapfRespText Text corresponding to the

response code returned

by the Processor.

RESULT VRSN_EXTEND_DATA.RES

ULT

OapfResult Result

RETURNALLOWED VRSN_EXTEND_DATA.

RETURNALLOWED

OapfReturnAllowed Return Allowed (Y/N)

SETTLE_DATE NA NA NA

SHIPCARRIER VRSN_EXTEND_DATA.

SHIPCARRIER

OapfShipCarrier Shipping Carrier

SHIPFROMZIP VRSN_EXTEND_DATA.

SHIPFROMZIP

OapfShipFromZip Ship From Postal Code

SHIPMENTNO VRSN_EXTEND_DATA.

SHIPMENTNO

OapfShipmentNo Shipment Number

SHIPMETHOD VRSN_EXTEND_DATA.

SHIPMETHOD

OapfShipMethod Shipping Method (N, T,

W, C, D, I, M, P, O)

SHIPTOCITY VRSN_EXTEND_DATA.

SHIPTOCITY

OapfShipToCity Ship To City

SHIPTOCOUNTRY VRSN_EXTEND_DATA.

SHIPTOCOUNTRY

OapfShipToCountry Country code of the

shipping country. (US,

USA, 840)

SHIPTOEMAIL VRSN_EXTEND_DATA.

SHIPTOEMAIL

OapfShipToEmail Ship To E-mail

SHIPTOFIRSTNAME VRSN_EXTEND_DATA.

SHIPTOFIRSTNAMEOapfShipToFirstName Ship To First Name

SHIPTOLASTNAME VRSN_EXTEND_DATA.

SHIPTOLASTNAME

OapfShipToLastName Ship To Last Name

SHIPTOMIDDLENA

ME

VRSN_EXTEND_DATA.

SHIPTOMIDDLENAME

OapfShipToMiddleName Ship To Middle Name


PF Pro Parameter

Database -


Oapf Parameter



64/76


Parameters MappingB


SHIPTOPHONE VRSN_EXTEND_DATA.SHIPTOPHONE

OapfShipToPhone Ship To Phone

SHIPTOPHONE2 VRSN_EXTEND_DATA.

SHIPTOPHONE2

OapfShipToPhone2 Alternative Phone

Number For The

Shipping Contact

SHIPTOSTATE VRSN_EXTEND_DATA.

SHIPTOSTATE

OapfShipToState Ship To State

SHIPTOSTREET VRSN_EXTEND_DATA.

SHIPTOSTREET

OapfShipToStreet Ship To Street Address

SHIPTOSTREET2 VRSN_EXTEND_DATA.

SHIPTOSTREET2

OapfShipToStreet2 Extended shipping

address

SHIPTOZIP VRSN_EXTEND_DATA.SHIP

TOZIP

OapfShipToZip Ship To Zip Code

SS VRSN_EXTEND_DATA.SS OapfSS Account Holder's Social

Security Number

SSN VRSN_EXTEND_DATA.SSN OapfSSN Customer's Social

Security Number (SSN)

STARTTIME VRSN_EXTEND_DATA.

STARTTIME

OapfStartTime Optional for Inquiry

transactions when using

CUSTREF to specify the

transaction.STARTTIME specifies

the beginning of the time

period during which the

transaction specified by

the CUSTREF occurred.

If you set STARTTIME,

and not ENDTIME, then

ENDTIME is defaulted to

30 days after

STARTTIME.

If neither STARTTIME

nor ENDTIME isspecified, then the system

searches the last 30 days.

(yyyymmddhhmmss)

STATE HZ_LOCATIONS.COUNTY OapfState Billing State

STREET HZ_LOCATIONS.ADDRESS1 OapfAddr1 Billing Street Address


PF Pro Parameter

Database -


Oapf Parameter



65/76



Parameters MappingB

SUBTOTAL VRSN_EXTEND_DATA.SUBTOTAL

OapfSubTotal Subtotal

SWIPE VRSN_EXTEND_DATA.SWI

PE

OapfSwipe Swipe

TAXAMT VRSN_EXTEND_DATA.TAX

AMT

OapfTaxAmt Tax Amount

TAXEXEMPT (Y/N) VRSN_EXTEND_DATA.

TAXEXEMPT

OapfTaxExempt Tax Exempt (Y/N)

TENDER VRSN_EXTEND_DATA.TEN

DER

OapfExtendTender Brand

TERMCITY VRSN_EXTEND_DATA.TER

MCITY

OapfTermCity City of terminal that

captured the transaction

TERMSTATE VRSN_EXTEND_DATA.

TERMSTATE

OapfTermState State of terminal that

captured the transaction

TERMURL NA Taken from

vpsipayment.properties

at initialization.

URL of the Merchant

Application

TIMEOUT NA NA Time-out period for the

transaction. The

minimum recommended

time-out value is 30seconds. The PayPal

client begins tracking

from the time that it

sends the transaction

request to the PayPal

server.

TRXTYPE This is not saved in DB. It is

generated at transaction time

according to the action sent by

the OIP to the BEP servlet.

E.g. If we are doing an

authorization transaction, thenOapfAction=oraauth and from

this trxtype is set to "A"

OapfAction (S=Sale, C=Credit,

A=Authorize,

D=Capture, V=Void,

F=Force/Voice

Authorization, I=Inquiry)


PF Pro Parameter

Database -


Oapf Parameter



66/76


Parameters MappingB


USER VRSN_EXTEND_DATA.VSGNUSER

In the preTxn method ofTxnCustomizer_vps. If


USER, and VENDOR





field. These are

mandatory for Buyer

Authentication.

User Name.

VATREGNUM VRSN_EXTEND_DATA.

VATREGNUM

OapfVatRegNum VAT Registration

Number

VATTAXAMT VRSN_EXTEND_DATA.

VATTAXAMT

OapfVatTaxAmt Not used currently by the

Payment Gateway

VATTAXPERCENT VRSN_EXTEND_DATA.

VATTAXPERCENT

OapfVatTaxPercent Not used currently by the

Payment Gateway

VENDOR VRSN_EXTEND_DATA.

VSGNVENDOR




USER, and VENDOR





field. These are

mandatory for Buyer

Authentication.

Vendor Name

VERBOSITY VRSN_EXTEND_DATA.

VERBOSITY

OapfVerbosity Verbosity (HIGH,

MEDIUM, LOW)

WRAPPED VRSN_EXTEND_DATA.WR

APPED

OapfWrapped Gift Wrapping (Y/N)

XID VRSN_EXTEND_DATA.XID OapfXID Buyer Authentication

Transaction Id.

ZIP HZ_LOCATIONS.POSTALCO

DE

OapfPostalCode Billing Zip Code


PF Pro Parameter

Database -


Oapf Parameter



67/76


C Troubleshooting

This appendix contains troubleshooting topics. It describes how to enable debug log file

creation and identifies what information you should have available before contacting

Customer Support.

Enabling Debug Lo g File Creation

By default the debug logs are disabled. To enable the log files, set debug to true in your

zone. proper t i esfile for the following servlets:

servl et. orami pp_vps

servl et . orami pp_sampl estore

servl et . orami pp_Payee2VPS

Before Contact ing Customer Suppor t

Before contacting Customer Support, ensure that you have done the following:

Obtain and send the following log files after doing an isolated independent transaction.

Clear the log files before doing the transaction. i byvpsserv. l og

Oracle iPayment patch set 11i.IBY.N and previous

i by_debug. l og

i by_er ror . l og

Oracle iPayment patch set 11i.IBY.O

i by. l og

For details on generating log files on 11i.IBY.O and later, see Note 265330.1.

Obtain and send the following properties files.

vpsi payment . propert i es

j serv. propert i es

zone. proper t i es

j ava. secur i tyfile

T