Developer's Guide
Table Of Contents
- Contents
- Introduction
- Downloading, Installing, and Activating
- Simple Payflow Transaction
- Credit Card Transactions
- Credit Card Features
- About Credit Card Processing
- Parameters Used in Credit Card Transactions
- Submitting Sale Transactions
- Submitting Authorization/Delayed Capture Transactions
- When To Use Authorization/Delayed Capture Transactions
- Required Authorization Transaction Parameters
- Typical Authorization 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 Account Verifications With TRXTYPE=A
- Submitting Voice Authorization Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Submitting Purchasing Card Transactions
- Using Address Verification Service
- Processing Platforms Supporting Address Verification Service
- Example Address Verification Service Request Parameter List
- Example Address Verification Service Response
- Card Security Code Validation
- Credit Card Testing
- Responses to Transaction Requests
- Processors Requiring Additional Transaction Parameters
- Performing TeleCheck Electronic Check Transactions
- Submitting Purchasing Card Level 2 and Level 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions - Phoenix Processor
- American Express Phoenix Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing
- First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
- Global Payments - Central Purchasing Card Transaction Processing
- Global Payments - East Purchasing Card Transaction Processing
- Merchant e-Solutions Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- VERBOSITY: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- ISO Country Codes
- Codes Used by FDMS South Only
- XMLPay
- Additional Processor Information
- Index
Simple Payflow Transaction
Transaction Requests
3
20 Website Payments Pro Payflow Edition Developer’s Guide
Connection Parameters
The connection parameters are described below. Pass them in the format and syntax required
by the Payflow SDK and programming language that you are using. See your integration
documentation for details.
PARMLIST Syntax Guidelines
Follow these guidelines when creating the PARMLIST:
z Spaces are allowed in values.
z Enclose the PARMLIST in quotation marks (“”).
z Do not place quotation marks (“”) within the body of the PARMLIST.
z Separate all name-value pairs in the PARMLIST using an ampersand (&).
z Set the VERBOSITY transaction parameter to MEDIUM (default is LOW) if you want the
response to return more detailed information. For details, see Appendix A, “Verbosity:
Viewing Processor-Specific Transaction Results.”
Using Special Characters in Values
Because the ampersand (&) and equal sign (=) characters have special meanings in the
PARMLIST, name-value pairs like the following examples are not valid:
TABLE 3.1 Connection parameters
Parameter Description
HOSTADDRESS (Required) Payflow host name. See “Host Addresses” on page 13 for details on host
addresses.
HOSTPORT (Required) Use port 443.
PARMLIST (Required) List of parameters that specify the payment information for the transaction.
The quotation marks “ ” at the beginning and end are required. The following is an
example:
TRXTYPE=S&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=Sup
erMerchant&PWD=SuperUserPassword&ACCT=5555555555554444&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 a Sale.
TIMEOUT (Required) Time-out period for the transaction. The minimum recommended time-out
value is 30 seconds. The client begins tracking from the time that it sends the
transaction request to the server.
PROXYADDRESS (Optional) Proxy server address. Use the PROXY parameters for servers behind a
firewall. Your network administrator can provide the values.
PROXYPORT (Optional) Proxy server port.
PROXYLOGON (Optional) Proxy server logon ID.
PROXYPASSWORD (Optional) Proxy server logon password.