Developer's Guide
Table Of Contents
- Payflow Pro Developer’s Guide
- 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 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
- American Express
- First Data Merchant Services (FDMS) Nashville
- First Data Merchant Services (FDMS) South
- First Data Merchant Services (FDMS) North
- Merchant e-Solutions
- Elavon (Formerly Nova)
- Paymentech
- TSYS Acquiring Solutions
- 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
- Index
Payflow Pro Developer’s Guide 53
6
Responses to Transaction
Requests
When a transaction finishes, the Payflow server returns a response string made up of name-
value pairs. This is an example response string.
RESULT=0&PNREF=EFHP0D426A53&RESPMSG=APPROVED&AUTHCODE=25TEST&AVSADDR=Y&AVSZ
IP=N&CVV2MATCH=Y
Contents of a Response to a Credit Card Transaction Request
Table 6.1 describes values that can be returned in response strings.
TABLE 6.1 Transaction response values
Field Description Type Length
PNREF Payflow Transaction ID, a unique number that
identifies the transaction. PNREF is described in
“PNREF Format” on page 56.
Alpha-
numeric
12
RESULT The outcome of the attempted transaction. A
result of 0 (zero) indicates the transaction was
approved. Any other number indicates a decline
or error. RESULT values are described in
“RESULT Values and RESPMSG Text” on
page 56.
Numeric Variable
CVV2MATCH Result of the card security code (CVV2) check.
The issuing bank may decline the transaction if
there is a mismatch. In other cases, the
transaction may be approved despite a mismatch.
Alpha
Y, N, X, or
no response
1
RESPMSG The response message returned with the
transaction result. Exact wording varies.
Sometimes a colon appears after the initial
RESPMSG followed by more detailed
information. Response messages are described in
“RESULT Values and RESPMSG Text” on
page 56.
Alpha-
numeric
Va ri abl e