Developer's Guide
Table Of Contents
- Payflow Pro Developer’s Guide
- Contents
- Preface
- Introduction
- Installing and Configuring the Payflow APIs
- Performing Credit Card Transactions
- About Credit Card Processing
- Contents of a Transaction Request
- How To Format a Transaction
- Parameters Used in Credit Card Transactions
- Values Required by All Transaction Types
- Submitting Sale Transactions
- Submitting Authorisation/Delayed Capture Transactions
- When To Use Authorisation/Delayed Capture Transactions
- Required Authorisation Transaction Parameters
- Typical Authorisation Transaction Parameter String
- Required Delayed Capture Transaction Parameters
- Delayed Capture Transaction: Capturing Transactions for Lower Amounts
- Delayed Capture Transaction: Capturing Transactions for Higher Amounts
- Delayed Capture Transaction: Error Handling and Retransmittal
- Submitting Voice Authorisation Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Card Security Code Validation
- Responses to Credit Card Transaction Requests
- Testing Payflow Pro Credit Card Transactions
- Activating Your Payflow Pro Account
- Processor Details
- Verbosity: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- XMLPay
- Index
Performing Credit Card Transactions
Contents of a Transaction Request
3
18 Payflow Pro Developer’s Guide
the card to your Payflow Pro account through PayPal Manager. See PayPal Manager online
help for details.
Contents of a Transaction Request
Table 3-1 describes the connection parameters that you need to pass when submitting a
transaction request to the Payments gateway. Pass them in the format and syntax required by
the SDK and programming language that you are using. See your integration documentation
for details.
PARMLIST Syntax Guidelines
Follow these guidelines when creating the PARMLIST:
TABLE 3.1 Connection parameters
Argument Required Description
HOSTADDRESS Yes PayPal’s host name.
For live transactions, use payflowpro.verisign.com
For testing purposes, use pilot-payflowpro.verisign.com
HOSTPORT Yes Use port 443
PARMLIST Yes 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=PayPal&VENDOR=SuperMercha
nt&USER=SuperMerchant&PWD=x1y2z3&ACCT=555555555555444
4&EXPDATE=0308&AMT=123.00”
The content of the PARMLIST varies by the type of transaction being
processed. For example, a Void transaction requires a different set of
parameters than does a Sale transaction.
“Parameters Used in Credit Card Transactions” on page 19 defines the
parameters used to create credit card transactions. “Values Required by
All Transaction Types” on page 23 lists the parameters required by each
transaction type.
TIMEOUT Yes Time-out period for the transaction. The minimum recommended time-
out value is 30 seconds. The PayPal client begins tracking from the time
that it sends the transaction request to the PayPal server.
PROXYADDRESS No Proxy server address. Use the PROXY parameters for servers behind a
firewall. Your network administrator can provide the values.
PROXYPORT No Proxy server port
PROXYLOGON No Proxy server logon ID
PROXYPASSWORD No Proxy server logon password