Paypal Payflow Pro 2008 Developers Guide PayflowPro_Guide

Payflow Pro - 2008 - Developer’s Guide PP_PayflowPro_2008 Free User Guide for PayPal Software, Manual

2015-07-27

: Paypal Paypal-Payflow-Pro-2008-Developers-Guide-777984 paypal-payflow-pro-2008-developers-guide-777984 paypal pdf

Open the PDF directly: View PDF .
Page Count: 170

Download
Open PDF In Browser	View PDF

Payflow Pro
Developer’s Guide

For Professional Use Only
Currently only available in English.
A usage Professional Uniquement
Disponible en Anglais uniquement pour l’instant.

Last updated: October 2008

Payflow Pro Developer’s Guide
Document Number: 200010.en_US-200810

© 2008 PayPal, Inc. All rights reserved. PayPal is a registered trademark of PayPal, Inc. The PayPal logo is a trademark of PayPal, Inc. Other
trademarks and brands are the property of their respective owners.
The information in this document belongs to PayPal, Inc. It may not be used, reproduced or disclosed without the written approval of PayPal, Inc.
Copyright © PayPal. All rights reserved. PayPal S.à r.l. et Cie, S.C.A., Société en Commandite par Actions. Registered office: 22-24 Boulevard Royal, L2449, Luxembourg, R.C.S. Luxembourg B 118 349
Consumer advisory: The PayPal™ payment service is regarded as a stored value facility under Singapore law. As such, it does not require the approval
of the Monetary Authority of Singapore. You are advised to read the terms and conditions carefully.
Notice of non-liability:
PayPal, Inc. is providing the information in this document to you “AS-IS” with all faults. PayPal, Inc. makes no warranties of any kind (whether express,
implied or statutory) with respect to the information contained herein. PayPal, Inc. assumes no liability for damages (whether direct or indirect), caused
by errors or omissions, or resulting from the use of this document or the information contained in this document or resulting from the application or use
of the product or service described herein. PayPal, Inc. reserves the right to make changes to any information herein without further notice.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
How to Contact Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Payflow Pro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Payflow Pro Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Host Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
How Payflow Pro Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Supported Processing Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Supported Payment Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Payflow Pro Recurring Billing Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
About Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2

Downloading, Installing, and Activating

. . . . . . . . . . 17

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Preparing the Payflow Client Application . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Activating Your Payflow Pro Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 3

Simple Payflow Transaction . . . . . . . . . . . . . . . . . 19

Transaction Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Request Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Data Modes for Sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
User Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Sale Transaction Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Typical Sale Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Formatting Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Payflow Pro Developer’s Guide

Contents

Chapter 4

Credit Card Transactions . . . . . . . . . . . . . . . . . . 23

Credit Card Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
About Credit Card Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Obtaining an Internet Merchant Account . . . . . . . . . . . . . . . . . . . . . . . . 24
Planning Your Payflow Pro Integration . . . . . . . . . . . . . . . . . . . . . . . . . 24
Complying With the E-commerce Indicator (ECI) . . . . . . . . . . . . . . . . . . . . 25
Handling Credit Card Type Information . . . . . . . . . . . . . . . . . . . . . . . . . 25
Parameters Used in Credit Card Transactions. . . . . . . . . . . . . . . . . . . . . . . . 26
Submitting Sale Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
When To Use a Sale Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Additional Parameters For Sale Transactions . . . . . . . . . . . . . . . . . . . . . . 28
Typical Sale Transaction Parameter String . . . . . . . . . . . . . . . . . . . . . . . 28
Submitting Authorization/Delayed Capture Transactions . . . . . . . . . . . . . . . . . . 29
When To Use Authorization/Delayed Capture Transactions . . . . . . . . . . . . . . . 29
Required Authorization Transaction Parameters . . . . . . . . . . . . . . . . . . . . 29
Typical Authorization Transaction Parameter String . . . . . . . . . . . . . . . . . . . 29
Required Delayed Capture Transaction Parameters . . . . . . . . . . . . . . . . . . 30
Delayed Capture Transaction: Capturing Transactions for Lower Amounts . . . . . . . 31
Delayed Capture Transaction: Capturing Transactions for Higher Amounts . . . . . . 31
Delayed Capture Transaction: Error Handling and Retransmittal . . . . . . . . . . . . 32
Submitting Voice Authorization Transactions . . . . . . . . . . . . . . . . . . . . . . . . 32
When to Use a Voice Authorization Transaction. . . . . . . . . . . . . . . . . . . . . 32
Required Voice Authorization Transaction Parameters . . . . . . . . . . . . . . . . . 32
Submitting Credit Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Required Credit Transaction Parameters . . . . . . . . . . . . . . . . . . . . . . . . 33
Credit Transaction Parameter Strings . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Submitting Void Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
When To Use a Void Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Required Void Transaction Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 35
Example Void Transaction Parameter String . . . . . . . . . . . . . . . . . . . . . . 36
Submitting Inquiry Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
When To Use an Inquiry Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Required Parameters When Using the PNREF . . . . . . . . . . . . . . . . . . . . . 37
Inquiry Transaction Parameter String Using the PNREF . . . . . . . . . . . . . . . . 37
Required Parameters When Using the CUSTREF . . . . . . . . . . . . . . . . . . . 37
Inquiry Transaction Parameter String Using the CUSTREF . . . . . . . . . . . . . . . 38
Recharging to the Same Credit Card (Reference Transactions). . . . . . . . . . . . . . . 38
When To Use a Reference Transaction . . . . . . . . . . . . . . . . . . . . . . . . . 38
Transaction Types that Can Be Used as the Original Transaction . . . . . . . . . . . 39

Payflow Pro Developer’s Guide

Contents

Fields Copied From Reference Transactions . . . . . . . . . . . . . . . . . . . . . . 40
Example Reference Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Submitting Card-Present (SWIPE) Transactions. . . . . . . . . . . . . . . . . . . . . . . 41
Supported Processing Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Card-present Transaction Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Submitting Purchasing Card Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Using Address Verification Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Processing Platforms Supporting Address Verification Service . . . . . . . . . . . . . . . 43
Example Address Verification Service Request Parameter List . . . . . . . . . . . . . . . 44
Example Address Verification Service Response . . . . . . . . . . . . . . . . . . . . . . 44
Card Security Code Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Processing Platforms and Credit Cards Supporting Card Security Code . . . . . . . . 45

Chapter 5

Credit Card Testing . . . . . . . . . . . . . . . . . . . . . 47

Testing Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Credit Card Numbers Used for Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Result Values in Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Testing Result Values in Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . 48
RESULT Values Returned Based on Transaction Amount. . . . . . . . . . . . . . . . . . 48
Alternative Methods for Generating Specific RESULT Values . . . . . . . . . . . . . . 49
Testing Address Verification Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Testing Card Security Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 6

Responses to Transaction Requests . . . . . . . . . . . . 53

Contents of a Response to a Credit Card Transaction Request . . . . . . . . . . . . . . . 53
BALAMT Response Parameter and Stored Value Cards . . . . . . . . . . . . . . . . . . 55
American Express CAPN Stored Value Card Example . . . . . . . . . . . . . . . . . 55
PNREF Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
PNREF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
RESULT Values and RESPMSG Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
RESULT Values for Transaction Declines or Errors . . . . . . . . . . . . . . . . . . . 56
RESULT Values for Communications Errors . . . . . . . . . . . . . . . . . . . . . . 62

Appendix A Processors Requiring Additional Transaction Parameters . 65
American Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
American Express Additional Credit Card Parameters (CAPN) . . . . . . . . . . . . . 66
American Express Additional Credit Card Parameters (Legacy) . . . . . . . . . . . . 71

Payflow Pro Developer’s Guide

Contents

First Data Merchant Services (FDMS) Nashville . . . . . . . . . . . . . . . . . . . . . . . 74
FDMS Nashville, Additional Credit Card Parameters . . . . . . . . . . . . . . . . . . 74
First Data Merchant Services (FDMS) South . . . . . . . . . . . . . . . . . . . . . . . . 75
FDMS South, Additional Credit Card Parameters . . . . . . . . . . . . . . . . . . . . 75
First Data Merchant Services (FDMS) North. . . . . . . . . . . . . . . . . . . . . . . . . 75
FDMS North, Additional Credit Card Parameters . . . . . . . . . . . . . . . . . . . . 75
Merchant e-Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Merchant e-Solutions, Additional Credit Card Parameters . . . . . . . . . . . . . . . 76
Elavon (Formerly Nova) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Elavon, Additional Credit Card Parameters . . . . . . . . . . . . . . . . . . . . . . . 77
Paymentech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Paymentech Salem (New Hampshire), Additional Credit Card Parameters (CAPN) . . 77
Paymentech, Additional Credit Card Parameters (Legacy) . . . . . . . . . . . . . . . 80
TSYS Acquiring Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
TSYS Acquiring Solutions, Additional Credit Card Parameters (CAPN). . . . . . . . . 81
TSYS Acquiring Solutions, Additional Credit Card Parameters (Legacy) . . . . . . . . 87

Appendix B Performing TeleCheck Electronic Check Transactions . . . 89
TeleCheck Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Required Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Testing TeleCheck Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Example Test Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Preparing for TeleCheck Production Transactions . . . . . . . . . . . . . . . . . . . . . . 92
Responses to Telecheck Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
HOSTCODE Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Appendix C Submitting Purchasing Card Level 2 and Level 3
Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
About Purchasing Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
About Program Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Accepted BIN Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
About American Express Purchasing Card Transactions - Phoenix Processor . . . . . . . 98
Supported Transaction Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Avoiding Downgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Submitting Successful Level 3 Transactions . . . . . . . . . . . . . . . . . . . . . . 99
Edit Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Accepted BIN Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
American Express Phoenix Purchasing Card Transaction Processing . . . . . . . . . . .100

Payflow Pro Developer’s Guide

Contents

American Express Phoenix Level 2 Parameters (CAPN) . . . . . . . . . . . . . . . .101
American Express Phoenix Level 2 Parameters (Legacy). . . . . . . . . . . . . . . .103
Example American Express Phoenix Level 2 Transaction Parameter String . . . . . .103
American Express Phoenix Level 3 Parameters. . . . . . . . . . . . . . . . . . . . .103
Example American Express Phoenix Level 3 Transaction Parameter String . . . . . .105
First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing.106
First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing . .107
FDMS North Purchasing Card Line Item Parameters . . . . . . . . . . . . . . . . . .108
First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing . .109
FDMS South Line Item Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Example FDMS South Purchasing Card Level 2 and 3 Parameter String . . . . . . . . 111
Example FDMS South Line Item Parameter String . . . . . . . . . . . . . . . . . . . 111
Global Payments - Central Purchasing Card Transaction Processing . . . . . . . . . . . . 112
Global Payments - Central Level 2 Parameters . . . . . . . . . . . . . . . . . . . . . 112
Example Global Payments - Central Level 2 Visa or MasterCard Transaction Parameter
String. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Global Payments - East Purchasing Card Transaction Processing . . . . . . . . . . . . . 112
Global Payments - East Level 2 Parameters . . . . . . . . . . . . . . . . . . . . . . 113
Example Global Payments - East Level 2 Visa or MasterCard Transaction
Parameter String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Merchant e-Solutions Purchasing Card Transaction Processing . . . . . . . . . . . . . . 113
Merchant e-Solutions Level 2 Parameters. . . . . . . . . . . . . . . . . . . . . . . . 113
Merchant e-Solutions Level 3 MasterCard Parameters . . . . . . . . . . . . . . . . . 114
Merchant e-Solutions Level 3 Visa Parameters . . . . . . . . . . . . . . . . . . . . . 116
Elavon (Formerly Nova) Purchasing Card Transaction Processing . . . . . . . . . . . . .120
Elavon Level 2 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Elavon Additional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Example Elavon Level 2 Transaction Parameter String . . . . . . . . . . . . . . . . .121
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing . . . . . .121
Paymentech Salem (New Hampshire) Level 2 Parameters (CAPN) . . . . . . . . . .121
Paymentech Salem (New Hampshire) Level 2 Parameters (Legacy) . . . . . . . . . .123
Paymentech Salem (New Hampshire) Level 3 Purchasing Card Parameters. . . . . .124
Paymentech Tampa Level 2 Purchasing Card Transaction Processing . . . . . . . . . . .127
Paymentech Tampa Level 2 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameter String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
TSYS Acquiring Solutions Purchasing Card Transaction Processing . . . . . . . . . . . .128
TSYS Acquiring Solutions Level 2 Parameters . . . . . . . . . . . . . . . . . . . . .128
TSYS Acquiring Solutions Level 3 MasterCard Parameters. . . . . . . . . . . . . . .129
TSYS Acquiring Solutions Level 3 Visa Parameters. . . . . . . . . . . . . . . . . . .131

Payflow Pro Developer’s Guide

Contents

Appendix D VERBOSITY: Viewing Processor-Specific
Transaction Results . . . . . . . . . . . . . . . . . . . . . . . . 135
Supported Verbosity Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Changing the Verbosity Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140
Setting the Verbosity Level on a Per-Transaction Basis . . . . . . . . . . . . . . . . .140
Setting the Default Verbosity Level for All Transactions . . . . . . . . . . . . . . . . .140

Appendix E Additional Reporting Parameters . . . . . . . . . . . . . 141
Appendix F

ISO Country Codes . . . . . . . . . . . . . . . . . . . . 143

Appendix G Codes Used by FDMS South Only . . . . . . . . . . . . . 149
MasterCard Country Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Visa Country Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
FDMS South Currency Codes and Decimal Positions . . . . . . . . . . . . . . . . . . .162

Appendix H XMLPay . . . . . . . . . . . . . . . . . . . . . . . . . . 163
About XMLPay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Payflow Pro XMLPay Developer’s Guide . . . . . . . . . . . . . . . . . . . . . . . . . .163

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Payflow Pro Developer’s Guide

Preface

This guide describes Payflow Pro, a high performance TCP/IP-based Internet payment
solution and how to use it to process credit card . Payflow Pro is pre-integrated with leading ecommerce solutions and is also available as a downloadable software development kit (SDK).

Scope
This guide explains how to integrate Payflow Pro into your website or application to process
credit card transactions over the Payflow payments gateway. It includes information and
special requirements for all supported processors. To process Express Checkout transactions
over the Payflow gateway, see the following Payflow guide: Express Checkout for Payflow
Pro.

Intended Audience
This guide assumes that its readers:
z

Are experienced web or application developers

Have a background in payments services

Related Documentation
For additional Payflow information, see the following related documentation:
z

Express Checkout for Payflow Pro, for integrating Express Checkout as a payment
solution. Use this guide in conjunction with the Express Checkout guide for complete
information on Payflow transaction processing.
PayPal Manager online help, for processing transactions manually, issuing credit cards, and
generating reports
For additional help, see the Help Center at the following URL:
https://www.paypal.com/us/cgi-bin/helpweb?cmd=help

The Sample Code and Documentation section of the PayPal Developer Central home page
provides a link to the Payflow documentation.

Payflow Pro Developer’s Guide

How to Contact Customer Support

How to Contact Customer Support
For problems with transaction processing or your connection to the server, contact Customer
Support by opening a ticket on the under Contact Support tab at http://www.paypal.com/mts.

Revision History
Revision history for Payflow Pro Developer’s Guide.
TABLE 1.1 Revision history
Date
November 2008

Description
z
z
z
z
z
z
z
z

June 2008

Moved coverage of Express Checkout to a separate new document, Express Checkout
for Payflow Pro.
Removed coverage of the version 3 Payflow SDK, including test and live URLs.
Changed Paymentech New Hampshire to Paymentech Salem (New Hampshire)
Updated name of Nova processor to Elavon.
Corrected format of TSYS ORDERDATE field
Added more clarification to description of RESULT value 25
Added more clarification of AMEX CAPN parameters in Appendix A
Updated Table 4.1 , “Credit card transaction request parameters,” to reflect credit card
parameter descriptions only and moved the non-credit card parameter descriptions to
new tables in applicable sections of the chapter
Minor corrections for technical accuracy and clarification

Updated live and test URLs to reflect PayPal only: payflowpro.paypal.com live URL and
pilot-payflowpro.paypal.com test URL
Added Help Center URL to Preface.
Added Paymentech New Hampshire processor specification updates, including:
z CAPN requirements
z
z
z

March 2008

Support of card security code for American Express and Discover cards
Support of Switch/Solo Maestro card
Full authorization reversals

Added PayPal processor responses.
Updated RESULT value 0 to include information about PayPal processor success with warning
message

February 2008

Removed note that PayPal processor does not support non-referenced credits. It supports them now.
Updated test and live host URLs.
Added BILLTOCOUNTRY to Paymentech additional parameters.
Combined Telecheck transactions content into one appendix.

Payflow Pro Developer’s Guide

Revision History
TABLE 1.1 Revision history
Date

Description

November 2007

Explains how merchant can determine what SDK version they are using.
Provides guidelines to merchant to determine if merchant is following American Express CAPN
requirements.
Explains more about VERBOSITY parameter.
Combines appendixes on performing Telecheck transactions with Telecheck responses.
Adds BIN ranges.
Explains how to eliminate TRANSSTATE 106 results.
Updates Index to include an alphabetical listing of all Payflow parameters cited in the guide.
Adds new transaction type N.

Includes other minor edits for technical accuracy.

Payflow Pro Developer’s Guide

Revision History

Payflow Pro Developer’s Guide

Introduction

About Payflow Pro
Payflow Pro is a high performance TCP/IP-based internet payment solution that resides on
your computer system. You can download it in the following forms from the SDKs and
Downloads page on PayPal Developer Central:
z

.NET library

Java library

HTTPS interface

Using the HTTPS interface, you can build your own API by posting directly to the Payflow
servers via HTTPS.
N O T E : If

you prefer to have Payflow Pro integration performed for you, you can obtain
Payflow Pro pre-integrated with leading e-commerce solutions. For a list of preintegrated solutions, see the Partner Solutions>Shopping Carts page on PayPal
Developer Central.

Payflow Pro Documentation
Payflow Pro is described in the Payflow Pro documentation set on PayPal Developer Central.
If you are implementing PayPal as a solution into your website, use this guide for general
guidelines and guidelines on integrating credit card processing. If you are also implementing
PayPal Express Checkout as a payment solution, see the Express Checkout for Payflow Pro
guide for integration details.

Host Addresses
Use the following host addresses for the Payflow V4 SDK:
z

For live transactions, use payflowpro.paypal.com

For testing purposes, use pilot-payflowpro.paypal.com

How Payflow Pro Works
Payflow Pro uses a client/server architecture to transfer transaction data from you to the
processing networks, and then returns the authorization results to you. Payflow Pro can
process real-time credit card transactions and other transaction types to most of the financial
processing centers in the United States.

Payflow Pro Developer’s Guide

Introduction
Supported Processing Platforms

1. The Payflow client encrypts each transaction request using the latest Secure Sockets Layer
(SSL) encryption and establishes a secure link with the Payflow server over the internet.
2. The Payflow server, a multi-threaded processing environment, receives the request and
transmits it (over a secure private network) to the appropriate financial processing network
for real-time payment authorization.
3. The response (approved/declined, and so on) is received from the financial network and is
returned in the same session to the Payflow client.
4. The Payflow client completes each transaction session by transparently sending a
transaction receipt to the server before disconnecting the session.
The entire process is a real-time synchronous transaction. Once connected, the transaction is
immediately processed and the answer returned in about three seconds. Processing
transactions through the Payflow service does not affect or define the time periods of
authorizations, nor does it influence the approval or denial of a transaction by the issuer.
When integrating with Payflow Pro, you need only be concerned with passing all the required
data for transaction authorization. For transactions that you want to be settled (close batch),
the operation is handled by PayPal.

Supported Processing Platforms
Payflow Pro supports the following processing platforms:

PayPal

American Express Phoenix

American Express Brighton

First Data Merchant Services (FDMS) Nashville

First Data Merchant Services (FDMS) North

First Data Merchant Services (FDMS) South

First Data TeleCheck

Global Payments Central

Global Payments East

Merchant e-Solutions

Elavon (Formerly Nova)

Paymentech Salem (New Hampshire)

Paymentech Tampa

TSYS Acquiring Solutions (Formerly Vital Processing Services)

Payflow Pro Developer’s Guide

Introduction
Supported Payment Types

Supported Payment Types
Payflow Pro supports multiple payment types in a single installation, including:
z

Credit cards

PayPal (supported by PayPal’s Express Checkout product)

Pinless debit cards

Electronic checks

Check cards

Purchasing cards (also referred to as commercial cards, corporate cards, procurement
cards, or business cards) Level II and Level III
Automated Clearing House (ACH). For information on performing ACH transactions,
contact your PayPal Sales Representative at paymentsales@PayPal.com

Payflow Pro Recurring Billing Service
The Recurring Billing Service is a scheduled payment solution that enables you to
automatically bill your customers at regular intervals—for example, a monthly fee of $42 for
36 months with an initial fee of $129.
You enroll separately for the Payflow Pro Recurring Billing Service. Using Payflow Pro to
define and manage recurring transactions programmatically is described in Payflow Pro –
Recurring Billing Service User’s Guide. You can manage Recurring Billing tasks in PayPal
Manager. See the online help for details.

About Security
It is your responsibility to protect your passwords and other confidential data and to
implement security safeguards on your website and in your organization, or to ensure that your
hosting company or internal web operations team is implementing them on your behalf.
IMPO RTANT: To enable testing of Payflow Pro, PayPal provides sample transaction scripts

that you customize with your Payflow Pro account information and
password. Because the password is initially stored in the text of the program,
it is vulnerable.
Do not use the test scripts in your production environment. To minimize
fraud, machine passwords should always be encrypted. You must write a
program that encrypts and decrypts your Payflow Pro account password.

Payflow Pro Developer’s Guide

Introduction
About Security

Payflow Pro Developer’s Guide

Downloading, Installing, and
Activating
The Payflow Software Development Kit (SDK) is a set of APIs to allow you to integrate
Payflow Pro with your application or website.
IMPO RTANT: Full

API documentation is included with each SDK.

S u p p o r t e d P l a tf o r m s
Payflow Pro is available on all major web server platforms in a variety of formats to support
your integration requirements. Payflow Pro is available as a .NET or Java library, or you can
build your own API by posting directly to the Payflow servers via HTTPS.

Preparing the Payflow Client Application
Unless you are building your own API and using HTTPS to post to the servers, you will need
to obtain the Payflow SDK. Follow these steps.
1. Download the Payflow SDK.
From the from the SDKs and Downloads page linked to the Library tab on PayPal
Developer Central, download the Payflow SDK appropriate for your platform.
2. Extract the files to a local directory.
3. Configure your firewall.
If you have a stateful firewall, enable outbound traffic for SSL (port 443). The firewall
keeps state on the connection, and automatically permits the inbound response from
PayPal.
If you do not have a stateful firewall, enable inbound and outbound traffic for SSL (port
443). Outbound traffic permits the initial request by Payflow Pro, while inbound permits
the response from PayPal.
4. Read the Readme.txt file.
The Readme.txt file includes integration information and samples that illustrate how to use
the Payflow client application in your development environment.

Payflow Pro Developer’s Guide

Downloading, Installing, and Activating
Activating Your Payflow Pro Account

Activating Your Payflow Pro Account
When you are ready to activate your Payflow Pro account to begin submitting live
transactions, follow these steps:
1. Log in to PayPal Manager at https://manager.paypal.com.
2. Click ActivateYour Account and follow the on-screen instructions.
3. Change the URL within your web or desktop application to point to the live Payflow
servers. For details on Payflow server URLs, see “Host Addresses” on page 9.

Payflow Pro Developer’s Guide

Simple Payflow Transaction

All Payflow transactions include a common set of required parameters. Additional parameters
are required depending on the transaction type.You can also provide many optional
parameters, depending on the results you want returned. For example, you can set the
VERBOSITY parameter to return PayPal processor-specific details rather than normalized
information if you are looking for this kind of information. VERBOSITY is described in detail
in Appendix D, “VERBOSITY: Viewing Processor-Specific Transaction Results.”

Transaction Requests
Request Contents
A transaction request includes:
z

Connection parameters

User parameters

Parameters specific to the type of the transaction, such as a sale or an authorization

Data Modes for Sending
You can send parameter data in the transaction request to the Payflow server in either of two
modes:
z

Name-value pair

XMLPay

The examples in this guide are presented in name-value pair format. Name-value pair syntax
guidelines are described in “PARMLIST Syntax Guidelines” on page 20.
XMLPay is an XML syntax for payment requests and associated responses in a paymentprocessing network. Instead of using name-value pairs, you can send XML documents to the
Payflow server based on the XMLPay 2.0 schema. For details on XMLPay, see XMLPay
Developer’s Guide in the Payflow Pro documentation on Developer Central.

Payflow Pro Developer’s Guide

Simple Payflow Transaction
Transaction Requests

Connection Parameters
The connection parameters are described below. Pass them in the format and syntax required
by the Payflow SDK and programming language that you are using. See your integration
documentation for details.
TABLE 3.1 Connection parameters
Parameter

Description

HOSTADDRESS

(Required) Payflow host name. See “Host Addresses” on page 13 for details on host
addresses.

HOSTPORT

(Required) Use port 443.

PARMLIST

(Required) List of parameters that specify the payment information for the transaction.
The quotation marks “ ” at the beginning and end are required. The following is an
example:
TRXTYPE=S&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=Sup
erMerchant&PWD=SuperUserPassword&ACCT=5555555555554444&EXPDATE=
0308&AMT=123.00
The content of the PARMLIST varies by the type of transaction being processed. For
example, a Void transaction requires a different set of parameters than a Sale.

TIMEOUT

(Required) Time-out period for the transaction. The minimum recommended time-out
value is 30 seconds. The client begins tracking from the time that it sends the
transaction request to the server.

PROXYADDRESS

(Optional) Proxy server address. Use the PROXY parameters for servers behind a
firewall. Your network administrator can provide the values.

PROXYPORT

(Optional) Proxy server port.

PROXYLOGON

(Optional) Proxy server logon ID.

PROXYPASSWORD

(Optional) Proxy server logon password.

PARMLIST Syntax Guidelines

Follow these guidelines when creating the PARMLIST:
z

Spaces are allowed in values.

Enclose the PARMLIST in quotation marks (“”).

Do not place quotation marks (“”) within the body of the PARMLIST.

Separate all name-value pairs in the PARMLIST using an ampersand (&).

Set the VERBOSITY transaction parameter to MEDIUM (default is LOW) if you want the
response to return more detailed information. For details, see Appendix A, “Verbosity:
Viewing Processor-Specific Transaction Results.”

Using Special Characters in Values

Because the ampersand (&) and equal sign (=) characters have special meanings in the
PARMLIST, name-value pairs like the following examples are not valid:
20

Payflow Pro Developer’s Guide

Simple Payflow Transaction
Sale Transaction Example
NAME=Ruff & Johnson
COMMENT1=Level=5

To use special characters in the value of a name-value pair, use a length tag. The length tag
specifies the exact number of characters and spaces that appear in the value. The following
name-value pairs are valid.
NAME[14]=Ruff & Johnson
COMMENT1[7]=Level=5
N O T E : Quotation

marks (“ ”) are not allowed even if you use a length tag.

User Parameters
All Payflow Pro transactions require the user parameters described below.
TABLE 3.2 User parameters
Parameter

Description

USER

(Required) The ID provided to you by the authorized PayPal Reseller who registered you
for the Payflow SDK. If you purchased your account directly from PayPal, use PayPal.
Limitations: Sixty-four alphanumeric, case-sensitive characters.

VENDOR

(Required) Your merchant login ID that you created when you registered for the account.
Limitations: Sixty-four alphanumeric, case-sensitive characters.

PARTNER

PWD

(Required) The password that you defined while registering for the account.
Limitations: Six- to thirty-two alphanumeric, case-sensitive characters.

Sale Transaction Example
In addition to the connection and user parameters, each transaction type has additional
parameter requirements and can include a number of optional parameters as well. The
transaction parameters common to all processors are described in detail in Table 4.1 on
page 26.
To perform a credit card Sale transaction, you are required to pass the following parameters:
z

TRXTYPE - The type of the transaction, such as S for Sale

TENDER - The method of payment, such as C for credit card

ACCT - The buyer’s credit card number

AMT - The amount of the sale

EXPDATE - The expiration date of the credit card

Payflow Pro Developer’s Guide

Simple Payflow Transaction
Formatting Transactions

Typical Sale Transaction
The following is a typical request transaction string for a Sale transaction.
TRXTYPE=S&TENDER=C&USER=SuperMerchant&PWD=SuperUserPassword&PARTNER=PayPal&
ACCT=5105105105105100&EXPDATE=1209&AMT=99.06&COMMENT1=Reservation&FIRSTNAME
=John&LASTNAME=Jones&STREET=123 Main St.&CITY=San
Jose&STATE=CA&ZIP=123451234&COUNTRY=US&CVV2=123&CUSTIP=0.0.0.0

Note that, besides the required Sale transaction parameters, the above string includes other
Payflow Pro parameters typically included in a credit card Sale transaction request.
When the transaction completes, the Payflow server returns a response string made up of
name-value pair response parameters. If the transaction is successful, a RESULT value of 0 is
returned. The value of PNREF identifies the transaction in future requests, and RESPMSG is a
string indicating whether the transaction was approved. This is an example response to a credit
card Sale transaction request:
RESULT=0&PNREF=VXYZ01234567&RESPMSG=APPROVED&AVSADDR=Y&AVSZIP=N&IAVS=Y&CVV2
MATCH=Y

Formatting Transactions
For details on how to format a transaction based on the above information, see the examples
and the supporting documentation provided with your SDK.

Payflow Pro Developer’s Guide

Credit Card Transactions

This chapter describes how to plan for implementing credit card processing, presents the core
set of parameters used by all credit card processors, explains how to submit a transaction for
each transaction type supported, and describes other credit card features such as card security.

Credit Card Features
Payflow Pro supports the following transaction types for credit card processing:
z

Sale

Authorization (including Voice Authorization)

Delayed Capture

Credit

Void

Inquiry

Payflow Pro also supports the following credit card features:
z
z

Recharging to the same credit card (also called reference transactions)
Securing credit card transactions by means of the Address Verification Service and card
security code validation

About Credit Card Processing
Credit card processing occurs in two steps — a real-time Authorization and a capture
(settlement) of the funds that were authorized. As discussed below, you perform these two
steps either as a single transaction or as two transactions, depending on your business model
For an Authorization, the server sends the transaction information to a credit card processor
who routes the transaction through the financial networks to the cardholder’s issuing bank.
The issuing bank checks whether the card is valid, evaluates whether sufficient credit exists,
checks values such as address verification service and card security codes (discussed below),
and returns a response: Approved, Declined, Referral, or other response values.
You receive the response a few seconds after you submit the transaction to the server. If an
Authorization is approved, the bank temporarily reserves the credit for the amount of the
transaction to prepare to capture (fulfill) the transaction. The hold on funds typically lasts for
about a week.

Payflow Pro Developer’s Guide

Credit Card Transactions
About Credit Card Processing
N O T E : You

cannot remove a hold on funds through the processing networks—you must
contact the card issuing bank to lift a hold early.

Capturing a transaction actually transfers the funds to your bank. At least once a day, PayPal
gathers all transactions that are flagged to be settled and sends them in a batch file to the
processor. The processor then charges the issuing bank and transfers the funds to your bank. It
typically takes a few days before the money is actually available in your account, depending
on your bank.

Obtaining an Internet Merchant Account
To accept credit cards over the internet, you need a special account called an Internet Merchant
Account. Your account provider or merchant (acquiring) bank works with a PayPal-supported
credit card processor, such as First Data, TSYS Acquiring Solutions (formerly Vital
Processing Services), or Paymentech. To use Payflow Pro to accept live credit cards, you must
provide certain details about your account to PayPal during the “Go Live” part of the
enrollment process.
N O T E : An Internet Merchant Account is a different type of merchant account than a merchant

account used for face-to-face (in-person) retail transactions. It has additional risks
associated with card-not-present (e-commerce) transactions. You need to obtain an
Internet Merchant Account even if you already accept credit cards at your location.
To apply for an Internet Merchant Account, contact your merchant (acquiring) bank.

Planning Your Payflow Pro Integration
In designing your Payflow Pro integration, you should evaluate the following:
z

Whether to use a one-step or two-step transaction process. One-step: Submit a Sale
transaction, which performs the Authorization and (if successful) then flags the transaction
for settlement. Two-step: Perform an Authorization-only transaction and then later perform
a Delayed Capture transaction. The Delayed Capture transaction can be for the same
amount as the original transaction or for a lower amount. (In the case of a split shipment,
you can perform a Delayed Capture transaction for the initial shipment and a reference
transaction for the final payment. These transaction types, plus the details of performing a
Delayed Capture for an amount higher than the original, are described in “Delayed Capture
Transaction: Capturing Transactions for Higher Amounts” on page 31.
According to card association rules, most physical goods merchants should use a two-step
process, since settlement should occur when the goods are fulfilled or shipped. A two-step
process is also useful if you want to evaluate information in the response, such as whether
the issuer verifies the billing address, and so on. Electronic goods merchants, who fulfill
the order immediately, can use the one-step process. Check with your Internet Merchant
Account provider for suggestions on the best method for you.

Whether or how to use risk management tools such as address verification service and card
security code. For address verification service, if the data is submitted with the initial
transaction, the issuer checks the street address and/or the ZIP (postal) code against the

Payflow Pro Developer’s Guide

Credit Card Transactions
About Credit Card Processing

billing address on file for the consumer. Address verification service is described on page
“Using Address Verification Service” on page 42.
Card security code refers to a 3- or 4-digit number that appears on the back of most credit
cards. On American Express, the number appears above and to the right of the embossed
card number. Card security code is known by other names, such as CVV2, depending on
the type of card. If card security code data is submitted, the issuer can notify you whether
the number matches the number assigned to the card. Card security code is described on
page “Card Security Code Validation” on page 44.
It may also be possible to implement additional safeguards yourself or to use a fraud
service. You might want to discuss risk management with your Internet Merchant Account
provider.
z

Store information in your local database or use PayPal Manager reports to manage the data.
You may want to store shipping information in your system, or you may prefer to send the
information to PayPal with the transaction and report on it later.
N O T E : PayPal

recommends that you do not store credit card numbers. If you must store
numbers, encrypt and store them behind properly configured firewalls. You should
also consider whether and how to use the merchant-defined fields COMMENT1 and
COMMENT2 to help tie reports to your orders/customers or to report on other
information about the transaction.

If or how you want to integrate with other systems, such as order fulfillment, customer
service, and so on. You may wish to connect these systems directly to Payflow Pro for
capturing funds, issuing refunds/credits, and so on. Alternatively, you may prefer to
perform these steps manually using PayPal Manager. Either way, PayPal recommends that
you monitor transaction activity using PayPal Manager.
You may want to discuss, with your Internet Merchant Acquirer, practices that help you to
obtain the most advantageous rates.

Complying With the E-commerce Indicator (ECI)
Some processors support a software flag called E-commerce Indicator (ECI) that indicates that
the associated transaction is an internet transaction. Payflow Pro complies with ECI basic
requirements for all supported processors.
If you use the Buyer Authentication Service, then the ECI values reflects the Authentication
status. See Payflow Pro Fraud Protection Service User’s Guide on Developer Central.

Handling Credit Card Type Information
The Payflow SDK does not check the credit card types that you are accepting. If a customer
uses a card type that you are not signed up to accept, the Payflow SDK responds with RESULT
value 23, “Invalid account number,” or the processor returns a message that the customer is
not signed up for the card type. For details on RESULT values and response messages, see
“RESULT Values and RESPMSG Text” on page 56. Optionally, you can provide your

Payflow Pro Developer’s Guide

Credit Card Transactions
Parameters Used in Credit Card Transactions

customer with a list of the card types that you accept (in a drop-down list or menu, for
example).
To accept additional credit card types, you must contact your acquiring bank (the merchant
that holds your Internet Merchant Account) and ask them to add the card type to your account.
Upon notification from your Acquirer that you can start accepting the card type, you must add
the card to your Payflow Pro account through PayPal Manager. See PayPal Manager online
help for details.

Parameters Used in Credit Card Transactions
All credit card processors accept the basic parameters described in the table below with one
exception: the PayPal processor does not support SWIPE.
Some processors require additional parameters described in the following sections:
z

“Processors Requiring Additional Transaction Parameters” on page 65.

“Additional Reporting Parameters” on page 141

TABLE 4.1 Credit card transaction request parameters

Parameter

Description

ACCT

(Required for credit cards) Credit card or purchase card number. For the Pinless debit
TENDER type, ACCT can be the bank account number.
Limitations: This value may not contain spaces, non-numeric characters, or dashes.
For example, ACCT=5555555555554444

EXPDATE

(Required) Expiration date of the credit card.
Limitations: mmyy format. For example, 1008 represents November 2008.

AMT

(Required) Amount (Default: U.S. based currency).
Limitations: Specify the exact amount to the cent using a decimal point—use 34.00,
not 34. Do not include comma separators—use 1199.95 not 1,199.95. Your processor
and/or Internet Merchant Account provider may stipulate a maximum amount.
9 numeric characters plus decimal.

COMMENT1

(Optional) Merchant-defined value for reporting and auditing purposes.
Limitations: 128 alphanumeric characters.

COMMENT2

(Optional) Merchant-defined value for reporting and auditing purposes.
Limitations: 128 alphanumeric characters.

CVV2

(Optional) A code that is printed (not imprinted) on the back of a credit card. Used as
partial assurance that the card is in the buyer’s possession.
Limitations: 3 or 4 digits.

FIRSTNAME

(Optional) Account holder's first name.
Limitations: 30 alphanumeric characters.

Payflow Pro Developer’s Guide

Credit Card Transactions
Parameters Used in Credit Card Transactions
TABLE 4.1 Credit card transaction request parameters
Parameter

Description

LASTNAME

(Optional but recommended) Account holder's last name.
Limitations: 30 alphanumeric characters.

STREET

(Optional) The cardholder’s street address (number and street name).
The STREET address is verified by the address verification service.
Limitations: 30 alphanumeric characters.

SWIPE

(Required for card-present transactions only) Used to pass the Track 1 or Track 2 data
(card’s magnetic stripe information) for card-present transactions. Include either
Track 1 or Track 2 data—not both. If Track 1 is physically damaged, the point-of-sale
(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 20.
N O T E : SWIPE (card-present transactions) are not supported by the PayPal processor..

Limitations: Alphanumeric characters.
TENDER

(Required) The method of payment. Values are:
z A = Automated clearinghouse
z C = Credit card
z D = Pinless debit
z K = Telecheck
z P = PayPal
See the Payflow ACH Payment Service Guide for details on the Automated
clearinghouse tender type.

TRXTYPE

(Required) Indicates the type of transaction to perform. Values are:
z S = Sale transaction
z C = Credit
z A = Authorization
z D = Delayed Capture
z V = Void
z F = Voice Authorization
z I = Inquiry
z N = Duplicate transaction
N O T E : A type N transaction represents a duplicate transaction (version 4 SDK or

HTTPS interface only) with a PNREF the same as the original. It appears only
in the PayPal Manager user interface and will never settle.
ZIP

Payflow Pro Developer’s Guide

(Optional) Account holder’s 5- to 9-digit ZIP (postal) code.
Limitations: Nine characters maximum. Do not use spaces, dashes, or non-numeric
characters.

Credit Card Transactions
Submitting Sale Transactions

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 Authorization and a Delayed Capture transaction.
For details, see “Submitting Authorization/Delayed Capture Transactions” on page 29. 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.

Additional Parameters For Sale Transactions
To perform a Sale transaction, you are required to pass the following parameters:
z

ACCT

AMT

EXPDATE

N O T E : 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. The First Data Merchant Services (FDMS) South
processing platform supports Sale and Credit transactions only.

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&PA
RTNER=PayPal&ACCT=5105105105105100&EXPDATE=1209&CVV2=123&AMT=99.00&FIRSTNAM
E=John&LASTNAME=Smith&STREET=123 Main St.&CITY=San
Jose&STATE=CA&ZIP=12345&COMMENT1=Reservation&INVNUM=1234567890&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
transaction information. The customer’s street address (STREET) and ZIP should be passed to
use address verification service. CVV2 is needed for card security code validation. For details
on address verification service and card security code, see the following sections:

“Submitting Card-Present (SWIPE) Transactions” on page 41

“Card Security Code Validation” on page 44

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Authorization/Delayed Capture Transactions

Submitting Authorization/Delayed Capture Transactions
An Authorization (TRXTYPE=A) transaction places a hold on the cardholder’s open-to-buy
limit, lowering the cardholder’s limit by the amount of the transaction. It does not transfer
funds.
A Delayed Capture (TRXTYPE=D) transaction is performed after an Authorization to capture
the original Authorization amount. The Delayed Capture is scheduled for settlement during the
next settlement period.
Because Visa and MasterCard regulations prohibit capturing credit card transaction funds until
a product or service has shipped to the buyer, most processing networks implement an
Authorization transaction followed by a Delayed Capture transaction.

When To Use Authorization/Delayed Capture Transactions
If your business does not provide immediate fulfillment of products or services, you should
use this two-stage transaction solution, also known as Delayed Capture processing, because it
enables you to capture credit card transaction funds when your are ready to collect them.
N O T E : If you signed up for the PayPal processor with Fraud Protection Services, you must use

delayed capture processing for all sale transactions.
If your business provides immediate fulfillment and you are not using the PayPal processor
with Fraud Protection Services, you can use a simple Sale transaction instead. For details, see
“Submitting Sale Transactions” on page 28. 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. For details, see “Submitting Authorization/Delayed Capture
Transactions” on page 29.
IMPO RTANT: Only

one Delayed Capture transaction is allowed per Authorization
transaction.

Required Authorization Transaction Parameters
To perform an Authorization transaction, you are required to pass the following parameters:
z

ACCT

AMT

EXPDATE

Typical Authorization Transaction Parameter String
A typical parameter string passed in an Authorization transaction is the same as a Sale
transaction string. The only difference is that the TRXTYPE value is A in an Authorization.

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Authorization/Delayed Capture Transactions
TRXTYPE=A&TENDER=C&USER=SuperUser&PWD=SuperUserPassword&VENDOR=SuperUser&PA
RTNER=PayPal&ACCT=5105105105105100&EXPDATE=1209&CVV2=123&AMT=99.00&
FIRSTNAME=John&LASTNAME=Smith&STREET=123 Main St.&CITY=San Jose
&STATE=CA&ZIP=12345&COMMENT1=Reservation&INVNUM=1234567890&PONUM=C12345&CVV
2=567&VERBOSITY=MEDIUM

Required Delayed Capture Transaction Parameters
To perform a Delayed Capture transaction, you are required to pass the following parameter:
ORIGID
TABLE 4.2 Delayed Capture required parameter
Parameter

Description

ORIGID

(Required by some transaction types) ID of the original transaction that is being
referenced. This ID is returned by the PNREF parameter and appears as the
Transaction ID in PayPal Manager reports.
Limitations: 12 case-sensitive alphanumeric characters.

Set ORIGID to the PNREF (Transaction ID in PayPal Manager reports) value returned from the
original transaction. In addition, if the amount of the capture differs from the amount of the
Authorization, you also must pass a value for AMT.
Fields Copied From the Authorization Transaction into the Delayed Capture
Transaction

The following fields are copied from the Authorization transaction into the Delayed Capture
transaction (if they exist in the original transaction). If you provide a new value for any of
these parameters when submitting the Delayed Capture transaction, then the new value is
used. (Exceptions are ACCT, EXPDATE, and SWIPE. These parameters retain their original
values.)
TABLE 4.3 Fields copied from Authorization to Delayed Capture transaction
ACCT

AMT

CITY

COMMENT1

COMMENT2

COMPANYNAME

BILLTOCOUNTRY

CUSTCODE

CUSTIP

DUTYAMT

EXPDATE

FIRSTNAME

MIDDLENAME

LASTNAME

FREIGHTAMT

INVNUM

PONUM

SHIPTOCITY

SHIPTOCOUNTRY

SHIPTOFIRSTNAME

SHIPTOMIDDLENAME

SHIPTOLASTNAME

SHIPTOSTATE

SHIPTOSTREET

SHIPTOZIP

STATE

STREET

SWIPE

TAXAMT

PHONENUM

TAXEXEMPT

ZIP

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Authorization/Delayed Capture Transactions

To perform the Delayed Capture:
1. Perform the Authorization transaction.
The Authorization transaction uses the same parameters as Sale transactions, except that
the transaction type is A.
The return data for an Authorization transaction is the same as for a Sale transaction. To
capture the authorized funds, perform a Delayed Capture transaction that includes the value
returned for PNREF, as described in Step 2 below.
Example: Authorization-only Transaction
TRXTYPE=A&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=SuperMerchant&USER=S
uperMerchant&ACCT=5555555555554444&EXPDATE=0308&AMT=123.00&COMMENT1=Seco
nd purchase&COMMENT2=Low risk customer&INVNUM=123456789&STREET=5199
MAPLE&ZIP=94588

Example:Authorization Response
RESULT=0&PNREF=VXYZ01234567&RESPMSG=APPROVED&AUTHCODE=123456
&AVSADDR=Y&AVSZIP=N

2. Perform the Delayed Capture transaction.
Set ORIGID to the PNREF value returned in the original Authorization transaction response
string. (There is no need to retransmit the credit card or billing address information—it is
stored at PayPal.)
If the capture succeeds, the amount of the Capture is transferred to the merchant’s account
during the daily settlement process. If the capture does not succeed, the hold on the
cardholder’s open-to-buy is still in effect.
Example:Delayed Capture Transaction
TRXTYPE=D&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=.SuperMerchant
&USER=SuperMerchant&ORIGID=VXYZ00887892

Example:Delayed Capture Response
RESULT=0&PNREF=VXYZ00895642&AUTHCODE=25TEST&AVSADDR=Y&AVSZIP=N

Delayed Capture Transaction: Capturing Transactions for Lower Amounts
You can perform a Delayed Capture transaction for an amount lower than the original
Authorization amount (useful, for example, when you make a partial shipment).

Delayed Capture Transaction: Capturing Transactions for Higher Amounts
You can perform a Delayed Capture transaction for an amount higher than the original
Authorization amount. The cardholder’s open-to-buy could be reduced by the sum of the
original Authorization-only amount and the final Delayed Capture amount.

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Voice Authorization Transactions

Delayed Capture Transaction: Error Handling and Retransmittal
If an error occurs while processing a Delayed Capture transaction, it is safe to retry the capture
with values that allow the Payflow server to successfully process it. Conversely, if a capture
for a previous Authorization succeeds, subsequent attempts to capture it again will return an
error.

Submitting Voice Authorization Transactions
A Voice Authorization (TRXTYPE=F) transaction is a transaction that is authorized over the
telephone from the processing network.
N O T E : The

PayPal processor does not support Voice Authorization transactions.

When to Use a Voice Authorization Transaction
Some transactions cannot be authorized over the internet (for example, high dollar amounts)
and require manual authorization. These transactions generate RESULT value 13 and are called
Referral transactions.
In these situations, you contact the customer service department of your merchant bank and
provide the payment information as requested. If the transaction is approved, the bank
provides you with a voice Authorization code (AUTHCODE) for the transaction. .
Once a Voice Authorization transaction has been approved, it is treated like a Sale transaction
and is settled with no further action on your part.
Like Sale transactions, approved Voice Authorization transactions can be voided before
settlement occurs.

Required Voice Authorization Transaction Parameters
When sending a Voice Authorization transaction request, you are required to include the
AUTHCODE provided by your merchant bank.
TABLE 4.4 Voice Authorization transaction required parameter
Parameter

Description

AUTHCODE

(Required for Voice Authorizations only) Returned only for approved Voice
Authorization transactions. AUTHCODE is the approval code obtained over the
telephone from the processing network.
Limitations: Six alphanumeric characters.

The following is an example Voice Authorization transaction request parameter string:
TRXTYPE=F&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&P
WD=x1y2z3&AUTHCODE=AB34RT56&ACCT=5555555555554444&EXPDATE=0308&AMT=123.00

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Credit Transactions

Submitting Credit Transactions
The Credit transaction (TRXTYPE=C) refunds the specified amount to the cardholder.

Required Credit Transaction Parameters
The required parameter data for a Credit transaction depends on the Allow non-referenced
credits security setting for your Payflow Pro account. A non-referenced credit is a Credit
transaction that does not use the credit card information from an existing transaction. Credit
card information must be supplied. As an example, Sally Smith calls you on the telephone to
cancel an order from your business. To refund her money, you credit her credit card by
submitting a non-referenced Credit transaction.
Guidelines and parameter requirements for Credit transactions differ depending on whether or
not non-referenced credits are allowed.
Non-Referenced Credits Not Allowed

When non-referenced credits are not allowed (the setting recommended by PayPal), then
Credit transactions are permitted only against existing Sale, Delayed Capture, and Voice
Authorization transactions. To submit a Credit transaction when non-referenced credits are not
allowed, you must pass the following parameter:
ORIGID
TABLE 4.5 Credit required parameter
Parameter

Description

ORIGID

Set the value of ORIGID to the PNREF value returned for the original transaction. (PNREF is
displayed as the Transaction ID in PayPal Manager reports.) If you do not specify an amount,
then the amount of the original transaction is credited to the cardholder.
Non-Referenced Credits Allowed

When non-referenced credits are allowed, then Credit transactions are permitted in any
amount up to the transaction limit for the credit card account that you specify. To submit a
Credit transaction when non-referenced credits are allowed, you must pass values for the
following parameters:
z

ACCT

EXPDATE

AMT

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Credit Transactions
IMPO RTANT: The

default security setting for Payflow Pro accounts is Allow
non-referenced credits = No, so sending the ORIGID is the preferred method
for performing Credit transactions. Using the ACCT, EXPDATE, or AMT
parameters for such accounts leads to RESULT value 117 (failed the security
check). For information on setting the security settings, see PayPal Manager
online help.

Fields Copied From the Original Transaction into the Credit Transaction

The following fields are copied from the original transaction into the Credit transaction (if
they exist in the original transaction). If you provide a new value for any of these parameters
when submitting the Credit transaction, then the new value is used. (Exceptions are ACCT,
EXPDATE, and SWIPE. These parameters retain their original values).
N O T E : These

fields are not copied for referenced credits: TAXAMT, TAXEXEMPT, DUTYAMT,
FREIGHTAMT, and (for American Express only) DESC4.

N O T E : For

processors that use the RECURRING parameter: If the RECURRING parameter was
set to Y for the original transaction, then the setting is ignored when forming the Credit
transaction.

TABLE 4.6 Fields copied from original to Credit transaction
ACCT

AMT

CITY

COMMENT1

COMMENT2

COMPANYNAME

BILLTOCOUNTRY

CUSTCODE

CUSTIP

EXPDATE

FIRSTNAME

MIDDLENAME

LASTNAME

INVNUM

PONUM

SHIPTOCITY

SHIPTOCOUNTRY

SHIPTOFIRSTNAME

SHIPTOMIDDLENAME

SHIPTOLASTNAME

SHIPTOSTREET

SHIPTOSTATE

SHIPTOZIP

STATE

STREET

SWIPE

PHONENUM

ZIP

Credit Transaction Parameter Strings
This is an example Credit transaction string (non-referenced credits not allowed):
TRXTYPE=C&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&P
WD=x1y2z3&ORIGID=VPNE12564395

This is an example Credit transaction string (non-referenced credits allowed):
TRXTYPE=C&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&P
WD=x1y2z3&ACCT=5555555555554444&EXPDATE=0308&AMT=123.00

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Void Transactions

Submitting Void Transactions
The Void transaction (TRXTYPE=V) prevents a transaction from being settled.
As part of its internal process, PayPal makes reasonable effort to process authorization
reversals for void transactions for debit and credit cards. Because the honoring of
authorization reversals is ultimately decided by the bank or issuer, there is no accurate way to
determine if an individual bank or issuer has honored an authorization reversal request.
N O T E : For

more information on authorization reversals, see
http://en.wikipedia.org/wiki/Authorization_hold.

For information on authorization reversals related to the Paymentech New Hampshire and
FDMS North processors, see “Processors Requiring Additional Transaction Parameters” on
page 65.

When To Use a Void Transaction
Follow these guidelines:
z

You can void Delayed Capture, Sale, Credit, Authorization, and Voice Authorization
transactions. You cannot void a Void transaction.
You can only use a Void transaction on a transaction that has not yet settled. To refund a
customer’s money for a settled transaction, you must submit a Credit transaction.

Required Void Transaction Parameters
To submit a Void transaction, you must pass the following parameter:
ORIGID
TABLE 4.7 Void required parameter
Parameter

Description

ORIGID

Set ORIGID to the PNREF (Transaction ID in PayPal Manager reports) value returned for the
original transaction.
Fields Copied From the Original Transaction into the Void Transaction

The following fields are copied from the original transaction into the Void transaction (if they
exist in the original transaction). If you provide a new value for any of these parameters when
submitting the Void transaction, then the new value is used. (Exceptions are ACCT, EXPDATE,
and SWIPE. These parameters retain their original values).

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Inquiry Transactions
N O T E : For

processors that use the RECURRING parameter: If the RECURRING parameter was
set to Y for the original transaction, then the setting is ignored when forming the Void
transaction.

TABLE 4.8 Fields copied from original Void transaction
ACCT

AMT

CITY

COMMENT1

COMMENT2

COMPANYNAME

BILLTOCOUNTRY

CUSTCODE

CUSTIP

DUTYAMT

EXPDATE

FIRSTNAME

MIDDLENAME

LASTNAME

FREIGHTAMT

INVNUM

PONUM

SHIPTOCITY

SHIPTOCOUNTRY

SHIPTOFIRSTNAME

SHIPTOMIDDLENAME

SHIPTOLASTNAME

SHIPTOSTATE

SHIPTOSTREET

SHIPTOZIP

STATE

STREET

SWIPE

TAXAMT

PHONENUM

TAXEXEMPT

ZIP

Example Void Transaction Parameter String
This is an example Void transaction parameter string:
“TRXTYPE=V&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&
PWD=x1y2z3&ORIGID=VPNE12564395”

Submitting Inquiry Transactions
An Inquiry transaction (TRXTYPE=I) returns the result and status of a transaction.

When To Use an Inquiry Transaction
You perform an inquiry using a reference to an original transaction—either the PNREF value
returned for the original transaction or the CUSTREF value that you specified for the original
transaction.
While the amount of information returned in an Inquiry transaction depends upon the
VERBOSITY setting, Inquiry responses mimic the verbosity level of the original transaction as
much as possible. For details on VERBOSITY, see “VERBOSITY: Viewing Processor-Specific
Transaction Results” on page 135.

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Inquiry Transactions

Required Parameters When Using the PNREF
To submit an Inquiry transaction when using the PNREF, you must pass the following
parameter:
ORIGID
TABLE 4.9 Inquiry request required parameter when using the PNREF
Parameter

Description

ORIGID

(Required by some transaction types) ID of the original transaction that is being
referenced. This ID is returned by the PNREF parameter.
Limitations: 12 case-sensitive alphanumeric characters.

Set ORIGID to the PNREF (Transaction ID in PayPal Manager reports) value returned for the
original transaction.

Inquiry Transaction Parameter String Using the PNREF
This is an example Inquiry transaction parameter string using the ORIGID parameter set to the
PNREF value:
TRXTYPE=I&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant
&USER=SuperMerchant&PWD=x1y2z3&ORIGID=VPNE12564395

Required Parameters When Using the CUSTREF
To submit an Inquiry transaction when using the CUSTREF, you must pass the following
parameter:
CUSTREF
Optionally, specify the STARTTIME and ENDTIME parameters. The Inquiry transaction request
parameters are described below.
TABLE 4.10 Inquiry transaction request parameters when using the CUSTREF
Parameter

Description

CUSTREF

(Required) Merchant-defined identifier for reporting and auditing purposes. For
example, you can set CUSTREF to the invoice number.
You can use CUSTREF when performing Inquiry transactions. To ensure that you
can always access the correct transaction when performing an Inquiry, you must
provide a unique CUSTREF when submitting any transaction, including retries.
Limitations: 12 alphanumeric characters.

Payflow Pro Developer’s Guide

Credit Card Transactions
Recharging to the Same Credit Card (Reference Transactions)
TABLE 4.10 Inquiry transaction request parameters when using the CUSTREF
Parameter

Description

STARTTIME

(Optional) For Inquiry transactions when using CUSTREF to specify the
transaction.
ENDTIME specifies the end of the time period during which the transaction
specified by the CUSTREF occurred. See STARTTIME.
ENDTIME must be less than 30 days after STARTTIME. An inquiry cannot be
performed across a date range greater than 30 days.
If you set ENDTIME, and not STARTTIME, then STARTTIME is defaulted to 30 days
before ENDTIME.
If neither STARTTIME nor ENDTIME is specified, then the system searches the last
30 days.
Limitations: 14 numeric characters in the format yyyymmddhhmmss.

ENDTIME

there are multiple transactions with a particular CUSTREF value, then the
Inquiry transaction returns only the last transaction with the specified
CUSTREF. So, to ensure that you can always access the correct transaction,
you must use a unique CUSTREF when submitting any transaction, including
retries.

Inquiry Transaction Parameter String Using the CUSTREF
This is an example Inquiry transaction parameter string using the CUSTREF:
TRXTYPE=I&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&P
WD=x1y2z3&CUSTREF=Inv00012345

Recharging to the Same Credit Card (Reference Transactions)
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 reference transaction. A reference transaction takes the
existing credit card information that is on file and reuses it.

When To Use a Reference Transaction
Say that Joe Smith purchases a holiday gift from your web site store and requests that it be sent
by UPS ground service. That evening, Joe becomes concerned that the item might not arrive in
time for the holiday. So he calls you to upgrade shipping to second-day air. You obtain his

Payflow Pro Developer’s Guide

Credit Card Transactions
Recharging to the Same Credit Card (Reference Transactions)

approval for charging an extra $10 for the upgrade. In this situation, you can create a reference
transaction based on the original Authorization and charge an additional $10 to Joe’s credit
card without having to ask him again for his credit card information.
IMPO RTANT: As a security measure, reference transactions are disallowed by default. Only

your account administrator can enable reference transactions for your
account. If you attempt to perform a reference transaction in an account for
which reference transactions are disallowed, RESULT value 117 is returned.
See PayPal Manager online help for instructions on setting reference
transactions and other security features.
Sale and Authorization transactions can make use of a reference transaction as a source of
transaction data. PayPal looks up the reference transaction and copies its transaction data into
the new Sale or Authorization transaction. With the exception of dollar amount data, which
triggers a filter if out of range, reference transactions are not screened by Fraud Protection
Services filters.
IMPO RTANT: When PayPal looks up the reference transaction, neither the transaction being

referenced nor any other transaction in the database is changed in any way.
That is, a reference transaction is a read-only operation—only the new
transaction is populated with data and acted upon. No linkage is maintained
between the reference transaction and the new transaction.
You can also initiate reference transactions from PayPal Manager. See PayPal Manager online
help for details.

Transaction Types that Can Be Used as the Original Transaction
You can reference the following transaction types to supply data for a new Sale or
Authorization transaction:
z

Authorization (To capture the funds for an approved Authorization transaction, be sure to
perform a Delayed Capture transaction—not a Reference transaction.)

Credit

Delayed Capture

Sale

Voice Authorization (The Voice Authorization code is not copied to the new transaction)

Void

Payflow Pro Developer’s Guide

Credit Card Transactions
Recharging to the Same Credit Card (Reference Transactions)

Fields Copied From Reference Transactions
The following fields are copied from the reference transaction into the new Sale or
Authorization transaction (if they exist in the original transaction). If you provide a value for
any of these parameters when submitting the new transaction, then the new value is used.
TABLE 4.11 Fields copied from reference transactions
ACCTTYPE

STREET

ACCT

CITY

EXPDATE

STATE

FIRSTNAME

ZIP

MIDDLENAME

BILLTOCOUNTRY

LASTNAME

SWIPE

Example Reference Transaction
In this example, you authorize an amount of $100 for a shipment and charge $66 for the first
partial shipment using a normal Delayed Capture transaction. You charge the $34 for the final
part of the shipment using a reference transaction to draw credit card and shipping address
information from the initial Authorization transaction.
This example procedure creates a reference transaction:
1. Submit the initial transaction, such as an Authorization.
You use an Authorization transaction for the full amount of the purchase of $100 as shown
in this transaction request:
TRXTYPE=A&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=SuperMerchant&USER=S
uperMerchant&ACCT=5555555555554444&EXPDATE=0308&AMT=100.00&INVNUM=123456
789&STREET=5199 MAPLE&ZIP=94588

Note the value of the PNREF in the response:
RESULT=0&PNREF=VXYZ01234567&RESPMSG=APPROVED&AUTHCODE=123456&AVSADDR=Y&A
VSZIP=N

2. Capture the authorized funds for a partial shipment of $66.
When you deliver the first $66 worth of product, you use a normal Delayed Capture
transaction to collect the $66. Set ORIGID to the value of PNREF in the original
Authorization as in this transaction request (See “Required Delayed Capture Transaction
Parameters” on page 30):
TRXTYPE=D&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=SuperMerchant&USER=S
uperMerchant&ORIGID=VXYZ01234567&AMT=66.00

This is the response:
RESULT=0&PNREF=VXYZ01234568&AUTHCODE=25TEST&AVSADDR=Y&AVSZIP=N

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Card-Present (SWIPE) Transactions

3. Submit a new Sale transaction or Authorization/Delayed Capture transaction of $34 for the
rest of the shipment.
Once you have shipped the remainder of the product, you can collect the remaining $34 in
a Sale transaction that uses the initial Authorization as a reference transaction. (This is a
Sale transaction because only one Delayed Capture transaction is allowed per
Authorization.) This is the Sale transaction request:
TRXTYPE=S&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=SuperMerchant&USER=S
uperMerchant&ORIGID=VXYZ01234567&AMT=34.00

This is the response:
RESULT=0&PNREF=VXYZ01234569&AUTHCODE=25TEST&AVSADDR=Y&AVSZIP=N

Submitting Card-Present (SWIPE) Transactions
Payflow Pro supports card-present transactions (face-to-face purchases).
N O T E : SWIPE (card-present) transactions are not supported by the PayPal processor.

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.
Contact PayPal Customer Service to request having your account set up properly for
accepting and passing swipe data.
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.
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:
z

American Express Phoenix

First Data Merchant Services (FDMS) Nashville

First Data Merchant Services (FDMS) North

First Data Merchant Services (FDMS) South

Global Payments Central

Global Payments East

Merchant e-Solutionss

Elavon (Formerly Nova)

Payflow Pro Developer’s Guide

Credit Card Transactions
Submitting Purchasing Card Transactions

Paymentech Salem (New Hampshire)

Paymentech Tampa

TSYS Acquiring Solutions

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 20. 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.
This is an example card-present transaction parameter string:
“TRXTYPE=S&TENDER=C&PARTNER=PayPal&USER=SuperMerchant&PWD=SuperMerchant&SWI
PE[40]=;4912000033330026=15121011000012345678?&AMT=21.00”

Submitting Purchasing Card Transactions
A purchasing card (also referred to as a commercial card, corporate card, procurement card or
business card) is a credit card that is issued at the request of an employer. It is usually reserved
for business-related charges. The card issuer provides specialized reporting for this card type
so the employer can monitor the use of the card. There is no method for determining whether a
card is a purchase card or a commercial card based on the card number.
To obtain the best bank interchange rates for commercial cards, you must pass specific
additional transaction information. Commercial card support and parameters vary from
processor to processor. See“Submitting Purchasing Card Level 2 and Level 3 Transactions” on
page 97.
N O T E : Purchasing

card transactions are not supported by the PayPal processor.

Using Address Verification Service
To qualify for the lowest bank rate, you must pass address verification service information—
street address and ZIP (postal) code.

Payflow Pro Developer’s Guide

Credit Card Transactions
Processing Platforms Supporting Address Verification Service

Address verification service compares the submitted billing street address and ZIP code with
the values on file at the cardholder’s bank. The response includes values for AVSADDR and
AVSZIP: Y, N, or X for the match status of the customer’s street address and ZIP code.
Y = match, N = no match, X = cardholder’s bank does not support address verification service.
The address verification service result is for advice only. Banks do not decline transactions
based on the address verification service result—the merchant makes the decision to approve
or decline a transaction. Address verification service is supported by most US banks and some
international banks.
N O T E : Address

verification service checks only for a street number match, not a street name
match, so 123 Main Street returns the same response as 123 Elm Street.

The international address verification service (IAVS) response indicates whether address
verification service response is international (Y), USA (N), or cannot be determined (X).

Processing Platforms Supporting Address Verification Service

TABLE 4.12 Processing platforms supporting Address Verification Service
Processing Platform

American
Express

Discover

Master Card

Visa

American Express Phoenix

—

American Express Brighton

—

FDMS Nashville

FDMS North

FDMS South

Global Payments Central

Global Payments East

Merchant e-Solutions

Elavon (formerly Nova)

Paymentech Salem (New
Hampshire)

Paymentech Tampa

TSYS Acquiring Solutions
(formerly Vital Processing
Services)

See your processor’s information in “Processors Requiring Additional Transaction
Parameters” on page 65 for information on their handling of address verification service.
Payflow Pro Developer’s Guide

Credit Card Transactions
Example Address Verification Service Request Parameter List

Example Address Verification Service Request Parameter List
This example request include the address verification service request parameters STREET and
ZIP:
TRXTYPE=A&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=SuperMerchant&USER=Supe
rMerchant&&ACCT=5555555555554444&EXPDATE=0308&AMT=123.00&STREET=5199
Maple&ZIP=98765

Example Address Verification Service Response
In this example, the address value matches the value in the bank’s records, but the ZIP code
does not. The AVSZIP response is N.
RESULT=0&PNREF=VXW412345678&RESPMSG=APPROVED&AUTHCODE=123456&AVSADDR=Y&AVSZ
IP=N&IAVS=X

Card Security Code Validation
The card security code is a 3- or 4-digit number (not part of the credit card number) that is
printed on the credit card. Because the card security code appears only on the card and not on
receipts or statements, the card security code provides some assurance that the physical card is
in the possession of the buyer.
This fraud prevention tool has various names, depending on the payment network. Visa calls it
CVV2 and MasterCard calls it CVC2. To ensure that your customers see a consistent name,
PayPal recommends use of the term card security code on all end-user materials.
IMPO RTANT: To

comply with credit card association regulations, do not store the CVV2
value.

On most cards, the card security code is printed on the back of the card (usually in the
signature field). All or part of the card number appears before the card security code (567 in
the example). For American Express, the 4-digit number (1122 in the example) is printed on
the front of the card, above and to the right of the embossed account number. Be sure to
explain this to your customers.

Payflow Pro Developer’s Guide

Credit Card Transactions
Card Security Code Validation
FIGURE 4.1 Card security code

Processing Platforms and Credit Cards Supporting Card Security Code
N O T E : You

need to contact American Express to be set up to accept their CID card security
code.

TABLE 4.13 Processing platforms supporting card security code
Processing Platform

American
Express

Discover

Master Card

Visa

American Express Phoenix

—

American Express Brighton

—

FDMS Nashville

FDMS North

FDMS South

Global Payments Central

Global Payments East

Merchant e-Solutions

Elavon (formerly Nova)

Paymentech Salem (New
Hampshire)

Paymentech Tampa

TSYS Acquiring Solutions
(formerly Vital Processing
Services)

Payflow Pro Developer’s Guide

Credit Card Transactions
Card Security Code Validation

Payflow Pro Developer’s Guide

Credit Card Testing

To test your application, direct all transactions to the host address for testing. For details, see
“Host Addresses” on page 13. Transactions directed to this URL are processed through
PayPal’s simulated payment network, enabling you to test the configuration and operation of
your application or storefront — no money changes hands. (You must activate your account
and configure your application for live transactions before accepting real orders.)

Testing Guidelines
The following are testing guidelines:
z

z
z

While testing, use only the credit card numbers listed in this chapter. Other numbers
produce an error.
Expiration Date must be a valid date in the future (use the mmyy format).
To view the credit card processor that you have selected for testing, see Account Info >
Processor Info in PayPal Manager.

Credit Card Numbers Used for Testing
Use the following credit card numbers for testing. Any other card number produces a general
failure.
TABLE 5.1 Test credit card numbers
American Express

378282246310005

American Express

371449635398431

American Express Corporate

378734493671000

Diners Club

30569309025904

Diners Club

38520000023237

Discover

6011111111111117

Discover

6011000990139424

JCB

3530111333300000

JCB

3566002020360505

MasterCard

5555555555554444

Payflow Pro Developer’s Guide

Credit Card Testing
Result Values in Responses
TABLE 5.1 Test credit card numbers
MasterCard

5105105105105100

Visa

4111111111111111

Visa

4012888888881881

Visa

4222222222222
N O T E : Even though this number has a different character count than the

other test numbers, it is the correct and functional number.

Result Values in Responses
This section describes the result value responses that you receive.

Testing Result Values in Responses
You can use the amount of the transaction to generate a particular result value. The table below
lists the general guidelines for specifying amounts to submit in requests.
TABLE 5.2 Results generated by the amount submitted
Amount

Result

$0 – $1000

RESULT value 0 (Approved)

$1001 – $2000

Certain amounts in this range will return specific PayPal results, and can be generated
by adding $1000 to that RESULT value. For example, for RESULT value 13 (Referral),
submit the amount 1013.
If the amount is in this range but does not correspond to a PayPal result supported by
this testing mechanism, RESULT value 12 (Declined) is returned

$2001+

RESULT value 12 (Declined)

RESULT Values Returned Based on Transaction Amount
This table lists the RESULT values that you can generate using the amount of the transaction.
To generate a specific code, submit an amount of 1000 plus the code number (for example,
submit an amount of 1013 for a result code of 13).
TABLE 5.3 Result values supporting the amount control

Processing Platform

RESULT Values Available for Testing

American Express Phoenix
American Express Brighton

0, 12, 13, 104, 1000

Payflow Pro Developer’s Guide

Credit Card Testing
RESULT Values Returned Based on Transaction Amount
TABLE 5.3 Result values supporting the amount control
Processing Platform

RESULT Values Available for Testing

Elavon (Formerly Nova)

0, 12, 13, 104

First Data Merchant Services Nashville

0, 12, 13, 104

First Data Merchant Services North

0, 4, 5, 12, 13, 23, 24,114, 1000

First Data Merchant Services South

0, 12, 13, 104

Global Payments Central

0, 4, 5, 8, 12, 13, 23, 24, 104, 111, 114, 1000

Global Payments East

0, 4, 5, 12, 13, 23, 24, 30, 100, 104, 114, 1000

Paymentech Salem (New Hampshire)

0, 12, 13, 104

Paymentech Tampa

0, 3, 4, 5, 12, 13, 23, 24, 1000

TSYS Acquiring Solutions (Formerly Vital Processing
Services)

0, 4, 12, 13, 23, 104, 114, 1000

Alternative Methods for Generating Specific RESULT Values
The table below shows another method for obtaining RESULT values. Non-zero RESULT
values from processors are not returned by the servers, and therefore cannot be simulated
using the amount. In some cases, you may get certain results using the RESULT value plus
1000 even though this table suggests another means of obtaining the RESULT value.
TABLE 5.4 Obtaining RESULT value
RESULT

Definition

How to test using Payflow Pro

Approved

Use an AMOUNT of $1000 or less
For all Processors except Global Payments Central (MAPP) and FDI
Credit (C) and Force (F) transactions will always be approved
regardless of dollar amount or card number

User authentication failed

Use an invalid PWD

Invalid tender

Use an invalid TENDER, such as G

Invalid transaction type

Use an invalid TRXTYPE, such as G

Invalid amount

Use an invalid AMOUNT, such as –1

Invalid merchant
information

Use the AMOUNT 1005 - Applies only to the following processors:
Global Payments East and Central, and American Express

Field format error

Submit a Delayed Capture transaction with no ORIGID

Declined

Use the AMOUNT 1012 or an AMOUNT of 2001 or more

Referral

Use the AMOUNT 1013

Payflow Pro Developer’s Guide

Credit Card Testing
RESULT Values Returned Based on Transaction Amount
TABLE 5.4 Obtaining RESULT value

RESULT

Definition

How to test using Payflow Pro

Original transaction ID not
found

Submit a Delayed Capture transaction with an invalid ORIGID

Invalid ABA number

Applies only to ACH transactions – submit an invalid ABA number
(8 digits)

Invalid account number

Submit an invalid account number, for example,
000000000000000

Invalid expiration date

Submit an invalid expiration date, for example, 0298

Transaction type not
mapped to this host
(Processor)

Submit a transaction for a card or tender you are not currently set up
to accept, for example, a Diners card if you aren’t set up to accept
Diners

Invalid XML document

Pass a bad XML document (XMLPay users only)

Duplicate Transaction

Use the AMOUNT 1030 - Only applies to Global Payments East and
Central processors

Insufficient funds available

Use the AMOUNT 1050 - Only applies to Paymentech

General error

Use the AMOUNT 1099 - Only applies to Global Payments East

100

Invalid transaction returned
from host (Processor)

Use the AMOUNT 1100. Only applies to Global Payments East and
Central

101

Time-out value too small

Set timeout value to 1

103

Error reading response from
host (Processor)

Use the AMOUNT 1103

104

Timeout waiting for
processor response

Use the AMOUNT 1104

105

Credit error

Attempt to credit an authorization

108

Void error

Attempt to void a captured authorization

111

Capture error

Capture an Authorization transaction twice or attempt to capture a
transaction that is not an Authorization transaction

112

Failed AVS check

You cannot generate this RESULT value by submitting an amount of
1112, but must submit a value for Address Verification Servicethat
will fail In production, this error occurs only if your account is
configured by PayPal customer service to use the “AVS Deny”
feature

113

Cannot exceed sales cap

Applies to ACH transactions only

114

CVV2 Mismatch

Use the AMOUNT 1114. Only applies to TSYS Acquiring Solutions,
Merchant e-Solutions, and Global Payments East and Central
processors

Payflow Pro Developer’s Guide

Credit Card Testing
Testing Address Verification Service
TABLE 5.4 Obtaining RESULT value
RESULT

Definition

How to test using Payflow Pro

1000

Generic Host (Processor)
Error

Use the AMOUNT 2000 - Does not apply to Elavon (formerly Nova),
American Express, or Global Payments East processors

Testing Address Verification Service
The Payflow testing server simulates Address Verification Service by returning a value for
AVSADDR based on the first three characters of the submitted value for STREET.
The testing server returns a value for AVSZIP based on the submitted ZIP value as shown in
the table.
If STREET starts with 667 or higher or begins with a non-numeric character, then the simulator
returns AVSADDR=X, AVSZIP=X.
TABLE 5.5 Testing AVSADDR
Submitted Value for STREET

Example STREET Value

AVSADDR Result

000-333

24285 Elm

334-666

49354 Main

667 or higher or begins with a non-numeric
character

79232 Maple

Submitted Value for ZIP

Example ZIP Value

AVSZIP Result

00000-50000

00382

50001-99999

94303

Any value (if street address is 667 or higher or
begins with a non-numeric character)

STREET=79232 Maple, ZIP=20304

TABLE 5.6 Testing AVSZIP

Testing Card Security Code
If you submit a value for the card security code, the cardholder’s bank returns a
Yes / No / Not Supported (Y / N / X) response on whether the value matches the number on
file at the bank. Card security code is described in “Card Security Code Validation” on
page 44.
N O T E : Some processors will decline (RESULT value 12) a transaction if the card security code

does not match without returning a CVV2MATCH value. Test the results and check with
your processor to determine whether they support card security code checking.

Payflow Pro Developer’s Guide

Credit Card Testing
Testing Address Verification Service

For the testing server, the first three characters of the CVV2 value determine the CVV2MATCH
result, as shown here.
TABLE 5.7 Testing CVV2MATCH

CVV2 Value

CVV2MATCH Value

000

Null

001-300

301-600

601 or higher

Payflow Pro Developer’s Guide

Responses to Transaction
Requests
When a transaction finishes, the Payflow server returns a response string made up of namevalue pairs. This is an example response string.
RESULT=0&PNREF=EFHP0D426A53&RESPMSG=APPROVED&AUTHCODE=25TEST&AVSADDR=Y&AVSZ
IP=N&CVV2MATCH=Y

Contents of a Response to a Credit Card Transaction Request
Table 6.1 describes values that can be returned in response strings.
TABLE 6.1

Transaction response values

Field

Description

Type

Length

PNREF

Payflow Transaction ID, a unique number that
identifies the transaction. PNREF is described in
“PNREF Format” on page 56.

Alphanumeric

RESULT

The outcome of the attempted transaction. A
result of 0 (zero) indicates the transaction was
approved. Any other number indicates a decline
or error. RESULT values are described in
“RESULT Values and RESPMSG Text” on
page 56.

Numeric

Variable

CVV2MATCH

Result of the card security code (CVV2) check.
The issuing bank may decline the transaction if
there is a mismatch. In other cases, the
transaction may be approved despite a mismatch.

Alpha
Y, N, X, or
no response

RESPMSG

The response message returned with the
transaction result. Exact wording varies.
Sometimes a colon appears after the initial
RESPMSG followed by more detailed
information. Response messages are described in
“RESULT Values and RESPMSG Text” on
page 56.

Alphanumeric

Variable

Payflow Pro Developer’s Guide

Responses to Transaction Requests
Contents of a Response to a Credit Card Transaction Request
TABLE 6.1

Transaction response values(Continued)

Field

Description

Type

Length

AUTHCODE

Returned for Sale, Authorization, and Voice
Authorization credit card transactions.
AUTHCODE is the approval code obtained over
the telephone from the processing network.
AUTHCODE is required when submitting a Force
(F) transaction.

Alphanumeric

AVSADDR

Address Verification Service address response
returned if you are using Address Verification
Service. Address Verification Service address
responses are for advice only. This process does
not affect the outcome of the authorization. See
“Using Address Verification Service” on
page 33.

Alpha
Y, N, X, or
no response

AVSZIP

Address Verification Service zip code response
returned if you are using Address Verification
Service. AVSZIP responses are for advice only.
This process does not affect the outcome of the
authorization. See “Using Address Verification
Service” on page 33.

Alpha
Y, N, X, or
no response

IAVS

International Address Verification Service
address responses may be returned if you are
using Address Verification Service. IAVS
responses are for advice only. This value does
not affect the outcome of the transaction.
Indicates whether Address Verification Service
response is international (Y), US (N), or cannot
be determined (X). Client version 3.06 or later is
required.
See “Using Address Verification Service” on
page 33.

Alpha
Y, N, X, or
no response

PROCAVS

Address Verification Service response from the
processor when you use Address Verification
Service and send a VERBOSITY request
parameter value of MEDIUM. See Appendix D,
“VERBOSITY: Viewing Processor-Specific
Transaction Results,” for details.

Char

PROCCVV2

CVV2 response from the processor when you
send a VERBOSITY request parameter value of
MEDIUM. See Appendix D, “VERBOSITY:
Viewing Processor-Specific Transaction
Results,” for details.

Char

Payflow Pro Developer’s Guide

Responses to Transaction Requests
BALAMT Response Parameter and Stored Value Cards
TABLE 6.1

Transaction response values(Continued)

Field

Description

Type

Length

AMEXID

Unique transaction ID returned when
VERBOSITY = medium or high for tracking
American Express CAPN transactions.

Numeric

Alphanumeric

N O T E : American Express CAPN transactions

only: used by merchants who authorize
transactions through the payflow gateway
but settle through a third-party solution.
AMEXPOSDATA

Value returned when VERBOSITY = medium or
high.
N O T E : American Express CAPN transactions

only: used by merchants who authorize
transactions through the payflow gateway
but settle through a third-party solution.

BALAMT Response Parameter and Stored Value Cards
BALAMT is a parameter that may be returned by transactions meeting Card Acceptance
Processing Network (CAPN) requirements when that transaction involves a stored value card.
Stored value cards typically are offered as “gift” cards, allowing the user to spend any amount
up to the balance remaining on the card. BALAMT returns the balance on the card provided
that the card is active and is not compromised. If the card is used to purchase merchandise
exceeding the card balance, American Express declines the transaction and returns the card
balance in BALAMT.
For details on American Express CAPN request transaction parameters, see Appendix A,
“Processors Requiring Additional Transaction Parameters.”

American Express CAPN Stored Value Card Example
The Authorization request is for a purchase of 123.00.
TRXTYPE=A&TENDER=C&PWD=x1y2z3&PARTNER=PayPal&VENDOR=SuperMerchant&USER=Supe
rMerchant&ACCT=5555555555554444&EXPDATE=0308&AMT=123.00&STREET=5199
MAPLE&ZIP=94588

Because the response returns a BALAMT of 99.00, the Authorization is declined.
RESULT=12&PNREF=VXYZ01234567&RESPMSG=DECLINED&BALANCE=99.00&AVSADDR=Y&AVSZI
P=N

Payflow Pro Developer’s Guide

Responses to Transaction Requests
PNREF Value

PNREF Value
The PNREF is a unique transaction identification number issued by PayPal that identifies the
transaction for billing, reporting, and transaction data purposes. The PNREF value appears in
the Transaction ID column in PayPal Manager reports.
z

The PNREF value is used as the ORIGID value (original transaction ID) in Delayed Capture
transactions (TRXTYPE=D), Credits (TRXTYPE=C), Inquiries (TRXTYPE=I), and Voids
(TRXTYPE=V).
The PNREF value is used as the ORIGID value (original transaction ID) value in reference
transactions for Authorization (TRXTYPE=A) and Sale (TRXTYPE=S).

N O T E : The

PNREF is also referred to as the Transaction ID in PayPal Manager.

PNREF Format
The PNREF is a 12-character string of printable characters, for example:
z

VADE0B248932

ACRAF23DB3C4

N O T E : Printable

characters also include symbols other than letters and numbers such as the
question mark (?). A PNREF typically contains letters and numbers only.

The PNREF in a transaction response tells you that your transaction is connecting to PayPal.

RESULT Values and RESPMSG Text
The RESULT parameter and value is the first name-value pair returned in the response string.
The value of RESULT indicates the overall status of the transaction attempt:
z
z

A value of 0 (zero) indicates that no errors occurred and the transaction was approved.
A value less than zero indicates that a communication error occurred. In this case, no
transaction is attempted.
A value greater than zero indicates a decline or error.

The response message (RESPMSG) provides a brief description for decline or error results.

RESULT Values for Transaction Declines or Errors
For non-zero RESULT values, the response string includes a RESPMSG name-value pair. The
exact wording of the RESPMSG (shown in bold) may vary. Sometimes a colon appears after the
initial RESPMSG followed by more detailed information.

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text

TABLE 6.2

Payflow transaction RESULT values and RESPMSG text

RESULT

RESPMSG and Explanation

Approved.

User authentication failed. Error is caused by one or more of the following:
z Login information is incorrect. Verify that USER, VENDOR, PARTNER, and
PASSWORD have been entered correctly. VENDOR is your merchant ID and
USER is the same as VENDOR unless you created a Payflow Pro user. All fields
are case sensitive.
z Invalid Processor information entered. Contact merchant bank to verify.
z "Allowed IP Address" security feature implemented. The transaction is coming
from an unknown IP address. See PayPal Manager online help for details on how to
use Manager to update the allowed IP addresses.
z You are using a test (not active) account to submit a transaction to the live PayPal
servers. Change the host address from the test server URL to the live server URL.

Invalid tender type. Your merchant bank account does not support the following
credit card type that was submitted.

Invalid transaction type. Transaction type is not appropriate for this transaction. For
example, you cannot credit an authorization-only transaction.

Invalid amount format. Use the format: “#####.##” Do not include currency
symbols or commas.

Invalid merchant information. Processor does not recognize your merchant account
information. Contact your bank account acquirer to resolve this problem.

Invalid or unsupported currency code

Field format error. Invalid information entered. See RESPMSG.

Not a transaction server

Too many parameters or invalid stream

Too many line items

Client time-out waiting for response

Declined. Check the credit card number, expiration date, and transaction information to
make sure they were entered correctly. If this does not resolve the problem, have the
customer call their card issuing bank to resolve.

Referral. Transaction cannot be approved electronically but can be approved with a
verbal authorization. Contact your merchant bank to obtain an authorization and submit
a manual Voice Authorization transaction.

Original transaction ID not found. The transaction ID you entered for this
transaction is not valid. See RESPMSG.

Cannot find the customer reference number

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text
TABLE 6.2

Payflow transaction RESULT values and RESPMSG text (Continued)

RESULT

RESPMSG and Explanation

Invalid ABA number

Invalid account number. Check credit card number and re-submit.

Invalid expiration date. Check and re-submit.

Invalid Host Mapping. Error is caused by one or more of the following:
z You are trying to process a tender type such as Discover Card, but you are not set up
with your merchant bank to accept this card type.
z You are trying to process an Express Checkout transaction when your account is not
set up to do so. Contact your account holder to have Express Checkout added to
your account.

Invalid vendor account. Login information is incorrect. Verify that USER, VENDOR,
PARTNER, and PASSWORD have been entered correctly. VENDOR is your merchant
ID and USER is the same as VENDOR unless you created a Payflow Pro user. All
fields are case sensitive.

Insufficient partner permissions

Insufficient user permissions

Invalid XML document. This could be caused by an unrecognized XML tag or a bad
XML format that cannot be parsed by the system.

Duplicate transaction

Error in adding the recurring profile

Error in modifying the recurring profile

Error in canceling the recurring profile

Error in forcing the recurring profile

Error in reactivating the recurring profile

OLTP Transaction failed

Invalid recurring profile ID

Insufficient funds available in account

Exceeds per transaction limit

General error. See RESPMSG.

100

Transaction type not supported by host

101

Time-out value too small

102

Processor not available

103

Error reading response from host

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text
TABLE 6.2

Payflow transaction RESULT values and RESPMSG text (Continued)

RESULT

RESPMSG and Explanation

104

Timeout waiting for processor response. Try your transaction again.

105

Credit error. Make sure you have not already credited this transaction, or that this
transaction ID is for a creditable transaction. (For example, you cannot credit an
authorization.)

106

Host not available

107

Duplicate suppression time-out

108

Void error. See RESPMSG. Make sure the transaction ID entered has not already been
voided. If not, then look at the Transaction Detail screen for this transaction to see if it
has settled. (The Batch field is set to a number greater than zero if the transaction has
been settled). If the transaction has already settled, your only recourse is a reversal
(credit a payment or submit a payment for a credit).

109

Time-out waiting for host response

110

Referenced auth (against order) Error

111

Capture error. Either an attempt to capture a transaction that is not an authorization
transaction type, or an attempt to capture an authorization transaction that has already
been captured.

112

Failed AVS check. Address and ZIP code do not match. An authorization may still
exist on the cardholder’s account.

113

Merchant sale total will exceed the sales cap with current transaction. ACH
transactions only.

114

Card Security Code (CSC) Mismatch. An authorization may still exist on the
cardholder’s account.

115

System busy, try again later

116

PayPal internal error. Failed to lock terminal number

117

Failed merchant rule check. One or more of the following three failures occurred:
An attempt was made to submit a transaction that failed to meet the security settings
specified on the PayPal Manager Security Settings page. If the transaction exceeded the
Maximum Amount security setting, then no values are returned for AVS or CSC.
AVS validation failed. The AVS return value should appear in the RESPMSG.
CSC validation failed. The CSC return value should appear in the RESPMSG.

118

Invalid keywords found in string fields

120

Attempt to reference a failed transaction

121

Not enabled for feature

122

Merchant sale total will exceed the credit cap with current transaction. ACH
transactions only.

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text
TABLE 6.2

Payflow transaction RESULT values and RESPMSG text (Continued)

RESULT

RESPMSG and Explanation

125

Fraud Protection Services Filter — Declined by filters

126

Fraud Protection Services Filter — Flagged for review by filters
Important Note: Result code 126 indicates that a transaction triggered a fraud filter.
This is not an error, but a notice that the transaction is in a review status. The
transaction has been authorized but requires you to review and to manually accept the
transaction before it will be allowed to settle.
Result code 126 is intended to give you an idea of the kind of transaction that is
considered suspicious to enable you to evaluate whether you can benefit from using the
Fraud Protection Services.
To eliminate result 126, turn the filters off.
For more information, see the Fraud Protection Services documentation for your
payments solution. It is available on the PayPal Manager Documentation page.

127

Fraud Protection Services Filter — Not processed by filters

128

Fraud Protection Services Filter — Declined by merchant after being flagged for
review by filters

132

Card has not been submitted for update

133

Data mismatch in HTTP retry request

150

Issuing bank timed out

151

Issuing bank unavailable

200

Reauth error

201

Order error

600

Cybercash Batch Error

601

Cybercash Query Error

1000

Generic host error. This is a generic message returned by your credit card processor.
The RESPMSG will contain more information describing the error.

1001

Buyer Authentication Service unavailable

1002

Buyer Authentication Service — Transaction timeout

1003

Buyer Authentication Service — Invalid client version

1004

Buyer Authentication Service — Invalid timeout value

1011

Buyer Authentication Service unavailable

1012

Buyer Authentication Service unavailable

1013

Buyer Authentication Service unavailable

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text
TABLE 6.2

Payflow transaction RESULT values and RESPMSG text (Continued)

RESULT

RESPMSG and Explanation

1014

Buyer Authentication Service — Merchant is not enrolled for Buyer
Authentication Service (3-D Secure).

1016

Buyer Authentication Service — 3-D Secure error response received. Instead of
receiving a PARes response to a Validate Authentication transaction, an error response
was received.

1017

Buyer Authentication Service — 3-D Secure error response is invalid. An error
response is received and the response is not well formed for a Validate Authentication
transaction.

1021

Buyer Authentication Service — Invalid card type

1022

Buyer Authentication Service — Invalid or missing currency code

1023

Buyer Authentication Service — merchant status for 3D secure is invalid

1041

Buyer Authentication Service — Validate Authentication failed: missing or
invalid PARES

1042

Buyer Authentication Service — Validate Authentication failed: PARES format is
invalid

1043

Buyer Authentication Service — Validate Authentication failed: Cannot find
successful Verify Enrollment

1044

Buyer Authentication Service — Validate Authentication failed: Signature
validation failed for PARES

1045

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid amount in PARES

1046

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid acquirer in PARES

1047

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid Merchant ID in PARES

1048

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid card number in PARES

1049

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid currency code in PARES

1050

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid XID in PARES

1051

Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid order date in PARES

1052

Buyer Authentication Service — Validate Authentication failed: This PARES was
already validated for a previous Validate Authentication transaction

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text

RESULT Values for Communications Errors
A RESULT value less than zero indicates that a communication error occurred. In this case, no
transaction is attempted.
A value of -1 or -2 usually indicates a configuration error caused by an incorrect URL or by
configuration issues with your firewall. A value of -1 or -2 can also be possible if the PayPal
servers are unavailable, or an incorrect server/socket pair has been specified. A value of -1 can
also result when there are internet connectivity errors. Contact customer support regarding any
other errors.
For information on firewall configuration, see Chapter , “Downloading, Installing, and
Activating.”
N O T E : To

eliminate RESULT -31 and -108 errors described below, upgrade to a version 4
SDK or post directly to the Payflow servers via HTTPS. For details on determining the
version of your SDK, see “Payflow SDK Version” on page 15.

Details of the response message may vary slightly from that shown in the table, depending on
your SDK integration.
TABLE 6.3

RESULT values for communications errors

RESULT

Description

-1

Failed to connect to host

-2

Failed to resolve hostname

-5

Failed to initialize SSL context

-6

Parameter list format error: & in name

-7

Parameter list format error: invalid [ ] name length clause

-8

SSL failed to connect to host

-9

SSL read failed

-10

SSL write failed

-11

Proxy authorization failed

-12

Timeout waiting for response

-13

Select failure

-14

Too many connections

-15

Failed to set socket options

-20

Proxy read failed

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text
TABLE 6.3

RESULT values for communications errors(Continued)

RESULT

Description

-21

Proxy write failed

-22

Failed to initialize SSL certificate

-23

Host address not specified

-24

Invalid transaction type

-25

Failed to create a socket

-26

Failed to initialize socket layer

-27

Parameter list format error: invalid [ ] name length clause

-28

Parameter list format error: name

-29

Failed to initialize SSL connection

-30

Invalid timeout value

-31

The certificate chain did not validate, no local certificate found

-32

The certificate chain did not validate, common name did not match URL

- 40

Unexpected Request ID found in request.

- 41

Required Request ID not found in request

-99

Out of memory

-100

Parameter list cannot be empty

-103

Context initialization failed

-104

Unexpected transaction state

-105

Invalid name value pair request

-106

Invalid response format

-107

This XMLPay version is not supported

-108

The server certificate chain did not validate

-109

Unable to do logging

-111

The following error occurred while initializing from message file:

-113

Unable to round and truncate the currency value simultaneously

Payflow Pro Developer’s Guide

Responses to Transaction Requests
RESULT Values and RESPMSG Text

Payflow Pro Developer’s Guide

Processors Requiring Additional
Transaction Parameters
This appendix lists both required and optional parameters supplementary to the common
parameter set.
In this Appendix
z

“American Express” on page 65

“First Data Merchant Services (FDMS) Nashville” on page 74

“First Data Merchant Services (FDMS) South” on page 75

“First Data Merchant Services (FDMS) North” on page 75

“Elavon (Formerly Nova)” on page 77

“Paymentech” on page 77

“TSYS Acquiring Solutions” on page 81

American Express
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
American Express accepts the parameters described in this section. Parameters to meet
American Express Card Acceptance and Processing Network (CAPN) requirements are
described in Table A.1. American Express (legacy) platform parameters are described in
Table A.2.

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express

American Express Additional Credit Card Parameters (CAPN)
N O T E : You should start coding to the CAPN parameters if you want to be able to impact what

appears on AMEX statements and reports. With a few exceptions, most merchants in
the United States follow CAPN requirements; international merchants do not. If you
are not sure whether you should make the coding changes, contact Customer Service.
See “How to Contact Customer Support” on page 10 for contact information.
American Express Phoenix accepts the following parameters to meet CAPN requirements.
TABLE A.1
Parameter

American Express CAPN parameters
Description

Required

Type

Length

Retail Transaction Advice Addendum Parameters (for SWIPE transactions)
L_DESCn

Description of this line-item (n is a line item
number from 1 to 6)

Alphanumeric

L_AMTn

Amount of this line-item (n is a line item number
from 1 to 6)
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)
Examples: tip=3.00, convenience charge=2.00

Numeric

L_QTYn

Quantity of this line-item (n is a line item number
from 1 to 6)

Numeric

Internet Transaction Data Parameters

Account holder’s email address

Alphanumeric

PHONENUM

Account holder’s telephone number

String

PHONETYPE

Telephone company provided ANI information
identifier digits indicating the telephone call type
Examples: cellular (61-63), payphone (27)

Alphanumeric

CUSTHOSTNAME

Name of the server that the account holder is
connected to
Example: PHX.QW.AOL.COM

Alphanumeric
and
special
characters

CUSTBROWSER

Account holder’s HTTP browser type
Example:
MOZILLA/4.0~(COMPATIBLE;~MSIE~5.0;~W
INDOWS~95)

Alphanumeric
and
special
characters

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express
TABLE A.1

American Express CAPN parameters (Continued)

Parameter

Description

Required

Type

Length

CUSTIP

Account holder’s IP address

Alphanumeric
and
special
characters

SHIPTOCOUNTRY

Numeric country code of ship-to country
Example:
USA: 840

Alphanumeric

SHIPMETHOD

Shipping method code. The values are:
01 = Same day
02 = Overnight/next day
03 = Priority, 2 - 3 days
04 = Ground, 4 or more days
05 = Electronic delivery
06 - ZZ = Reserved for future use

Alphanumeric

SKU

Merchant product SKU

Alphanumeric

STREET

Account holder’s street address (number and street
name)

Alphanumeric

ZIP

Account holder’s 5- to 9-digit ZIP (postal) code
excluding spaces, dashes, and non-numeric
characters
Example: 951121737

String

PHONENUM

Account holder’s telephone number. The formats
are
xxx-xxx-xxxx (US numbers)
+xxxxxxxxxxx (international numbers)

String

SHIPTOFIRSTNAME

First name in the shipping address

Alphanumeric

SHIPTOLASTNAME

Last name in the shipping address

Alphanumeric

SHIPTOSTREET

Shipping street address

Alphanumeric

SHIPTOCOUNTRY

Numeric country code
Example:
USA: 840

Alphanumeric

AVS Parameters

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express
TABLE A.1

American Express CAPN parameters (Continued)

Parameter

Description

Required

Type

Length

SHIPTOZIP

Shipping 5- to 9-digit ZIP (postal) code excluding
spaces, dashes, and non-numeric characters
Example: 951121737

Alphanumeric

SHIPTOPHONENUM

Shipping telephone number

String

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 Virtual Terminal. 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.

Alphanumeric
Y or N

Alphanumeric

Location Transaction Advice Addendum Parameters
MERCHANTNAME

Name of merchant

MERCHANTSTREET

Merchant’s street address (number and street
name)

MERCHANTCITY

Merchant’s city

MERCHANTSTATE

Merchant’s state

MERCHANTCOUNTRYCO
DE

Merchant’s numeric country code
Example:
USA: 840

Alphanumeric

MERCHANTZIP

Merchant’s 5- to 9-digit ZIP (postal) code
excluding spaces, dashes, and non-numeric
characters
Example: 951121737

Alphanumeric

Transaction Advice Detail Parameters

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express
TABLE A.1

American Express CAPN parameters (Continued)

Parameter

Description

Required

Type

Length

ADDLAMTn

Detail of a charge where n is a value from 1 - 5
Use for additional breakdown of the amount
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)
Examples: tip=3.00, convenience charge=2.00

Numeric

ADDLAMTTYPEn

A 3-digit code indicating the type of the
corresponding charge detail, where n is a value
from 1 - 5

Alphanumeric

Airline Passenger Data Parameters
AIR-DEPARTUREDATE

Departure date in the format YYYYMMDD.

Alphanumeric

AIR-PASSENGERNAME

Name of the passenger in the following format
with fields separated by a space:
surname firstname middleinitial title

Alphanumeric

AIR-ORIGIN

Airport code of the originating airport.
For a list of airport codes, see http://www.worldairport-codes.com/alphabetical/airportcode/a.html.

Alphanumeric

N O T E : Present day airport codes are three

characters in length. The five character
length is designed to allow for future
expansion.
AIR-DESTINATION

Destination airport code for the first segment of
the trip; this is not necessarily the final
destination. For example, if a passenger flies from
STL to MIA with a layover at JFK, the destination
airport is JFK.
For a list of airport codes, see http://www.worldairport-codes.com/alphabetical/airportcode/a.html.
N O T E : Present day airport codes are three

characters in length. The five character
length is designed to allow for future
expansion.

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express
TABLE A.1

American Express CAPN parameters (Continued)

Parameter

Description

Required

Type

Length

AIRNUMBEROFCITIES

Number of unique cities in this trip including the
cities of origin and destination, where a maximum
value of 10 is allowed. For example, AIRNUMBEROFCITIES is 3 for the following trip:
DEN to LAX
LAX to SFO
SFO to DEN
If not provided, this value is equal to the number
of AIR-ROUTINGCITYn parameters.

Numeric

AIR-ROUTINGCITYn

Airport codes of each city in this flight including
cities of origin and destination, where n is a value
from 1 to 10.
For a list of airport codes, see http://www.worldairport-codes.com/alphabetical/airportcode/a.html.

Alphanumeric

N O T E : Present day airport codes are three

characters in length. The five character
length is designed to allow for future
expansion.

AIR-CARRIERn

Two character airline code for each unique airline
in this flight, where n is a value from 1 to 10.
If the same carrier is used for multiple segments of
the trip, it is passed only once. For example, the
two AIR-CARRIERn values for the following trip
are UA and AA:
UA flight from IAD to DEN
UA flight from DEN to LAX
UA flight from LAX to SFO
AA flight from SFO to DFW
For information about airlines codes, see
http://en.wikipedia.org/wiki/Airline_codes-All.

Alphanumeric

AIR-FAREBASIS

List discounts associated with the travel.

Alphanumeric

AIRNUMBEROFPASSENGER
S

Number of passengers on this trip.

Numeric

AIR-ISETICKET

If this is an electronic ticket. The values are:
Y = yes
N = no

Alphanumeric

AIRRESERVATIONCODE

Code assigned to the travel reservation before the
ticket was purchased.

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express
TABLE A.1
Parameter

American Express CAPN parameters (Continued)
Description

Required

Type

Length

FIRSTNAME

Account holder's first and last name. Note: Even
though the parameter name indicates only the first
name, this single parameter holds all of the
person's name information (both first and last
name, at a minimum).

Alphanumeric

LASTNAME

Account holder's last name.

Alphanumeric

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.

Alphanumeric

ORDERDATE

Order date
For example, July 28, 2003 is 072803.
Format: mmddyy (with no slashes or dashes)

Numeric

ORDERDATETIME

Order time and date
Format is either
YYYY-MM-DD or
YYYY-MM-DD HH:MI:SS
(where HH is in 24-hour time).If the value does
not conform to one of the formats or if the date is
not valid (for example, 2004-17-35), then the
transaction is rejected with:
RESULT=7(SIG_FIELD_ERR)
RESPMSG=Invalid ORDERTIME
A truncated version of the ORDERTIME value (up
to 7 characters) overwrites any value provided by
ORDERDATE. If no value is provided, a NULL value
is stored.

SWIPE

Allows Track 1 and Track 2 data to be passed to
enable a card-present transaction

Other

Alphanumeric

American Express Additional Credit Card Parameters (Legacy)
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
American Express Phoenix accepts the following legacy parameters.
N O T E : Merchants

in the United States follow the CAPN requirements and use the parameters
described in Table A.1; international merchants do not and instead use the legacy

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express

parameters described in Table A.2. There are a few exceptions. If you are not sure,
contact Customer Service. See “How to Contact Customer Support” on page 10 for
contact information.
TABLE A.2

American Express legacy parameters

Parameter

Description

Required

Type

Length

DESC

Describes the transaction.

Alphanumeric

Brighton
40
Other
American
Express
platforms
23

DESC1

Describes the transaction.

Alphanumeric

DESC2

Describes the transaction.

Alphanumeric

DESC3

Describes the transaction.

Alphanumeric

DESC4

Describes the transaction.

Alphanumeric

FIRSTNAME

Alphanumeric

LASTNAME

Account holder's last name.

Alphanumeric

INVNUM

Alphanumeric

ORDERDATE

Specifies an order date.
For example, July 28, 2003 is 072803.
Format: mmddyy (with no slashes or dashes)

Numeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
American Express
TABLE A.2

American Express legacy parameters (Continued)

Parameter

Description

Required

ORDERDATETIME

Specifies an order time and date.
Format is either
YYYY-MM-DD or
YYYY-MM-DD HH:MI:SS
(where HH is in 24-hour time).If the value does
not conform to one of the formats or if the date is
not valid (for example, 2004-17-35), then the
transaction is rejected with:
RESULT=7(SIG_FIELD_ERR)
RESPMSG=Invalid ORDERTIME
A truncated version of the ORDERTIME value (up
to 7 characters) overwrites any value provided by
ORDERDATE. If no value is provided, a NULL value
is stored

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.

Alphanumeric
Y or N

SWIPE

Allows Track 1 and Track 2 data to be passed to
enable a card-present transaction.

Alphanumeric

Payflow Pro Developer’s Guide

Type

Length
19

Processors Requiring Additional Transaction Parameters
First Data Merchant Services (FDMS) Nashville

First Data Merchant Services (FDMS) Nashville
FDMS Nashville, Additional Credit Card Parameters
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
FDMS Nashville accepts the following parameters:
TABLE A.3

FDMS Nashville additional parameters

Parameter

Description

Required

Type

Length

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.

Alphanumeric

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.

Alphanumeric
Y or N

SWIPE

Allows Track 1 and Track 2 data to be passed to enable a
card-present transaction.

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
First Data Merchant Services (FDMS) South

First Data Merchant Services (FDMS) South
FDMS South, Additional Credit Card Parameters
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
FDMS South accepts the following parameters:
TABLE A.4

FDMS South additional parameters

Parameter

Description

Required

Type

Length

SWIPE

Allows Track 1 and Track 2 data to be passed to enable a
card-present transaction.

Alphanumeric

First Data Merchant Services (FDMS) North
FDMS North, Additional Credit Card Parameters
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
FDMS North (also known as FDMS CardNet) accepts the parameters in Table A.5.
FDMS North supports partial authorization reversals for Visa only when the capture amount is
less than the authorization amount; full Authorization reversals are not supported. FDMS
North does not support unreferenced credits.
TABLE A.5

FDMS North additional parameters

Parameter

Description

Required

Type

Length

DESC

Use the DESC* parameters to pass in your DBA name
and other data describing the transaction. This
information will be displayed in the end user’s
statement.
Note: FDMS North passes the descriptive data to the
card associations with the following character
lengths:
z Visa: 25
z MasterCard: 22
z AMEX: 20
z DISC: 22
Some card associations truncate the value to 19
characters. If you have questions, consult the card
association.

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
Merchant e-Solutions
TABLE A.5

FDMS North additional parameters(Continued)

Parameter

Description

Required

Type

Length

MERCHSVC

Defaults to CITY (where the merchant outlet is
located) for retail and to PHONENUM for non-retail.
For example, 800 111-1111. Use uppercase
characters. The first three positions must be numeric.

Alphanumeric

Merchant e-Solutions
Merchant e-Solutions, Additional Credit Card Parameters
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”
Merchant e-Solutions accepts the following parameters:
TABLE A.6

TSYS Acquiring Solutionsa additional parameters

Parameter

Description

Required

Type

Length

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.

Alphanumeric

SWIPE

Allows Track 1 and Track 2 data to be passed to enable a
card-present transaction.

Alphanumeric

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 Virtual
Terminal 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.

Alphanumeric
Y or N

a. Formerly Vital Processing Services

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
Elavon (Formerly Nova)

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:
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.

Alphanumeric
Y or N

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.
Paymentech Salem (New Hampshire) supports full authorization reversals for Visa,
Mastercard, and Switch/Solo Maestro cards. PayPal sends a Void and a full Authorization

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
Paymentech

request against the original transaction to the Paymentech Salem (New Hampshire) processor
to remove the balance hold on the buyer’s credit card.
TABLE A.8
Parameter

Additional Paymentech parameters to meet CAPN requirements
Description

Required

Type

Length

Internet Transaction Data Parameters

Account holder’s email address

Alphanumeric

PHONENUM

Account holder’s telephone number

String

PHONETYPE

Telephone company provided ANI information
identifier digits indicating the telephone call type
Examples: cellular (61-63), payphone (27)

Alphanumeric

CUSTHOSTNAME

Name of the server that the account holder is
connected to
Example: PHX.QW.AOL.COM

Alphanumeric
and
special
character
s

CUSTBROWSER

Account holder’s HTTP browser type
Example:
MOZILLA/4.0~(COMPATIBLE;~MSIE~5.0;~WI
NDOWS~95)

Alphanumeric
and
special
character
s

CUSTIP

Account holder’s IP address

Alphanumeric
and
special
character
s

SHIPTOCOUNTRY

Numeric country code of ship-to country
Example:
USA: 840

Alphanumeric

SHIPMETHOD

Shipping method code. The values are:
01 = Same day
02 = Overnight/next day
03 = Priority, 2 - 3 days
04 = Ground, 4 or more days
05 = Electronic delivery
06 - ZZ = Reserved for future use

Alphanumeric

SKU

Merchant product SKU

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
Paymentech
TABLE A.8
Parameter

Additional Paymentech parameters to meet CAPN
requirements(Continued)
Description

Required

Type

Length

STREET

Account holder’s street address (number and street
name)

Alphanumeric

ZIP

Account holder’s 5- to 9-digit ZIP (postal) code
excluding spaces, dashes, and non-numeric
characters
Example: 951121737

String

PHONENUM

Account holder’s telephone number. The formats
are
xxx-xxx-xxxx (US numbers)
+xxxxxxxxxxx (international numbers)

String

SHIPTOFIRSTNAME

First name in the shipping address

Alphanumeric

SHIPTOLASTNAME

Last name in the shipping address

Alphanumeric

SHIPTOSTREET

Shipping street address

Alphanumeric

SHIPTOCOUNTRY

Numeric country code
Example:
USA: 840

Alphanumeric

SHIPTOZIP

Shipping 5- to 9-digit ZIP (postal) code excluding
spaces, dashes, and non-numeric characters
Example: 951121737

Alphanumeric

SHIPTOPHONENUM

Shipping telephone number

String

AVS Parameters

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
Paymentech
TABLE A.8

Additional Paymentech parameters to meet CAPN
requirements(Continued)

Parameter

Description

Required

Type

Length

RECURRING

Identifies the transaction as recurring. This value
does not activate the PayPal 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 Virtual
Terminal. 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.

Alphanumeric
Y or N

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.

Alpha

BILLTOCOUNTRY

Cardholder’s billing country code

Yes

Numeric

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.

Alphanumeric

MERCHDESCR

Merchant descriptor.
For example, ABCCMPY*FALLCATALOG

Alphanumeric

MERCHSVC

Merchant telephone number.
For example, 603-555-1212

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions
TABLE A.9

Additional Paymentech parameters (legacy)(Continued)

Parameter

Description

Required

Type

Length

STATE

Cardholder’s billing state.

Alpha

SWIPE

Allows Track 1 and Track 2 data to be passed to
enable a card-present transaction.

Alphanumeric

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.

Alphanumeric
Y or N

RECURRINGTYPE

(Paymentech Tampa only) Type of transaction
occurrence. The values are:
F = First occurrence
S = Subsequent occurrence (default)

Alpha

TSYS Acquiring Solutions
TSYS Acquiring Solutions, Additional Credit Card Parameters (CAPN)
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,” TSYS
Acquiring Solutions accepts the following parameters to meet CAPN requirements.
TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements
Parameter

Description

Required

Type

Length

Alphanumeric

Retail Transaction Advice Addendum Parameters (for SWIPE transactions)
L_DESCn

Payflow Pro Developer’s Guide

Description of this line-item (n is a line item
number from 1 to 6)

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions
TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements (Continued)
Parameter

Description

Required

Type

Length

L_AMTn

Numeric

L_QTYn

Quantity of this line-item (n is a line item number
from 1 to 6)

Numeric

Internet Transaction Data Parameters

Account holder’s email address

Alphanumeric

PHONENUM

Account holder’s telephone number

String

PHONETYPE

Telephone company provided ANI information
identifier digits indicating the telephone call type
Examples: cellular (61-63), payphone (27)

Alphanumeric

CUSTHOSTNAME

Name of the server that the account holder is
connected to
Example: PHX.QW.AOL.COM

Alphanumeric
and
special
characters

CUSTBROWSER

Account holder’s HTTP browser type
Example:
MOZILLA/4.0~(COMPATIBLE;~MSIE~5.0;~W
INDOWS~95)

Alphanumeric
and
special
characters

CUSTIP

Account holder’s IP address

Alphanumeric
and
special
characters

SHIPTOCOUNTRY

Numeric country code of ship-to country
Example:
USA: 840

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions

TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements (Continued)
Parameter

Description

Required

Type

Length

SHIPMETHOD

Shipping method code. The values are:
01 = Same day
02 = Overnight/next day
03 = Priority, 2 - 3 days
04 = Ground, 4 or more days
05 = Electronic delivery
06 - ZZ = Reserved for future use

Alphanumeric

SKU

Merchant product SKU

Alphanumeric

STREET

Account holder’s street address (number and street
name)

Alphanumeric

ZIP

Account holder’s 5- to 9-digit ZIP (postal) code
excluding spaces, dashes, and non-numeric
characters
Example: 951121737

String

PHONENUM

Account holder’s telephone number. The formats
are
xxx-xxx-xxxx (US numbers)
+xxxxxxxxxxx (international numbers)

String

SHIPTOFIRSTNAME

First name in the shipping address

Alphanumeric

SHIPTOLASTNAME

Last name in the shipping address

Alphanumeric

SHIPTOSTREET

Shipping street address

Alphanumeric

SHIPTOCOUNTRY

Numeric country code
Example:
USA: 840

Alphanumeric

SHIPTOZIP

Shipping 5- to 9-digit ZIP (postal) code excluding
spaces, dashes, and non-numeric characters
Example: 951121737

Alphanumeric

SHIPTOPHONENUM

Shipping telephone number

String

AVS Parameters

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions
TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements (Continued)
Parameter

Description

Required

Type

Length

RECURRING

Alphanumeric
Y or N

Alphanumeric

Location Transaction Advice Addendum Parameters
MERCHANTNAME

Name of merchant

MERCHANTSTREET

Merchant’s street address (number and street
name)

MERCHANTCITY

Merchant’s city

MERCHANTSTATE

Merchant’s state

MERCHANTCOUNTRYCO
DE

Merchant’s numeric country code
Example:
USA: 840

Alphanumeric

MERCHANTZIP

Merchant’s 5- to 9-digit ZIP (postal) code
excluding spaces, dashes, and non-numeric
characters
Example: 951121737

Alphanumeric

Numeric

Transaction Advice Detail Parameters
ADDLAMTn

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions

TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements (Continued)
Parameter

Description

Required

Type

Length

ADDLAMTTYPEn

A 3-digit code indicating the type of the
corresponding charge detail, where n is a value
from 1 - 5

Alphanumeric

Airline Passenger Data Parameters
AIR-DEPARTUREDATE

Departure date in the format YYYYMMDD.

Alphanumeric

AIR-PASSENGERNAME

Name of the passenger in the following format
with fields separated by a space:
surname firstname middleinitial title

Alphanumeric

AIR-ORIGIN

Airport code of the originating airport.
For a list of airport codes, see http://www.worldairport-codes.com/alphabetical/airportcode/a.html.

Alphanumeric

Numeric

N O T E : Present day airport codes are three

characters in length. The five character
length is designed to allow for future
expansion.
AIR-DESTINATION

characters in length. The five character
length is designed to allow for future
expansion.
AIRNUMBEROFCITIES

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions
TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements (Continued)
Parameter

Description

Required

Type

Length

AIR-ROUTINGCITYn

Alphanumeric

N O T E : Present day airport codes are three

characters in length. The five character
length is designed to allow for future
expansion.
AIR-CARRIERn

Alphanumeric

AIR-FAREBASIS

List discounts associated with the travel.

Alphanumeric

AIRNUMBEROFPASSENGER
S

Number of passengers on this trip.

Numeric

AIR-ISETICKET

If this is an electronic ticket. The values are:
Y = yes
N = no

Alphanumeric

AIRRESERVATIONCODE

Code assigned to the travel reservation before the
ticket was purchased.

Alphanumeric

FIRSTNAME

Alphanumeric

LASTNAME

Account holder's last name.

Alphanumeric

Other

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions

TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN
requirements (Continued)
Parameter

Description

Required

Type

Length

INVNUM

Alphanumeric

ORDERDATE

Order date
For example, July 28, 2003 is 072803.
Format: mmddyy (with no slashes or dashes)

Numeric

ORDERDATETIME

SWIPE

Allows Track 1 and Track 2 data to be passed to
enable a card-present transaction

Alphanumeric

TSYS Acquiring Solutions, Additional Credit Card Parameters (Legacy)
In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,” TSYS
Acquiring Solutions accepts the following legacy parameters:
TABLE A.11 TSYS Acquiring Solutions additional parameters (legacy)
Parameter

Description

Required

Type

Length

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.

Alphanumeric

Payflow Pro Developer’s Guide

Processors Requiring Additional Transaction Parameters
TSYS Acquiring Solutions
TABLE A.11 TSYS Acquiring Solutions additional parameters (legacy)(Continued)

Parameter

Description

Required

Type

Length

SWIPE

Allows Track 1 and Track 2 data to be passed to enable a
card-present transaction.

Alphanumeric

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 Virtual
Terminal 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.

Alphanumeric
Y or N

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic
Check Transactions
This chapter describes Telecheck (electronic check) transaction processing and testing.
N O T E : TeleCheck

transactions are not supported on the PayPal processor.

Paypal offers electronic check acceptance through TeleCheck. Before processing electronic
check transactions, merchants must obtain an account through TeleCheck
(www.telecheck.com).
For information on:
z

Performing credit card transactions, skip this chapter and see “Credit Card Transactions”
on page 23.”
Performing ACH transactions, contact your PayPal Sales Representative at
paymentsales@PayPal.com

TeleCheck Parameters
Parameters used for processing electronic checks through TeleCheck are described in
Table B.1. Required and optional parameters are noted.
N O T E : Appendix

E, “Additional Reporting Parameters,” provides a list of parameters that you
can pass for reporting purposes.

Required Parameters
As a summary of Table B.1, the following parameters are required for every electronic check
transaction:
TRXTYPE
TENDER
CHKTYPE
PARTNER
VENDOR
USER
PWD
AMT
CITY
DL or SS
CHKNUM
EMAIL
MICR
NAME
STATE

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic Check Transactions
TeleCheck Parameters
STREET
ZIP
TABLE B.1

TeleCheck Parameters

Parameter

Description

Required

Type

Length

AMT

This is the transaction amount. Default: U.S. dollars. The
transaction amount should always specify a decimal, and
the exact amount to the cent (for example, 34.00, instead of
34). Do not include comma separators in the amount. Use
1199.95 not 1,199.95.

Yes

Numeric
US
Dollars
only.

CITY

Account holder’s city

Yes

Alpha

COMMENT1

User-defined value for reporting and auditing purposes.

Alphanumeric

128

COMMENT2

User-defined value for reporting and auditing purposes.

Alphanumeric

128

CHKNUM

Account holder’s next unused (available) check number

Yes

Numeric

CHKTYPE

Check type: P: personal (default) or
C: company
If CHKTYPE=P, then a value for either DL or SS must be
passed as an identifier.
If CHKTYPE=C, then the Federal Tax ID must be passed as
the SS value.

Yes

Alpha

Driver’s license number. If CHKTYPE=P, a value for either
DL or SS must be passed as an identifier.
Format: XXnnnnnnnn
XX = State Code
nnnnnnnn = DL Number

Yes

Alphanumeric

DOB

Account holder’s date of birth.
Format: mmddyyyy. For example, July 28, 1965 is
represented as 07281965.

Alphanumeric

Account holder’s e-mail address

Yes

Alphanumeric

INVNUM

Check invoice number

Alphanumeric

MICR

Magnetic Ink Check Reader. This is the entire line of
numbers at the bottom of all checks. It includes the transit
number, account number, and check number.

Yes

Alphanumeric

NAME

Account holder’s name as it appears on the check

Yes

Alphanumeric

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic Check Transactions
Testing TeleCheck Transactions
TABLE B.1

TeleCheck Parameters (Continued)

Parameter

Description

Required

Type

Length

PARTNER

The authorized PayPal Reseller that registered you for the
Payflow service provided you with a Partner ID. If you
registered yourself, use PayPal.
This parameter is case-sensitive.

Yes

Alphanumeric

PHONENUM

Account holder’s telephone number

Numeric

PWD

Case-sensitive 6- to 32-character password that you
created while registering for the account.

Yes

Alphanumeric

Account holder’s social security number.
If CHKTYPE=P, a value for either DL or SS must be
passed as an identifier.
If CHKTYPE=C, the Federal Tax ID must be passed as the
SS value.

Alphanumeric

STATE

Account holder’s state

Yes

Alpha

STREET

Account holder’s street address

Yes

Alphanumeric

TENDER

Tender type (method of payment). Use only the value K
(electronic check).

Yes

Alpha

TRXTYPE

Type of transaction that should be processed. Allowed
transaction types: Sale (S), Void (V), Inquiry (I).

Yes

Alpha

USER

Case-sensitive login ID for the Payflow Pro account that
you created while registering for the account.
In the future, each account will allow multiple users. This
parameter will specify the user.

Yes

Alphanumeric

VENDOR

Case-sensitive Vendor ID that you created while
registering for the account.

Yes

Alphanumeric

ZIP

Account holder’s 5- to 9-digit postal code (called ZIP code
in the USA). Do not use spaces, dashes, or non-numeric
characters.

Yes

Alpha

Testing TeleCheck Transactions
PayPal provides a test server to support testing and configuration. For information on the test
server URL, see “Host Addresses” on page 13.

Example Test Transaction
“TRXTYPE=S&TENDER=K&CHKTYPE=P&PARTNER=&VENDOR=&USER=&PWD=&
AMT=42.00&STREET=1234 Main&CITY=Buffalo&DL=CA123456&CHKNUM=1001&EMAIL=&MICR=&NAME=Sally&STATE=CA&ZIP=95050”
TABLE B.2

MICR values for testing

MICR

HOSTCODE

TeleCheck Result

1234567804390850001001

000800

Check Approved ECA

1234567804390850011001

000801

Check Approved No ECA

1234567804390850021001

000802

Check Approved ECA, No Guarantee

1234567804390850031001

000803

Check Approved No ECA, No Guarantee

1234567804390850041001

000804

Check Decline Negative Data

1234567804390850051001

000805

Check Decline Scoring

1234567804390850071001

000807

Check Failed

Preparing for TeleCheck Production Transactions
Before going into production with your check integration, you must certify your storefront
with TeleCheck. To begin the certification process, send an e-mail to
ica_certification@telecheck.com. Be sure to include the following information:
z
z

Your test website address where test transactions can be processed
The name, e-mail address, and phone number of the person to contact about any needed
corrections.

The certification process usually takes 2-3 days.
Use the host address of the live server described in “Host Addresses” on page 13.

Responses to Telecheck Transactions
When a transaction finishes, PayPal returns a response string made up of name-value pairs.
For example:
RESULT=0&PNREF=VXYZ01234567&HOSTCODE=000500&RESPMSG=Approved

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic Check Transactions
HOSTCODE Values

Telecheck transaction response values are described in Table B.3.
TABLE B.3

Transaction responses common to all tender types

Field

Description

Type

Length

RESULT

The outcome of the attempted transaction. A result of 0 (zero) indicates
the transaction was approved. Any other number indicates a decline or
error. RESULT values are described in “Responses to Transaction
Requests” on page 53.

Numeric

Variable

PNREF

PayPal Reference ID, a unique number that identifies the transaction.
PNREF is described in “HOSTCODE Values” on page 93.

Alphanumeric

HOSTCODE

TeleCheck’s response code representing the results of the transaction
authorization attempt. These values are described in “HOSTCODE
Values” on page 93.

Numeric

RESPMSG

A descriptive message associated with decline or error RESULTs.
Response messages are described in “Responses to Transaction
Requests” on page 53.

Alphanumeric

Variable

HOSTCODE Values
The HOSTCODE reflects the TeleCheck server result. The following tables describe the
HOSTCODE values. TeleCheck requires that you display certain verbiage to the purchaser
based on the returned HOSTCODE value—check with TeleCheck for details.
N O T E : Many of these codes will not be encountered under normal operating conditions—they

are included as a troubleshooting aid. In the tables, the Frequency column indicates the
likelihood that you will encounter the code.
TABLE B.4

Sale Approved HOSTCODE values

Code

Response

Description

Frequency

000500

Sale Approved

Sale Approved by credit card network

Common

000501

Sale Time-out

Sale transaction time-out in credit card network

Common

000502

Test Card

Test card sale approved (never billed)

Common

000504

ANI Sale Approved

900/Telco sale approved

ANI bill only

000505

PB Sale Approved

Private billing sale approved

PB only

000800

Sale Approved

Direct Check Sale/ECA approved

Direct Check

000801

Sale Approved

Direct Check Sale approved (no ECA)

Direct Check

000802

Sale Approved

Direct Check Sale/ECA approved no guarantee

Direct Check

000803

Sale Approved

Direct Check Sale approved no ECA no guarantee

Direct Check

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic Check Transactions
HOSTCODE Values

TABLE B.5
Code

Response

Description

Frequency

000300

Sale Declined

Sale declined by credit card network

Common

000301

Sale Rejected

Sale does not meet risk standards

Common

000804

Check Declined

Direct Check Sale declined negative data

Direct Check

000805

Check Declined

Direct Check Sale Decline Scoring

Direct Check

000807

Check Failure

Direct Check Sale

Direct Check

TABLE B.6

Inquiry Approved HOSTCODE values

Code

Response

Description

Frequency

000400

OTB Approved

Preauthorization approved. AVS matches if provided.

Common

000401

No Response

No response from credit card network for preauth.

Common

000402

AVS Time-out

Preauthorization approved, AVS timed out

AVS only

000403

PB Approved

Private billing approved.

PB only

000410

Positive Record

Previous positive history.

Common

000420

Test card Approved

Test Card

Common

000421

OTB/AVS Approval

Preauthorization approved, AVS match

AVS only

000503

ANI Bill approved

900/TELCO billing approved

ANI bill only

TABLE B.7

General Failure HOSTCODE values

Code

Response

Description

Frequency

000100

General Failure

General host based failure

Rare

000101

Invalid Value

Invalid for one or more fields in transaction

Common

999999

Unknown Response

TeleCheck received an unknown response

Rare

TABLE B.8

Sale Declined HOSTCODE values

Inquiry Declined HOSTCODE values

Code

Response

Description

Frequency

000200

Preauth Declined

Declined by credit card or Telco network (LIDB)

Common

000201

PIN Mismatch

Mismatch on PIN stored in TeleCheck database

Not Used

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic Check Transactions
HOSTCODE Values
TABLE B.8

Inquiry Declined HOSTCODE values

Code

Response

Description

Frequency

000210

Negative Card Record

Temporary and permanent blocks. Prior OTB decline, sale
decline or CS block Transaction falls below minimum
scoring standards. Most frequently used for risk scoring
declines, where a transaction falls below minimum
standards.

Common

000215

Negative ANI Record

ANI previously blocked by CS

Common

000220

Chargeback Card

Card with chargeback history

Common

000225

Chargeback ANI

ANI with chargeback history

Common

000230

Exceed card profilea

Card has exceeded usage limits

Uncommon

ANI has excessive number of cards

Uncommon

000240

Too many Cards

000250

Exceed ANI profilea

ANI has exceeded usage limits

Uncommon

000260

Too Many Phonesa

Card has been used from excessive ANI

Uncommon

000270

OTB/AVS Decline

OTB decline and AVS mismatch

AVS OTB
only

000271

OTB/AVS Decline

OTB approved and AVS mismatch

AVS OTB
only

000272

OTB/AVS Decline

OTB decline and AVS match

AVS OTB
only

000280

Risk Referral

Temporary Risk referral, AVS necessary

Common

000281

Card Not Qualified

Card does not meet minimum bank restrictions

Not Used

000282

PB Risk Referral

Private billing risk referral, AVS necessary

PB Only

a. This

data is included in risk scoring decisions and a response of 210 has higher precedence.

Payflow Pro Developer’s Guide

Performing TeleCheck Electronic Check Transactions
HOSTCODE Values

Payflow Pro Developer’s Guide

Submitting Purchasing Card
Level 2 and Level 3 Transactions
PayPal Payment Services supports passing Purchasing Card Level 2 information (such as
purchase order number, tax amount, and charge description) in the settlement file.
If additional required invoice information and line item details are included in the transaction,
PayPal formats Purchasing Card Level 3 information in an appropriate format, for example,
EDI (Electronic Data Interchange) 810 format as required by American Express during
settlement processing.

About Purchasing Cards
Purchasing Cards are used in the procurement process to eliminate paper-based order systems
and associated costs, to improve control and accountability through itemized statements, to
foster better risk controls through spending limits and buying from approved vendors, to
reduce administrative overhead because employees are empowered to make small purchases,
and to enable enterprises to negotiate better contract pricing and discounts with suppliers
through the use of vendor detail reports.
To promote acceptance and usage of Purchasing Card programs, card issuers have established
incentive rates for merchants. These rates are available for merchants who comply at either
Level 2 or Level 3 (described in the next section). Transactions that comply at Level 1 qualify
as normal credit card transactions.
N O T E : Card

issuing institutions perform strict data verification on the enhanced data that is
submitted with Level 2 or Level 3 transactions. Issuers may charge stiff penalties if
fields contain either inaccurate or filler data. Only transactions that contain accurate
data are eligible for the incentive rates.

About Program Levels
The term Level does not apply to the card, but to the transaction data submitted for that card.
Generally, a higher level means more detailed data for reporting.
Table C.1 describes the transaction levels that are recognized.
TABLE C.1

Transaction levels

Level

Description

Level 1

Function as normal credit cards and are authorized and associated with normal
transaction data in authorization and settlement. Any merchant who accepts
credit cards supports this level.

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
About American Express Purchasing Card Transactions - Phoenix Processor
TABLE C.1

Transaction levels

Level

Description

Level 2

Additional data regarding sales tax, customer code, purchase order number,
invoice number are captured at the point of sale. In most cases, this
information is combined with the merchant’s tax ID number, state, and postal
code data and is then passed through during settlement. For some processors
and banks, however, a Level 2 authorization may include some of this data.

Level 3

Significant additional information such as line items, product codes, item
descriptions, unit price, unit quantities, and ship-to postal data are added to the
Level 2 data to provide optimal reporting to buyers and sellers. Settlement
transactions typically carry Level 3 data.

Level 2 and Level 3 data is generally considered non-financial data. Lack of adequate data
may cause a transaction to be downgraded.
PayPal generally requires up to Level 2 information in an Authorization transaction followed
by additional Level 3 data in the associated Delayed Capture transaction. A Sale transaction
should include all Level 3 data since it is authorized and later settled.

Accepted BIN Ranges
Visa, MasterCard, and American Express publish specific Bank Identification Number (BIN)
ranges for purchasing cards. Sometimes the determination of whether a card is a purchasing
card is left to the processor (for example, TSYS Acquiring Solutions1). In other cases, the
Payflow payments gateway makes the determination based on the BIN range (for example,
FDMS South and American Express).
BIN ranges accepted for American Express Level 2 and Level 3 transactions are listed on
page 100.

About American Express Purchasing Card Transactions Phoenix Processor
The information in this section applies to transactions processed by the American Express
Phoenix Processor, not necessarily to all American Express cards. Level 2 and Level 3
purchasing card rules may differ for American Express card transactions processed by other
processors such as Paymentech or First Data Nashville.

1. Formerly Vital Processing Services

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
About American Express Purchasing Card Transactions - Phoenix Processor

Supported Transaction Types
You can submit Level 3 parameters with Delayed Capture, Sale, Credit, or Force transactions.
Level 3 data in Authorization transactions is ignored. The Payflow payments gateway decides
whether a transaction meets Level 3 requirements during authorization.
Level 3 data is passed to the American Express Phoenix processor only during settlement.

Avoiding Downgrade
If a transaction uses the purchasing card BIN range (see “Accepted BIN Ranges” on page 98)
and contains a line item but does not include all mandatory Level 3 parameters, then the
transaction succeeds but is processed as Level 2 or Level 1 during settlement (depending on
which data was passed).
For downgraded transactions, with the VERBOSITY parameter set to MEDIUM or HIGH, a
message like the following is returned in the ADDLMSGS field:
Features not processed: PCARD L3 (missing or invalid: InvoiceNumber
RequestorName)

— or —
Features not processed: PCARD L3 (line item 3 missing: Description)

For details on VERBOSITY, see Appendix D, “VERBOSITY: Viewing Processor-Specific
Transaction Results.”

Submitting Successful Level 3 Transactions
If a transaction uses the purchasing card BIN range, contains all mandatory Level 3 fields, and
has at least one line item (with all mandatory line item fields), the Payflow payments gateway
flags it as Level 3.

Edit Check
PayPal performs an edit check on the transaction’s amount fields to ensure that all line item
and tax amounts balance.
If the edit check fails, the transaction fails with Result 4: Invalid Amount.
To pass the edit check, the following relationship must be true:
Transaction Amount = Total Tax Amount + Total Freight Amount + Total Handling
Amount + Total Line Item Amount.
Transaction Amount

Total amount for the transaction, AMT

Total Tax Amount

TAXAMT

Total Freight Amount

FREIGHTAMT, or, if not present, the summation of
L_FREIGHTAMTn for all line items

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
American Express Phoenix Purchasing Card Transaction Processing

Total Handling Amount

HANDLINGAMT, or, if not present, the summation of
L_HANDLINGAMTn for all line items

Total Line Item Amount

Summation of L_QTYn * L_COSTn for all line items (n as the
line item number). For example, if there are 2 line items, then the
Total Line Item Amount would be (LQTY1*LCOST1) +
(LQTY2*LCOST2)

Accepted BIN Ranges
The following BIN ranges are accepted for American Express Level 2 and Level 3
transactions:
37326
37429
37857
37859
37873
37965

American Express Phoenix Purchasing Card Transaction
Processing
The American Express Phoenix platform supports Level 2 transaction data. The parameters to
meet card acceptance and processor network (CAPN) requirements are described in Table C.2.
Level 2 parameters supported for legacy applications are described in Table C.3.
N O T E : Most

merchants in the United States follow CAPN requirements; international
merchants do not.There are a few exceptions. If you are not sure, contact Customer
Service. See “How to Contact Customer Support” on page 10 for contact information.

100

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
American Express Phoenix Purchasing Card Transaction Processing

American Express Phoenix Level 2 Parameters (CAPN)
TABLE C.2
Parameter

American Express Phoenix CAPN Level 2 parameters

Description

Required

Type

Length

CPC Level 2 Transaction Advice Addendum Parameters
PONUM

Purchase order number

Yes

Alphanumeric

SHIPTOZIP

Ship-to postal code (called ZIP code in the USA)

Yes

Alphanumeric

TAXAMT

Total tax amount
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56

Numeric

L_DESC1

Description of this line item; if not provided,
DESC1 (if present) is used

Alphanumeric

140

L_AMT1

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56

Numeric

L_QTY1

Quantity of this line item

Numeric

L_DESC2

Description of this line item; if not provided,
DESC2 (if present) is used

Alphanumeric

L_AMT2

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)

Numeric

L_QTY2

Quantity of this line item

Numeric

L_DESC3

Description of this line item; if not provided, DESC3
(if present) is used

Alphanumeric

L_AMT3

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)

Numeric

L_QTY3

Quantity of this line item

Numeric

L_DESC4

Description of this line item; if not provided, DESC4
(if present) is used

Alphanumeric

L_AMT4

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)

Numeric

Payflow Pro Developer’s Guide

101

Submitting Purchasing Card Level 2 and Level 3 Transactions
American Express Phoenix Purchasing Card Transaction Processing
TABLE C.2

American Express Phoenix CAPN Level 2 parameters (Continued)

Parameter

Description

Required

Type

Length

L_QTY4

Quantity of this line item

Numeric

Location Transaction Advice Addendum Parameters
MERCHANTNAME

Name of merchant

MERCHANTSTREET

Merchant’s street address (number and street name)

MERCHANTCITY

Merchant’s city

MERCHANTSTATE

Merchant’s state

MERCHANTCOUNTRY Merchant’s numeric country code
CODE
Example:
USA: 840
MERCHANTZIP

Merchant’s 5- to 9-digit ZIP (postal) code excluding
spaces, dashes, and non-numeric characters
Example: 951121737

38
Alphanumeric

Alphanumeric

Transaction Advice Detail Parameters

102

ADDLAMTn

Detail of a charge (n is the line item number, a value
from 1 - 5); use for additional breakdown of the
charge
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)
Examples: tip=3.00, convenience charge=2.00

Numeric

ADDLAMTTYPEn

A 3-digit code indicating the type of the
corresponding charge detail (n is the line item
number, a value from 1 - 5)

Alphanumeric

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
American Express Phoenix Purchasing Card Transaction Processing

American Express Phoenix Level 2 Parameters (Legacy)
TABLE C.3

American Express Phoenix Legacy Level 2 parameters

Parameter

Description

Required

Type

Length

PONUM

Purchase order number

Yes

Alphanumeric

SHIPTOZIP

Ship-to postal code (called ZIP code in the USA)

Yes

Alphanumeric

DESC1

Freeform description

Alphanumeric

DESC2

Freeform description

Alphanumeric

DESC3

Freeform description

Alphanumeric

DESC4

Freeform description

Alphanumeric

Example American Express Phoenix Level 2 Transaction Parameter String
TRXTYPE=S&ACCT=372449635311003&AMT=20.06&CITY=Mountain
View&DESC1=desc1&DESC2=desc2&DESC3=desc3&DESC4=FRT10.00&EXPDATE=1209&NAME=C
ardholder
Name&PARTNER=PayPal&PONUM=12345&PWD=pwd&SHIPTOZIP=94045&STATE=CA&STREET=123
Main St.&TENDER=C&USER=user&ZIP=123451234

American Express Phoenix Level 3 Parameters
The American Express Phoenix platform supports Level 3 transaction data. PayPal provides
the Merchant Registration data values: Supplier Name, Supplier City, Supplier State, Supplier
Postal code, Merchant No, and Federal Tax ID. The merchant provides the values listed in
Table C.4.

AMEX Name
(per American
Express
Specification)

Mandatory
/ Optional

TABLE C.4

Supplier
Reference
Number

Payflow Pro Developer’s Guide

American Express Phoenix Level 3 Parameters

Pay Flow SDK parameter
INVNUM
Defaults to PNREF if not present.

XMLPayRequest parameter
(See Payflow Pro XMLPay
Developer’s Guide for
detailed instructions.)

Format
(min/max,
type)

Invoice.InvNum

1/9, AN

103

Submitting Purchasing Card Level 2 and Level 3 Transactions
American Express Phoenix Purchasing Card Transaction Processing
American Express Phoenix Level 3 Parameters (Continued)

AMEX Name
(per American
Express
Specification)

Mandatory
/ Optional

TABLE C.4

Authorization
Code

AUTHCODE
(Passed transparently for delayed
capture. Use only with voice
authorized force capture
transactions)

ForceCapture.Authcode

Requester Name

REQNAME

ExtData ”REQNAME”

1/40, AN

Cardmember
Reference No

PONUM

BillTo.PONum

1/17, AN

Ship to ZIP

SHIPTOZIP

ShipTo.Address.ZIP

5/6, AN

Invoice Date

INVOICEDATE
Defaults to Transaction Date if not
present.

Invoice.Date

YYYYMM
DD, string

Total Transaction
Amount

AMT
The value must include a decimal
and the exact amount to the cent
(42.00, not 42). Do not include
comma separators (1234.56 not
1,234.56).

Invoice.TotalAmt

1/8 NUM

Pay Flow SDK parameter

XMLPayRequest parameter
(See Payflow Pro XMLPay
Developer’s Guide for
detailed instructions.)

Format
(min/max,
type)

N O T E : American Express Phoenix

Level 3 processing requires
that this parameter have a
maximum field length of 8
for Level 3 processing.

104

Total Tax
Amount

TAXAMT
The value must include a decimal
and the exact amount to the cent
(42.00, not 42). Do not include
comma separators (1234.56 not
1,234.56).

Invoice.TaxAmt

1/6 NUM

Charge
Description

DESC
Defaults to “NO”

Invoice.Description

1/40, AN

Total Freight Amt

FREIGHTAMT

Invoice.FreightAmt

1/15, AN

Total Handling
Amt

HANDLINGAMT

Invoice.HandlingAmt

1/15, AN

Quantity Invoiced

L_QTYn

Item.Quantity

1/10, NUM

Unit of Measure

L_UOMn

Item.UnitOfMeasurement

2/2, AN

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
American Express Phoenix Purchasing Card Transaction Processing
American Express Phoenix Level 3 Parameters (Continued)

Mandatory
/ Optional

TABLE C.4

Pay Flow SDK parameter

XMLPayRequest parameter
(See Payflow Pro XMLPay
Developer’s Guide for
detailed instructions.)

Format
(min/max,
type)

L_COSTn

Item.UnitPrice

1/15, NUM

Item Description

L_DESCn

Item.Description

1/80, AN

Supplier Catalog
No

L_CATALOGNUMn

Item.CatalogNumber

1/20, AN

Cost Center No

L_COSTCENTERNUMn

Item.CostCenterNumber

1/30, AN

Supplier Stock
Keeping Unit
Number

L_PRODCODEn

Item.SKU

1/30, AN

Universal Product
Code

L_UPCn

Item.UPC

1/30, AN

Item Tax Amount

L_TAXAMTn

Item.TaxAmt

1/6, NUM

Freight Amount

L_FREIGHTAMTn

Item.FreightAmt

1/15, NUM

Handling Amount

L_HANDLINGAMTn

Item.HandlingAmt

1/15, NUM

Tracking Number

L_TRACKINGNUMn

Item.TrackingNumber

1/30, AN

Drop-off
Address1

L_PICKUPSTREETn

Item.PickUp.Address.Street

1/40, AN

Drop-off City

L_PICKUPCITYn

Item.PickUp.Address.City

2/30, AN

Drop-off State

L_PICKUPSTATEn

Item.PickUp.Address.State

2/2, AN

Drop-off ZIP

L_PICKUPZIPn

Item.PickUp.Address.ZIP

3/15, AN

Drop-off Country

L_PICKUPCOUNTRYn

Item.PickUp.Address.Country

2/3, AN

UNSPSC Code

L_UNSPSCCODEn

Item.UNSPSCCode

1/30, AN

AMEX Name
(per American
Express
Specification)
Unit Price

Example American Express Phoenix Level 3 Transaction Parameter String
TRXTYPE=S&TENDER=C&partner=partner&PWD=test&USER=test&ACCT=378734493671000&EXPDATE=12
13&AMT=5.00&COMMENT1=PCARD Test&COMMENT2=Testing&ZIP=940151234&STREET=123 Lincoln
WAY&CVV2=052&SHIPTOCOUNTRY=USA&CUSTCODE=12345&FREIGHTAMT=1.00&ORDERDATE=021700&HANDLI
NGAMT=1.00&PONUM=1234567890123456789012345&SHIPFROMZIP=940151234&SHIPTOZIP=940151234&
TAXAMT=1.00&TAXEXEMPT=N&L_UPC1=PN&L_QTY1=1&L_DESC1=Test
123&L_UOM1=12&L_COST1=1.00&L_PRODCODE1=123&L_COSTCENTERNUM1=55&L_TAXAMT1=0&L_QTY2=1&L
_UPC1=PN&L_DESC2=Test&L_UOM2=12&L_COST2=1.00&L_PRODCODE2=1234&L_COSTCENTERNUM2=55&L_T
AXAMT2=1.00&REQNAME=Robert&SHIPTOZIP=543210&INVNUM=123456789&VERBOSITY=2

Payflow Pro Developer’s Guide

105

Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing

First Data Merchant Services (FDMS) Nashville Purchasing Card
Transaction Processing
N O T E : FDMS

Nashville supports Level 2 transaction processing only.

The following parameters are recommended to obtain the best rates for purchasing card
transactions with FDMS Nashville.
TABLE C.5

106

FDMS commercial card parameters

Parameter

Description

Required

Type

Length

COMMCARD

One-character value representing type of
purchasing card account number sent.
P Purchase Card
C Corporate Card
B Business Card
U Unknown (default)
N None

No (defaults to
U - Unknown)

Alphanumeric

DUTYAMT

Sometimes called import tax.
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not
include comma separators (1234.56 not
1,234.56).

Currency

FREIGHTAMT

Freight amount.
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not
include comma separators (1234.56 not
1,234.56)..

Currency

PONUM

Purchase order number.

No (but
provides best
rate when used)

Alphanumeric

SHIPTOZIP

Ship to postal code (called ZIP code in the USA).

No (but
provides best
rate when used)

Numeric

TAXAMT

Tax amount.
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not
include comma separators (1234.56 not
1,234.56)..

No (but
provides best
rate when used)

Currency

TAXEXEMPT

Is the customer tax exempt? Y or N

Alpha

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing

First Data Merchant Services (FDMS) North Purchasing Card
Transaction Processing
The following parameters are recommended to obtain the best rates for Level 2 and Level 3
purchasing card transactions with FDMS North:
TABLE C.6

FDMS North purchasing card parameters

Parameter

Description

Required

Type

Length

SHIPTOCOUNTRY

Destination country code. Visa and MasterCard
are different. Refer to country code tables. (See
Appendix F, “ISO Country Codes)

Alpha

DISCOUNT

Discount amount on total sale

Currency

DUTYAMT

Sometimes called import tax.
If the currency uses a decimal, then the value
must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma
separators (1234.56 not 1,234.56)
See “FDMS South Currency Codes and Decimal
Positions” on page 162.

Currency

FREIGHTAMT

Freight amount
If the currency uses a decimal, then the value
must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma
separators (1234.56 not 1,234.56).
See “FDMS South Currency Codes and Decimal
Positions” on page 162.

Currency

PONUM

Purchase order number / merchant-related data.

No (but
provides
best rate
when used)

Alphanumeric

SHIPFROMZIP

The postal code (called ZIP code in the USA)
from which shipping occurs.

No (but
provides
best rate
when used)

Numeric

SHIPTOZIP

Ship to postal code (called ZIP code in the USA).

No (but
provides
best rate
when used)

Numeric

Payflow Pro Developer’s Guide

107

Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing
TABLE C.6

FDMS North purchasing card parameters (Continued)

Parameter

Description

Required

Type

Length

TAXAMT

Tax amount.
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not include
comma separators (1234.56 not 1,234.56). See
“FDMS South Currency Codes and Decimal
Positions” on page 162.

No (but
provides
best rate
when used)

Currency

FDMS North Purchasing Card Line Item Parameters
Line item data (Level 3) describes the details of the item purchased and can be passed for each
transaction. The convention for passing line item data in name/value pairs is that each
name/value starts with L_ and ends with n where n is the line item number. For example
L_QTY0=1 is the quantity for line item 0 and is equal to 1, with n starting at 0. In addition, the
SHIPFROMZIP parameter is required for Level 3 transactions.
TABLE C.7

108

FDMS North line item parameters

Parameter

Description

Required

Type

Length

L_QTYn

Quantity (whole units only).

Yes

Numeric

L_COMMCODEn

Item commodity code.

Alphanumeric

L_DESCn

Item description.

Alphanumeric

L_UOMn

Item unit of measure. See “Units of Measure” on
page 157.

Alpha

L_COSTn

Cost per item, excluding tax.

Currency

L_UPCn

Supplier specific product code.

Alphanumeric

L_DISCOUNTn

Discount per line item.

Currency

L_AMTn

Total line item amount including tax and discount. +
for debit, - for credits.

Yes

Currency

L_TAXAMTn

Line item tax amount.

Currency

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing

First Data Merchant Services South (FDMS) Purchasing Card
Transaction Processing
The following parameters are recommended to obtain the best rates for Level 2 and Level 3
purchasing card transactions with FDMS South.
TABLE C.8

FDMS South Level 2 and Level 3 purchasing card parameters

Parameter

Description

Required

Type

Length

CITY

Cardholder’s city.

Alpha

SHIPTOCOUNTRY

Destination Country Code. Visa and MasterCard
are different. Refer to Country Code tables. (See
Appendix F, “ISO Country Codes)

Alpha

CUSTCODE

Customer code/customer reference ID.

Alphanumeric

DISCOUNT

Discount amount on total sale.

Currency

DUTYAMT

Sometimes called import tax.
If the currency uses a decimal, then the value
must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma
separators (1234.56 not 1,234.56).
See “FDMS South Currency Codes and Decimal
Positions” on page 162.

Currency

FIRSTNAME

Cardholder’s first name.

Alpha

FREIGHTAMT

Freight amount.
If the currency uses a decimal, then the value
must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma
separators (1234.56 not 1,234.56)).
See “FDMS South Currency Codes and Decimal
Positions” on page 162.

Currency

INVNUM

Merchant invoice number. This reference number
(PNREF—generated by PayPal) is used for
authorizations and settlements.
The acquirer decides if this information will
appear on the merchant’s bank reconciliation
statement.

Alphanumeric

LASTNAME

Cardholder’s last name.

Alpha

ORDERDATE

Order date.
Format is mmddyy with no slashes or dashes. For
example,
July 28, 2003 is 072803.

Numeric

Payflow Pro Developer’s Guide

109

Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
TABLE C.8

FDMS South Level 2 and Level 3 purchasing card parameters (Continued)

Parameter

Description

Required

Type

Length

ORDERTIME

Order time and date. Format is either YYYY-MMDD or YYYY-MM-DD HH:MI:SS (where HH is in
24-hour time).
If the value does not conform to one of the
formats or if the date is not valid (for example,
2004-17-35), then the transaction is rejected
with a RESULT=7 (SIG_FIELD_ERR) and
RESPMSG=Invalid ORDERTIME.
A truncated version of the ORDERTIME value (up
to 7 characters) overwrites any value provided by
ORDERDATE.
If no value is provided, a NULL value is stored.

Alphanum
eric

PONUM

Purchase order number / merchant-related data.

No (but
provides
best rate
when used)

Alphanumeric

SHIPFROMZIP

The postal code (called ZIP code in the USA)
from which shipping occurs.

No (but
provides
best rate
when used)

Numeric

SHIPTOZIP

Ship to postal code (called ZIP code in the USA).

No (but
provides
best rate
when used)

Numeric

STATE

Cardholder’s state.

Alpha

SWIPE

Allows Track 1 and Track 2 data to be passed to
enable a card-present transaction.

Alphanumeric

TAXAMT

Tax amount.
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not
include comma separators (1234.56 not
1,234.56). See “FDMS South Currency Codes
and Decimal Positions” on page 162.

No (but
provides
best rate
when used)

Currency

TAXEXEMPT

Is the customer tax exempt? Y or N

Alpha

FDMS South Line Item Parameters
Line item data (Level 3) describes the details of the item purchased and can be can be passed
for each transaction. The convention for passing line item data in name-value pairs is that each

110

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing

name-value starts with L_ and ends with n where n is the line item number. For example
L_QTY0=1 is the quantity for line item 0 and is equal to 1, with n starting at 0.
TABLE C.9

FDMS South purchasing card line item parameters

Parameter

Description

Required

Type

Length

L_QTYn

Quantity (whole units only).

Yes

Numeric

L_COMMCODEn

Item commodity code.

Alphanumeric

L_DESCn

Item description.

Alphanumeric

L_UOMn

Item unit of measure. See “Units of Measure” on
page 157.

Alpha

L_COSTn

Cost per item, excluding tax.

Currency

L_PRODCODEn

Supplier-specific product code.

Alphanumeric

L_DISCOUNTn

Discount per line item.

Currency

L_AMTn

Total line item amount including tax and discount. +
for debit, - for credits.

Yes

Currency

L_TAXAMTn

Line item tax amount.

Currency

Example FDMS South Purchasing Card Level 2 and 3 Parameter String
“TRXTYPE=S&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&
PWD=x1y2z3&STATE=CA&FIRSTNAME=John&LASTNAME=Smith&CITY=Redwood&SHIPTOCOUNTR
Y=USA&CUSTCODE=12345&DISCOUNT=.25&DUTYAMT=34.00&FREIGHTAMT=12.00&INVNUM=123
456789&ORDERDATE=021700&PONUM=1234567890123456789012345&SHIPFROMZIP=9401512
34&SHIPTOZIP=94065&TAXAMT=1.00&TAXEXEMPT=Y”

Example FDMS South Line Item Parameter String
“TRXTYPE=S&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&
PWD=x1y2z3&STATE=CA&FIRSTNAME=John&LASTNAME=Smith&CITY=Redwood&SHIPTOCOUNTR
Y=USA&CUSTCODE=12345&DISCOUNT=.25&DUTYAMT=34.00&FREIGHTAMT=12.00&INVNUM=123
456789&ORDERDATE=021700&PONUM=1234567890123456789012345&SHIPFROMZIP=9401512
34&SHIPTOZIP=94065&TAXAMT=1.00&TAXEXEMPT=Y&L_QTY1=1&L_UPC1=PN&L_DESC1=Test&
L_UOM1=INQ&L_COST1=1.00&L_PRODCODE1=12345&L_DISCOUNT1=.25&&L_AMT1=.75&L_TAX
AMT1=0”

Payflow Pro Developer’s Guide

111

Submitting Purchasing Card Level 2 and Level 3 Transactions
Global Payments - Central Purchasing Card Transaction Processing

Global Payments - Central Purchasing Card Transaction
Processing
Global Payments - Central (MAPP) supports Level 2 parameters for MasterCard, and Visa
Sale, Credit, and Delayed Capture transactions.

Global Payments - Central Level 2 Parameters
Both Level 2 parameters in Table C.10 are required to get the discount rate. You must pass the
following parameters.
TABLE C.10 Global Payments - Central Level 2 parameters
Data Items

Mandatory /
Optional

Payflow Parameter

Format
(min/max, type)

Customer Code

CUSTCODE

1/16, Char

Sales Tax

TAXAMT
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not include
comma separators (1234.56 not 1,234.56). To qualify
for Level 2 discounts, this value must not be all zeros
or blank spaces.

NUM

Example Global Payments - Central Level 2 Visa or MasterCard Transaction
Parameter String
TRXTYPE=S&ACCT=5105105105105100&AMT=20.10&CITY=Mountain View&COMMENT1=L2
Testing&EXPDATE=1209&NAME=Cardholder
Name&PARTNER=PayPal&PWD=pwd&STATE=CA&STREET=123 Main
St.&TENDER=C&USER=user&ZIP=94043&CUSTCODE=123456&TAXAMT=1.34

Global Payments - East Purchasing Card Transaction
Processing
Global Payments - East (NDCE) supports Level 2 parameters for American Express,
MasterCard, and Visa.

112

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing

Global Payments - East Level 2 Parameters
Both Level 2 parameters listed in Table C.11 are required to get the discount rate. You must
pass these parameters in Authorization and Sale transactions.
TABLE C.11 Global Payments - East Level 2 parameters
Data Items

Payflow Parameter

Required

Type

Length
(min/ max)

Customer Code

CUSTCODE

Yes

char

1/16

Sales Tax

TAXAMT
The value must include a decimal and the
exact amount to the cent (42.00, not 42). Do
not include comma separators (1234.56 not
1,234.56). To qualify for Level 2 discounts,
this value must not be all zeros or blank
spaces.

Yes

numeric

Example Global Payments - East Level 2 Visa or MasterCard Transaction
Parameter String
TRXTYPE=S&ACCT=5105105105105100&AMT=20.10&CITY=Mountain View&COMMENT1=L2
Testing&EXPDATE=1209&NAME=Cardholder
Name&PARTNER=PayPal&PWD=pwd&STATE=CA&STREET=123 Main
St.&TENDER=C&USER=user&ZIP=94043&CUSTCODE=123456&TAXAMT=1.34

Global Payments - Central (MAPP) supports Level 2 for MasterCard, and Visa Sale, Credit,
and Delayed Capture transactions.

Merchant e-Solutions Purchasing Card Transaction Processing
Merchant e-Solutions Level 2 Parameters
Merchant e-Solutions supports MasterCard and Visa for Level 2 processing.
Merchant e-Solutions indicates in the authorization response whether or not the credit card in
the transaction is a commercial card. Based in the commercial card indicator, PayPal will
format the Level 2 information in the settlement request.

Payflow Pro Developer’s Guide

113

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing
Merchant e-Solutions Level 2 Transaction Data

Level 2 values marked as mandatory in Table C.12 are required to get the discount rate.
TABLE C.12 Merchant e-Solutions Level 2 parameters
Merchant eSolutions
Name

Mandatory /
Optional

Payflow Parameter

Format
(min/max,
type)

Cust Ref ID

PONUM

1/17, AN

Tax Amount

TAXAMT
The value must include a decimal and the exact amount to the
cent (42.00, not 42). Do not include comma separators
(1234.56 not 1,234.56).

NUM

Tax Amount
Identifier

TAXEXEMPT, Y or N

1, A

Example Merchant e-Solutions Level 2 Visa Transaction Parameter String
TRXTYPE=S&ACCT=4111111111111111&AMT=20.02&CITY=Mountain View&COMMENT1=L2
Testing&EXPDATE=1209&INVNUM=661254585&NAME=CardHolder
Name&PARTNER=PayPal&PWD=pwd&STATE=CA&STREET=123 Main
St.&TAXAMT=1.01&TAXEXEMPT=N&TENDER=C&USER=user&ZIP=94043

Merchant e-Solutions Level 3 MasterCard Parameters
To qualify for Level 3, the authorization response for the transaction must have the
commercial card indicator set and one or more line items should be present in the Delayed
Capture or Sale request.
Level 2 transaction parameters marked as mandatory are required for Level 3 transactions.
Level 3 transactions that do not include the mandatory Level 2 values are rejected.
IMPO RTANT: The values required for Level 3 status vary by bank, so contact your bank for

details.

114

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing

Merchant e-Solutions Level 2 MasterCard Parameters Required for Level 3
Transactions
TABLE C.13 Merchant e-Solutions Level 2 MasterCard parameters for Level 3 line
item transactions
Merchant
e-Solutions
Name

Mandatory
/ Optional

Purchase Identifier

PONUM
Value of TransID is sent if no value is provided.

25, AN

Tax Amt

TAXAMT
The value must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma
separators (1234.56 not 1,234.56).

NUM

Lcl Tax

LOCALTAXAMT

12, NUM

Lcl Tax Incl Flag

TAXEXEMPT, Y or N

1, AN

National Tax Amt

NATIONALTAXAMT
You may omit this parameter if there is no such tax.

12, NUM

Purch Ord #/Cust
Ref ID

INVNUM
Value of PNREF is sent if no value is provided.

9, AN

Payflow Parameter

Length,
Data Type

Merchant e-Solutions Level 3 MasterCard Extended Data

The parameters listed in Table C.14 apply to Level 3 MasterCard transactions as extended
data.
TABLE C.14 Merchant e-Solutions Level 3 MasterCard Extended Data
Merchant e-Solutions
Name

Mandatory /
Optional

Payflow Parameter

Length,
Data Type

Freight Amt

FREIGHTAMT

12, NUM

Duty Amt

DUTYAMT

12, NUM

Dest Postal / ZIP Code

SHIPTOZIP
The ZIP code of the address to which the goods are
shipped.

10, AN

Ship from Postal / ZIP
Code

SHIPFROMZIP
The postal code (called ZIP code in the USA) from
which shipping occurs.

10, AN

Dest Country Code

SHIPTOCOUNTRY

4, AN

Alt Tax Amt

ALTTAXAMT

9, NUM

Payflow Pro Developer’s Guide

115

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing
Merchant e-Solutions Level 3 MasterCard Line item Detail Records
TABLE C.15 Merchant e-Solutions Level 3 MasterCard line item detail record
Merchant e-Solutions Name

Mandatory /
Optional

Payflow Parameter

Length,
Data Type

N O T E : For these values, n is a sequence counter that should begin with 1 and increase in sequence. Each line item

should also contain quantity (L_QUANTITY) and unit price (L_COST) fields.
Item Descriptor

L_DESCn

35, AN

Product Code

L_UPCn

12, AN

Quantity

L_QTYn

12, NUM

Unit of Measure/Code

L_UOMn

12, AN

Tax Rate Applied

L_TAXRATEn

4, NUM

Tax Type Applied

L_TAXTYPEn

4, AN

Tax Amount

L_TAXAMTn

12, NUM

Discount Amount

L_DISCOUNTn

12, NUM

Example Merchant e-Solutions Level 3 MasterCard Transaction Parameter
String
TRXTYPE=S&TENDER=C&PARTNER=Partner&USER=User&PWD=Password&ACCT=552500000000
0005&EXPDATE=0406&AMT=1.00&STREET=5199
JOHNSON&ZIP=94588&ALTTAXAMT=1.00&CUSTVATREGNUM=11111&LOCALTAXAMT=1.00&NATIO
NALTAXAMT=1.00&COMMCODE=22222&VATAXAMT=1.00&VATAXPERCENT=10&TAXEXEMPT=Y&DIS
COUNT=1.00&FREIGHTAMT=1.00&DUTYAMT=1.00&SHIPTOZIP=33333&SHIPFROMZIP=44444&S
HIPTOCOUNTRY=840&ORDERDATE=020725&L_COMMCODE1=123456789ABC&L_DESC1=Line
item 1
description&L_UPC1=CBA987654321&L_QTY1=1&L_UOM1=123456789012&L_COST1=1.00&L
_TAXAMT1=1.00&L_TAXRATE1=1.00&L_DISCOUNT1=1.00&L_AMT1=1.00&L_TAXTYPE1=TT3

Merchant e-Solutions Level 3 Visa Parameters
To qualify for Level 3 transactions, the authorization response for the transaction must have
the commercial card indicator set and one or more line items should be present in the Delayed
Capture or Sale request.
Level 2 transaction parameters marked as mandatory are required for Level 3 transactions.
Level 3 transactions that do not include the mandatory Level 2 values are rejected.
IMPO RTANT: The values required for Level 3 status vary by bank, so contact your bank for

details.

116

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing

Merchant e-Solutions Level 2 Visa Parameters Required for Level 3
Transactions
TABLE C.16 Merchant e-Solutions Level 2 Visa parameters for Level 3 line item
transactions
Merchant eSolutions
Name

Mandatory
/ Optional

Payflow Parameter

Length,
Data Type

Purchase
Identifier

PONUM
Value of TransID is sent if no value is provided.

25, AN

Tax Amount

TAXAMT
The value must include a decimal and the exact amount to the
cent (42.00, not 42). Do not include comma separators
(1234.56 not 1,234.56).

NUM

Lcl Tax

LOCALTAXAMT

12, NUM

TAXEXEMPT, Y or N.

1, AN

Lcl Tax Incl Flag
National Tax Amt

NATIONALTAXAMT

12, NUM

Purch Ord #/Cust
Ref ID

INVNUM
Value of TransID is sent if no value is provided.

9, AN

Merchant e-Solutions Level 3 Visa Extended Data

The parameters listed in Table C.17 apply to Level 3 Visa transactions as extended data.
TABLE C.17 Merchant e-Solutions Level 3 Visa extended data
Merchant eSolutions Name

Mandatory /
Optional

Summary Commodity
Code

COMMCODE
Commodity code identifier for the business.

4, AN

Discount Amt

DISCOUNT

12, NUM

Freight Amt

FREIGHTAMT

12, NUM

Duty Amt

DUTYAMT

12, NUM

Order Date

ORDERDATE
Format is mmddyy with no slashes or dashes. For
example,
July 28, 2003 is 072803

6, NUM

Dest Postal / ZIP Code

SHIPTOZIP
The ZIP code of the address to which the goods are
shipped.

10, AN

Payflow Pro Developer’s Guide

Payflow Parameter

Length,
Data Type

117

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing
TABLE C.17 Merchant e-Solutions Level 3 Visa extended data (Continued)

118

Merchant eSolutions Name

Mandatory /
Optional

Length,
Data Type

Ship from Postal / ZIP
Code

SHIPFROMZIP
The postal code (called ZIP code in the USA) from
which shipping occurs.

10, AN

Dest Country Code

SHIPTOCOUNTRY

4, AN

VAT Registration
Number

VATREGNUM
Can be part of the registration data or passed with each
transaction.

20, AN

Unique VAT Inv Ref #

INVNUM
Can be part of the registration data or passed with each
transaction.

9, AN

Cust VAT Registr #

CUSTVATREGNUM

13, AN

VAT/Tax Amt
(Freight/Ship)

VATTAXAMT

12, NUM

VAT/Tax Rate
(Freight/Ship)

VATTAXPERCENT

4, NUM

Payflow Parameter

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Merchant e-Solutions Purchasing Card Transaction Processing

Merchant e-Solutions Level 3 Visa Line item Detail Records
TABLE C.18 Merchant e-Solutions Level 3 Visa line item detail record
Merchant e-Solutions Name

Mandatory /
Optional

Payflow Parameter

Length, Data
Type

N O T E : For these values, n is a sequence counter that should begin with 1 and increase in sequence. Each line item

should also contain quantity (L_QUANTITY) and unit price (L_COST) fields.
Item Commodity Code

L_COMMCODEn

12, AN

Item Descriptor

L_DESCn

35, AN

Product Code

L_UPCn

12, AN

Quantity

L_QTYn

12, NUM

Unit of Measure/Code

L_UOMn

12, AN

Unit Cost

L_COSTn

12, NUM

VAT/Tax Amount

L_TAXAMTn

12, NUM

VAT/Tax Rate

L_TAXRATEn

4, NUM

Discount Per Line Item

L_DISCOUNTn

12, NUM

Line-item Total

L_AMTn

12, NUM

Example Merchant e-Solutions Level 3 Visa Transaction Parameter String
TRXTYPE=S&TENDER=C&PARTNER=Partner&USER=User&PWD=Password&ACCT=411111111111
1111&EXPDATE=0406&AMT=1.00&STREET=5199
JOHNSON&TAXAMT=106&ZIP=94588&ALTTAXAMT=1.00&CUSTVATREGNUM=11111&LOCALTAXAMT
=1.01&NATIONALTAXAMT=1.02&COMMCODE=22222&VATAXAMT=1.03&VATAXPERCENT=55&TAXE
XEMPT=N&DISCOUNT=.50&FREIGHTAMT=1.00&DUTYAMT=1.00&SHIPTOZIP=33333&SHIPFROMZ
IP=44444&SHIPTOCOUNTRY=840&ORDERDATE=020725&L_COMMCODE1=123456789ABC&L_DESC
1=Line item 1
description&L_UPC1=CBA987654321&L_QTY1=1&L_UOM1=123456789012&L_COST1=1.50&L
_TAXAMT1=1.05&L_TAXRATE1=12&L_DISCOUNT1=.50&L_AMT1=1.00&L_TAXTYPE1=TT1

Payflow Pro Developer’s Guide

119

Submitting Purchasing Card Level 2 and Level 3 Transactions
Elavon (Formerly Nova) Purchasing Card Transaction Processing

Elavon (Formerly Nova) Purchasing Card Transaction
Processing
Elavon supports Level 2 for Visa or MasterCard Sale, Credit, or Delayed Capture transactions.

Elavon Level 2 Parameters
Both Level 2 parameters listed in Table C.19 are required to get the discount rate. You must
pass these parameters in Authorization and Sale transactions.
TABLE C.19 Elavon Level 2 parameters

Data Items

Mandatory /
Optional

Format
(min/max,
type)

Payflow Parameter

Customer
Code

CUSTCODE
Value of {ServerID}{TransID} is sent if no value is provided.

1/16, char

Sales Tax

TAXAMT
Value of 0 (zero) is sent if no value is provided.
The value must include a decimal and the exact amount to the cent
(42.00, not 42). Do not include comma separators (1234.56 not
1,234.56).

NUM

Elavon Additional Parameters
The following parameters are recommended to obtain the best rates for purchasing card
transactions with Elavon:
TABLE C.20 Elavon additional parameters

120

Parameter

Description

Required

Type

Length

COMMCARD

One-character value representing the type of
commercial card.
P Purchase Card
C Corporate Card
B Business Card
U Unknown (default)
N None

No (defaults to
U - Unknown)

PONUM

Purchase Order Number.

No (when used
provides best
rate)

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing

TABLE C.20 Elavon additional parameters (Continued)
Parameter

Description

Required

Type

Length

TAXAMT

Tax Amount.
The value must include a decimal and the exact
amount to the cent (42.00, not 42). Do not include
comma separators (1234.56 not 1,234.56).

No (when used
provides best
rate)

Currency

Example Elavon Level 2 Transaction Parameter String
TRXTYPE=S&ACCT=5105105105105100&AMT=20.10&CITY=Mountain View&COMMENT1=L2
Testing&EXPDATE=1209&NAME=Cardholder
Name&PARTNER=PayPal&PWD=pwd&STATE=CA&STREET=123 Main
St.&TENDER=C&USER=user&ZIP=94043&CUSTCODE=123456&TAXAMT=1.34

Paymentech Salem (New Hampshire) Purchasing Card
Transaction Processing
Paymentech Salem (New Hampshire) Level 2 Parameters (CAPN)
The Paymentech Salem (New Hampshire) platform supports Level 2 parameters for American
Express, MasterCard, Visa, and Switch/Solo Maestro.
The parameters to meet card acceptance and processor network (CAPN) requirements are
described in Table C.21. Level 2 parameters supported for legacy applications are described in
Table C.22.
N O T E : Most

TABLE C.21 Paymentech Salem (New Hampshire) CAPN Level 2 parameters
Parameter

Description

Required

Type

Length

CPC Level 2 Transaction Advice Addendum Parameters
PONUM

Purchase order number

Yes

Alphanumeric

SHIPTOZIP

Ship-to postal code (called ZIP code in the USA)

Yes

Alphanumeric

Payflow Pro Developer’s Guide

121

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
TABLE C.21 Paymentech Salem (New Hampshire) CAPN Level 2 parameters
(Continued)

Parameter

Description

Required

Type

Length

TAXAMT

Total tax amount
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)

Numeric

L_DESC1

Description of this line item; if not provided,
DESC1 (if present) is used

Alphanumeric

140

L_AMT1

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)

Numeric

L_QTY1

Quantity of this line item

Numeric

L_DESC2

Description of this line item; if not provided,
DESC2 (if present) is used

Alphanumeric

L_AMT2

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56))

Numeric

L_QTY2

Quantity of this line item

Numeric

L_DESC3

Description of this line item; if not provided,
DESC3 (if present) is used

Alphanumeric

L_AMT3

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56))

Numeric

L_QTY3

Quantity of this line item

Numeric

L_DESC4

Description of this line item; if not provided,
DESC4 (if present) is used

Alphanumeric

L_AMT4

Charge for this line item
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56)

Numeric

L_QTY4

Quantity of this line item

Numeric

Location Transaction Advice Addendum Parameters

122

MERCHANTNAME

Name of merchant

MERCHANTSTREET

Merchant’s street address (number and street name)

38
Alphanumeric

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing

TABLE C.21 Paymentech Salem (New Hampshire) CAPN Level 2 parameters
(Continued)

Parameter

Description

Required

MERCHANTCITY

Merchant’s city

MERCHANTSTATE

Merchant’s state

MERCHANTCOUNTRY Merchant’s numeric country code
CODE
Example:
USA: 840
MERCHANTZIP

Merchant’s 5- to 9-digit ZIP (postal) code excluding
spaces, dashes, and non-numeric characters
Example: 951121737

Type

Length

Alphanumeric

Transaction Advice Detail Parameters
ADDLAMTn

Numeric

ADDLAMTTYPEn

A 3-digit code indicating the type of the
corresponding charge detail (n is the line item
number, a value from 1 - 5)

Alphanumeric

Paymentech Salem (New Hampshire) Level 2 Parameters (Legacy)
Paymentech Salem (New Hampshire) supports Level 2 parameters for American Express,
MasterCard, Visa, and Switch/Solo Maestro.
Both Level 2 parameters listed in Table C.22 are required to get the discount rate.
TABLE C.22 Paymentech Salem (New Hampshire) Level 2 legacy parameters
Paymentech
Data Items

Mandatory /
Optional

Payflow Parameter

Format
(min/max,
type)

Customer Ref No

PONUM

1/17, char

Sales Tax

TAXAMT
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56) To qualify for Level 2
discounts, this value must not be all zeros or blank
spaces.

NUM

Payflow Pro Developer’s Guide

123

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
Example Paymentech Salem (New Hampshire) Level 2 Visa and MasterCard
Transaction Parameter String
TRXTYPE=S&TENDER=C&PARTNER=Partner&PWD=Password&USER=User&ACCT=548018000000
0024&EXPDATE=1203&AMT=1.00&COMMENT1=0508&NAME=Robert&STREET=1600&ZIP=94065&
CVV2=426&PONUM=ABCDEFGHIJ&TAXAMT=1.00
TRXTYPE=S&TENDER=C&PARTNER=Partner&PWD=Password&USER=User&ACCT=427533001234
5626&EXPDATE=1203&AMT=1.00&COMMENT1=0508&STREET=1600&ZIP=94065&CVV2=426&PON
UM=ABCDEFGHIJ&TAXAMT=1.00
Example American Express Level 2 Transaction Parameter String
TRXTYPE=S&TENDER=C&PARTNER=Partner&PWD=Password&USER=User&ACCT=378734493671
000&EXPDATE=1203&AMT=1.00&COMMENT1=0508&NAME=Robert&STREET=1600&ZIP=94065&D
ESC=Descriptor&DESC1=Descriptor1&DESC2=Descriptor2&DESC3=Descriptor3&DESC4=
Descriptor4

Paymentech Salem (New Hampshire) Level 3 Purchasing Card Parameters
Paymentech Salem (New Hampshire) supports Level 3 parameters for MasterCard and Visa.
Both Level 2 transaction parameters are required for Level 3 transactions. Level 3 transactions
that do not include the Level 2 values are rejected.
Paymentech Salem (New Hampshire) Level 2 Parameters Required for Level 3
Transactions

Both Level 2 parameters listed in Table C.23 are required to get the discount rate.
TABLE C.23 Paymentech Salem (New Hampshire) Level 2 parameters

124

Paymentech Data
Items

Mandatory /
Optional

Payflow Parameter

Format
(min/max,
type)

Customer Ref No

PONUM

1/17, char

Sales Tax

TAXAMT
Must include a decimal and be exact to the cent
(42.00, not 42) and exclude comma separators
(1234.56 not 1,234.56). To qualify for Level 2
discounts, this value must not be all zeros or blank
spaces.

NUM

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing

Paymentech Salem (New Hampshire) Level 3 MasterCard Parameters
TABLE C.24 Paymentech Salem (New Hampshire) Level 3 MasterCard order and line
item parameters
Paymentech MasterCard
data item

Mandatory /
Optional

Payflow Parameter

Format
(min/max, type)

Freight Amt

FREIGHTAMT

NUM

Duty Amt

DUTYAMT

NUM

Destination ZIP

SHIPTOZIP

Destination Country

SHIPTOCOUNTRY

Ship from ZIP

SHIPPEDFROMZIP

Discount Amount

DISCOUNT

Alternate Tax ID

ALTERNATETAXID

Alternate Tax Amt

ALTERNATETAXAMT

Description

L_DESCn

Product Code

L_PRODCODEn

Quantity

L_QTYn

Unit of measure

L_UOMn

Tax Amt

TAXAMTn

Tax Rate

TAXPERCENTAGEn

Line-item Total

L_AMTn

NUM

Discount Amt

L_DISCOUNTn

NUM

Tax Type Applied

L_TAXTYPEn

Order

NUM

Line Item Record #1

NUM

Line Item Record #2

Payflow Pro Developer’s Guide

125

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
Paymentech Salem (New Hampshire) Level 3 Visa Parameters

Level 3 transactions should include at least one line item.
TABLE C.25 Paymentech Salem (New Hampshire) Level 3 Visa order and line item
parameters
Paymentech Visa data
item

Mandatory /
Optional

Payflow Parameter

Format
(min/max, type)

Freight Amt

FREIGHTAMT

NUM

Duty Amt

DUTYAMT

NUM

Destination ZIP

SHIPTOZIP

Destination Country

SHIPTOCOUNTRY

Ship from ZIP

SHIPPEDFROMZIP

Discount Amount

DISCOUNT

NUM

VAT/Tax Amt

TAXAMT

NUM

VAT/Tax Rate

TAXPERCENTAGE

Description

L_DESCn

Product Code

L_PRODCODEn

Quantity

L_QTYn

Unit of measure

L_UOMn

Tax Amt

L_TAXAMTn

Tax Rate

L_TAXRATEn

Line-item Total

L_AMTn

NUM

Discount Amt

L_DISCOUNTn

NUM

Item commodity code

L_UPCn

Unit cost

L_COSTn

Order

Line Item Record #1

NUM

Line Item Record #2

126

NUM

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
Paymentech Tampa Level 2 Purchasing Card Transaction Processing

Example Paymentech Salem (New Hampshire) Level 3 MasterCard Transaction
Parameter String
TRXTYPE=S&TENDER=C&PARTNER=Partner&PWD=Password&USER=User&ACCT=548018000000
0024&EXPDATE=1203&AMT=1.00&COMMENT1=0508&NAME=Robert&STREET=1600&ZIP=94065&
CVV2=426&PONUM=ABCDEFGHIJ&TAXAMT=1.00&FREIGHTAMT=2.00&DUTYAMT=3.00&SHIPTOZI
P=94543&SHIPTOCOUNTRY=840&SHIPFROMZIP=94509&ALTERNATETAXID=10&ALTERNATETAXA
MT=4.00&L_DESC1=MC Pcard&L_UPC1=1&L_QTY1=2&L_UOM1=3&L_TAXAMT1=4&L_TAXRATE1=
5&L_AMT1=6&L_DISCOUNT1=7&L_TAXTYPE1=8
Example Paymentech Salem (New Hampshire) Level 3 Visa Transaction
Parameter String
TRXTYPE=S&TENDER=C&PARTNER=Partner&PWD=Password&USER=User&ACCT=427533001234
5626&EXPDATE=1203&AMT=1.00&COMMENT1=0508&NAME=Robert&STREET=1600&ZIP=94065&
CVV2=426&PONUM=ABCDEFGHIJ&TAXAMT=1.00&FREIGHTAMT=2.00&DUTYAMT=3.00&SHIPTOZI
P=94543&SHIPTOCOUNTRY=840&SHIPFROMZIP=94509&DISCOUNT=4.00&VATAXAMT=5.00&VAT
AXPERCENT=10&L_DESC1=TSYS Acquiring Solutions Pcard&L_UPC1=1&L_UOM1=2&L_QTY
1=3&L_TAXAMT1=4&L_TAXRATE1=5&L_AMT1=6&L_DISCOUNT1=7&L_COMMCODE1=8&L_COST1=9
&L_COST1=10

Paymentech Tampa Level 2 Purchasing Card Transaction
Processing
Paymentech Tampa supports Level 2 purchasing card processing for MasterCard and Visa.

Payflow Pro Developer’s Guide

127

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing

Pa ymentech Tampa Level 2 Parameters
TABLE C.26 Paymentech Tampa Level 2 parameters
Paymentech
Data Items

Mandatory /
Optional

Payflow Parameter

Format
(min/max,
type)

Customer Ref
No

PONUM

1/17, char

Sales Tax

TAXAMT
The value must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma separators
(1234.56 not 1,234.56). To qualify for Level 2 discounts,
this value must not be all zeros or blank spaces.

NUM

Tax Exempt

TAXEXEMPT, Y or N
Contact your acquiring bank to determine if your
transactions are tax exempt.

Ship to ZIP
Code

SHIPTOZIP
(called ZIP code in the USA).

1/16

Example Paymentech Tampa Level 2 Visa and MasterCard Transaction
Parameter String
“TRXTYPE=S&TENDER=C&PWD=PWD&USER=USER&PARTNER=PARTNER&ACCT=4275330012345675&EXPDATE=0
209&AMT=12.59&VERBOSITY=1&STREET=123 main
street&ZIP=49801&CVV2=248&TAXAMT=1.22&PONUM=AB12345678&SHIPTOZIP=98765&TAXEXEMPT=N”

TSYS Acquiring Solutions Purchasing Card Transaction
Processing
TSYS Acquiring Solutions supports MasterCard and Visa for performing Level 2 and Level 3
purchasing card transactions.

TSYS Acquiring Solutions Level 2 Parameters
TSYS Acquiring Solutions supports MasterCard and Visa for Level 2 purchasing card
transactions.
TSYS Acquiring Solutions indicates in the authorization response whether or not the credit
card in the transaction is a commercial card. Based in the commercial card indicator, PayPal
will format the Level 2 information in the settlement request.

128

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing

Level 2 parameters marked as mandatory in Table C.27 are required to get the discount rate.
TABLE C.27 TSYS Acquiring Solutions Level 2 parameters

Name

Mandatory /
Optional

Payflow Parameter

Format
(min/max,
type)

Cust Ref ID

PONUM

1/17, AN

Tax Amount

TAXAMT
The value must include a decimal and the exact amount to the
cent (42.00, not 42). Do not include comma separators
(1234.56 not 1,234.56).

NUM

Tax Amount
Identifier

TAXEXEMPT, Y or N

1, A

Example TSYS Acquiring Solutions Level 2 Visa Transaction Parameter String
TRXTYPE=S&ACCT=4111111111111111&AMT=20.02&CITY=Mountain View&COMMENT1=L2
Testing&EXPDATE=1209&INVNUM=661254585&NAME=CardHolder
Name&PARTNER=PayPal&PWD=pwd&STATE=CA&STREET=123 Main
St.&TAXAMT=1.01&TAXEXEMPT=N&TENDER=C&USER=user&ZIP=94043

TSYS Acquiring Solutions Level 3 MasterCard Parameters
To qualify for Level 3 purchasing card transaction processing, the authorization response for
the transaction must have the commercial card indicator set and one or more line items should
be present in the Delayed Capture or Sale request.
Level 2 transaction parameters marked as mandatory are required for Level 3 transactions.
Level 3 transactions that do not include the mandatory Level 2 values are rejected.
IMPO RTANT: The values required for Level 3 status vary by bank, so contact your bank for

details.

Payflow Pro Developer’s Guide

129

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing
TSYS Acquiring Solutions Level 2 MasterCard Parameters Required for Level 3
Line Item Transactions
TABLE C.28 TSYS Acquiring Solutions Level 2 MasterCard transaction data for line
item transactions
Name

Mandatory
/ Optional

Length,
Data Type

Purchase Identifier

PONUM
Value of TransID is sent if no value is provided.

25, AN

Tax Amt

TAXAMT
The value must include a decimal and the exact amount to
the cent (42.00, not 42). Do not include comma
separators (1234.56 not 1,234.56).

NUM

Lcl Tax

LOCALTAXAMT

12, NUM

Lcl Tax Incl Flag

TAXEXEMPT, Y or N

1, AN

National Tax Amt

NATIONALTAXAMT
You may omit this parameter if there is no such tax.

12, NUM

Purch Ord #/Cust
Ref ID

INVNUM
Value of PNREF is sent if no value is provided.

9, AN

Payflow Parameter

TSYS Acquiring Solutions Level 3 MasterCard Extended Data

The parameters listed in Table C.29 apply to Level 3 MasterCard transactions as extended
data.
TABLE C.29 TSYS Acquiring Solutions Level 3 MasterCard Extended Data

130

Name

Mandatory /
Optional

Payflow Parameter

Length,
Data Type

Freight Amt

FREIGHTAMT

12, NUM

Duty Amt

DUTYAMT

12, NUM

Dest Postal / ZIP Code

SHIPTOZIP
The ZIP code of the address to which the goods are
shipped.

10, AN

Ship from Postal / ZIP
Code

SHIPFROMZIP
The postal code (called ZIP code in the USA) from
which shipping occurs.

10, AN

Dest Country Code

SHIPTOCOUNTRY

4, AN

Alt Tax Amt

ALTTAXAMT

9, NUM

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing

TSYS Acquiring Solutions Level 3 MasterCard Line item Detail Records
TABLE C.30 TSYS Acquiring Solutions Level 3 MasterCard line item detail record
Mandatory /
Optional

Name

Payflow Parameter

Length,
Data Type

N O T E : For these values, n is a sequence counter that should begin with 1 and increase in sequence. Each line item

should also contain quantity (L_QUANTITY) and unit price (L_COST) fields.
Item Descriptor

L_DESCn

35, AN

Product Code

L_UPCn

12, AN

Quantity

L_QTYn

12, NUM

Unit of Measure/Code

L_UOMn

12, AN

Tax Rate Applied

L_TAXRATEn

4, NUM

Tax Type Applied

L_TAXTYPEn

4, AN

Tax Amount

L_TAXAMTn

12, NUM

Discount Amount

L_DISCOUNTn

12, NUM

Example TSYS Acquiring Solutions Level 3 MasterCard Transaction Parameter
String
TRXTYPE=S&TENDER=C&PARTNER=Partner&USER=User&PWD=Password&ACCT=552500000000
0005&EXPDATE=0406&AMT=1.00&STREET=5199
JOHNSON&ZIP=94588&ALTTAXAMT=1.00&CUSTVATREGNUM=11111&LOCALTAXAMT=1.00&NATIO
NALTAXAMT=1.00&COMMCODE=22222&VATAXAMT=1.00&VATAXPERCENT=10&TAXEXEMPT=Y&DIS
COUNT=1.00&FREIGHTAMT=1.00&DUTYAMT=1.00&SHIPTOZIP=33333&SHIPFROMZIP=44444&S
HIPTOCOUNTRY=840&ORDERDATE=020725&L_COMMCODE1=123456789ABC&L_DESC1=Line
item 1
description&L_UPC1=CBA987654321&L_QTY1=1&L_UOM1=123456789012&L_COST1=1.00&L
_TAXAMT1=1.00&L_TAXRATE1=1.00&L_DISCOUNT1=1.00&L_AMT1=1.00&L_TAXTYPE1=TT3

TSYS Acquiring Solutions Level 3 Visa Parameters
To qualify for Level 3 purchasing card transaction processing, the authorization response for
the transaction must have the commercial card indicator set and one or more line items should
be present in the Delayed Capture or Sale request.
Level 2 transaction parameters marked as mandatory are required for Level 3 transactions.
Level 3 transactions that do not include the mandatory Level 2 values are rejected.
IMPO RTANT: The values required for Level 3 status vary by bank, so contact your bank for

details.

Payflow Pro Developer’s Guide

131

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing
TSYS Acquiring Solutions Level 2 Visa Parameters for Level 3 Line Item
Transactions
TABLE C.31 TSYS Acquiring Solutions Level 2 Visa transaction data for line item
transactions
Mandatory
/ Optional

Name

Length,
Data Type

Payflow Parameter

Purchase
Identifier

PONUM
Value of TransID is sent if no value is provided.

25, AN

Tax Amount

TAXAMT
The value must include a decimal and the exact amount to the
cent (42.00, not 42). Do not include comma separators
(1234.56 not 1,234.56).

NUM

Lcl Tax

LOCALTAXAMT

12, NUM

TAXEXEMPT, Y or N

1, AN

Lcl Tax Incl Flag
National Tax Amt

NATIONALTAXAMT

12, NUM

Purch Ord #/Cust
Ref ID

INVNUM
Value of TransID is sent if no value is provided.

9, AN

TSYS Acquiring Solutions Level 3 Visa Extended Data

The parameters listed in Table C.32 apply to Level 3 Visa transactions as extended data.
TABLE C.32 TSYS Acquiring Solutions Level 3 Visa extended data
Name

132

Mandatory /
Optional

Length,
Data Type

Payflow Parameter

Summary Commodity
Code

COMMCODE
Commodity code identifier for the business.

4, AN

Discount Amt

DISCOUNT

12, NUM

Freight Amt

FREIGHTAMT

12, NUM

Duty Amt

DUTYAMT

12, NUM

Order Date

ORDERDATE
Format is yymmdd with no slashes or dashes. For
example,
November 28, 2008 is 081128

6, NUM

Dest Postal / ZIP Code

SHIPTOZIP
The ZIP code of the address to which the goods are
shipped.

10, AN

Payflow Pro Developer’s Guide

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing

TABLE C.32 TSYS Acquiring Solutions Level 3 Visa extended data (Continued)
Name

Mandatory /
Optional

Payflow Parameter

Length,
Data Type

Ship from Postal / ZIP
Code

SHIPFROMZIP
The postal code (called ZIP code in the USA) from
which shipping occurs.

10, AN

Dest Country Code

SHIPTOCOUNTRY

4, AN

VAT Registration
Number

VATREGNUM
Can be part of the registration data or passed with each
transaction.

20, AN

Unique VAT Inv Ref #

INVNUM
Can be part of the registration data or passed with each
transaction.

9, AN

Cust VAT Registr #

CUSTVATREGNUM

13, AN

VAT/Tax Amt
(Freight/Ship)

VATTAXAMT

12, NUM

VAT/Tax Rate
(Freight/Ship)

VATTAXPERCENT

4, NUM

Payflow Pro Developer’s Guide

133

Submitting Purchasing Card Level 2 and Level 3 Transactions
TSYS Acquiring Solutions Purchasing Card Transaction Processing
TSYS Acquiring Solutions Level 3 Visa Line item Detail Records
TABLE C.33 TSYS Acquiring Solutions Level 3 Visa line item detail record
Mandatory /
Optional

Name

Length, Data
Type

Payflow Parameter

N O T E : For these values, n is a sequence counter that should begin with 1 and increase in sequence. Each line item

should also contain quantity (L_QUANTITY) and unit price (L_COST) fields.
Item Commodity Code

L_COMMCODEn

12, AN

Item Descriptor

L_DESCn

35, AN

Product Code

L_UPCn

12, AN

Quantity

L_QTYn

12, NUM

Unit of Measure/Code

L_UOMn

12, AN

Unit Cost

L_COSTn

12, NUM

VAT/Tax Amount

L_TAXAMTn

12, NUM

VAT/Tax Rate

L_TAXRATEn

4, NUM

Discount Per Line Item

L_DISCOUNTn

12, NUM

Line-item Total

L_AMTn

12, NUM

Example TSYS Acquiring Solutions Level 3 Visa Transaction Parameter String
TRXTYPE=S&TENDER=C&PARTNER=Partner&USER=User&PWD=Password&ACCT=411111111111
1111&EXPDATE=0406&AMT=1.00&STREET=5199
JOHNSON&TAXAMT=106&ZIP=94588&ALTTAXAMT=1.00&CUSTVATREGNUM=11111&LOCALTAXAMT
=1.01&NATIONALTAXAMT=1.02&COMMCODE=22222&VATAXAMT=1.03&VATAXPERCENT=55&TAXE
XEMPT=N&DISCOUNT=.50&FREIGHTAMT=1.00&DUTYAMT=1.00&SHIPTOZIP=33333&SHIPFROMZ
IP=44444&SHIPTOCOUNTRY=840&ORDERDATE=081125&L_COMMCODE1=123456789ABC&L_DESC
1=Line item 1
description&L_UPC1=CBA987654321&L_QTY1=1&L_UOM1=123456789012&L_COST1=1.50&L
_TAXAMT1=1.05&L_TAXRATE1=12&L_DISCOUNT1=.50&L_AMT1=1.00&L_TAXTYPE1=TT1

134

Payflow Pro Developer’s Guide

VERBOSITY: Viewing ProcessorSpecific Transaction Results
Transaction results (especially values for declines and error conditions) returned by each
PayPal-supported processor vary in detail level and in format. The Payflow VERBOSITY
parameter described below enables you to control the kind and level of information you want
returned.

TABLE D.1

VERBOSITY parameter

Parameter

Description

VERBOSITY

(Optional) Enables you to obtain additional processor information for a transaction.
Values are LOW or MEDIUM.
z LOW is the default setting—normalized values
z MEDIUM returns the processor’s raw response values
VERBOSITY is also part of an Inquiry transaction. For more information, see
“Submitting Inquiry Transactions” on page 36.

By default, VERBOSITY is set to LOW.. A LOW setting causes PayPal to normalize the
transaction result values. Normalizing the values limits them to a standardized set of values
and simplifies the process of integrating the Payflow SDK.
By setting VERBOSITY to MEDIUM, you can view the processor’s raw response values. This
setting is more “verbose” than the LOW setting in that it returns more detailed, processorspecific information.

Supported Verbosity Settings
The following VERBOSITY settings are supported for PayPal-supported processors. Contact
your processor or bank for definitions of the returned values.
z

LOW: This is the default setting for PayPal accounts. The following values are returned:
{RESULT, PNREF, RESPMSG, AUTHCODE, AVSADDR, AVSZIP, CVV2MATCH, IAVS,
CARDSECURE}
MEDIUM: All of the values returned for a LOW setting, plus the following values:

N O T E : For information on interpreting the responses returned by the processor for the MEDIUM

VERBOSITY setting, contact your processor directly.

Payflow Pro Developer’s Guide

135

VERBOSITY: Viewing Processor-Specific Transaction Results
Supported Verbosity Settings

TABLE D.2

136

Processor responses

Field Name

Type

Length

Description

HOSTCODE

Char

Response code returned by the processor. This
value is not normalized by PayPal.

RESPTEXT

Char

Text corresponding to the response code returned by
the processor. This text is not normalized by
PayPal.

PROCAVS

Char

Address Verification Service response from the
processor

PROCCVV2

Char

CVV2 (buyer authentication) response from the
processor

PROCCARDSECURE

Char

VPAS/SPA response from the processor

ADDLMSGS

char

Up to 1048
characters.
Typically 50
characters.

Additional error message that indicates that the
merchant used a feature that is disabled

Payflow Pro Developer’s Guide

VERBOSITY: Viewing Processor-Specific Transaction Results
Supported Verbosity Settings
TABLE D.2

Processor responses(Continued)

Field Name

Type

Length

Description

TRANSSTATE

Integer

State of the transaction. The values are:
0 = General succeed state
1 = General error state
3 = Authorization approved
6 = Settlement pending (transaction is scheduled to
be settled)
7 =Settlement in progress (transaction involved in a
currently ongoing settlement)
8 = Settled successfully
9 = Authorization captured (once an authorization
type transaction is captured, its TRANSSSTATE
becomes 9)
10 =Capture failed (an error occurred while trying
to capture an authorization because the transaction
was already captured)
11 = Failed to settle (transactions fail settlement
usually because of problems with the merchant’s
processor or because the card type is not set up with
the merchant’s processor)
12 - Unsettled transaction because of incorrect
account information
14 = For various reasons, the batch containing this
transaction failed settlement
15 = Settlement incomplete due to a charge back
16 = Merchant ACH settlement failed; (need to
manually collect it)
106 = Unknown Status Transaction - Transactions
not settled
206 = Transactions on hold pending customer
intervention

DATE_TO_SETTLE

Date format
YYYY-MM-DD
HH:MM:SS

Value available only before settlement has started

BATCHID

Integer

Value available only after settlement has assigned a
Batch ID

SETTLE_DATE

Date format
YYYY-MM-DD
HH:MM:SS

Value available only after settlement has completed

Payflow Pro Developer’s Guide

137

VERBOSITY: Viewing Processor-Specific Transaction Results
Supported Verbosity Settings
TABLE D.2

Processor responses(Continued)

Field Name

Type

Length

Description

AMEXID

Numeric

American Express transactions meeting CAPN
requirements:
N O T E : Used only by merchants who authorize

transactions through the payflow gateway
but settle through a third-party solution.
AMEXPOSDATA

Alphanumeric

American Express transactions meeting CAPN
requirements:
N O T E : Used only by merchants who authorize

transactions through the payflow gateway
but settle through a third-party solution.

138

Payflow Pro Developer’s Guide

VERBOSITY: Viewing Processor-Specific Transaction Results
Supported Verbosity Settings
TABLE D.2

Processor responses(Continued)

Field Name

Type

Length

Description

VISACARDLEVEL

Alphanumeric

Card product level indicator returned by VISA. The
values are:
A = Visa Traditional
B = Visa Traditional Rewards
C = Visa Signature
D = Visa Infinite
E = Reserved
F = Reserved
G = Visa Business Card
H = Visa Check Card
I = Visa Commerce
J = Reserved
K = Visa Corporate Card
L = Reserved
M = MasterCard/EuroCard and Diners*
N = Reserved
O = Reserved
P = Reserved
Q = Private Label
R = Proprietary Card
S = Visa Purchasing Card
T = Reserved/Interlink
U = Visa TravelMoney
W -Z = Reserved
0 - 9 = Reserved
G1 = Visa Signature Business
G2= Visa Business Check Card
J1 = Visa General Prepaid
J2 = Visa Prepaid Gift Card
J3 = Visa Prepaid Healthcare
J4 = Visa Prepaid Commercial
K1 = Visa GSA Corporate T&E
Q1 = Private Label Prepaid
S1 = Visa Purchasing with Fleet
S2 = Visa GSA Purchasing
S3 = Visa GSA Purchasing with Fleet
V1 = Reserved
DI = Discover*
AX = American Express*
N O T E : Because length is 2, single character values

are followed by a space.

Payflow Pro Developer’s Guide

139

VERBOSITY: Viewing Processor-Specific Transaction Results
Changing the Verbosity Setting

Table D.3 shows the increments that are possible on basic TRANSSTATE values.
TABLE D.3

TRANSSTATE increments

Increment

Meaning

+100

If no client acknowledgment (ACK) is received for the transaction, the original TRANSSTATE
value is incremented by 100. For example, if the original TRANSSTATE is 6, it is incremented to
106. Transactions in this range do not settle.
For transactions in TRANSSTATE 106, use Auto Resettle in PayPal Manager’s Virtual Terminal
to submit them for settlement or void them using a manual Void.

+200

If the host process never receives an ACK from the transaction broker (or backend payment
server) for the transaction, the original TRANSSTATE value is incremented by 200. For example,
if the original TRANSSTATE is 6, it is incremented to 206.
Transactions in this range are basically in limbo and will not be settled.

+1000

If a Void transaction is run (through the API, PayPal Virtual Terminal, or by PayPal Customer
Service) against a successful Authorization or Sale transaction, the original TRANSSTATE is
incremented by 1000. For example, if the original TRANSSTATE is 6, it is incremented to 1006.

Changing the Verbosity Setting
Setting the Verbosity Level on a Per-Transaction Basis
To specify a setting for Verbosity that differs from your account’s current setting, include the
VERBOSITY= name-value pair in the transaction request, where is LOW or
MEDIUM.

Setting the Default Verbosity Level for All Transactions
Contact Customer Service to set your account’s VERBOSITY setting to LOW or MEDIUM for all
transaction requests. For details, see “How to Contact Customer Support” on page 10.

140

Payflow Pro Developer’s Guide

Additional Reporting Parameters

This appendix lists parameters whose values can appear in PayPal Manager reports. For
example, the Shipping and Billing report displays these values. Some of the following
parameters may also have other purposes. The STREET and ZIP parameters, for instance, are
also used for Address Verification Service.
N O T E : For

regular credit card transactions, reporting parameters are normally not passed to
the processor. See Appendix A, “Processors Requiring Additional Transaction
Parameters,” to learn which fields are sent to your processor.

TABLE E.1

Additional reporting parameters

Parameter

Description

Required

Type

Max
Length

CITY

Cardholder’s billing city

Alpha

COMMENT1

User-defined value for reporting
and auditing purposes (PayPal
parameter only)

Alphanumeric

128

COMMENT2

User-defined value for reporting
and auditing purposes (PayPal
parameter only)

Alphanumeric

128

BILLTOCOUNTRY

Cardholder’s billing country code

Alphanumeric

CUSTCODE

Customer code

Alphanumeric

DUTYAMT

Duty amount

Alphanumeric

Cardholder’s email address

Alphanumeric

FIRSTNAME

Cardholder’s first name

Alphanumeric

FREIGHTAMT

Freight amount

Alphanumeric

LASTNAME

Cardholder’s last name

Alphanumeric

NAME

Cardholder’s name

Alphanumeric

Payflow Pro Developer’s Guide

141

Additional Reporting Parameters

TABLE E.1

142

Additional reporting parameters
Max
Length

Parameter

Description

Required

Type

PONUM

Purchase order number

Alphanumeric

SHIPTOCITY

Shipping city

Alphanumeric

SHIPTOFIRSTNAME

First name in the shipping address

Alphanumeric

SHIPTOLASTNAME

Last name in the shipping address

Alphanumeric

SHIPTOSTATE

Shipping state
US = 2 letter state code; outside US,
use full name

Alphanumeric

SHIPTOSTREET

Shipping street address

Alphanumeric

SHIPTOZIP

Shipping postal code (called ZIP
code in the USA)

Alphanumeric

STATE

Cardholder’s billing state code

Alphanumeric

STREET

Cardholder’s billing street address
(used for Address Verification
Service and reporting)

Alphanumeric

TAXAMT

Tax amount

Currency

ZIP

Account holder’s 5-to-9-digit postal
code (called ZIP in the USA). Do
not use spaces, dashes, or nonnumeric characters. The postal code
is verified by Address Verification
Service.

Numeric

Payflow Pro Developer’s Guide

ISO Country Codes

The following International Standards Organization (ISO) country codes are used when filling the order fields
BILLTOCOUNTRY, SHIPTOCOUNTRY, and CORPCOUNTRY:
TABLE F.1

ISO country codes

Country Name

Code

Country Name

Code

Afghanistan

Bangladesh

Albania

Barbados

Algeria

Belarus

112

American Samoa

Belgium

Andorra

Belize

Angola

Benin

204

Anguilla

660

Bermuda

Antarctica

Bhutan

Antigua and Barbuda

Bolivia

Argentina

Bosnia-Herzegovina

Armenia

Botswana

Aruba

533

Bouvet Island

Australia

Brazil

Austria

British Indian Ocean Territory

Azerbaijan

Brunei Darussalam

Bahamas

Bulgaria

100

Bahrain

Burkina Faso

854

Burundi

108

Dominican Republic

214

Cambodia

116

East Timor

626

Cameroon

120

Ecuador

218

Canada

124

Egypt

818

Cape Verde

132

El Salvador

222

Cayman Islands

136

Equatorial Guinea

226

Central African Republic

140

Eritrea

232

Payflow Pro Developer’s Guide

November 2008

143

ISO Country Codes

TABLE F.1

144

ISO country codes

Country Name

Code

Country Name

Code

Chad

148

Estonia

233

Chile

152

Ethiopia

231

China

156

Falkland Islands (Malvinas)

238

Christmas Island

162

Faroe Islands

234

Cocos (Keeling) Islands

166

Fiji

242

Colombia

170

Finland

246

Comoros

174

France

250

Congo

178

France, Metropolitan

249

Cook Islands

184

French Guiana

254

Costa Rica

188

French Polynesia

258

Cote D’ivoire (Ivory Coast)

384

French Southern Territories

260

Croatia (local name: Hrvatska)

191

Gabon

266

Cuba

192

Gambia

270

Cyprus

196

Georgia

268

Czech Republic

203

Germany

276

Denmark

208

Ghana

288

Djibouti

262

Gibraltar

292

Dominica

212

Greece

300

Greenland

304

Jordan

400

Grenada

308

Kazakhstan

398

Guadeloupe

312

Kenya

404

Guam

316

Kiribati

296

Guatemala

320

Korea, Democratic People’s Republic of
(formerly North Korea)

408

Guinea

324

Korea, Republic of (formerly South
Korea)

410

Guinea-Bissau

624

Kuwait

414

Guyana

328

Kyrgyzstan

417

Haiti

332

Lao People’s Democratic Republic
(formerly Laos)

418

Heard and McDonald Islands

334

Latvia

428

November 2008

Payflow Pro Developer’s Guide

ISO Country Codes

TABLE F.1

ISO country codes

Country Name

Code

Country Name

Code

Honduras

340

Lebanon

422

Hong Kong

344

Lesotho

426

Hungary

348

Liberia

430

Iceland

352

Libyan Arab Jamahiriya (formerly Libya)

434

India

356

Liechtenstein

438

Indonesia

360

Lithuania

440

Iran (Islamic Republic of)

364

Luxembourg

442

Iraq

368

Macau

446

Ireland

372

Macedonia, the Former Yugoslav
Republic of

807

Israel

376

Madagascar

450

Italy

380

Malawi

454

Jamaica

388

Malaysia

458

Japan

392

Maldives

462

Mali

466

Niue

570

Malta

470

Norfolk Island

574

Marshall Islands

584

Northern Mariana Islands

580

Martinique

474

Norway

578

Mauritania

478

Oman

512

Mauritius

480

Pakistan

586

Mayotte

175

Palau

585

Mexico

484

Panama

591

Micronesia, Federated States of

583

Papua New Guinea

598

Moldova, Republic of

498

Paraguay

600

Monaco

492

Peru

604

Mongolia

496

Philippines

608

Montserrat

500

Pitcairn

612

Morocco

504

Poland

616

Mozambique

508

Portugal

620

Myanmar (formerly Burma)

104

Puerto Rico

630

Payflow Pro Developer’s Guide

November 2008

145

ISO Country Codes

TABLE F.1

146

ISO country codes

Country Name

Code

Country Name

Code

Namibia

516

Qatar

634

Nauru

520

Reunion

638

Nepal

524

Romania

642

Netherlands

528

Russian Federation

643

Netherlands Antilles

530

Rwanda

646

New Caledonia

540

Saint Kitts and Nevis

659

New Zealand

554

Saint Lucia

662

Nicaragua

558

Saint Vincent and the Grenadines

670

Niger

562

Samoa

882

Nigeria

566

San Marino

674

Sao Tome and Principe

678

Tajikistan

762

Saudi Arabia

682

Tanzania, United Republic of

834

Senegal

686

Thailand

764

Seychelles

690

Togo

768

Sierra Leona

694

Tokelau

772

Singapore

702

Tonga

776

Slovakia (Slovak Republic)

703

Trinidad and Tobago

780

Slovenia

705

Tunisia

788

Solomon Islands

Turkey

792

Somalia

706

Turkmenistan

795

South Africa

710

Turks and Caicos Islands

796

South Georgia and the South Sandwich
Islands

239

Tuvalu

798

Spain

724

Uganda

800

Sri Lanka

144

Ukraine

804

St. Helena

654

United Arab Emirates

784

St. Pierre and Miquelon

666

United Kingdom

826

Sudan

736

United States

840

Suriname

740

United States Minor Outlying Islands

581

Svalbard and Jan Mayen Islands

744

Uruguay

858

November 2008

Payflow Pro Developer’s Guide

ISO Country Codes

TABLE F.1

ISO country codes

Country Name

Code

Country Name

Code

Swaziland

748

Uzbekistan

860

Sweden

752

Vanuatu

548

Switzerland

756

Vatican City State

336

Syrian Arab Republic (formerly Syria)

760

Venezuela

862

Taiwan, Province of China

158

Viet Nam

704

Virgin Islands (British)

Western Samoa

882

Virgin Islands (U.S.)

850

Yemen

887

Wallis and Futuna Islands

876

Yugoslavia

891

Virgin Islands (British)

Zaire

180

Virgin Islands (U.S.)

850

Zambia

894

Western Sahara

732

Zimbabwe

716

Payflow Pro Developer’s Guide

November 2008

147

148

ISO Country Codes

November 2008

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only

Codes used by FDMS South only are Country Codes, Units of Measure, and Currency Codes.

MasterCard Country Codes
TABLE G.1

MasterCard country codes

ALBANIA

ALB

ALGERIA

DZA

AMERICAN SAMOA

ASM

ANDORRA

AND

ANGOLA

AGO

ANGUILLA

AIA

ANTARCTICA

ATA

ANTIGUA

ATG

AO PEOPLES DEMOCRATIC

LAO

APHGANISTAN

AFG

ARGENTINA

ARG

ARMENIA

ARN

ARUBA

ABW

AUSTRALIA

AUS

AUSTRIA

AUT

AZERBAIJAN

AZE

BAHAMAS

BHS

BAHRAIN

BHR

BANGLADESH

BGD

BARBADOS

BRB

BELARUS

BLR

BELGIUM

BEL

Payflow Pro Developer’s Guide

149

Codes Used by FDMS South Only
MasterCard Country Codes
TABLE G.1

150

MasterCard country codes

TABLE G.1

MasterCard country codes

BELIZE

BLZ

COTED'IVOIRE

CIV

BENIN

BEN

CROATIA

HRV

BERMUDA

BMU

CYPRUS

CYP

BHUTAN

BTN

CZECH REPUBLIC

CZE

BOLIVIA

BOL

DENMARK

DNK

BOSNIA AND HERZIGOVINA

BIH

DJIBOUTI

DJI

BOTSWANA

BWA

DOMINICA

DMA

BOUVET ISLAND

BVT

DOMINICAN REPUBLIC

DOM

BRAZIL

BRA

EL SALVADOR

SLV

BRITISH INDIAN OCEAN
TERRITORY

IOT

EQUATORIAL GUINEA

GNQ

ESTONIA

EST

BRUNEI

BRN

ETHIOPIA

ETH

BULGARIA

BGR

FAEROE ISLANDS

FRO

BURKINA FASO

BFA

FALKLAND ISLANDS (MALVINAS)

FLK

BURUNDI

BDI

FIJI

FJI

CAMBODIA

KHM

FINLAND

FIN

CANADA

CAN

FRANCE

FRA

CAPE VERDE

CPV

FRENCH GUIANA

GUF

CAYMAN ISLANDS

CYM

FRENCH POLYNESIA

PYF

CENTRAL AFRICAN REPUBLIC

CAF

FRENCH SOUTHERN TERRITORY

ATF

CHAD

TCD

GABON

GAB

CHILE

CHL

GAMBIA

GMB

CHINA

CHN

GEORGIA

GEO

CHRISTMAS ISLAND

CXR

GERMAN DEMOCRATIC REP

DDR

CMEROON, UNITED REP.

CMR

GERMANY

DEU

COCOS (KEELING) ISLAND

CCK

GHANA

GHA

COLOMBIA

COL

GIBRALTER

GIB

COMOROS

COM

GRECE

GRC

CONGO

GOG

GREENLAND

GRL

COOK ISLANDS

COK

GRENADA

GRD

COSTA RICA

CRI

GUADALUPE

GLP

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only
MasterCard Country Codes
TABLE G.1

MasterCard country codes

TABLE G.1

MasterCard country codes

GUAM

GUM

LIECHTNSTIEN

LIE

GUATEMALA

GTM

LITHUANIA

LTU

GUINEA

GIN

LUXEMBOURG

LUX

GUINEA-BISSAU

GNB

MACAU

MAC

GUYANA

GUY

MALAYSIA

MYS

HAITI

HTI

MALDIVES

MDV

HEARD & MCDONALDS ISLAND

HMD

MALI

MLI

HONDURAS

HND

MALTA

MLT

HONG KONG

HKG

MANACO

MCO

HUNGARY

HUN

MARSHALL ISLANDS

MHL

ICELAND

ISL

MATINIQUE

MTQ

INDIA

IND

MAURITANIA

MRT

INDONESIA

IDN

MAURITIUS

MUS

IRAN

IRN

MEXICO

MEX

IRAQ

IRQ

MICRONESIA

FSM

IRELAND

IRL

MOLDOVA

MDA

ISRAEL

ISR

MONGOLIA

MNG

ITALY

ITA

MONTSERRAT

MSR

JAMAICA

JAM

MOROCCO

MAR

JAPAN

JPN

MOZAMBIQUE

MOZ

JORDAN

JOR

MYANMAR

MMR

KAZAKHSTAN

KAZ

NAMIBIA

NAM

KENYA

KEN

NAURU

NRU

KOREA, REPUBLIC OF

KOR

NEGEL

SEN

KUWAIT

KWT

NEPAL

NPL

KYRGYZSTAN

KGZ

NETHERLANDS

NLD

LATVIA

LVA

NETHERLANDS ANTILLES

ANT

LEBANON

LBN

NEW CALDONIA

NCL

LESOTHO

LSO

NEW ZEALAND

NZL

LIBERIA

LBR

NICARAGUA

NIC

LIBYAN ARAB JAMAHIRIYA

LBY

NIGER

NER

Payflow Pro Developer’s Guide

151

Codes Used by FDMS South Only
MasterCard Country Codes
TABLE G.1

152

MasterCard country codes

TABLE G.1

MasterCard country codes

NIGERIA

NGA

ST. LUCIA

LCA

NIUE

NIU

ST. PIERRE AND MIQUELON

SPM

NORFOLK ISLAND

NFK

VCT

NORTHERN MARIANA ISLAND

MNP

ST. VINCENT AND THE
GRENADINES

NORWAY

NOR

SUDAN

SDN

OMAN

OMN

SURINAM

SUR

PAKISTAN

PAK

SVALBARD & JAN MAYEN IS.

SJM

PALAU

PLW

SWAZILAND

SWZ

PANAMA

PAN

SWEDEN

SWE

PAPAU NEW GUINEA

PNG

SWITZERLAND

CHE

PARAGUAY

PRY

SYRIAN ARAB REPUBLIC

SYR

PERU

PER

TAIWAN, PROVIDENCE OF CHINA

TWN

PHILIPPINES

PHI

TAJIKISTAN

TJK

PITCAIRN ISLAND

PCN

TANZANIA, UNITED REPUBLIC

TZA

POLAND

POL

THAILAND

THA

PORTUGUL

PRT

TOGO

TGO

PUERTO RICO

PRI

TOKELAU

TKL

QATAR

QAT

TONGA

TON

REUNION

REU

TRINIDAD AND TOBAGO

TTO

ROMANIA

ROM

TUNISIA

TUN

RUSSIAN FERERATION

RUS

TURKEY

RWANDA

RWA

TURKMENISTAN

SAMOA

WSM

TURKS & CAICOS ISLANDS

SAN MARINO

SMR

TUVALU

TUV

SAN TOME AND PRICIPEL

STP

U.S. MINOR OUTLYING ISL.

UMI

SAUDI ARABIA

UGANDA

UGA

SEYCHELLES

SYC

UKRAINIAN SSR

UKR

SIERRA LEONE

SLE

UNITED ARAB EMIRATES

ARE

SINGAPORE

SGP

UNITED KINGDOM

GBR

ST. HELENA

SHN

UNITED STATES

USA

ST. KITTS-NEVIS-ANGUILLA

KNA

URAGUAY

URY

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only
Visa Country Codes
TABLE G.1

MasterCard country codes

UZBEKISTAN

UZB

VANUATU

VUT

VATICAN CITY STATE

VAT

VENEZUELA

VEN

VIETNAM

VNM

VIRGIN ISLANDS BRITISH

VGB

VIRGIN ISLANDS US

VIR

WALLIS AND FUTUNA IS

WLF

WESTERN SAHARA

ESH

YEMEN

YEM

YUGOSLAVIA

YUG

ZAIRE

ZAR

ZAMBIA

ZMB

ZIMBABWE

RHO

Visa Country Codes
TABLE G.2
TABLE G.2

Visa country codes

ARUBA

ALBANIA

AUSTRALIA

ALGERIA

AUSTRIA

AMERICAN SAMOA

AZERBAIJAN

ANDORRA

BAHAMAS

ANGOLA

BAHRAIN

ANGUILLA

BANGLADESH

ANTARCTICA

BARBADOS

ANTIGUA

BELARUS

APHGANISTAN

BELGIUM

ARGENTINA

BELIZE

ARMENIA

BENIN

BERMUDA

Payflow Pro Developer’s Guide

153

Codes Used by FDMS South Only
Visa Country Codes
TABLE G.2

154

TABLE G.2

Visa country codes

BHUTAN

CZECH REPUBLIC

BOLIVIA

DENMARK

BOSNIA AND HERZIGOVINA

DJIBOUTI

BOTSWANA

DOMINICA

BOUVET ISLAND

DOMINICAN REPUBLIC

BRAZIL

EAST TIMOR

BRITISH INDIAN OCEAN
TERRITORY

ECUADOR

EGYPT

BRUNEI

EL SALVADOR

BULGARIA

EQUATORIAL GUINEA

BURKINA FASO

ERITREA

BURUNDI

ESTONIA

CAMBODIA

ETHIOPIA

CANADA

FAEROE ISLANDS

CAPE VERDE

FALKLAND ISLANDS

CAYMAN ISLANDS

FIJI

CENTRAL AFRICAN REPUBLIC

FINLAND

CHACOS (KEELING) ISLAND

FRANCE

CHAD

FRENCH GUIANA

CHILE

FRENCH METROPOLITAN

CHINA

FRENCH POLYNESIA

CHRISTMAS ISLAND

FRENCH SOUTHERN TERRITORY

CMEROON, UNITED REP.

GABON

COLUMBIA

GAMBIA

COMOROS

GEORGIA

CONGO

GERMANY

COOK ISLANDS

GHANA

COSTA RICA

GIBRALTER

COTED'IVOIRE

GRECE

CROATIA

GREENLAND

CYPRUS

GRENADA

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only
Visa Country Codes
TABLE G.2

TABLE G.2

Visa country codes

GUADALUPE

LESOTHO

GUAM

LIBERIA

GUATEMALA

LIBYAN ARAB JAMAHIRIYA

GUINEA

LIECHTNSTIEN

GUINEA-BISSAU

LITHUANIA

GUYANA

LUXEMBOURG

HAITI

MACAU

HEARD & MCDONALDS ISLAND

MACEDONIA

HONDURAS

MADAGASCAR

HONG KONG

MALAWI

HUNGARY

MALAYSIA

ICELAND

MALDIVES

INDIA

MALI

INDONESIA

MALTA

IRAN

MANACO

IRAQ

MARSHALL ISLANDS

IRELAND

MATINIQUE

ISRAEL

MAURITANIA

ITALY

MAURITIUS

JAMAICA

MAYOTTE

JAPAN

MEXICO

JORDAN

MICRONESIA

KAZAKHSTAN

MOLDOVA

KENYA

MONGOLIA

KIRIBATI

MONTSERRAT

KOREA, REPUBLIC OF

MOROCCO

KUWAIT

MOZAMBIQUE

KYRGYZSTAN

MYANMAR

LAO PEOPLES DEMOCRATIC

NAMIBIA

LATVIA

NAURU

LEBANON

NEPAL

Payflow Pro Developer’s Guide

155

Codes Used by FDMS South Only
Visa Country Codes
TABLE G.2

156

TABLE G.2

Visa country codes

NETHERLANDS

SAUDI ARABIA

NETHERLANDS ANTILLES

SENEGAL

NEW CALDONIA

SEYCHELLES

NEW ZEALAND

SIERRA LEONE

NICARAGUA

SINGAPORE

NIGER

ST. HELENA

NIGERIA

ST. KITTS-NEVIS-ANGUILLA

NIUE

ST. LUCIA

NORFOLK ISLAND

ST. PIERRE AND MIQUELON

NORTHERN MARIANA ISLAND

NORWAY

ST. VINCENT AND THE
GRENADINES

OMAN

SUDAN

PAKISTAN

SURINAM

PALAU

SVALBARD & JAN MAYEN IS.

PANAMA

SWAZILAND

PAPAU NEW GUINEA

SWEDEN

PARAGUAY

SWITZERLAND

PERU

SYRIAN ARAB REPUBLIC

PHILIPPINES

TAIWAN, PROVIDENCE OF CHINA

PITCAIRN ISLAND

TAJIKISTAN

POLAND

TANZANIA, UNITED REPUBLIC

PORTUGUL

THAILAND

PUERTO RICO

TOGO

QATAR

TOKELAU

REUNION

TONGA

ROMANIA

TRINIDAD AND TOBAGO

RUSSIAN FERERATION

TUNISIA

RWANDA

TURKEY

SAMOA

TURKMENISTAN

SAN MARINO

TURKS & CAICOS ISLANDS

SAN TOME AND PRICIPEL

TUVALU

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only
Units of Measure
TABLE G.2

Visa country codes

U.S. MINOR OUTLYING ISL.

UGANDA

UKRAINIAN SSR

UNITED ARAB EMIRATES

UNITED KINGDOM

UNITED STATES

URAGUAY

UZBEKISTAN

VANUATU

VATICAN CITY STATE

VENEZUELA

VIETNAM

VIRGIN ISLANDS BRITISH

VIRGIN ISLANDS US

WALLIS AND FUTUNA IS

WESTERN SAHARA

YEMEN

YUGOSLAVIA

ZAIRE

ZAMBIA

ZIMBABWE

Units of Measure
TABLE G.3
TABLE G.3

Units of measure

Ampere=hour (3,6 kC)*

AMH

Acre (4840 yd2)

ACR

Are (100 m2)

ARE

Alcoholic strength by mass

ASM

Bar*

BAR

Alcoholic strength by volume

ASV

Barrel (petroleum) (158,987 dm3)

BLL

Ampere*

AMP

Becquerel*

BQL

Billion EUR

BIL

Payflow Pro Developer’s Guide

157

Codes Used by FDMS South Only
Units of Measure
TABLE G.3

158

TABLE G.3

Units of measure

Billion US

MLD

Decimetre*

DMT

Board foot

BFT

Decitonne*

DTN

Brake horse power (245,7 watts)

BHP

Degree Celsius

CEL

British thermal unit (1,055 kilojoules)

BTU

Degree Fahrenheit

FAH

Bushel (35,2391 dm3)

BUA

Degree Kelvin: Kelvin

Bushel (36,36874 dm3)

BUI

Displacement tonnage

DPT

Candela*

CDL

Dozen

DZN

Carrying capacity in metric tonnes

CCT

Dozen packs

DZP

Cental GB (45,359237 kg)

CNT

Dozen pairs

DZR

Center, metric (100 kg) (syn.:
Hectokilogram)

DTN

Dozen pieces

DCP

Dozen rolls

DRL

Centigram*

CGM

Drachm GB (3,887935 g)

DRM

Centilitre*

CLT

Dram GB (1,771745 g)

DRI

Centimetre*

CMT

Dram US (3,887935 g)

DRA

Cord (3,63 m3)

WCD

Dry Barrel (115,627 dm3)

BLD

Coulomb per kilogram*

CKG

Dry gallon (4,404884 dm3)

GLD

Coulomb*

COU

Dry pint (0,55061 dm3)

PTD

Cubic centimetre*

CMQ

Dry quart (1,101221 dm3)

QTD

Cubic decimetre*

DMQ

Farad*

FAR

Cubic foot

FTQ

Fluid ounce (28,413 cm3)

OZI

Cubic inch

INQ

Fluid ounce (29,5735 cm3)

OZA

Cubic metre per hour*

MQH

Foot (0,3048 m)

FOT

Cubic metre per second*

MQS

Gallon (4,546092 dm3)

GLI

Cubic metre*

MTQ

Gigabecquerel*

GBQ

Cubic millimetre*

MMQ

Gigawatt-hour (1 million kW/h)*

GWH

Cubic yard

YDQ

Gill (0,142065 dm3)

GII

Curie

CUR

Gill (11,8294 cm3)

GIA

Day*

DAY

Grain GB, US (64,798910 mg)

GRN

Decade (ten years)

DEC

Gram of fissile isotopes

GFI

Decare

DAA

Gram*

GRM

Decilitre*

DLT

Great gross (12 gross)

GGR

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only
Units of Measure
TABLE G.3

TABLE G.3

Units of measure

Gross

GRO

Kilogram of sodium hydroxide

KSH

Gross (register) ton

GRT

Kilogram of substance 90 percent dry

KSD

Half year (six months)

SAN

Kilogram per cubic meter*

KMQ

Hectare

HAR

Kilogram per second*

KGS

Hectobar*

HBA

Kilogram*

KGM

Hectogram*

HGM

Kilohertz*

KHZ

Hectokilogram*

DTH

Kilojoule*

KJO

Hectolitre of pure alcohol

HPA

Kilometre per hour*

KMH

Hectolitre*

HLT

Kilometre*

KMT

Hectometre*

HMT

Kilopascal*

KPA

Hertz*

HTZ

Kilorgram of uranium

KUR

Hour*

HUR

Kilotonne*

KTN

Hundred

CEN

Kilovar

KVR

Hundred boxes

BHX

Kilovolt*

KVT

Hundred international units

HIU

Kilovolt-ampere*

KVA

Hundred leaves

CLF

Kilowatt*

KWT

Hundred packs

CNP

Kilowatt-hour*

KWH

Hundredweight US
(45,3592 kg)

CWA

Knot (1 nautical mile per hour)

KNT

Leaf

LEF

Inch (25,4 mm)

INH

Liquid gallon (3,78541 dm3)

GLL

Joule*

JOU

Liquid pint (0,473176 dm3)

PTL

Kelvin*

KEL

Liquid quart (0,946353 dm3)

QTL

Kilobar*

KBA

Litre (1 dm3)*

LTR

Kilogram of caustic potash

KPH

Litre of pure alcohol

LPA

Kilogram of caustic soda

KSH
KNS

Long ton GB, US
(1,0160469 t)

LTN

Kilogram of named substance
Kilogram of nitrogen

KNI

(long) hundredweight GB (50,802345 kg)

CWI

Kilogram of phosphonic anhydride

KPP

Lumen*

LUM

Kilogram of phosphorus pentoxide

KPP

Lux

LUX

Kilogram of potassium
hydroxide

KPH

Megahertz*

MHZ

Megalitre*

MAL

Kilogram of potassium oxide

KPO

Payflow Pro Developer’s Guide

159

Codes Used by FDMS South Only
Units of Measure
TABLE G.3

160

TABLE G.3

Units of measure

Megametre*

MAM

Number of parcels

NPL

Megapascal*

MPA

Number of parts

NPT

Megavolt-ampere (1000 KVA)*

MVA

Number of rolls

NRL

Megawatt*

MAW

Ohm*

OHM

Megawatt-hour (100 kW/h)*

MWH

Ounce GB, US (28,349523 g)

ONZ

Metre per second squared*

MSK

APZ

Metre per second*

MTS

Ounce GB, US (31,103448 g) (syn: Troy
ounce)

Metre*

MTR

Pascal*

PAL

Metric carat (200 mg=2,10-4 kg)

CTM

Pennyweight GB, US (1555174 g)

DWT

Metric ton (1000 kg)

TNE

Piece

PCE

Milliard

MLD

Pint (0,568262 dm3)

PTI

Millibar*

MBR

Pound GB, US (0,45359237 kg)

LBR

Millicurie

MCU

Proof gallon

PGL

Milligram*

MGM

Quart (1,136523 dm3)

QTI

Millilitre*

MLT

Quarter (of a year)

QAN

Millimetre*

MMT

Quarter, GB (12,700586 kg)

QTR

Million

MIO

Quintal, metric (100 kg)

DTN

Million cubic metres*

HMQ

Revolution per minute*

RPM

Million international units

MIU

Revolution per second*

RPS

Minute*

MIN

Score

SCO

Month

MON

scruple, GB (1,2955982 g)

SCR

Nautical mile (1852 m)

NMI

Second*

SEC

Net (register) ton

NTT

Set

SET

Newton*

NEW

Shipping ton

SHT

Number

NMB

Short standard (7200 matches)

SST

Number of articles

NAR

Short ton GB, US (0,90718474 t)

STN

Number of bobbons

NBB

Siemens*

SIE

Number of cells*

NCL

Square centimetre*

CMK

Number of international units

NIU

Square decimetre*

DMK

Number of packs

NMP

Square foot

FTK

Number of pairs

NMR

Square inch

INK

Payflow Pro Developer’s Guide

Codes Used by FDMS South Only
Units of Measure
TABLE G.3

Units of measure

Square kilometre*

KMK

Square metre*

MTK

Square mile

MIK

Square millimetre*

MMK

Square yard

YDK

Standard

WSD

standard atmosphere (101325 Pa)

ATM

(statue) mile (1609,344 m)

SMI

Stone GB (6,350293 kg)

STI

Technical atmosphere (98066,5 Pa)

ATT

Ten days

DAD

Ten pairs

TPR

Thousand

MIL

Thousand ampere-hour*

TAH

Thousand board feet (2,36 m3)

MBF

Thousand cubic metres per day*

TQD

Thousand standard brick equivalent

MBE

Ton of steam per hour

TSH

Tonne (1000 kg)*

TNE

Tonne of substance 90 percent dry

TSD

Trillion EUR

TRL

Trillion US

BIL

Troy ounce

APZ

Troy pound, US (373,242 g)

LBT

Volt*

VLT

Watt*

WTT

Watt-hour*

WHR

Weber

WEB

Week

WEE

Yard (0,9144 m)

YRD

Year

ANN

Payflow Pro Developer’s Guide

161

Codes Used by FDMS South Only
FDMS South Currency Codes and Decimal Positions

FDMS South Currency Codes and Decimal Positions
TABLE G.4
TABLE G.4

162

FDMS South currency codes

Currency Name

Currency
Code

Decimal
Positions

Portuguese Escudo

620

Currency Name

Currency
Code

Decimal
Positions

Argentine Peso

Rand

710

Australian Dollar

Spanish Peseta

724

Austrian Schilling

Swedish Krona

752

Belgian Franc

Swiss Franc

756

Canadian Dollar

124

Thailand Baht

764

Chilean Peso

152

Pound Sterling

826

Czech Koruna

203

Russian Ruble

810

Danish Krone

208

U.S Dollar

840

Dominican Peso

214

Bolivar

862

Markka

246

New Taiwan Dollar

901

French Franc

250

Euro

978

Deutsche Mark

280

Polish New Zloty

985

Drachma

300

Brazilian Real

986

Hong Kong Dollar

344

Indian Rupee

356

Irish Punt

372

Shekel

376

Italian Lira

380

Yen

392

Won

410

Luxembourg Franc

442

Mexican Duevo Peso

484

Netherlands Guilder

528

New Zealand Dollar

554

Norwegian Frone

578

Philippine Peso

608

Payflow Pro Developer’s Guide

XMLPay

About XMLPay
XMLPay specifies an XML syntax for payment requests and associated responses in a
payment-processing network. Instead of using name/value pairs, the Payflow SDK allows the
use of XML documents based on XMLPay 2.0 schema.
The typical user of XMLPay is an internet merchant or merchant aggregator who wants to
dispatch credit card, corporate purchase card, Automated Clearinghouse (ACH), or other
payment requests to a financial processing network.
Using the data type definitions specified by XMLPay, such a user creates a client payment
request and dispatches it in the same fashion as using name/value pairs to an associated
XMLPay-compliant server component. Responses are also formatted in XML and convey the
results of the payment requests to the client.

Payflow Pro XMLPay Developer’s Guide
Payflow Pro XMLPay Developer’s Guide defines an XML syntax for payment transaction
requests, responses, and receipts in a payment processing network.
You may obtain a copy of this document via the PayPal Manager Documentation page.
N O T E : For specific examples of how to submit XML documents using the Payflow client API,

see the Payflow SDK Download package.

Payflow Pro Developer’s Guide

163

164

XMLPay
Payflow Pro XMLPay Developer’s Guide

Payflow Pro Developer’s Guide

Index
A
ADDLMSGS 99
address verification service 42
ALTERNATETAXAMT parameter 125
ALTERNATETAXID parameter 125
ALTTAXAMT parameter 115, 130
American Express 65
American Express CAPN 55, 66, 81, 100, 121
AMEXID parameter 55
AMEXPOSDATA parameter 55
AMT 99
AMT parameter 26, 104
APIs
documentation 17
downloading 17
application
testing 47
AUTHCODE 54
AUTHCODE parameter 32, 104
AVSADDR 54
AVSZIP 54

B
BALAMT 55
BALAMT parameter 55
Bank Identification Numbers. See 98
BIN 99

C
CAPN 55, 66, 81, 100, 121
card acceptance and processing network (CAPN) 100,
121
CHKNUM parameter 90
CITY parameter 80, 109
close batch
see settlement operation
COMMCARD parameter 106
COMMCODE parameter 117, 132
COMMENT1 parameter 26
COMMENT2 parameter 26

communications errors 62
credit transaction type 33
CUSTCODE parameter 109, 113
CUSTREF parameter 37
CUSTVATREGNUM parameter 118, 133
CVV2 parameterPayflow parameters
CVV2 26
CVV2MATCH 53

D
DESC parameter 72, 75, 104
DESC1 parameter 72, 103
DESC2 parameter 72, 103
DESC3 parameter 72, 103
DESC4 parameter 72, 103
DISCOUNT parameter 107, 109, 117, 125, 126, 132
DL parameter 90
DOB parameter 90
documentation
API 17
downgraded transactions 99
downloading APIs 17
duplicate transactions 27
DUTYAMT parameter 106, 107, 109, 115, 117, 126,
130, 132

E
Elavon (Formerly Nova) 77
electronic check transaction
required parameters 89
ENDTIME parameter 38
EXPDATE parameter 26

F
FDMS CardNet 75
FDMS North 75, 107
FDMS South 75, 109
FIRSTNAME parameter 26, 71, 72, 86, 109
FREIGHTAMT 99

Index

FREIGHTAMT parameter 104, 106, 107, 109, 115,
117, 125, 126, 130, 132

H
HANDLINGAMT parameter 104
HOSTCODE parameter 93

I
IAVS 54
inquiry transaction type 36
INVNUM parameter 71, 72, 74, 76, 80, 87, 103, 109,
115, 118, 130, 133
INVOICEDATE parameter 104

L
L_AMTn parameter 108, 111, 119, 125, 126, 134
L_CATALOGNUMn parameter 105
L_COMMCODEn parameter 108, 111, 119, 134
L_COSTCENTERNUMn parameter 105
L_COSTn parameter 105, 108, 111, 119, 126
L_COSTn parameterPayflow parameters
L_COSTn 134
L_DESCn parameter 105, 108, 111, 116, 119, 125, 126,
131, 134
L_DISCOUNTn 134
L_DISCOUNTn parameter 108, 111, 116, 119, 125,
126, 131, 134
L_FREIGHTAMTn 99
L_FREIGHTAMTn parameter 105
L_HANDLINGAMTn parameter 105
L_PICKUPCITYn parameter 105
L_PICKUPCOUNTRYn parameter 105
L_PICKUPSTATEn parameter 105
L_PICKUPSTREETn parameter 105
L_PICKUPZIPn parameter 105
L_PRODCODEn parameter 105, 111, 125, 126
L_QTYn 134
L_QTYn parameter 104, 108, 111, 116, 119, 125, 126,
131, 134
L_TAXAMTn parameter 105, 108, 111, 116, 119, 126,
131, 134
L_TAXRATEn parameter 116, 119, 126, 131, 134
L_TAXTYPEn parameter 116, 125, 131
L_TRACKINGNUMn parameter 105
L_UNSPSCCODEn parameter 105

166

L_UOMn parameter 104, 108, 111, 116, 119, 125, 126,
131, 134
L_UPCn parameter 105, 108, 116, 119, 126, 131, 134
LASTNAME parameter 27, 71, 72, 86, 109
length tags 21
Level 2 parameters
American Express Phoenix (CAPN) 101
American Express Phoenix (legacy) 103
Elavon (Formerly Nova) 120
Global Payments - East 113
Global Payments Central 112
Merchant e-Solutions 113
Paymentech Salem (New Hampshire) 121, 123
Paymentech Tampa 128
Level 3 MasterCard transactions
TSYS Acquiring Solutions 114
Level 3 parameters
Merchant e-Solutions 116
Paymentech Salem (New Hampshire) 124, 125, 126
TSYS Acquiring Solutions 129, 131
Level 3 transactions
American Express Brighton 106
American Express Phoenix 103, 108
Level 3 Visa transactions, TSYS Acquiring
Solutions 116
levels, transaction parameters 97
Line item parameters
First Data Merchant Services North 108
Line item paramters
First Data Merchant Services South 110
live transactions 18
live transactions host address 13
LOCALTAXAMT parameter 115, 117, 130, 132
Logging Transaction Information 95

M
MERCHDESCR parameter 80
MERCHSVC parameter 76, 80
MICR parameter 90

N
NATIONALTAXAMT parameter 115, 117, 130, 132
Nova. See Elavon. 77, 120

Payflow Pro Developer’s Guide

Index

O
online help 9
operation
testing 47
ORDERDATE parameter 71, 72, 87, 109, 117, 132
ORDERDATETIME parameter 71, 73, 87
ORDERTIME parameter 110
ORIGID parameter 30, 33, 35, 37

P
parameters
required for electronic check 89
PARTNER parameter 21
Payflow documentation 9
Payflow parameters
ACCT 21, 28, 29, 30, 33, 34, 36, 40, 42
ACCTTYPE 40
ADDLAMTn 69, 84, 102, 123
ADDLAMTTYPEn 69, 85, 102, 123
ADDLMSGS 99, 136
ALTERNATETAXAMT 125
ALTERNATETAXID 125
ALTTAXAMT 115, 130
AMEXID 55, 138
AMEXPOSDATA 55, 138
AMT 21, 26, 28, 29, 30, 33, 34, 36, 89, 90, 99, 104
AUTHCODE 32, 54, 104
AVSADDR 51, 54
AVSZIP 51, 54
BALAMT 55
BATCHID 137
BILLTOCOUNTRY 30, 34, 36, 40, 80, 141
CHKNUM 89, 90
CHKTYPE 89, 90
CITY 30, 34, 36, 40, 80, 89, 90, 109, 141
COMMCARD 106
COMMCODE 117, 132
COMMENT1 26, 30, 34, 36, 90, 141
COMMENT2 26, 30, 34, 36, 90, 141
COMPANYNAME 30, 34, 36
CUSTBROWSER 66, 78, 82
CUSTCODE 30, 34, 36, 109, 112, 113, 141
CUSTHOSTNAME 66, 78, 82
CUSTIP 30, 34, 36, 67, 78, 82
CUSTREF 37

Payflow Pro Developer’s Guide

CUSTVATREGNUM 118, 133
CVV2 52
CVV2MATCH 51, 53
DATE_TO_SETTLE 137
DESC 72, 75, 104
DESC1 72, 103
DESC2 72, 103
DESC3 72, 103
DESC4 34, 72, 103
DISCOUNT 107, 109, 117, 125, 126, 132
DL 89, 90
DOB 90
DUTYAMT 30, 34, 36, 106, 107, 109, 115, 117, 126,
130, 132, 141
EMAIL 30, 34, 36, 66, 78, 82, 89, 90, 141
ENDTIME 37, 38
EXPDATE 21, 26, 28, 29, 30, 33, 34, 36, 40, 42
FIRSTNAME 26, 30, 34, 36, 40, 71, 72, 86, 109, 141
FREIGHTAMT 30, 34, 36, 99, 104, 106, 107, 109,
115, 117, 125, 126, 130, 132, 141
HANDLINGAMT 100, 104
HOSTADDRESS 20
HOSTCODE 93, 136
HOSTPORT 20
IAVS 54
INVNUM 30, 34, 36, 71, 72, 74, 76, 80, 87, 90, 103,
109, 115, 117, 118, 130, 133
INVOICEDATE 104
L_AMT1 101, 122
L_AMT2 101, 122
L_AMT3 101, 122
L_AMT4 101, 122
L_AMTn 66, 82, 108, 111, 119, 125, 126, 134
L_CATALOGNUMn 105
L_COMMCODEn 108, 111, 119, 134
L_COSTCENTERNUMn 105
L_COSTn 100, 105, 108, 111, 119, 126
L_DESC1 101, 122
L_DESC2 101, 122
L_DESC3 101, 122
L_DESC4 101, 122
L_DESCn 66, 81, 105, 108, 111, 116, 119, 125, 126,
131, 134
L_DISCOUNTn 108, 111, 116, 119, 125, 126, 131
L_FREIGHTAMTn 99, 105
L_HANDLINGAMTn 100, 105
L_PICKUPCITYn 105

167

Index

L_PICKUPCOUNTRYn 105
L_PICKUPSTATEn 105
L_PICKUPSTREETn 105
L_PICKUPZIPn 105
L_PRODCODEn 105, 111, 125, 126
L_QTY1 101, 122
L_QTY2 101, 122
L_QTY3 101, 122
L_QTY4 102, 122
L_QTYn 66, 82, 100, 104, 108, 111, 116, 119, 125,
126, 131
L_TAXAMTn 105, 108, 111, 116, 119, 126, 131, 134
L_TAXRATEn 116, 119, 126, 131, 134
L_TAXTYPEn 116, 125, 131
L_TRACKINGNUMn 105
L_UNSPSCCODEn 105
L_UOMn 104, 111, 116, 119, 125, 126, 131, 134
L_UPCn 105, 108, 116, 119, 126, 131, 134
LASTNAME 27, 30, 34, 36, 40, 71, 72, 86, 109, 141
LOCALTAXAMT 115, 117, 130, 132
MERCHANTCITY 68, 84, 102, 122
MERCHANTCOUNTRYCODE 68, 84, 102, 123
MERCHANTNAME 68, 84, 102, 122
MERCHANTSTATE 68, 84, 102, 122
MERCHANTSTREET 68, 84, 102, 122
MERCHANTZIP 68, 84, 102, 123
MERCHDESCR 80
MERCHSVC 76, 80
MICR 89, 90
MIDDLENAME 30, 34, 36, 40
NAME 89, 90, 141
NATIONALTAXAMT 115, 117, 130, 132
ORDERDATE 71, 72, 87, 109, 117, 132
ORDERDATETIME 71, 73, 87
ORDERTIME 110
ORIGID 30, 33, 35, 37, 56
PARMLIST 20
PARTNER 21, 89, 91
PHONENUM 30, 34, 36, 66, 67, 78, 79, 82, 83, 91
PHONETYPE 66, 78, 82
PNREF 30, 33, 35, 37, 53, 56, 93
PONUM 30, 34, 36, 101, 103, 104, 106, 107, 110,
114, 115, 117, 121, 123, 128, 129, 130, 132,
142
PROCAVS 54, 136
PROCCARDSECURE 136
PROCCVV2 54, 136

168

PROXYADDRESS 20
PROXYLOGON 20
PROXYPASSWORD 20
PROXYPORT 20
PWD 21, 89, 91
RECURRING 34, 36, 68, 73, 74, 76, 80, 81, 84, 88
RECURRINGTYPE 81
REQNAME 104
RESPMSG 53, 56, 93
RESPTEXT 136
RESULT 53, 56, 62, 93
SETTLE_DATE 137
SHIPFROMZIP 107, 110, 115, 118, 130, 133
SHIPMETHOD 67, 78, 83
SHIPPEDFROMZIP 125, 126
SHIPTOCITY 30, 34, 36, 142
SHIPTOCOUNTRY 30, 34, 36, 67, 78, 79, 82, 83,
107, 109, 115, 118, 126, 130, 133
SHIPTOFIRSTNAME 30, 34, 36, 67, 79, 83, 142
SHIPTOLASTNAME 30, 34, 36, 67, 79, 83, 142
SHIPTOMIDDLENAME 30, 34, 36
SHIPTOPHONENUM 68, 79, 83
SHIPTOSTATE 30, 34, 36, 142
SHIPTOSTREET 30, 34, 36, 67, 79, 83, 142
SHIPTOZIP 30, 34, 36, 68, 79, 83, 101, 103, 104,
106, 107, 115, 117, 121, 126, 128, 130, 132,
142
SKU 67, 78, 83
SS 89, 91
STARTTIME 37, 38
STATE 30, 34, 36, 40, 80, 89, 91, 110, 142
STREET 27, 30, 34, 36, 40, 44, 51, 67, 79, 83, 90,
91, 142
SWIPE 27, 30, 34, 36, 40, 41, 42, 71, 73, 74, 76, 81,
87, 88, 110
TAXAMT 30, 34, 36, 99, 101, 104, 106, 108, 110,
112, 113, 114, 115, 117, 121, 123, 126, 128,
129, 130, 132, 142
TAXAMTn 125
TAXEXEMPT 30, 34, 36, 106, 110, 114, 115, 117,
128, 129, 130, 132
TAXPERCENTAGE 126
TAXPERCENTAGEn 125
TENDER 27, 89, 91
TIMEOUT 20
TRANSSTATE 137
TRXTYPE 27, 28, 29, 32, 33, 35, 56, 89, 91
USER 21, 89, 91

Payflow Pro Developer’s Guide

Index

VATREGNUM 118, 133
VATTAXAMT 118, 133
VATTAXPERCENT 118, 133
VENDOR 21, 89, 91
VERBOSITY 19, 20, 99, 135
ZIP 24, 27, 30, 34, 36, 40, 42, 44, 51, 67, 79, 83, 90,
91, 142
payflowpro.paypal.com 13
payment types 15
PayPal Developer Central 9
PHONENUM parameter 67, 79, 83, 91
pilot-payflowpro.paypal.com 13
PINless debit 27
pinless debit 15, 26, 27, 28
PNREF 53
format of value 56
PNREF parameter 93
PNREF value 56
PONUM parameter 101, 103, 104, 106, 107, 110, 114,
115, 117, 121, 123, 128, 129, 130, 132
PROCAVS parameter 54
PROCCVV2 parameter 54
Purchasing card transactions
American Express Phoenix 98
First Data Merchant Services Nashville 106
First Data Merchant Services North 107
First Data Merchant Services South 109
Global Payments - Central 112
Global Payments East 112
Merchant e-Solutions 113
Nova 120
Paymentech Salem (New Hampshire) 121
Paymentech Tampa 127
TSYS Acquiring Solutions 128
purchasing cards
about 97
BIN ranges 98
PWD parameter 21

R
RECURRING parameter 68, 73, 74, 76, 80, 81, 84, 88
REQNAME parameter 104
required parameters
electronic check 89
RESPMSG 53
RESPMSG parameter 93

Payflow Pro Developer’s Guide

RESPMSG value 56
RESULT 53
RESULT parameter 93
RESULT value 56
RESULT values
communication errors 62

S
sale transaction type 28
Sample Code and Documentation 9
Secure Sockets Layer 14
settlement operation 14
SHIPFROMZIP parameter 107, 110, 115, 118, 130, 133
SHIPPEDFROMZIP parameter 125, 126
SHIPTOCOUNTRY parameter 107, 109, 115, 118, 125,
126, 130, 133
SHIPTOFIRSTNAME parameter 67, 79, 83
SHIPTOLASTNAME parameter 67, 79, 83
SHIPTOSTREET parameter 67, 79, 83
SHIPTOZIP parameter 68, 79, 83, 101, 103, 104, 106,
107, 110, 115, 117, 121, 126, 128, 130, 132
Software Development Kit 9
SS parameter 91
SSL, see Secure Sockets Layer
STARTTIME parameter 38
STATE parameter 80, 110
Stored Value 55
storefront
testing 47
STREET parameter 27, 67, 79, 83, 91
SWIPE 66, 81
SWIPE parameter 27, 71, 73, 74, 76, 81, 87, 88, 110

T
TAXAMT 99
TAXAMT parameter 104, 106, 108, 110, 113, 114, 115,
117, 123, 126, 128, 129, 130, 132
TAXAMTn parameter 125
TAXEXEMPT parameter 106, 110, 114, 115, 117, 128,
129, 130, 132
TAXPERCENTAGE parameter 126
TAXPERCENTAGEn parameter 125
TENDER parameter 27
testing operation 47
testing transactions host address 13

169

Index

transaction
types supporded for Level 3 procdessing 99
transaction levels
described 97
transaction response
PNREF parameter 56
RESPMSG parameter 56
RESULT parameter 56
transactions
credit 33
inquiry 36
sale 28
void 35
TRXTYPE parameter 27
TSYS Acquiring Solutions 81
type N transactions 27

U
USER parameter 21

V
VATREGNUM parameter 118, 133
VATTAXAMT parameter 118, 133
VATTAXPERCENT parameter 118, 133
VENDOR parameter 21
VERBOSITY 99
VERBOSITY parameter 135
void transaction type 35

Z
ZIP parameter 27, 67, 79, 83

170

Payflow Pro Developer’s Guide

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : Yes
Page Mode                       : UseOutlines
Signing Date                    : 2008:10:30 17:36:24-07:00
Signing Authority               : ARE_Acrobat Collaboration V7.0 P9 0000109
Annotation Usage Rights         : Create, Delete, Modify, Copy, Import, Export
XMP Toolkit                     : 3.1-702
Producer                        : Acrobat Distiller 7.0.5 (Windows)
Create Date                     : 2008:09:22 10:15:14Z
Creator Tool                    : FrameMaker 7.2
Modify Date                     : 2008:10:30 17:36:24-07:00
Metadata Date                   : 2008:10:30 17:36:24-07:00
Format                          : application/pdf
Title                           : PayflowPro_Guide.book
Creator                         : mmorris
Document ID                     : uuid:309fb9d3-211b-424a-92bd-b7c7fac70180
Instance ID                     : uuid:82af4436-fbe0-4b39-a950-de1c6933af42
Has XFA                         : No
Page Count                      : 170
Author                          : mmorris

EXIF Metadata provided by EXIF.tools

Paypal Payflow Pro 2008 Developers Guide PayflowPro_Guide

Payflow Pro - 2008 - Developer’s Guide PP_PayflowPro_2008 Free User Guide for PayPal Software, Manual

Navigation menu

Versions of this User Manual:

Views

Navigation