Developer's Guide

Processors Requiring Additional Transaction Parameters
Paymentech
A
82 Payflow Pro Developer’s Guide
Paymentech, Additional Credit Card Parameters (Legacy)
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
Paymentech accepts the following legacy parameters. For best AVS results, pass the city and
state parameters in the parameter list.
TABLE A.9 Additional Paymentech parameters (legacy)
Parameter Description Required Type Length
CITY Cardholder’s billing city. No Alpha 20
BILLTOCOUNTRY Cardholder’s billing country code Yes Numeric 3
INVNUM Merchant invoice number. The merchant invoice
number is used for authorizations and settlements
and, depending on your merchant bank, will appear
on your customer's credit card statement and your
bank reconciliation report. If you do not provide an
invoice number, the transaction ID (PNREF) will be
submitted.
No Alpha-
numeric
9
MERCHDESCR Merchant descriptor.
For example, ABCCMPY*FALLCATALOG
No Alpha-
numeric
22
MERCHSVC Merchant telephone number.
For example, 603-555-1212
No Alpha-
numeric
13
STATE Cardholder’s billing state. No Alpha 2
SWIPE Allows Track 1 and Track 2 data to be passed to
enable a card-present transaction.
No Alpha-
numeric
80
RECURRING Identifies the transaction as recurring. This value
does not activate PayPal’s Recurring Billing Service
APIs.
If the RECURRING parameter was set to Y for the
original transaction, then the setting is ignored when
forming Credit, Void, and Force transactions.
If you subscribe to PayPal’s Fraud Protection
Services:
To avoid charging you to filter recurring
transactions that you know are reliable, the fraud
filters do not screen recurring transactions.
To screen a prospective recurring customer, submit
the transaction data using PayPal Manager’s
Manual Transactions page. The filters screen the
transaction in the normal manner. If the transaction
triggers a filter, then you can follow the normal
process to review the filter results.
No Alpha-
numeric
Y or N
1