Oracle P Card and IExpense

DEVELOPER’S GUIDE
VeriSign Payment Services
Oracle iPayment Back-End Payment Servlet

Installation Guide
VeriSign Payment Services, including Payflow Link and Payflow Pro, was recently acquired by PayPal,
and will be integrated with PayPal's suite of web payment tools to form the e-commerce industry’s most
comprehensive web payment offering. The VeriSign Payment Services are no longer operated by, or
affiliated with, VeriSign, Inc. Use of the VeriSign name and logo is temporary and with the permission
of VeriSign, Inc.
VeriSign, Inc. VPS-0007/Rev11

VeriSign Payment Services Oracle iPayment Back-End Payment Servlet Installation Guide
-----------------------------------------------------------
Copyright © 1998 - 2006 VeriSign, Inc. All rights reserved.

The information in this document belongs to VeriSign. It may not be used, reproduced or disclosed
without the written approval of VeriSign.
DISCLAIMER AND LIMITATION OF LIABILITY

VeriSign, Inc. has made efforts to ensure the accuracy and completeness of the information in this
document. However, VeriSign, Inc. makes no warranties of any kind (whether express, implied or
statutory) with respect to the information contained herein.VeriSign, Inc. assumes no liability to any
party for any loss or damage (whether direct or indirect) caused by any errors, omissions, or
statements of any kind contained in this document.
Further, VeriSign, Inc. assumes no liability arising from the application or use of the product or service
described herein and specifically disclaims any representation that the products or services
described herein do not infringe upon any existing or future intellectual property rights. Nothing herein
grants the reader any license to make, use, or sell equipment or products constructed in accordance
with this document. Finally, all rights and privileges related to any intellectual property right described
herein are vested in the patent, trademark, or service mark owner, and no other person may exercise
such rights without express permission, authority, or license secured from the patent, trademark, or
service mark owner. VeriSign Inc. reserves the right to make changes to any information herein
without further notice.
TRADEMARKS
VeriSign, the VeriSign logo, “Where it all comes together.”, Intelligence and Control, VeriSign Trust
Network, Payflow, Payflow Pro, Payflow Link, XMLPay, and other trademarks, service marks, and
logos are registered or unregistered trademarks of VeriSign and its subsidiaries in the United States
and in foreign countries. Other trademarks and service marks in this document are the property of
their respective owners.
This document may describe features and/or functionality that are not present in your software or your service
agreement. Contact your account representative to learn more about what is available with this VeriSign product.
If you need help using this product, contact customer support.
vps-support@verisign.com
1.888.883.9770
Publication date: January 2006

Summary of Revisions
-----------------------------------------------------------
Summary of Revisions
VeriSign Payment Services Oracle iPayment Back-End Payment Servlet

Installation Guide
The following changes were made to this document since the last revision:
Throughout Document Converted document to wider format.

Updated with changes for Oracle 11.5.10--all
platforms.
Updated Windows and UNIX installation
instructions.
VeriSign Payment Services Oracle iPayment Back-End Payment Servlet

Installation Guide
The following changes were made to this document since the last revision:
Throughout Document Converted document to wider format.

Updated with changes for Oracle 11.5.10 release
on AIX 5.2.
Separated Windows and UNIX installation
instructions into two chapters.
Appendix C, Moved section on what to have available before

“Troubleshooting” contacting Customer Support to this appendix.
VeriSign, Inc. VPS-0007/Rev11 iii

-----------------------------------------------------------
VeriSign, Inc. VPS-0007/Rev11 iv

DEVELOPER’S GUIDE
- - - - - - -Contents
-----------------------------
+ Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . . . . iii
+ Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Accessing the VeriSign BEP Servlet for Oracle iPayment
3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
VeriSign Documents . . . . . . . . . . . . . . . . . . . . . . . . . 3
Oracle iPayment Documents . . . . . . . . . . . . . . . . . . . 3
How to Contact Customer Support . . . . . . . . . . . . . . . . 3
+ Chapter 2 Installing and Configuring on Windows

5
Manually Installing the VeriSign BEP Servlet on Windows
5
Uninstalling the BEP Servlet . . . . . . . . . . . . . . . . . . . . 12
+ Chapter 3 Installing and Configuring on

Non-Windows Platforms 13
Manually Installing the VeriSign BEP Servlet on
Non-Windows Platforms . . . . . . . . . . . . . . . . . . . . . . 14
Uninstalling the BEP Servlet . . . . . . . . . . . . . . . . . . . . 20
VeriSign, Inc. VPS-0007/Rev11 v

-----------------------------------------------------------
+ Chapter 4 Registering and Testing . . . . . . . . . . . . 21

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Registering the BEP Servlet in iPayment . . . . . . . . . . . 21
Testing the Installation Using the Oracle iPayment User
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Testing the Installation Using VeriSign’s Sample Store 34
Processing Live Transactions . . . . . . . . . . . . . . . . . . . . 36
+ Chapter 5 Building Your Own Web Site . . . . . . . . 37
+ Appendix A Transaction Decline or Error RESULTs

and RESPMSGs39
+ Appendix B Mapping VeriSign Parameters to

iPayment Parameters45
Parameters Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
+ Appendix C Troubleshooting . . . . . . . . . . . . . . . . . . 61
Enabling Debug Log File Creation . . . . . . . . . . . . . . . . 61
Before Contacting Customer Support . . . . . . . . . . . . . . 61
+ Appendix D Manually Uninstalling the VeriSign

BEP Servlet63
+ Appendix E Encrypting Your Database User

Password67
+ Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
vi VeriSign, Inc. VPS-0007/Rev11

CHAPTER 1
Introduction
1retpahC
This guide provides information on installing and configuring the VeriSign Back-end
Payment System (BEP) servlet for use with Oracle iPayment.
Intended Audience
This guide is for merchants and administrators who are implementing the Oracle
iPayment module with Oracle Applications and the VeriSign 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 (merchant’s version)
+ Oracle iPayment
Note In this guide, you refers to the merchant or administrator.
This guide assumes that you are familiar with the documents listed in “Related
Documents” on page 3.
VeriSign, Inc. VPS-0007/Rev11 1

----------------------------------------------------------------
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.
VeriSign Payment Services Payflow Pro is a real-time Secure Socket Layer (SSL) payment
system supporting credit card transactions using pure Java libraries. Payflow Pro
supports all iPayment core operations. It also supports the following additional
operations through the iPayment’s extensibility API:
+ Fraud Protection services
+ Purchase cards, Level 2 and 3
+ Buyer Authentication
The BEP servlet integrates Payflow Pro with Oracle iPayment to manage online payment
processing.
iStore (or any

iPayment
core operation)
Order Capture Administrative

Interface
Accounts Order
Receivable Management
EC
Extensibility
app.
BEP APIs
Java iPayment HTTP(S) VeriSign

APIs engine Adapter Servlet
EC
servlet
Figure 1-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.
2 VeriSign, Inc. VPS-0007/Rev11

Chapter 1 Introduction
----------------------------------------------------------------
Accessing the VeriSign BEP Servlet for Oracle iPayment

To access the BEP servlet, you must register for a VeriSign Payflow Pro Payment Services
account.
Register with VeriSign either directly from the following VeriSign Payment Web site or
through a reseller of VeriSign Payment Services.
http://www.verisign.com/products-services/payment-processing/index.html
You can request the BEP servlet for Oracle iPayment by sending an e-mail to
vps-integrator@verisign.com.
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, and
permissions. See the Oracle documentation for details.
+ You must create an Administration User for Oracle iPayment. See the Oracle
documentation for details.
+ VeriSign has tested with Oracle Applications 11.5.9 and 11.5.10 on AIX 5.2 and
Windows.
Related Documents
The following documents support information found in this guide. You should read these
documents before using this guide.
VeriSign Documents
+ VeriSign Payment Services Payflow Pro Developer’s Guide
+ VeriSign Payment Services User’s Guide for Payflow Pro with Fraud Protection Services
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 VeriSign, contact
Customer Support at vps-integrator@verisign.com.
For a list of tasks that you need to complete before contacting Customer Support, see
“Before Contacting Customer Support” on page 61.

----------------------------------------------------------------

CHAPTER 2
Installing and Configuring on Windows

2retpahC
This chapter guides you through installing and configuring the VeriSign Payment
Services (VPS) servlet for use with Oracle iPayment on Windows.
The VeriSign BEP servlet is not configured as a part of Oracle Applications Rapid
Installation process. Follow the appropriate procedures in this section to install it.
VeriSign BEP servlet installation on Windows uses the directory references described in
Table 2-1.
Table 2-1 BEP Servlet path and directory notation
Notation Description
%VERISIGN_TOP% Represents the verisign directory into which the pfpro_ipayment.zip file
is unzipped, as shown in Figure 2-1.
If, for example, you unzipped pfpro_ipayment.zip into D:\oracle\,
%VERISIGN_TOP% would represent D:\oracle\verisign, the top-level
directory in the directory structure.
%ORACLE_TOP% Represents the top-level Oracle directory for Oracle Apps, for
example, D:\oracle\visora.
%APPL_TOP% Represents the top-level application directory for Oracle Apps, for
example D:\oracle\visappl.
%COMN_TOP% Represents the top-level Oracle Apps common directory, for example,
D:\oracle\viscomn.
%JAVA_HOME% Java home directory of your JDK, for example, C:\j2sdk1.4.2
Manually Installing the VeriSign BEP Servlet on Windows

Note Before you install or uninstall the VeriSign 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 <dbid>/<dbpwd>@<SID>

<dbid> is the database user ID
<dbpwd> is the database password
<SID> is the database instance ID

----------------------------------------------------------------
The following procedure explains how to manually install the VeriSign BEP Servlet. If
you are using VeriSign BEP Servlet version 3.1, follow the guidelines in “Manually
Uninstalling the VeriSign BEP Servlet” on page 63 before installing the current servlet
version.
Step 1 Unzip the pfpro_ipayment file

Unzip the pfpro_ipayment.zip file to a local directory. The file unzips into the directory
structure shown in Figure 2-1. The directory contains all files required to configure
iPayment to use the VeriSign BEP.
Figure 2-1 pfpro_ipayment directory structure
Table 2-2 pfpro_ipayment directory contents
Directory or File Contents / Description
certs directory f7389fd.0 (digital certificate)
classes directory Contains the following directories:

com directory - Contains verisign\iPayment\*.class (Classes
required by the VeriSign objects. The class files are in the
verisign\iPayment subdirectories such as bizcomp and
buyerauth.)
ibyextend directory - Contains TxnCustomizer_vps.class
(VeriSign requires iPayment extensibility. These classes
should be accessible to iPayment)
docs directory Contains OracleiPayment.pdf
lib directory Contains Verisign.jar
samplestore directory Contains files for VeriSign sample store:

Error.jsp - Error page for Sample Store
iPaymentSampleStore.jsp - Main page for Sample Store
VeriSignLogo.JPG - logo to be displayed on Sample Store

Chapter 2 Installing and Configuring on Windows
----------------------------------------------------------------
sql directory Contains the following sql files:

VRSN_Create_Table.sql - SQL script to create the
VeriSign-specific tables in the Oracle Apps database
VRSN_Drop_Table.sql - SQL script to drop the
VeriSign-specific tables from the Oracle Apps database
verisign directory Contains the following files:

param.xml
vpsipayment.properties - (vpsipayment.properties is the key
property file to be used by VeriSign’s integration of the Oracle
iPayment servlet.)
ReleaseNotes.txt Contains release notes
Step 2 Stop the Oracle Apache server

The Oracle Apache Server runs as a Windows service. Stop the service using the Services
control panel.
Step 3 Copy VeriSign files

1 Copy the following directories from the %VERISIGN_TOP%\payflowpro\ipayment
\classes directory into the %ORACLE_TOP% \iAS\Apache\Jserv\servlets
directory:
+ com directory
+ ibyextend directory
2 Copy the following files from the
%VERISIGN_TOP%\payflowpro\ipayment\verisign directory into the
%ORACLE_TOP%\8.0.6\verisign directory:
+ param.xml
+ vpsipayment.properties
%VERISIGN_TOP%\payflowpro\ipayment\samplestore directory into the
%COMN_TOP%\html directory:
+ VeriSignLogo.jpg
+ Error.jsp
+ iPaymentSampleStore.jsp
4 Copy the following file from the %VERISIGN_TOP%\payflowpro\ipayment\lib
directory into the %APPL_TOP%\iby\11.5.0\lib directory:

----------------------------------------------------------------
+ Verisign.jar
5 Copy the following directory from the %VERISIGN_TOP%\payflowpro\ipayment
directory into the %ORACLE_TOP%\8.0.6 directory:
+ certs directory
Step 4 Download Xerces XML Parser

1 Download the Xerces-J 2.7.1 package (XML parser) called Xerces-J-bin.2.7.1.zip
from Apache’s 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%\iby\11.5.0\lib directory:
+ xercesImpl.jar
+ xml-apis.jar
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%\iAS\Apache\jdk\jre\lib\ext directory:
+ jcert.jar
+ jnet.jar
+ jsse.jar

----------------------------------------------------------------
Step 6 Modify vpsipayment.properties

Table 2-3 shows the entries in the vpsipayment.properties file. You are going to modify these entries
to reflect your current environment, as described below:
1 Edit the properties in the
%ORACLE_TOP%\8.0.6\verisign\vpsipayment.properties file as indicated in Table
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 vpsipayment.properties file.
2 Replace the value of the dbpwd entry in your version of the vpsipayment.properties
file with your encrypted database user password. For instructions on how to encrypt
your password, see Appendix E, “Encrypting Your Database User Password.”
Table 2-3 vpsipayment.properties parameters to be modified
Name Default Value Description
hostname test-payflow.verisign.com VeriSign’s 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
certs /mv1/oracle/demoora/8.0.6/cer Digital certificates folder containing the

ts certificate file, fy3d89fd.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 VeriSign Buyer Authentication

server

----------------------------------------------------------------
termurl http://machine.yourdomain.co Merchant URL for Buyer Authentication.

m:8000/servlets/oramipp_ The format is:
Payee2VPS http://<hostname>:<port>/servlets/oramipp_
Payee2VPS
dburl jdbc:oracle:thin:@machine.you JDBC database connection URL for the

rdomain.com:1521:DEMO Oracle Apps instance. The format is:
jdbc:oracle:thin:@<db hostname>:<db
port>:<db SID>
Note: <db port> is your database listener
port number, not your Apache Web server
port.
dbuid apps Database user ID
dbpwd apps Database user password (encrypted)
Step 7 Modify zone.properties

1 Modify the zone.properties located in a directory such as:
%ORACLE_TOP%\iAS\Apache\Jserv\etc
2 Insert the contents of the Windows section from the
%VERISIGN_TOP%\verisign\payflowpro\ipayment\zone.properties.verisign file
between the “Begin Customizations” and “End Customizations” tags of your
zone.properties file.
If the Begin and End tags are not present, then insert the contents of the Windows
section from the
to the end of your zone.properties file.
Note If you have Oracle’s autoconfig utility turned on, then you must enclose the
statements from the
in between the “#Begin Customizations” and “#End Customizations” tags.
3 In the newly inserted statements in your zone.properties file, replace

%ORACLE_TOP% and %APPL_TOP% with 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%\iAS\Apache\Jserv\etc

----------------------------------------------------------------
2 Insert the contents of the Windows section from the

%VERISIGN_TOP%\verisign\payflowpro\ipayment\jserv.properties.verisign file
jserv.properties file.
If the Begin and End tags are not present, then insert the contents of the Windows
section from the
to the end of your jserv.properties file.
statements from the
3 In the newly inserted statements in your jserv.properties file, replace

%ORACLE_TOP% and %APPL_TOP% with the appropriate values for your
environment.
4 If the following lines are present in your jserv.properties file, remove Oracle’s SSL
implementation by commenting out the following two lines:
wrapper.classpath=%ORACLE_TOP%\iAS\jlib\javax-ssl-1_1.jar
5 Add the JSSE provider as described below.
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 your java.security file in the

%ORACLE_TOP%\iAS\Apache\jdk\jre\lib\security and
%JAVA_HOME%\jre\lib\security directories 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=”
security.provider.2=com.sun.net.ssl.internal.ssl.Provider
security.provider.3=com.sun.crypto.provider.SunJCE
Note If %ORACLE_TOP%\iAS\Apache\jdk\jre\lib\security\java.security does not

point to the default JDK version set in the class path, then this change also needs to be
made to the java.security file associated with the default JDK at
%JAVA_HOME%\jre\lib\security.

----------------------------------------------------------------
Step 9 Create the database tables

To create the database tables:
1 Log in to the Oracle database using sqlplus.
sqlplus $dbuid/$dbpwd@<SID>
(for example, sqlplus apps/apps@DEMO)

2 Run the Create Table sql script from the sql prompt.
@%VERISIGN_TOP%\payflowpro\ipayment\sql\VRSN_Create_Table.sql
Be sure to replace %VERISIGN_TOP% with its appropriate value.

3 To verify that all tables were created, run the following commands:
+ desc VRSN_EXTEND_DATA
+ desc VRSN_BUYERAUTH
+ desc VRSN_EXTEND_LINEITEM_DATA
The above commands should display the table structure for the table created.
Step 10 Start the Oracle Apache server

The Oracle Apache server runs as a Windows service. Start the service using the Services
control panel.
Step 11 Register the BEP Servlet in iPayment

For detailed instructions on registering the BEP servlet, see Chapter 4, “Registering and
Testing.”
Uninstalling the BEP Servlet

To uninstall the BEP servlet, undo the steps in “Manually Installing the VeriSign BEP
Servlet on Windows” starting on page 5. In substep 2 of “Create the database tables” on
page 12, run the VRSN_Drop_Table.sql script from the sql prompt instead of running
the VRSN_Create_Table.sql script.

CHAPTER 3
Installing and Configuring on Non-Windows

3retpahC
Platforms
This chapter guides you through installing and configuring the VeriSign Payment
Services (VPS) servlet for use with Oracle iPayment on non-Windows platforms.
The VeriSign BEP servlet is not configured as a part of Oracle Applications Rapid
Installation process. Follow the appropriate procedures in this section to install it.
VeriSign BEP servlet installation on non-Windows platforms uses the directory
references described in Table 3-1.
Table 3-1 BEP Servlet path and directory notation
$VERISIGN_TOP Represents the verisign directory into which the pfpro_ipayment.zip file
If, for example, you unzipped pfpro_ipayment.zip into /mv2/oracle/,
$VERISIGN_TOP would represent /mv2/oracle/verisign, the top-level
$ORACLE_TOP Represents the top-level Oracle directory for Oracle Apps, for
example, /mv2/oracle/visora.
$APPL_TOP Represents the top-level application directory for Oracle Apps, for
example /mv2/oracle/visappl.
$COMN_TOP Represents the top-level Oracle Apps common directory, for example,
/mv2/oracle/viscomn.
$JAVA_HOME Java home directory of your JDK, for example, /usr/j2sdk1.3.1

----------------------------------------------------------------
Manually Installing the VeriSign BEP Servlet on Non-Windows

Platforms
$ sqlplus <dbid>/<dbpwd>@<SID>
The following procedure explains how to manually install the VeriSign BEP Servlet. If
you are using VeriSign BEP Servlet version 3.1, follow the guidelines in “Manually
Uninstalling the VeriSign BEP Servlet” on page 63 before installing the current servlet
version.
Step 1 Unzip the pfpro_ipayment file

Unzip the pfpro_ipayment.zip file to a local directory. The file unzips into the directory
structure shown in Figure 3-1. The directory contains all files required to configure
iPayment to use the VeriSign BEP.
Figure 3-1 pfpro_ipayment directory structure
certs directory f7389fd.0 (digital certificate)

Chapter 3 Installing and Configuring on Non-Windows Platforms
----------------------------------------------------------------
classes directory Contains the following directories:

com directory - Contains verisign\iPayment\*.class (Classes
required by the VeriSign objects. The class files are in the
verisign\iPayment subdirectories such as bizcomp and
buyerauth.)
ibyextend directory - Contains TxnCustomizer_vps.class
(VeriSign requires iPayment extensibility. These classes
should be accessible to iPayment)
docs directory Contains OracleiPayment.pdf
lib directory Contains Verisign.jar
verisign directory Contains the following files:

param.xml
vpsipayment.properties - (vpsipayment.properties is the key
property file to be used by VeriSign’s integration of the Oracle
iPayment servlet.)
samplestore directory Contains files for VeriSign sample store:

Error.jsp - Error page for Sample Store
iPaymentSampleStore.jsp - Main page for Sample Store
VeriSignLogo.JPG - logo to be displayed on Sample Store
ReleaseNotes.txt Contains release notes
sql directory Contains the following sql files:

VRSN_Create_Table.sql - SQL script to create the
VeriSign-specific tables in the Oracle Apps database
VRSN_Drop_Table.sql - SQL script to drop the
VeriSign-specific tables from the Oracle Apps database

Stop the Oracle Apache Server by using the following command:
sh $COMN_TOP/admin/scripts/<DB Instance Name>_<Host Name>/adapcctl.sh stop
for example:
sh /mv2/oracle/demo2comn/admin/scripts/DEMO2_aix2/adapcctl.sh stop
Step 3 Copy VeriSign files

1 Copy the following directories from the $VERISIGN_TOP/payflowpro/ipayment
/classes directory into the $ORACLE_TOP/iAS/Apache/Jserv/servlets directory:
+ com directory
+ ibyextend directory

----------------------------------------------------------------

$VERISIGN_TOP/payflowpro/ipayment/verisign directory into the
$ORACLE_TOP/8.0.6/verisign directory:
+ param.xml
3 Copy the following files from
$VERISIGN_TOP/payflowpro/ipayment/samplestore directory into
$COMN_TOP/html directory:
+ VeriSignLogo.jpg
+ Error.jsp
4 Copy the following file from the $VERISIGN_TOP/payflowpro/ipayment/lib
directory into the $APPL_TOP/iby/11.5.0/lib directory:
+ Verisign.jar
5 Copy the following directory from the $VERISIGN_TOP/payflowpro/ipayment
directory into the $ORACLE_TOP/8.0.6 directory:
+ certs directory
Step 4 Download Xerces XML Parser

1 Download the Xerces-J 2.7.1 package (XML parser) called Xerces-J-bin.2.7.1.tar.gz
from Apache’s 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/iby/11.5.0/lib directory:
+ xercesImpl.jar
+ xml-apis.jar
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/iAS/Apache/jdk/jre/lib/ext directory:
+ jcert.jar
+ jnet.jar
+ jsse.jar
Step 6 Modify vpsipayment.properties

Table 2-3 shows the entries in the vpsipayment.properties file that you are going to modify to reflect
your current environment.
hostname test-payflow.verisign.com VeriSign’s host name

For test transactions, use
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/cer Digital certificates folder containing the

ts certificate file, fy3d89fd.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 VeriSign Buyer Authentication

server
termurl http://machine.yourdomain.co Merchant URL for Buyer Authentication.

m:8000/servlets/oramipp_ The format is:
Payee2VPS http://<hostname>:<port>/servlets/oramipp_
Payee2VPS

----------------------------------------------------------------
dburl jdbc:oracle:thin:@machine.you JDBC database connection URL for the

rdomain.com:1521:DEMO Oracle Apps instance. The format is:
jdbc:oracle:thin:@<db hostname>:<db
port>:<db SID>
Note: <db port> is your database listener
port number, not your Apache Web server
port.
dbuid apps Database user ID
dbpwd apps Database user password (encrypted)
1 Edit the properties in the $ORACLE_TOP/8.0.6/verisign/vpsipayment.properties

file as indicated in Table 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 vpsipayment.properties file.
2 Replace the value of the dbpwd entry in your version of the vpsipayment.properties
file with your encrypted database user password. For instructions on how to encrypt
your password, see Appendix E, “Encrypting Your Database User Password.”

1 Modify the zone.properties located in a directory such as:
$ORACLE_TOP/iAS/Apache/Jserv/etc
2 Insert the contents of the non-Windows platforms section from the
$VERISIGN_TOP/verisign/payflowpro/ipayment/zone.properties.verisign file
zone.properties file.
If the Begin and End tags are not present, then insert the contents of the
non-Windows platforms section from the
$VERISIGN_TOP/verisign/payflowpro/ipayment/zone.properties.verisign file to
the end of your zone.properties file.
statements from the
$VERISIGN_TOP/verisign/payflowpro/ipayment/zone.properties.verisign file in
between the “#Begin Customizations” and “#End Customizations” tags.

----------------------------------------------------------------
3 In the newly inserted statements in your zone.properties file, replace $ORACLE_TOP

and $APPL_TOP with 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/iAS/Apache/Jserv/etc
2 Insert the contents of the non-Windows platforms section from the
$VERISIGN_TOP/verisign/payflowpro/ipayment/jserv.properties.verisign file
jserv.properties file.
If the Begin and End tags are not present, then insert the contents of the non-Windows
platforms section from the
$VERISIGN_TOP/verisign/payflowpro/ipayment/jserv.properties.verisign file to
the end of your jserv.properties file.
statements from the
3 In the newly inserted statements in your jserv.properties file, replace $ORACLE_TOP

and $APPL_TOP with the appropriate values for your environment.
4 If the following lines are present in your jserv.properties file, remove Oracle’s SSL
implementation by commenting out the following two lines:
wrapper.classpath=$ORACLE_TOP/iAS/jlib/javax-ssl-1_1.jar
wrapper.classpath=$ORACLE_TOP/iAS/jlib/javax-ssl-1_2.jar
5 Add the JSSE provider as described below.
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 your java.security file in the

$ORACLE_TOP/iAS/Apache/jdk/jre/lib/security and
$JAVA_HOME/jre/lib/security directories 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=”
security.provider.3=com.sun.crypto.provider.SunJCE

----------------------------------------------------------------
Note If $ORACLE_TOP/iAS/Apache/jdk/jre/lib/security/java.security does not

point to the default JDK version set in the class path, then this change also needs to
be made to the java.security file associated with the default JDK at
$JAVA_HOME/jre/lib/security.
Step 9 Create the database tables

To create the database tables:
1 Log in to the Oracle database using sqlplus.
sqlplus $dbuid/$dbpwd@<SID>
(for example, sqlplus apps/apps@DEMO)

2 Run the Create Table sql script from the sql prompt.
@$VERISIGN_TOP/payflowpro/ipayment/sql/VRSN_Create_Table.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_LINEITEM_DATA
The above commands should display the table structure for the table created.

Start the Oracle Apache Server by using the following command:
sh $COMN_TOP/admin/scripts/<DB Instance Name>_<Host Name>/adapcctl.sh start
for example:
sh /mv2/oracle/demo2comn/admin/scripts/DEMO2_aix2/adapcctl.sh start
Step 11 Register the BEP Servlet in iPayment

For detailed instructions on registering the BEP servlet, see Chapter 4, “Registering and
Testing.”
Uninstalling the BEP Servlet

To uninstall the BEP servlet, undo the steps in “Manually Installing the VeriSign BEP
Servlet on Non-Windows Platforms” on page 14. In substep 2 of “Create the database
tables” on page 20, run the VRSN_Drop_Table.sql script from the sql prompt instead of
running the VRSN_Create_Table.sql script.

CHAPTER 4
Registering and Testing

4retpahC
Once you have successfully installed the VeriSign Payment Services (VPS) 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
Oracle’s iPayment documentation for details.
Registering the BEP Servlet in iPayment

In this procedure, you register the BEP servlet, register a payee, and then configure
routing rules. Refer to Oracle’s iPayment documentation for details.
Step 1 Register the BEP servlet

1 Log in (as an administrative user) to the iPayment administration site at
http://<host_name>:<port>/OA_HTML/jtflogin.jsp.
Replace host_name and port with your server information.
Figure 4-1 iPayment administration site

----------------------------------------------------------------
2 The Payment Systems page appears, displaying the Payment System tab.
Figure 4-2 Payment systems page
3 Click Create to generate the VeriSign payment system.

The Create Payment System page appears.
Figure 4-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 VeriSign.
Suffix Enter vps.

Note: For suffix, you must enter vps in all
lowercase letters.
Payment System Type Select Gateway.

Chapter 4 Registering and Testing
----------------------------------------------------------------
User Name Enter any value (not used by BEP

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

servlet).
Base URL http://<host_name>:<port>/servlet. The

host on which the VeriSign servlet is to be
installed, and any active port. For
example:
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.
5 Click Create. The Payment Systems page reappears with the VeriSign payment system
added to it.
Figure 4-4 Payment systems page with VeriSign added
Step 2 Register the Payee

1 Click the Payee tab. The Payees and Risk Management page appears.
Figure 4-5 Payees and risk management page

----------------------------------------------------------------
2 Click Create. The Create Payee page appears.
Figure 4-6 Create payee page
3 Enter the following values:
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 Select Purchase Card and Credit Card.

Credit Card
Merchant Category Code Leave this field empty.
4 On the Create Payee page, indicate the icon to be clicked for VeriSign under
Payment System Identifier > Payment System.
The Payment System Identifiers page appears.

----------------------------------------------------------------
Figure 4-7 Payment system identifiers
5 Select the first radio button under Default as shown in Figure 4-7 and arrange the data
that you used when registering for the PayFlow Pro account (and described in the table
below) in the following format.
<User>:<Password>:<Vendor>:<Partner>
For example, tjohnson:mypassword:tjohnson:VeriSign.
Note The values for the following parameters are case sensitive.
Parameter Meaning
User If you set up one or more additional users on the

account, this value is the ID of the user authorized to
process transactions. If, however, you have not set up
additional users on the account, User has the same
value as Vendor.
Password The 7- to 32-character password that you defined while

registering for the account.
Vendor Your merchant login ID that you created when you

registered for the Payflow Pro account.
Partner The ID provided to you by the authorized VeriSign

Reseller who registered you for the Payflow Pro service.
If you purchased your account directly from VeriSign,
use VeriSign.

----------------------------------------------------------------
6 Click Continue. The Payees and Risk Management page reappears, showing that the
payee has been added. In this example, tjohnson (vps).
Figure 4-8 Payees and Risk Management with tjohnson (vps) payee added
Step 3 Create and configure the routing rules for purchase cards and credit cards
1 Create and configure the routing rules for purchase cards. Click on the Routing Rule
tab.
Figure 4-9 Routing rules
2 Click Create. The Create Routing Rule page appears.
Figure 4-10 Routing rule

----------------------------------------------------------------
3 Enter the following values, and click Add Rule Condition.
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 on page 24.
When all enabled conditions Select VeriSign.

below are met route to
Payment System Identifier Enter in the format:

<User>:<Password>:<Vendor>:<Partner>
For example,
tjohnson:mypassword:tjohnson:VeriSign
The Add Rule Condition screen shown in Figure 4-11 appears.
Figure 4-11 Adding rule conditions
4 In the Condition Name field, enter a name, for example, Amount.

5 Select the radio button next to Amount, select an operation from the Operation list,
and fill in the required value.
6 Click Add Rule Condition. The Create Routing Rule page reappears.
Note You can only add one rule condition at a time, so you must click Add Rule
Condition and complete the Add Rule Condition screen 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 the appropriate values for credit card payments.

----------------------------------------------------------------
Testing the Installation Using the Oracle iPayment User Interface

Note Oracle iPayment does not support the following transaction types:
- Void (V) For Authorizations only
- Fraud filter (U). See VeriSign Payment Services User’s Guide for Payflow Pro with Fraud Protection
Services for details.
- Recurring Billing (R): See the VeriSign Payment Services Payflow Recurring Billing Service Guide
for Payflow Pro for details.
Step 1 Test the servlet configuration with iPayment
Note For testing parameters, see VeriSign Payment Services Payflow Pro Developer’s Guide.
1 On the Operation tab, click New Operation. The Authorization Details page appears.
Figure 4-12 Authorization details page
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.

----------------------------------------------------------------
3 Click Next. The second Authorization Details page appears.
Figure 4-13 Second authorization details page
4 Enter values for the following fields:
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.
5 Click Next. The Authorization Summary page appears.

----------------------------------------------------------------
6 Verify the values, and click Submit.
Figure 4-14 Authorization summary
iPayment processes the test transactions by calling the VPS BEP servlet, and the
Authorization Results page appears on the Operation tab. If the transaction is not
approved, review your configuration and retry.
Figure 4-15 Authorization results
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 iPayment’s extensibility APIs. To test
extensibility, you perform a follow-on Capture transaction for a previously authorized
transaction, as follows:

----------------------------------------------------------------
1 On the Operation tab, click the Follow-on Operation subtab. The Search Transactions page
appears.
Figure 4-16 Search transactions page
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.
3 Click Go to retrieve the authorized record.

The Matching Transactions page appears.
Figure 4-17 Matching transactions
4 To capture the transaction, click the Capture link for the record.

----------------------------------------------------------------
5 The Capture Details page appears. Verify the capture details and click Submit.
Figure 4-18 Capture details page
The Capture Results page appears. A successful capture transaction indicates that
extensibility is working properly. If the transaction is not successful, review your
configuration and retry.
Figure 4-19 Capture results page

----------------------------------------------------------------
Testing the Installation Using VeriSign’s Sample Store

Note VeriSign’s 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
shown here, where the port number is 8000 by default:
http://<hostname>:<port no.>/OA_HTML/iPaymentSampleStore.jsp
2 On the order form, enter the appropriate data and the suitable transaction type. Leave
the ORDER NUMBER field empty for primary transactions such as Authorization
Only, AuthCapture, and Credit (independent).
3 Click Submit Transaction at the bottom of the form.
Figure 4-20 iPayment Purchase

----------------------------------------------------------------
4 If Buyer Authentication Required was set to YES, an intermediate page appears for
Buyer Authentication. If the account number is enrolled for Buyer Authentication,
enter the password. Then click Submit.
Figure 4-21 Buyer Authentication
5 The order is submitted to the VeriSign Payment Gateway. Then a results page
appears, indicating the actual request sent and response received from the Payment
Gateway.
Figure 4-22 Results page

----------------------------------------------------------------
Figure 4-23 Purchase order follow-on transaction
6 To do a follow-on transaction, click on the order number link (Tangible ID value) on

the results page. Then, on the order form, click Get Order Details.
7 Choose the appropriate follow-on transaction; then click Submit Transaction. A
results page appears that is similar to the one shown in Figure 4-22.
Processing Live Transactions

To process live transactions, change test-payflow.verisign.com to payflow.verisign.com
in the appropriate file:
Windows: %ORACLE_TOP%\8.0.6\verisign\vpsipayment.properties
Non-Windows: $ORACLE_TOP/8.0.6 /verisign/vpsipayment.properties
Note You must use DNS resolution for transaction processing. In its effort to achieve
high availability, VeriSign retains the right to change the IP address of PayFlow hosts
without notice. VeriSign cannot be held responsible for any outages that result from your
not using DNS.

CHAPTER 5
Building Your Own Web Site

5retpahC
To build your own Web site, follow these guidelines:

+ Insert the VeriSign-specific parameters into the VRSN_EXTEND_DATA and the
VRSN_EXTEND_LINEITEM_DATA tables. See Appendix B, “Mapping
VeriSign 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 the TxnCustomizer_vps.java
class, which is part of the iPayment Extensibility API.
+ Use the respective iPayment APIs to call the relevant transactions. Refer to Oracle’s
iPayment documentation for details.

----------------------------------------------------------------

APPENDIX A
Transaction Decline or Error RESULTs and

AxidnepA
RESPMSGs
OapfVendErrCode 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.
Table A-1 VeriSign transaction 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 USER, VENDOR, PARTNER, or PASSWORD entered in your parameter
string. Login information is case-sensitive.
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 VeriSign 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 VeriSign
servers. Change the URL from test-payflow.verisign.com to payflow.verisign.com.
2 Invalid tender type. Your merchant bank account does not support the following
credit 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 currency
symbols or commas.
5 Invalid merchant information. Processor does not recognize your merchant

account information. Contact your bank account acquirer to resolve this problem.
7 Field format error. Invalid information entered. See RESPMSG.
8 Not a transaction server
9 Too many parameters or invalid stream

----------------------------------------------------------------
Table A-1 VeriSign transaction RESULT values and RESPMSG text (Continued)
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.
13 Referral. Transaction cannot be approved electronically but can be approved with

a verbal authorization. Contact your merchant bank to obtain an authorization and
submit a manual Voice Authorization transaction.
14 Invalid Client Certification ID. Check the HTTP header. If the tag,
X-VPS-VIT-CLIENT-CERTIFICATION-ID, is missing, RESULT code 14 is
returned.
19 Original transaction ID not found. The transaction ID you entered for this
transaction is not valid. See RESPMSG.
20 Cannot find the customer reference number
22 Invalid ABA number
23 Invalid account number. Check credit card number and re-submit.
24 Invalid expiration date. Check and re-submit.
25 Invalid Host Mapping. You are trying to process a tender type such as Discover
Card, but you are not set up with your merchant bank to accept this card type.
26 Invalid vendor account
27 Insufficient partner permissions
28 Insufficient user permissions
29 Invalid XML document. This could be caused by an unrecognized XML tag or a

bad XML format that cannot be parsed by the system.
30 Duplicate transaction
31 Error in adding the recurring profile
32 Error in modifying the recurring profile
33 Error in canceling the recurring profile
34 Error in forcing the recurring profile
35 Error in reactivating the recurring profile
36 OLTP Transaction failed
37 Invalid recurring profile ID
50 Insufficient funds available in account
99 General error. See RESPMSG.
100 Transaction type not supported by host

Appendix A Transaction Decline or Error RESULTs and RESPMSGs
----------------------------------------------------------------
101 Time-out value too small
102 Processor not available
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 this
transaction 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 been voided. 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
still exist on the cardholder’s account.
113 Merchant sale total will exceed the sales cap with current transaction. ACH
transactions only.
114 Card Security Code (CSC) Mismatch. An authorization may still exist on the
cardholder’s 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 VeriSign Manager Security Settings page. 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. ACH
transactions only.
125 Fraud Protection Services Filter — Declined by filters

----------------------------------------------------------------
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.
If this is a new Payflow Pro account, this result occurred because all new
accounts include a “test drive” of the Fraud Protection Services at no charge. The
filters are on by default. You can modify these settings based on your business
needs.
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 chapter entitled “Assessing Transactions that
Triggered Filters” in Fraud Protection Services Guide or User’s Guide for Payflow
Link Guide With Fraud Protection Services.
127 Fraud Protection Services Filter — Not processed by filters
128 Fraud Protection Services Filter — Declined by merchant after being flagged
for review by filters
131 Version 1 Payflow Pro SDK client no longer supported. Upgrade to the most
recent version 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). To enroll, log in to VeriSign Manager, click
Security, and then click the Buyer Authentication Service banner on the page.
1016 Buyer Authentication Service — 3-D Secure error response received. Instead
of receiving a PARes response to a Validate Authentication transaction, an error
response was received.

Appendix A Transaction Decline or Error RESULTs and RESPMSGs
----------------------------------------------------------------
1017 Buyer Authentication Service — 3-D Secure error response is invalid. An error
response is received and the response is not well formed for a Validate
Authentication transaction.
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 or

invalid PARES
1042 Buyer Authentication Service — Validate Authentication failed: PARES

format is invalid
1043 Buyer Authentication Service — Validate Authentication failed: Cannot find

successful Verify Enrollment
1044 Buyer Authentication Service — Validate Authentication failed: Signature

validation failed for PARES
1045 Buyer Authentication Service — Validate Authentication failed: Mismatched

or invalid amount in PARES

or invalid acquirer in PARES

or invalid Merchant ID in PARES

or invalid card number in PARES

or invalid currency code in PARES

or invalid XID in PARES

or invalid order date in PARES
1052 Buyer Authentication Service — Validate Authentication failed: This PARES

was already validated for a previous Validate Authentication transaction

----------------------------------------------------------------

APPENDIX B
Mapping VeriSign Parameters to iPayment

BxidnepA
Parameters
Parameters Mapping
Table B-1 Parameters mapping
PF Pro Parameter Database - Oapf Parameter Oapf Parameter Name

TableName.ColumnName Name
ABA VRSN_EXTEND_DATA.ABA OapfABA Cardholder's ABA
Number
ACCT IBY_CREDITCARD.CCNUMBER OapfPmtInstrID Cardholder's Account
Number
ACCTTYPE VRSN_EXTEND_DATA. OapfAcctType Cardholder's Account
ACCTTYPE Type
ACSURL NA NA ACS Url for Buyer
Authentication. Value
returned only if
AUTHENTICATION_STA
TUS=E.
ADDLMSGS VRSN_EXTEND_DATA. OapfAddlMsgs Additional error message
ADDLMSGS that indicates that the
merchant used a feature
that is disabled.
ALTTAXAMT VRSN_EXTEND_DATA. OapfAltTaxAmt Alternative Tax Amount
ALTTAXAMT
AMT IBY_TRXN_SUMMARIES_ALL. OapfPrice Order Amount

AMOUNT
AUTHCODE IBY_TRXN_CORE.AUTHCODE OapfAuthCode Authorization Code for

use in Voice Authorization
AUTHENTICATION_ID VRSN_EXTEND_DATA. OapfAuthentication_Id Unique identifier for Verify
AUTHENTICATION_ID Enrolment request in
Buyer Authentication.

----------------------------------------------------------------

AUTHENTICATION_ VRSN_EXTEND_DATA. OapfAuthentication_ Status for Buyer
STATUS AUTHENTICATION_STATUS Status Authentication:
E: Card Enrolled.
O: Card Not Enroled.
X: Unable to determine.
I: Verify Enrolment
request failed.
AUTHTYPE VRSN_EXTEND_DATA. OapfAuthType The type of authorization
AUTHTYPE 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: Accounts
Receivables 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.AVSADDR OapfAVSAddr AVS Address Match (Y, N,
X)
AVSZIP VRSN_EXTEND_DATA.AVSZIP OapfAVSZip AVS Zip Match (Y, N, X)
BILLTOPHONE2 VRSN_EXTEND_DATA. OapfBillToPhone2 Alternative Phone
BILLTOPHONE2 Number
For The Billing Contact
BILLTOSTREET2 VRSN_EXTEND_DATA. OapfBillToStreet2 Extended Billing Address
BILLTOSTREET2
BROWSERCOUNTRY VRSN_EXTEND_DATA. OapfBrowserCountry Browser Country Code

CODE BROWSERCOUNTRYCODE Code

Appendix B Mapping VeriSign Parameters to iPayment Parameters
----------------------------------------------------------------

BROWSERTIME VRSN_EXTEND_DATA. OapfBrowserTime Browser Time
BROWSERTIME
BROWSERUSER VRSN_EXTEND_DATA. OapfBrowserUserAgent Browser User Agent

AGENT BROWSERUSERAGENT
CARDSECURE VRSN_EXTEND_DATA. OapfCardSecure CAVV Validity. (Y=valid,

CARDSECURE N=Not Valid, X=Cannot
Determine)
CARRIER VRSN_EXTEND_DATA.CARRIER OapfCarrier Shipment Carrier
CAVV VRSN_EXTEND_DATA.CAVV 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.CHKNUM OapfChkNum Account Holder's Next
Available Check Number
CHKTYPE VRSN_EXTEND_DATA.CHKTYPE OapfChkType Check Type (P=Personal,
C=Company)
CITY HZ_LOCATIONS.CITY OapfCity Billing City
COMMCARD VRSN_EXTEND_DATA. OapfCommCard Commercial Card Type
COMMCARD (P=Purchase,
C=Corporate,
B=Business,
U=Unknown-default,
N=None)
COMMENT1 VRSN_EXTEND_DATA. OapfComment1 Comment
COMMENT1
COMMENT2 VRSN_EXTEND_DATA. OapfComment2 Comment

COMMENT2
COMPANYNAME VRSN_EXTEND_DATA. OapfCompanyName Cardholder’s company

COMPANYNAME
CORPNAME VRSN_EXTEND_DATA. OapfCorpName Corporation's Name

CORPNAME
CORPPURCHDESC VRSN_EXTEND_DATA. OapfCorpPurchDesc Description of Corporate

CORPPURCHDESC Purchase
COUNTRY HZ_LOCATIONS.COUNTRY OapfCntry Billing Country Code

----------------------------------------------------------------

COUNTRYCODE VRSN_EXTEND_DATA. OapfCountryCode Destination Country Code
COUNTRYCODE
CURRENCY This is not saved into database. It is NA Currency (840=US$)

required for BuyerAuth only.
CUSTAGE VRSN_EXTEND_DATA.CUSTAGE OapfCustAge Customer's Age (0-150)

CUSTCODE VRSN_EXTEND_DATA. OapfCustCode Customer Code
CUSTCODE
CUSTID VRSN_EXTEND_DATA.CUSTID OapfCustId Merchant Web site’s Id for

the Customer
CUSTIP VRSN_EXTEND_DATA.CUSTIP OapfCustIP Customer's IP Address
CUSTMAXAGE VRSN_EXTEND_DATA. OapfCustMaxAge Customer's Maximum
CUSTMAXAGE Age
CUSTMINAGE VRSN_EXTEND_DATA. OapfCustMinAge Customer's Minimum Age
CUSTMINAGE
CUSTREF VRSN_EXTEND_DATA.CUSTREF OapfCustRef Customer Reference

Number
CUSTTM VRSN_EXTEND_DATA.CUSTTM OapfCustTm Customer's Local Time
(hhmmss)
CUSTVATREGNUM VRSN_EXTEND_DATA. OapfCustVatRegNum VAT Registration Number
CUSTVATREGNUM
CVV2 VRSN_EXTEND_DATA.CVV2 OapfCVV2 Card Security Code

(CSC)
CVV2MATCH VRSN_EXTEND_DATA. OapfCVV2Result CSC Match
CVV2MATCH
(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 cardholder’s bank
does not support this
service)
DESC VRSN_EXTEND_DATA.DESCR OapfDesc Description
DESC1 VRSN_EXTEND_DATA.DESC1 OapfDesc1 Description of Goods
and/or Services
and/or Services
and/or Services

----------------------------------------------------------------

and/or Services
DISCOUNT VRSN_EXTEND_DATA. OapfDiscount Discount Amount
DISCOUNT
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.DUTYAMT oapfdutyamt Duty Amount /Import Tax
ECI VRSN_EXTEND_DATA.ECI OapfECI E-Commerce Indicator.
The ECI value indicates
the level of security
supported by the
merchant when the
cardholder provided the
payment card data for an
Internet purchase. When
returned in a buyer
auhentication response, it
is determined by the
issuing bank.
EMAIL VRSN_EXTEND_DATA.EMAIL OapfEmail Customer's E-mail
Address

----------------------------------------------------------------

ENDTIME VRSN_EXTEND_DATA.ENDTIME OapfEndTime Optional for Inquiry
transactions when using
CUSTREF to specify the
transaction.
ENDTIME specifies the
end of the time period
during which the
transaction specified by
the CUSTREF occurred.
ENDTIME must be less
than 30 days after
STARTTIME. An inquiry
cannot be performed
across a date range
greater than 30 days.
If you set ENDTIME, and
not STARTTIME, then
STARTTIME is defaulted
to 30 days before
ENDTIME.
If neither STARTTIME nor
ENDTIME is specified,
then the system searches
the last 30 days.
(yyyymmddhhmmss)
EXPDATE IBY_CREDITCARD.EXPIRYDATE OapfPmtInstrExp Card Expiration Date
(mmyy)
FAX VRSN_EXTEND_DATA.FAX OapfFax Customer's Fax Number
FIRSTNAME VRSN_EXTEND_DATA. OapfFirstName Customer's First Name
FIRSTNAME
FORGOTPWD VRSN_EXTEND_DATA. OapfForgotPwd Forgot Password (Y/N)

FORGOTPWD
FPS_POSTXMLDATA VRSN_EXTEND_DATA. OapfFPS_PostXmlData Itemized list of responses

FPS_POSTXMLDATA for triggered filters as an
xml.
FPS_PREXMLDATA VRSN_EXTEND_DATA. OapfFPS_PreXmlData Itemized list of responses
FPS_PREXMLDATA for triggered filters as an
xml.
FREIGHTAMT VRSN_EXTEND_DATA. OapfFreightAmt Freight Amount
FREIGHTAMT
GIFTCARDTYPE VRSN_EXTEND_DATA. OapfGiftCardType Gift Card Type (B, A, G, H,

GIFTCARDTYPE C, W, S or U)
GIFTMSG VRSN_EXTEND_DATA.GIFTMSG OapfGiftMsg Gift Message

----------------------------------------------------------------

HANDLINGAMT VRSN_EXTEND_DATA. OapfHandlingAmt Handling Amount
HANDLINGAMT
HOMEPHONE VRSN_EXTEND_DATA. OapfHomePhone Customer's Home Phone

HOMEPHONE
HOSTADDRESS NA NA VeriSign’s host name.

For testing purposes use
HOSTCODE VRSN_EXTEND_DATA. OapfHostCode Response code returned
HOSTCODE 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.INVNUM OapfInvNum Invoice Number
INVOICEDATE VRSN_EXTEND_DATA. OapfInvoiceDate Invoice Date (yyyymmdd)
INVOICEDATE
L_AMTn VRSN_EXTEND_LINEITEM_DATA. OapfL_Amt Item Amount

L_AMT
L_BILLEDUOMn VRSN_EXTEND_LINEITEM_DATA. OapfL_BilledUOM Not used currently by the

L_BILLEDUOM Payment Gateway
L_CATALOGNUMn VRSN_EXTEND_LINEITEM_DATA OapfL_CatalogNum Supplier Catalog Number
.L_CATALOGNUM
L_CATEGORYn VRSN_EXTEND_LINEITEM_DATA. OapfL_Category Item Category

L_CATEGORY
L_COMMCODEn VRSN_EXTEND_LINEITEM_DATA. OapfL_CommCode Item Commodity Code

L_COMMCODE
L_COSTCENTER VRSN_EXTEND_LINEITEM_DATA. apfL_CostCenterNum Cost Center Number

NUMn L_COSTCENTERNUM
L_COSTn VRSN_EXTEND_LINEITEM_DATA. OapfL_Cost Item Cost

L_COST
L_DESCn VRSN_EXTEND_LINEITEM_DATA. OapfL_Desc Item Description

L_DESC
L_DISCOUNTn VRSN_EXTEND_LINEITEM_DATA. OapfL_Discount Item Discount

L_DISCOUNT

----------------------------------------------------------------

L_FREIGHTAMTn VRSN_EXTEND_LINEITEM_DATA. OapfL_FreightAmt Item Freight Amount
L_FREIGHTAMT
L_FREIGHTUOMn VRSN_EXTEND_LINEITEM_DATA OapfL_FreightUOM Not used currently by the

L_FREIGHTUOM Payment Gateway
L_HANDLINGAMTn VRSN_EXTEND_LINEITEM_DATA. OapfL_HandlingAmt Item Handling Amount
L_HANDLINGAMT
L_HANDLINGUOMn VRSN_EXTEND_LINEITEM_DATA. OapfL_HandingUOM Not used currently by the

L_HANDLINGUOM Payment Gateway
L_MANUFACTURERn VRSN_EXTEND_LINEITEM_DATA. OapfL_Manufacturer Item Pickup City
L_MANUFACTURER
L_PICKUPCITYn VRSN_EXTEND_LINEITEM_DATA. OapfL_PickupCity Item Pickup Country

L_PICKUPCITY
L_PICKUPCOUNTRYn VRSN_EXTEND_LINEITEM_DATA. OapfL_PickupCountry Item Pickup State

L_PICKUPCOUNTRY
L_PICKUPSTATEn VRSN_EXTEND_LINEITEM_DATA. OapfL_PickupState Item Pickup Country

L_PICKUPSTATE
L_PICKUPSTREETn VRSN_EXTEND_LINEITEM_DATA. OapfL_PickupStreet Item Pickup Street

L_PICKUPSTREET
L_PICKUPZIPn VRSN_EXTEND_LINEITEM_DATA. OapfL_PickupZip Item Pickup Zip

L_PICKUPZIP
L_PRODCODEn VRSN_EXTEND_LINEITEM_DATA. OapfL_ProdCode Item Product Code

L_PRODCODE
L_QTYn VRSN_EXTEND_LINEITEM_DATA. OapfL_Qty Item Quantity Ordered

L_QTY
L_SKUn VRSN_EXTEND_LINEITEM_DATA. OapfL_SKU Item SKU Number

L_SKU
L_TAXAMTn VRSN_EXTEND_LINEITEM_DATA. OapfL_TaxAmt Item Tax Amount

L_TAXAMT
L_TAXRATEn VRSN_EXTEND_LINEITEM_DATA. OapfL_TaxRate Item Tax Rate

L_TAXRATE
L_TAXTYPEn VRSN_EXTEND_LINEITEM_DATA. OapfL_TaxType Tax Type Applied

L_TAXTYPE
L_TRACKINGNUMn VRSN_EXTEND_LINEITEM_DATA. OapfL_TrackingNum Item Tracking Number

L_TRACKINGNUM
L_TYPEn VRSN_EXTEND_LINEITEM_DATA. OapfL_Type Item Type

L_TYPE
L_UNSPSCCODEn VRSN_EXTEND_LINEITEM_DATA. OapfL_UnspscCode Item UNSPC Code

L_UNSPSCCODE
L_UOM VRSN_EXTEND_LINEITEM_DATA. OapfL_UOM Item Unit of Measurement

L_UOM

----------------------------------------------------------------

L_UPCn VRSN_EXTEND_LINEITEM_DATA. OapfL_UPC Item Universal Product
L_UPC Code
L_WEIGHTUOMn VRSN_EXTEND_LINEITEM_DATA. OapfL_WeightUOM Not used currently by the
L_WEIGHTUOM Payment Gateway
LASTNAME VRSN_EXTEND_DATA.LASTNAME OapfLastName Customer's Last Name
LOCALTAXAMT VRSN_EXTEND_DATA. OapfLocalTaxAmt Local Tax Amount
LOCALTAXAMT
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 its
content.
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. OapfMerchDescr Merchant Description
MERCHDESCR
MERCHSVC VRSN_EXTEND_DATA. OapfMerchSVC Merchant's Telephone

MERCHSVC number
MICR VRSN_EXTEND_DATA.MICR OapfMICR Magnetic Ink Check
Reader (MICR) Number
(Transit, Account and
Check Number)
NAME IBY_CREDITCARD.CHNAME OapfCustName Cardholder's Name
NATIONALTAXAMT VRSN_EXTEND_DATA. OapfNationalTaxAmt National Tax Amount
NATIONALTAXAMT
ORDERBIN VRSN_EXTEND_DATA.ORDERBIN OapfOrderBin Printed Numbers Under

the BIN on Credit Card
ORDERDATETIME VRSN_EXTEND_DATA. OapfOrderDateTime Date and time when the
ORDERDATETIME Order was ordered
(yyyymmddhhmmss)
ORIGID VRSN_EXTEND_DATA.ORIGID OapfOrigID VeriSign Payment
Network
Reference ID (PNREF)
Referencing a Previous
Transaction
PAREQ NA NA Payer Request for Buyer
Authentication. Value
returned only if
AUTHENTICATION_STA
TUS=E.
PARES NA NA Payer Response
message generated by
ACS for Buyer
Authentication.

----------------------------------------------------------------

PARMLIST NA NA The ParmList is the list of
parameters 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&TENDER
=C&PARTNER=VeriSign
&VENDOR=Super
Merchant&USER=Super
Merchant&PWD=x1y2z3
&ACCT=55555555
55554444&EXPDATE=03
08&AMT=123.00”
PARTNER VRSN_EXTEND_DATA. In the preTxn method Partner Name
VSGNPARTNER 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 are
mandatory for Buyer
Authentication.
PASSWORDGIVEN VRSN_EXTEND_DATA. OapfPasswordGiven Password Given (Y/N)
PASSWORDGIVEN
PHONE Not Supported Not Supported NA

PHONENUM VRSN_EXTEND_DATA. OapfPhone Account Holder's
PHONENUM Telephone Number
PNREF IBY_TRXN_CORE. OapfRefcode Reference Number for the
REFERENCECODE current transaction
PONUM VRSN_EXTEND_DATA.PONUM OapfPONum Purchase Order Number
POSTFPSMSG VRSN_EXTEND_DATA. OapfPostFPSMsg Post FPS Message
POSTFPSMSG
PREFPSMSG VRSN_EXTEND_DATA. OapfPreFPSMsg Pre FPS Message

PREFPSMSG
PRENOTE VRSN_EXTEND_DATA.PRENOTE OapfPreNote Prenote (Y/N)

PREVIOUSCUST VRSN_EXTEND_DATA. OapfPreviousCust Previous Customer (Y/N)
PREVIOUSCUST

----------------------------------------------------------------

PROCAVS VRSN_EXTEND_DATA.PROCAVS OapfProcAVS AVS (Address Verification
Service) response from
the Processor.
PROCCARDSECURE VRSN_EXTEND_DATA. OapfProcCardSecure VPAS/SPA response from
PROCCARDSECURE the Processor.
PROCCVV2 VRSN_EXTEND_DATA.PROCCVV2 OapfProcCVV2 CVV2 (Buyer
Authentication) 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 port
PUR_DESC VRSN_EXTEND_DATA.PUR_DESC OapfPur_Desc Purchase Description
PWD VRSN_EXTEND_DATA. In the preTxn method Merchant's Password.
VSGNPASSWORD of TxnCustomizer_vps.
If all of PARTNER,
PWD, USER, and
VENDOR are present
into the format of
OapfStoreId and put
field. These are
mandatory for Buyer
Authentication.
RECURRING VRSN_EXTEND_DATA. OapfRecurring Recurring Account (Y/N)
RECURRING
REGLOYALTY VRSN_EXTEND_DATA. OapfRegLoyalty Registered For Loyalty

REGLOYALTY program (Y/N)
REGPROMO VRSN_EXTEND_DATA. OapfRegPromo Registered For
REGPROMO Promotions (Y/N)
REQNAME VRSN_EXTEND_DATA.REQNAME OapfReqName
RESPMSG VRSN_EXTEND_DATA.RESPMSG OapfRespMsg Response Message
RESPTEXT VRSN_EXTEND_DATA.RESPTEXT OapfRespText Text corresponding to the
response code returned
by the Processor.
RESULT VRSN_EXTEND_DATA.RESULT OapfResult Result

----------------------------------------------------------------

RETURNALLOWED VRSN_EXTEND_DATA. OapfReturnAllowed Return Allowed (Y/N)
RETURNALLOWED
SETTLE_DATE NA NA NA
SHIPCARRIER VRSN_EXTEND_DATA. OapfShipCarrier Shipping Carrier
SHIPCARRIER
SHIPFROMZIP VRSN_EXTEND_DATA. OapfShipFromZip Ship From Postal Code

SHIPFROMZIP
SHIPMENTNO VRSN_EXTEND_DATA. OapfShipmentNo Shipment Number

SHIPMENTNO
SHIPMETHOD VRSN_EXTEND_DATA. OapfShipMethod Shipping Method (N, T, W,

SHIPMETHOD C, D, I, M, P, O)
SHIPTOCITY VRSN_EXTEND_DATA. OapfShipToCity Ship To City
SHIPTOCITY
SHIPTOCOUNTRY VRSN_EXTEND_DATA. OapfShipToCountry Country code of the

SHIPTOCOUNTRY shipping country. (US,
USA, 840)
SHIPTOEMAIL VRSN_EXTEND_DATA. OapfShipToEmail Ship To E-mail
SHIPTOEMAIL
SHIPTOFIRSTNAME VRSN_EXTEND_DATA. OapfShipToFirstName Ship To First Name

SHIPTOFIRSTNAME
SHIPTOLASTNAME VRSN_EXTEND_DATA. OapfShipToLastName Ship To Last Name

SHIPTOLASTNAME
SHIPTOMIDDLENAME VRSN_EXTEND_DATA. OapfShipToMiddleNa Ship To Middle Name

SHIPTOMIDDLENAME me
SHIPTOPHONE VRSN_EXTEND_DATA. OapfShipToPhone Ship To Phone
SHIPTOPHONE
SHIPTOPHONE2 VRSN_EXTEND_DATA. OapfShipToPhone2 Alternative Phone

SHIPTOPHONE2 Number For The Shipping
Contact
SHIPTOSTATE VRSN_EXTEND_DATA. OapfShipToState Ship To State
SHIPTOSTATE
SHIPTOSTREET VRSN_EXTEND_DATA. OapfShipToStreet Ship To Street Address

SHIPTOSTREET
SHIPTOSTREET2 VRSN_EXTEND_DATA. OapfShipToStreet2 Extended shipping

SHIPTOSTREET2 address
SHIPTOZIP VRSN_EXTEND_DATA.SHIPTOZIP 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. OapfStartTime Optional for Inquiry
STARTTIME 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 is specified,
then the system searches
the last 30 days.
(yyyymmddhhmmss)
STATE HZ_LOCATIONS.COUNTY OapfState Billing State
STREET HZ_LOCATIONS.ADDRESS1 OapfAddr1 Billing Street Address
SUBTOTAL VRSN_EXTEND_DATA.SUBTOTAL OapfSubTotal Subtotal
SWIPE VRSN_EXTEND_DATA.SWIPE OapfSwipe Swipe
TAXAMT VRSN_EXTEND_DATA.TAXAMT OapfTaxAmt Tax Amount
TAXEXEMPT (Y/N) VRSN_EXTEND_DATA. OapfTaxExempt Tax Exempt (Y/N)
TAXEXEMPT
TENDER VRSN_EXTEND_DATA.TENDER OapfExtendTender Brand

TERMCITY VRSN_EXTEND_DATA.TERMCITY OapfTermCity City of terminal that
captured the transaction
TERMSTATE VRSN_EXTEND_DATA. OapfTermState State of terminal that
TERMSTATE captured the transaction
TERMURL NA Taken from URL of the Merchant
vpsipayment.properties Application
at initialization.

----------------------------------------------------------------

TIMEOUT NA NA Time-out period for the
transaction. The minimum
recommended time-out
value is 30 seconds. The
VeriSign client begins
tracking from the time that
it sends the transaction
request to the VeriSign
server.
TRXTYPE This is not saved in DB. It is OapfAction (S=Sale, C=Credit,
generated at transaction time A=Authorize, D=Capture,
according to the action sent by the V=Void, F=Force/Voice
OIP to the BEP servlet. Authorization, I=Inquiry)
E.g. If we are doing an authorization
transaction, then
OapfAction=oraauth and from this
trxtype is set to "A"
USER VRSN_EXTEND_DATA. In the preTxn method User Name.

VSGNUSER of TxnCustomizer_vps.
If all of PARTNER,
PWD, USER, and
VENDOR are present
into the format of
OapfStoreId and put
field. These are
mandatory for Buyer
Authentication.
VATREGNUM VRSN_EXTEND_DATA. OapfVatRegNum VAT Registration Number
VATREGNUM
VATTAXAMT VRSN_EXTEND_DATA. OapfVatTaxAmt Not used currently by the

VATTAXAMT Payment Gateway
VATTAXPERCENT VRSN_EXTEND_DATA. OapfVatTaxPercent Not used currently by the
VATTAXPERCENT Payment Gateway
VENDOR VRSN_EXTEND_DATA. In the preTxn method Vendor Name
VSGNVENDOR of TxnCustomizer_vps.
If all of PARTNER,
PWD, USER, and
VENDOR are present
into the format of
OapfStoreId and put
field. These are
mandatory for Buyer
Authentication.

----------------------------------------------------------------

VERBOSITY VRSN_EXTEND_DATA. OapfVerbosity Verbosity (HIGH,
VERBOSITY MEDIUM, LOW)
WRAPPED VRSN_EXTEND_DATA.WRAPPED OapfWrapped Gift Wrapping (Y/N)
XID VRSN_EXTEND_DATA.XID OapfXID Buyer Authentication
Transaction Id.
ZIP HZ_LOCATIONS.POSTALCODE OapfPostalCode Billing Zip Code

APPENDIX C
Troubleshooting
CxidnepA
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 Log File Creation

By default the debug logs are disabled. To enable the log files, set debug to true in your
zone.properties file for the following servlets:
+ servlet.oramipp_vps
+ servlet.oramipp_samplestore
+ servlet.oramipp_Payee2VPS
Before Contacting Customer Support

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.
+ ibyvpsserv.log
Oracle iPayment patch set 11i.IBY.N and previous
+ iby_debug.log
+ iby_error.log
Oracle iPayment patch set 11i.IBY.O
+ iby.log
For details on generating log files on 11i.IBY.O and later, see Note 265330.1.
+ Obtain and send the following properties files.
+ jserv.properties

----------------------------------------------------------------
+ zone.properties
+ java.security file
Table C-1 shows the location of these files on Windows after installing the BEP
servlet
Table C-1 Locations of Windows configuration files
Properties file Default location
vpsipayment.properties %ORACLE_TOP%\8.0.6\verisign
jserv.properties %ORACLE_TOP%\iAS\Apache\Jserv\etc
zone.properties %ORACLE_TOP%\iAS\Apache\Jserv\etc
java.security (Oracle Apps) %ORACLE_TOP%\iAS\Apache\jdk\jre\lib\security
java.security (In the JDK) %JAVA_HOME%\jre\lib\security
Table C-2 shows the location of these files on non-Windows platforms after installing
the BEP servlet
Table C-2 Locations of Windows configuration files
Properties file Default location
vpsipayment.properties $ORACLE_TOP/8.0.6/verisign
jserv.properties $ORACLE_TOP/iAS/Apache/Jserv/etc
zone.properties $ORACLE_TOP/iAS/Apache/Jserv/etc
java.security (Oracle Apps) $ORACLE_TOP/iAS/Apache/jdk/jre/lib/security
java.security (In the JDK) $JAVA_HOME/jre/lib/security

APPENDIX D
Manually Uninstalling the VeriSign BEP Servlet

DxidnepA
Note This Appendix describes servlet uninstallation for Windows. If you are
uninstalling from a non-Windows platform, use the appropriate pathnames for that
platform.
This appendix guides you through manually uninstalling VeriSign BEP Servlet 3.1.
C:\> sqlplus <dbid>/<dbpwd>@<SID>

Refer to Table D-1 for directory notation.

Table D-1 BEP Servlet path and directory notation
%VERISIGN_TOP% Represents the verisign directory into which the pfpro_ipayment.zip file
If, for example, you unzipped pfpro_ipayment.zip into D:\oracle\,
%VERISIGN_TOP% would represent D:\oracle\verisign, the top-level
%ORACLE_TOP% Represents the top-level Oracle directory for Oracle Apps, for
example, D:\oracle\visora.
%APPL_TOP% Represents the top-level application directory for Oracle Apps, for
example D:\oracle\visappl.
%COMN_TOP% Represents the top-level Oracle Apps common directory, for example,
D:\oracle\viscomn.
%JAVA_HOME% Java home directory of your JDK, for example, C:\j2sdk1.3.1

----------------------------------------------------------------

The Oracle Apache Server runs as a Windows service. Stop the service using the Services
control panel.
Step 2 Remove VeriSign files

1 Remove the following directories from the %ORACLE_TOP%
\iAS\Apache\Jserv\servlets directory:
+ com
+ ibyextend
2 Remove the %ORACLE_TOP%\8.0.6\verisign directory.
3 Remove the following files from the %COMN_TOP%\html directory:
+ VeriSignLogo.jpg
+ Error.jsp
4 Remove the following file from the %APPL_TOP%\iby\11.5.0\lib directory:
+ Verisign.jar
5 Remove the full certs directory from the %ORACLE_TOP%\iAS\Apache\Apache
directory. This removes the f7389fd.0 certificate file. On non-Windows platforms,
remove the certs directory from the root (/) directory (/certs).
Step 3 Remove Java Secure Sockets Extension (JSSE) .jar Files

1 Remove the following JSSE jar files from the
%ORACLE_TOP%\iAS\Apache\jdk\jre\lib\ext directory:
+ jcert.jar
+ jnet.jar
+ jsse.jar

1 Remove the following line from your zone.properties file located in the
%ORACLE_TOP%\iAS\Apache\Jserv\etc directory:
servlet.oramipp_vps.code=vpsProcess
2 Remove initArgs info:
servlet.oramipp_vps.initArgs=properties=%ORACLE_TOP%\8.0.6
\verisign\vpsipayment.properties

Appendix D Manually Uninstalling the VeriSign BEP Servlet
----------------------------------------------------------------
Step 5 Modify jserv.properties

1 Remove the following lines from your jserv.properties file located in the
%ORACLE_TOP%\iAS\Apache\Jserv\etc directory:
wrapper.classpath=%APPL_TOP%\iby\11.5.0\lib\VeriSign.jar
wrapper.classpath=%ORACLE_TOP%\iAS\Apache\jdk\jre\lib\ext\jsse.jar
wrapper.classpath=%ORACLE_TOP%\iAS\Apache\jdk\jre\lib\ext\jcert.jar
wrapper.classpath=%ORACLE_TOP%\iAS\Apache\jdk\jre\lib\ext\jnet.jar
wrapper.classpath=%ORACLE_TOP%\iAS\Apache\Jserv\servlets\ibyextend
wrapper.classpath=%ORACLE_TOP%\iAS\Apache\Jserv\servlets
2 Uncomment the following lines in your jserv.properties file (if present):

Step 6 Modify java.security

Remove the JSSE provider from the
%ORACLE_TOP%\iAS\Apache\jdk\jre\lib\security\java.security file as follows:
(Remove this string in the file, decrementing the number by 1.)

The Oracle Apache server runs as a Windows service. Start the service using the Services
control panel.

----------------------------------------------------------------

APPENDIX E
Encrypting Your Database User Password

ExidnepA
You must encrypt your database user password before inserting it into your version of
the vpsipayment.properties file. To encrypt your database user password, use the
EncryptPassword utility, as described in the following procedure:
1 Open the command prompt.
2 Change directory to %ORACLE_TOP%\iAS\Apache\Jserv\servlets.
3 Run the following command (as one single line):
%JAVA_HOME%\bin\java -classpath "." com/verisign/iPayment/util/EncryptPassword
<dbpwd>
where
%JAVA_HOME% is the location of your SDK. See Table 2-1.
dbpwd is your current database user password.
On the console, your encrypted password will appear similar to this:
Encrypted Password = YXBwcw==
Note Your encrypted password will always end with a double equals sign (==).
4 In vpsipayment.properties, replace the apps value of the dbpwd entry with the new
encrypted database pasword that appears on your screen.

----------------------------------------------------------------

Index
-----------------------------------------------------------
Index
A S
Apache Web server 1 servlet
described 2
B installing 5, 13
registering 21
BEP servlet testing 29
described 2
installing 5, 13 SQLPlus 5, 14, 63
registering 21
testing 29 T
testing
C extensibility 31
contacting Customer Support 61 servlet configuration 29
testing servlet installation
D using Oracle iPayment user interface 29
using Sample Store 34
debug log files
disabling 61
U
enabling creation 61
directory structure, pfpro_ipayment 6, 14 uninstalling BEP servlet 20
DNS resolution, using 36

V
E VeriSign-specific parameters 37
extensibility vpsipayment.properties parameters 9, 17

testing 31
W
I Web site, building 37
installing the BEP servlet 5, 13
iPayment 2
L
logging into databases 5, 14, 63
O
Oracle iPayment 2
P
path and directory notation 5, 13, 63
Payflow Pro 2
registering 3
pfpro_ipayment directory structure 6, 14
R
registering BEP servlet 21
RESULTs/RESPMSGs 39

-----------------------------------------------------------

Oracle P Card and IExpense

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Oracle P Card and IExpense

Enviado por

Direitos autorais:

Formatos disponíveis

DEVELOPER’S GUIDE

VeriSign Payment Services

Oracle iPayment Back-End Payment Servlet

VeriSign, Inc. VPS-0007/Rev11

Copyright © 1998 - 2006 VeriSign, Inc. All rights reserved.

DISCLAIMER AND LIMITATION OF LIABILITY

Publication date: January 2006

VeriSign Payment Services Oracle iPayment Back-End Payment Servlet

Throughout Document  Converted document to wider format.

VeriSign Payment Services Oracle iPayment Back-End Payment Servlet

Throughout Document  Converted document to wider format.

Appendix C,  Moved section on what to have available before

VeriSign, Inc. VPS-0007/Rev11 iii

VeriSign, Inc. VPS-0007/Rev11 iv

+ Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . . . . iii

+ Chapter 2 Installing and Configuring on Windows

+ Chapter 3 Installing and Configuring on

VeriSign, Inc. VPS-0007/Rev11 v

+ Chapter 4 Registering and Testing . . . . . . . . . . . . 21

+ Chapter 5 Building Your Own Web Site . . . . . . . . 37

+ Appendix A Transaction Decline or Error RESULTs

+ Appendix B Mapping VeriSign Parameters to

+ Appendix D Manually Uninstalling the VeriSign

+ Appendix E Encrypting Your Database User

vi VeriSign, Inc. VPS-0007/Rev11

Note In this guide, you refers to the merchant or administrator.

VeriSign, Inc. VPS-0007/Rev11 1

iStore (or any

Order Capture Administrative

Java iPayment HTTP(S) VeriSign

Figure 1-1 BEP servlet integration

2 VeriSign, Inc. VPS-0007/Rev11

Accessing the VeriSign BEP Servlet for Oracle iPayment

Oracle iPayment Documents

How to Contact Customer Support

VeriSign, Inc. VPS-0007/Rev11 3

4 VeriSign, Inc. VPS-0007/Rev11

Installing and Configuring on Windows

%JAVA_HOME% Java home directory of your JDK, for example, C:\j2sdk1.4.2

Manually Installing the VeriSign BEP Servlet on Windows

C:\> sqlplus <dbid>/<dbpwd>@<SID>

VeriSign, Inc. VPS-0007/Rev11 5

Step 1 Unzip the pfpro_ipayment file

Figure 2-1 pfpro_ipayment directory structure

Table 2-2 pfpro_ipayment directory contents

Directory or File Contents / Description

certs directory f7389fd.0 (digital certificate)

classes directory Contains the following directories:

docs directory Contains OracleiPayment.pdf

lib directory Contains Verisign.jar

samplestore directory Contains files for VeriSign sample store:

6 VeriSign, Inc. VPS-0007/Rev11

Table 2-2 pfpro_ipayment directory contents

Directory or File Contents / Description

sql directory Contains the following sql files:

verisign directory Contains the following files:

ReleaseNotes.txt Contains release notes

Step 2 Stop the Oracle Apache server

Step 3 Copy VeriSign files

VeriSign, Inc. VPS-0007/Rev11 7

Step 4 Download Xerces XML Parser

Step 5 Configure Java Secure Sockets Extension (JSSE)

To configure the JSSE, use the following procedure:

Throughout Document Converted document to wider format.

Throughout Document Converted document to wider format.

Appendix C, Moved section on what to have available before