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 23
Performing Credit Card Transactions
Values Required by All Transaction Types
Values Required by All Transaction Types
All transaction types require values for the following parameters:
TRXTYPE
TENDER
PARTNER
VENDOR
TRXTYPE A single character indicating the type of transaction
to perform. Values are:
S = Sale transaction
C = Credit
A = Authorisation
D = Delayed Capture
V = Void
F = Voice Authorisation
I = Inquiry
Yes Alp h a 1
USER If you set up one or more additional users on the
account, this value is the ID of the user authorised to
process transactions. If, however, you have not set
up additional users on the account, USER has the
same value as VENDOR.
The examples in this document use
USER=SuperMerchant.
This value is case-sensitive.
Yes Alp h a-
numeric
64
VENDOR Your merchant login ID that you created when you
registered for the Payflow Pro account.
The examples in this document use VENDOR =
SuperMerchant.
This value is case sensitive.
Yes Alp h a-
numeric
64
VERBOSITY LOW or MEDIUM.
LOW is the default setting—normalized values.
MEDIUM returns the processor’s raw response
values.
See Appendix B, “Verbosity: Viewing Processor-
Specific Transaction Results.”
No Alpha
ZIP Account holder’s 5- to 9-digit ZIP (postal) code. Do
not use spaces, dashes, or non-numeric characters.
No Alpha 9
1. Some transaction types do not require this parameter. See “Values Required by All Transaction Types” on page 23
TABLE 3.2 Credit-card transaction parameters(Continued)
Parameter Description Required Type
Max.
Length