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
Submitting Authorisation/Delayed Capture Transactions
3
26 Payflow Pro Developer’s Guide
Typical Authorisation Transaction Parameter String
A typical parameter string passed in an Authorisation transaction is the same as a Sale
transaction string. The only difference is that the TRXTYPE value is A in an Authorisation.
"TRXTYPE=A&TENDER=C&USER=SuperUser&PWD=SuperUserPassword&VENDOR=SuperUser
&PARTNER=PayPal&ACCT=5105105105105100&EXPDATE=1209&CVV2=123&AMT=99.00&
FNAME=Bill&LNAME=Smith&STREET=123 Main
St.&CITY=Anywhere&STATE=CA&ZIP=12345&COMMENT1=Reservation&INVNUM=1234567
890&PONUM=C12345&CVV2=567&VERBOSITY=MEDIUM"
Required Delayed Capture Transaction Parameters
To perform a Delayed Capture transaction, you are required to pass the following parameter:
ORIGID
Set ORIGID to the PNREF (Transaction ID in PayPal Manager reports) value returned from
the original transaction. (For details on PNREF, see Chapter 4, “Responses to Credit Card
Transaction Requests) In addition, if the amount of the capture differs from the amount of the
Authorisation, you also must pass a value for AMT.
Fields Copied From the Authorisation Transaction into the Delayed Capture
Transaction
The following fields are copied from the Authorisation transaction into the Delayed Capture
transaction (if they exist in the original transaction). If you provide a new value for any of
these parameters when submitting the Delayed Capture transaction, then the new value is
used. (Exceptions are ACCT, EXPDATE, and SWIPE. These parameters retain their original
values.)
Step 1 Perform the Authorisation transaction
The Authorisation transaction uses the same parameters as Sale transactions, except that the
transaction type is A.
ACCT AMT CITY COMMENTt1
COMMENT2 COMPANYNAME BILLTOCOUNTRY CUSTCODE
CUSTIP DL DOB DUTYAMT
EMAIL EXPDATE FIRSTNAME FREIGHTAMT
INVNUM LASTNAME MIDDLENAME PONUM
SHIPTOCITY SHIPTOCOUNTRY SHIPTOFIRSTNAME SHIPTOLASTNAME
SHIPTOMIDDLENAME SHIPTOSTATE SHIPTOSTREET SHIPTO ZIP
SS STATE Street SWIPE
TAXAMT TAXEXEMPT PHONENUM ZIP