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 Card-Present (SWIPE) Transactions
3
36 Payflow Pro Developer’s Guide
Submitting Card-Present (SWIPE) Transactions
Payflow Pro supports card-present transactions (face-to-face purchases).
Follow these guidelines to take advantage of the lower card-present transaction rate:
z Contact your merchant account provider to ensure that they support card-present
transactions.
z Contact PayPal Customer Service to request having your account set up properly for
accepting and passing swipe data.
z If you plan to process card-present as well as card-not-present transactions, set up two
separate Payflow Pro accounts. Request that one account be set up for card-present
transactions, and use it solely for that purpose. Use the other for card-not-present
transactions. Using the wrong account may result in downgrades.
z A Sale is the preferred method to use for card-present transactions. Consult
with your acquiring bank for recommendations on other methods.
Supported Processing Platforms
PayPal is certified to submit card-present transactions for the following processing platforms:
American Express APA
Citibank Singapore (CSIN)
First Data Resources International (FDI)
Card-present Transaction Syntax
Use the SWIPE parameter to pass the Track 1 or Track 2 data (the card’s magnetic stripe
information). Include either Track 1 or Track 2 data—not both (up to 80 alphanumeric
characters). If Track 1 is physically damaged, the POS application can send Track 2 data
instead.
The track data includes the disallowed = (equal sign) character. To enable you to use the data,
the SWIPE parameter must include a length tag specifying the number of characters in the
track data. For this reason, in addition to passing the track data, the POS application must
count the characters in the track data and pass that number. Length tags are described in
“Using Special Characters in Values” on page 19. The length tag in the following example is
[40].
Do not include the ACCT or EXPDATE parameters in card-present transactions, as this data is
included in the SWIPE value.
Example Card-present Transaction Parameter String
This is an example card-present transaction parameter string: