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
Payflow Pro Developer’s Guide 21
Performing Credit Card Transactions
Parameters Used in Credit Card Transactions
CUSTREF Merchant-defined identifier for reporting and
auditing purposes. For example, you can set
CUSTREF to the invoice number.
You can use CUSTREF when performing Inquiry
transactions. To ensure that you can always access
the correct transaction when performing an Inquiry,
you must provide a unique CUSTREF when
submitting any transaction, including retries.
See STARTTIME and ENDTIME.
No Alpha-
numeric
12
CVV2 A 3- or 4-digit code that is printed (not imprinted)
on the back of a credit card. Used as partial
assurance that the card is in the buyer’s possession.
See “Card Security Code Validation” on page 37.
No Alpha-
numeric
4
ENDTIME Optional for Inquiry transactions when using
CUSTREF to specify the transaction.
ENDTIME specifies the end of the time period
during which the transaction specified by the
CUSTREF occurred. See STARTTIME.
ENDTIME must be less than 30 days after
STARTTIME. An inquiry cannot be performed
across a date range greater than 30 days.
If you set ENDTIME, and not STARTTIME, then
STARTTIME is defaulted to 30 days before
ENDTIME.
If neither STARTTIME nor ENDTIME is specified,
then the system searches the last 30 days.
Format: yyyymmddhhmmss
No Numeric 14
EXPDATE Expiration date of the credit card in mmyy format.
For example, 0308 represents March 2008.
Yes
1
Numeric 4
NAME or
FIRSTNAME
Account holder's name. This single field holds all of
the person’s name information.
No, but
recom-
mended
Alpha-
numeric
uppercase
30
ORIGID The ID of the original transaction that is being
referenced. This ID is returned by the PNREF
parameter and appears as the Transaction ID in
PayPal Manager reports.
This value is case-sensitive.
Yes
1
Alpha-
numeric
12
T
ABLE 3.2 Credit-card transaction parameters(Continued)
Parameter Description Required Type
Max.
Length