Documente Academic
Documente Profesional
Documente Cultură
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.
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
Summary of Revisions
- - - - - - -Contents
-----------------------------
+ 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
+ Appendix C Troubleshooting . . . . . . . . . . . . . . . . . . 61
Enabling Debug Log File Creation . . . . . . . . . . . . . . . . 61
Before Contacting Customer Support . . . . . . . . . . . . . . 61
+ Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
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
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.
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.
Accounts Order
Receivable Management
EC
Extensibility
app.
BEP APIs
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, 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
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.
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.
+ Verisign.jar
5 Copy the following directory from the %VERISIGN_TOP%\payflowpro\ipayment
directory into the %ORACLE_TOP%\8.0.6 directory:
+ certs directory
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
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
Note If you have Oracle’s autoconfig utility turned on, then you must enclose the
statements from the
%VERISIGN_TOP%\verisign\payflowpro\ipayment\zone.properties.verisign file
in between the “#Begin Customizations” and “#End Customizations” tags.
Note If you have Oracle’s autoconfig utility turned on, then you must enclose the
statements from the
%VERISIGN_TOP%\verisign\payflowpro\ipayment\jserv.properties.verisign file
in between the “#Begin Customizations” and “#End Customizations” tags.
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
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
Notation Description
$VERISIGN_TOP Represents the verisign directory into which the pfpro_ipayment.zip file
is unzipped, as shown in Figure 3-1.
If, for example, you unzipped pfpro_ipayment.zip into /mv2/oracle/,
$VERISIGN_TOP would represent /mv2/oracle/verisign, the top-level
directory in the directory structure.
$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.
$ 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.
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
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.”
Note If you have Oracle’s autoconfig utility turned on, then you must enclose the
statements from the
$VERISIGN_TOP/verisign/payflowpro/ipayment/zone.properties.verisign file in
between the “#Begin Customizations” and “#End Customizations” tags.
Note If you have Oracle’s autoconfig utility turned on, then you must enclose the
statements from the
%VERISIGN_TOP%\verisign\payflowpro\ipayment\jserv.properties.verisign file
in between the “#Begin Customizations” and “#End Customizations” tags.
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
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.
2 The Payment Systems page appears, displaying the Payment System tab.
5 Click Create. The Payment Systems page reappears with the VeriSign payment system
added to it.
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.
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
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.
Status Active.
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.
VeriSign, Inc. VPS-0007/Rev11 27
VeriSign Payment Services Oracle iPayment Back-End Payment Servlet Installation Guide
----------------------------------------------------------------
8 Repeat these procedures to create and configure the routing rules for credit cards,
using the appropriate values for credit card payments.
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.
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.
1 On the Operation tab, click the Follow-on Operation subtab. The Search Transactions page
appears.
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.
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.
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.
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.
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.
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.
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.
0 Approved
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.
Table A-1 VeriSign transaction RESULT values and RESPMSG text (Continued)
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.
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.
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.
30 Duplicate transaction
Table A-1 VeriSign transaction RESULT values and RESPMSG text (Continued)
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.)
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).
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.
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.
122 Merchant sale total will exceed the credit cap with current transaction. ACH
transactions only.
Table A-1 VeriSign transaction RESULT values and RESPMSG text (Continued)
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.
1000 Generic host error. This is a generic message returned by your credit card
processor. The RESPMSG will contain more information describing the error.
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.
Table A-1 VeriSign transaction RESULT values and RESPMSG text (Continued)
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.
Parameters
Parameters Mapping
Table B-1 Parameters mapping
SETTLE_DATE NA NA NA
SHIPCARRIER VRSN_EXTEND_DATA. OapfShipCarrier Shipping Carrier
SHIPCARRIER
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.
+ 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
vpsipayment.properties %ORACLE_TOP%\8.0.6\verisign
jserv.properties %ORACLE_TOP%\iAS\Apache\Jserv\etc
zone.properties %ORACLE_TOP%\iAS\Apache\Jserv\etc
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
vpsipayment.properties $ORACLE_TOP/8.0.6/verisign
jserv.properties $ORACLE_TOP/iAS/Apache/Jserv/etc
zone.properties $ORACLE_TOP/iAS/Apache/Jserv/etc
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.
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:
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.
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
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
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