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 Sale Transactions
3
24 Payflow Pro Developer’s Guide
USER
PWD
Each transaction type has additional parameter requirements, as listed in the following
sections. Transaction responses are described in Chapter 4, “Responses to Credit Card
Transaction Requests.”
Submitting Sale Transactions
The Sale transaction (TRXTYPE=S) charges the specified amount against the account, and
marks the transaction for immediate fund transfer during the next settlement period. PayPal
submits each merchant’s transactions for settlement on a daily basis.
When To Use a Sale Transaction
A Sale transaction is best suited to businesses that provide immediate fulfillment for their
products or services. If your business does not provide immediate fulfillment, then credit card
association rules recommend that you use an Authorisation and a Delayed Capture transaction.
For details, see “Submitting Authorisation/Delayed Capture Transactions” on page 25. If you
need to recharge a credit card and you are not storing the credit card information in your local
database, you can perform a new reference transaction based on a Sale transaction. For details,
see “Submitting Authorisation/Delayed Capture Transactions” on page 25.
Additional Parameters for Sale Transactions
To perform a Sale transaction, you are required to pass the following parameters:
ACCT
AMT
EXPDATE
N OTE: The pinless debit tender type requires essentially the same parameters as a credit card
transaction. In addition to the values required by all transactions, you must pass values
for the ACCT and AMT parameters.
Typical Sale Transaction Parameter String
The following is a typical PARMLIST string passed in a Sale transaction.
"TRXTYPE=S&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"
Note that, besides the required parameters that you pass in a Sale transaction, this string
includes other typical parameters. The COMMENT1 (and COMMENT2) fields help to track