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
Recharging to the Same Credit Card (Reference Transactions)
3
34 Payflow Pro Developer’s Guide
If you attempt to perform a reference transaction in an account for which
reference transactions are disallowed, result code 117 is returned. See PayPal
Manager online help for instructions on setting reference transactions and
other security features.
Sale and Authorisation transactions can make use of a reference transaction as a source of
transaction data. PayPal looks up the reference transaction and copies its transaction data into
the new Sale or Authorisation transaction. With the exception of dollar amount data, which
triggers a filter if out of range, reference transactions are not screened by Fraud Protection
Services filters.
IMPORTANT: When PayPal looks up the reference transaction, neither the transaction
being referenced nor any other transaction in the database is changed in any
way. That is, a reference transaction is a read-only operation—only the new
transaction is populated with data and acted upon. No linkage is maintained
between the reference transaction and the new transaction.
You can also initiate reference transactions from PayPal Manager. See PayPal Manager online
help for details.
Transaction Types that Can Be Used as the Original Transaction
You can reference the following transaction types to supply data for a new Sale or
Authorisation transaction:
z Authorisation (To capture the funds for an approved Authorisation transaction, be sure to
perform a Delayed Capture transaction—
not a Reference transaction.)
z Credit
z Delayed Capture
z Sale
z Voice Authorisation (The Voice Authorisation code is not copied to the new transaction)
z Vo i d
Fields Copied From Reference Transactions
The following fields are copied from the reference transaction into the new Sale or
Authorisation transaction (if they exist in the original transaction). If you provide a value for
any of these parameters when submitting the new transaction, then the new value is used.
ACCTTYPE STREET
ACCT CITY
EXPDATE STATE
FIRSTNAME ZIP