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.
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.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 How to Contact Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Revision History . . . . . . . . . . .
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) . . .
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 . . . . .
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. . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . .
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 . . . . . . . . . . . . . . . . .
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.
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 z June 2008 Moved coverage of Express Checkout to a separate new document, Express Checkout for Payflow Pro.
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.
Revision History 12 Payflow Pro Developer’s Guide
1 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 z Java library z HTTPS interface Using the HTTPS interface, you can build your own API by posting directly to the Payflow servers via HTTPS.
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.
Introduction Supported Payment Types Supported Payment Types Payflow Pro supports multiple payment types in a single installation, including: z Credit cards z PayPal (supported by PayPal’s Express Checkout product) z Pinless debit cards z Electronic checks z Check cards z z Purchasing cards (also referred to as commercial cards, corporate cards, procurement cards, or business cards) Level II and Level III Automated Clearing House (ACH).
Introduction About Security 16 Payflow Pro Developer’s Guide
2 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 .
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.
3 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.
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.
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.
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.
4 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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
Credit Card Transactions Submitting Purchasing Card Transactions z Paymentech Salem (New Hampshire) z Paymentech Tampa z 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.
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.
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.
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.
Credit Card Transactions Card Security Code Validation 46 Payflow Pro Developer’s Guide
5 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.
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.
Credit Card Testing RESULT Values Returned Based on Transaction Amount TABLE 5.
Credit Card Testing RESULT Values Returned Based on Transaction Amount TABLE 5.
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.
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.
6 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.
6 Responses to Transaction Requests Contents of a Response to a Credit Card Transaction Request TABLE 6.1 54 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.
Responses to Transaction Requests BALAMT Response Parameter and Stored Value Cards TABLE 6.1 6 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 15 Alphanumeric 12 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.
6 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 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).
Responses to Transaction Requests RESULT Values and RESPMSG Text TABLE 6.2 Payflow transaction RESULT values and RESPMSG text RESULT RESPMSG and Explanation 0 Approved. 1 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.
6 Responses to Transaction Requests RESULT Values and RESPMSG Text TABLE 6.2 58 Payflow transaction RESULT values and RESPMSG text (Continued) RESULT RESPMSG and Explanation 22 Invalid ABA number 23 Invalid account number. Check credit card number and re-submit. 24 Invalid expiration date. Check and re-submit. 25 Invalid Host Mapping.
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.
6 Responses to Transaction Requests RESULT Values and RESPMSG Text TABLE 6.2 60 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.
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.
6 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.
Responses to Transaction Requests RESULT Values and RESPMSG Text TABLE 6.
6 64 Responses to Transaction Requests RESULT Values and RESPMSG Text Payflow Pro Developer’s Guide
A Processors Requiring Additional Transaction Parameters This appendix lists both required and optional parameters supplementary to the common parameter set.
A 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.
Processors Requiring Additional Transaction Parameters American Express TABLE A.1 A American Express CAPN parameters (Continued) Parameter Description Required Type Length CUSTIP Account holder’s IP address No Alphanumeric and special characters 15 SHIPTOCOUNTRY Numeric country code of ship-to country Example: USA: 840 No Alphanumeric 3 SHIPMETHOD Shipping method code.
A 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 No Alphanumeric 9 SHIPTOPHONENUM Shipping telephone number No String 10 RECURRING Identifies the transaction as recurring. This value does not activate PayPal’s Recurring Billing Service APIs.
Processors Requiring Additional Transaction Parameters American Express TABLE A.1 A 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.
A 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.
Processors Requiring Additional Transaction Parameters American Express TABLE A.1 Parameter A 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). No Alphanumeric 13 LASTNAME Account holder's last name.
A 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 72 American Express legacy parameters Parameter Description Required Type Length DESC Describes the transaction. No Alphanumeric Brighton 40 Other American Express platforms 23 DESC1 Describes the transaction.
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).
A 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 74 FDMS Nashville additional parameters Parameter Description Required Type Length INVNUM Merchant invoice number.
Processors Requiring Additional Transaction Parameters First Data Merchant Services (FDMS) South A 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.
A 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.
Processors Requiring Additional Transaction Parameters Elavon (Formerly Nova) A Elavon (Formerly Nova) Elavon, Additional Credit Card Parameters In addition to the parameters in Table 4.1 , “Credit card transaction request parameters,”Elavon accepts the following parameter: 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.
A 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.
Processors Requiring Additional Transaction Parameters Paymentech TABLE A.8 Parameter A Additional Paymentech parameters to meet CAPN requirements(Continued) Description Required Type Length STREET Account holder’s street address (number and street name) No Alphanumeric 30 ZIP Account holder’s 5- to 9-digit ZIP (postal) code excluding spaces, dashes, and non-numeric characters Example: 951121737 No String 9 PHONENUM Account holder’s telephone number.
A 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.
Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions TABLE A.9 A Additional Paymentech parameters (legacy)(Continued) Parameter Description Required Type Length STATE Cardholder’s billing state. No Alpha 2 SWIPE Allows Track 1 and Track 2 data to be passed to enable a card-present transaction. No Alphanumeric 80 RECURRING Identifies the transaction as recurring. This value does not activate PayPal’s Recurring Billing Service APIs.
A 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 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.
Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions A TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN requirements (Continued) Parameter Description Required Type Length SHIPMETHOD Shipping method code.
A 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 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.
Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions A 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 No Alphanumeric 3 Airline Passenger Data Parameters AIR-DEPARTUREDATE Departure date in the format YYYYMMDD.
A 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 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.
Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions A TABLE A.10 Additional TSYS Acquiring Solutions parameters to meet CAPN requirements (Continued) 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.
A Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions TABLE A.11 TSYS Acquiring Solutions additional parameters (legacy)(Continued) 88 Parameter Description Required Type Length SWIPE Allows Track 1 and Track 2 data to be passed to enable a card-present transaction. No Alphanumeric 80 RECURRING Identifies the transaction as recurring. This value does not activate PayPal’s Recurring Billing Service API.
B 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).
B Performing TeleCheck Electronic Check Transactions TeleCheck Parameters STREET ZIP TABLE B.1 90 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.
Performing TeleCheck Electronic Check Transactions Testing TeleCheck Transactions TABLE B.1 B 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.
B Performing TeleCheck Electronic Check Transactions Preparing for TeleCheck Production Transactions Name>&PWD=& AMT=42.00&STREET=1234 Main&CITY=Buffalo&DL=CA123456&CHKNUM=1001&EMAIL=&MICR=
Performing TeleCheck Electronic Check Transactions HOSTCODE Values B 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.
B 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.
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.
B 96 Performing TeleCheck Electronic Check Transactions HOSTCODE Values Payflow Pro Developer’s Guide
C 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.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions About American Express Purchasing Card Transactions - Phoenix Processor C 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.
C 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).
Submitting Purchasing Card Level 2 and Level 3 Transactions American Express Phoenix Purchasing Card Transaction Processing C American Express Phoenix Level 2 Parameters (CAPN) TABLE C.
C Submitting Purchasing Card Level 2 and Level 3 Transactions American Express Phoenix Purchasing Card Transaction Processing TABLE C.
Submitting Purchasing Card Level 2 and Level 3 Transactions American Express Phoenix Purchasing Card Transaction Processing C American Express Phoenix Level 2 Parameters (Legacy) TABLE C.
C 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 M AUTHCODE (Passed transparently for delayed capture. Use only with voice authorized force capture transactions) ForceCapture.
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) M L_COSTn Item.UnitPrice 1/15, NUM Item Description M L_DESCn Item.Description 1/80, AN Supplier Catalog No M L_CATALOGNUMn Item.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing C 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.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing C 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.
C 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).
Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing C 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 10 L_COMMCODEn Item commodity code.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Merchant e-Solutions Purchasing Card Transaction Processing C 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.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Merchant e-Solutions Purchasing Card Transaction Processing C 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 M PONUM Value of TransID is sent if no value is provided.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Merchant e-Solutions Purchasing Card Transaction Processing C 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 M PONUM Value of TransID is sent if no value is provided.
C 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 M SHIPFROMZIP The postal code (called ZIP code in the USA) from which shipping occurs.
Submitting Purchasing Card Level 2 and Level 3 Transactions Merchant e-Solutions Purchasing Card Transaction Processing C 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.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing C 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).
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing C TABLE C.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing C Paymentech Salem (New Hampshire) Level 3 MasterCard Parameters TABLE C.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Tampa Level 2 Purchasing Card Transaction Processing C 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.
C 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 M PONUM 1/17, char Sales Tax M 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).
Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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 M PONUM 1/17, AN Tax Amount M TAXAMT The value must include a decimal and the exact amount to the cent (42.00, not 42).
C 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 M PONUM Value of TransID is sent if no value is provided.
Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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.
C 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 M PONUM Value of TransID is sent if no value is provided.
Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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 M SHIPFROMZIP The postal code (called ZIP code in the USA) from which shipping occurs.
C 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.
D 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.
D VERBOSITY: Viewing Processor-Specific Transaction Results Supported Verbosity Settings TABLE D.2 136 Processor responses Field Name Type Length Description HOSTCODE Char 7 Response code returned by the processor. This value is not normalized by PayPal. RESPTEXT Char 17 Text corresponding to the response code returned by the processor. This text is not normalized by PayPal.
VERBOSITY: Viewing Processor-Specific Transaction Results Supported Verbosity Settings TABLE D.2 D Processor responses(Continued) Field Name Type Length Description TRANSSTATE Integer 10 State of the transaction.
D VERBOSITY: Viewing Processor-Specific Transaction Results Supported Verbosity Settings TABLE D.2 Processor responses(Continued) Field Name Type Length Description AMEXID Numeric 15 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.
VERBOSITY: Viewing Processor-Specific Transaction Results Supported Verbosity Settings TABLE D.2 D Processor responses(Continued) Field Name Type Length Description VISACARDLEVEL Alphanumeric 2 Card product level indicator returned by VISA.
D 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.
E 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.
E Additional Reporting Parameters TABLE E.
F ISO Country Codes The following International Standards Organization (ISO) country codes are used when filling the order fields BILLTOCOUNTRY, SHIPTOCOUNTRY, and CORPCOUNTRY: TABLE F.
F ISO Country Codes TABLE F.
ISO Country Codes TABLE F.
F ISO Country Codes TABLE F.
ISO Country Codes TABLE F.1 F 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) 92 Western Samoa 882 Virgin Islands (U.S.) 850 Yemen 887 Wallis and Futuna Islands 876 Yugoslavia 891 Virgin Islands (British) 92 Zaire 180 Virgin Islands (U.S.
F 148 ISO Country Codes November 2008 Payflow Pro Developer’s Guide
G 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.
G Codes Used by FDMS South Only MasterCard Country Codes TABLE G.1 150 MasterCard country codes TABLE G.
Codes Used by FDMS South Only MasterCard Country Codes TABLE G.1 MasterCard country codes TABLE G.
G 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.
Codes Used by FDMS South Only Visa Country Codes TABLE G.1 G 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.
G Codes Used by FDMS South Only Visa Country Codes TABLE G.2 154 TABLE G.
Codes Used by FDMS South Only Visa Country Codes TABLE G.2 TABLE G.
G Codes Used by FDMS South Only Visa Country Codes TABLE G.2 156 TABLE G.2 Visa country codes Visa country codes NETHERLANDS NL SAUDI ARABIA SA NETHERLANDS ANTILLES AN SENEGAL SN NEW CALDONIA NC SEYCHELLES SC NEW ZEALAND NZ SIERRA LEONE SL NICARAGUA NI SINGAPORE SG NIGER NE ST. HELENA SH NIGERIA NG ST. KITTS-NEVIS-ANGUILLA KN NIUE NU ST. LUCIA LC NORFOLK ISLAND NF ST. PIERRE AND MIQUELON PM NORTHERN MARIANA ISLAND MP VC NORWAY NO ST.
Codes Used by FDMS South Only Units of Measure TABLE G.2 G Visa country codes U.S. MINOR OUTLYING ISL. UM UGANDA UG UKRAINIAN SSR UA UNITED ARAB EMIRATES AE UNITED KINGDOM GB UNITED STATES US URAGUAY UY UZBEKISTAN UZ VANUATU VU VATICAN CITY STATE VA VENEZUELA VE VIETNAM VN VIRGIN ISLANDS BRITISH VG VIRGIN ISLANDS US VI WALLIS AND FUTUNA IS WF WESTERN SAHARA EH YEMEN YE YUGOSLAVIA YU ZAIRE ZR ZAMBIA ZM ZIMBABWE ZW Units of Measure TABLE G.3 TABLE G.
G Codes Used by FDMS South Only Units of Measure TABLE G.3 158 TABLE G.
Codes Used by FDMS South Only Units of Measure TABLE G.3 TABLE G.
G Codes Used by FDMS South Only Units of Measure TABLE G.3 160 TABLE G.
Codes Used by FDMS South Only Units of Measure TABLE G.
G 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.
H 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.
H 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.
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 pa
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 AM
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,
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.
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 2
