Developer's Guide
Table Of Contents
- Contents
- Introduction
- Downloading, Installing, and Activating
- Simple Payflow Transaction
- Credit Card Transactions
- Credit Card Features
- About Credit Card Processing
- Parameters Used in Credit Card Transactions
- Submitting Sale Transactions
- Submitting Authorization/Delayed Capture Transactions
- When To Use Authorization/Delayed Capture Transactions
- Required Authorization Transaction Parameters
- Typical Authorization 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 Account Verifications With TRXTYPE=A
- Submitting Voice Authorization Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Submitting Purchasing Card Transactions
- Using Address Verification Service
- Processing Platforms Supporting Address Verification Service
- Example Address Verification Service Request Parameter List
- Example Address Verification Service Response
- Card Security Code Validation
- Credit Card Testing
- Responses to Transaction Requests
- Processors Requiring Additional Transaction Parameters
- Performing TeleCheck Electronic Check Transactions
- Submitting Purchasing Card Level 2 and Level 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions - Phoenix Processor
- American Express Phoenix Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing
- First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
- Global Payments - Central Purchasing Card Transaction Processing
- Global Payments - East Purchasing Card Transaction Processing
- Merchant e-Solutions Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- VERBOSITY: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- ISO Country Codes
- Codes Used by FDMS South Only
- XMLPay
- Additional Processor Information
- Index
Payflow Pro Developer’s Guide 79
Processors Requiring Additional Transaction Parameters
Elavon (Formerly Nova)
A
Elavon (Formerly Nova)
Elavon, Additional Credit Card Parameters
In addition to the parameters in Table 4.1 , “Credit card transaction request
parameters,”Elavon accepts the following parameter:
Paymentech
Paymentech Salem (New Hampshire), Additional Credit Card Parameters
(CAPN)
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
Paymentech Salem (New Hampshire) accepts the parameters in Table A.8 to meet CAPN
requirements.
TABLE A.7 Elavon additional parameters
Parameter Description Required Type Length
RECURRING Identifies the transaction as recurring. This value does
not activate PayPal’s Recurring Billing Service API.
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
T
ABLE A.8 Additional Paymentech parameters to meet CAPN requirements
Parameter Description Required Type Length
Internet Transaction Data Parameters
EMAIL Account holder’s email address No Alpha-
numeric
60