Payflow Pro Developer’s Guide Last updated: October 2009
Payflow Pro Developer’s Guide Document Number: 200010.en_US-200910 © 2009 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 (Europe) S.à r.l. et Cie., S.C.A.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 How to Contact Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 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 Recharging to the Same Credit Card (Reference Transactions). . . . . . . . . . . . . . . 40 When To Use a Reference Transaction . . . . . . . . . . . . . . . . . . . . . . . . . 40 Transaction Types that Can Be Used as the Original Transaction . . . . . . . . . . . 41 Fields Copied From Reference Transactions . . . . . . . . . . . . . . . . . . . . . . 41 Example Reference Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Submitting Card-Present (SWIPE) Transactions. . . . .
Contents American Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 American Express Additional Credit Card Parameters (CAPN) . . . . . . . . . . . . . 68 American Express Additional Credit Card Parameters (Legacy) . . . . . . . . . . . . 73 First Data Merchant Services (FDMS) Nashville . . . . . . . . . . . . . . . . . . . . . . . 76 FDMS Nashville, Additional Credit Card Parameters . . . . . . . . . . . . . . . . . . 76 First Data Merchant Services (FDMS) South . . .
Contents Edit Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Accepted BIN Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 American Express Phoenix Purchasing Card Transaction Processing . . . . . . . . . . .102 American Express Phoenix Level 2 Parameters (CAPN) . . . . . . . . . . . . . . . .103 American Express Phoenix Level 2 Parameters (Legacy). . . . . . . . . . . . . . . .
Contents TSYS Acquiring Solutions Level 2 Parameters . . . . . . . . . . . . . . . . . . . . .131 TSYS Acquiring Solutions Level 3 MasterCard Parameters. . . . . . . . . . . . . . .132 TSYS Acquiring Solutions Level 3 Visa Parameters. . . . . . . . . . . . . . . . . . .134 Appendix D VERBOSITY: Viewing Processor-Specific Transaction Results . . . . . . . . . . . . . . . . . . . . . . . . 139 Supported Verbosity Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
Revision History Revision History Revision history for Payflow Pro Developer’s Guide. TABLE 1.1 Revision history Date October 2009 Description z z z z Added COMPANYNAME to reporting parameters. Added new appendix on additional processor informaion. Currently includes Moneris processor information. Added Account Verification as a type of transaction that uses TRXTYPE=A and AMT=0 to verify credit card information. Updated length of PARTNER, USER, and VENDOR to 64 characters.
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 Purchasing cards (also referred to as commercial cards, corporate cards, procurement cards, or business cards) Level II and Level III z 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 .
2 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.
3 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 3 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.
3 Simple Payflow Transaction Formatting Transactions z EXPDATE - The expiration date of the credit card 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&BILLTOCOUNTRY=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 44. 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 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.
Credit Card Transactions Submitting Sale Transactions TABLE 4.1 Credit card transaction request parameters Parameter Description 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.
Credit Card Transactions Submitting Authorization/Delayed Capture Transactions 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.
Credit Card Transactions Submitting Authorization/Delayed Capture Transactions 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 z AMT z EXPDATE Typical Authorization Transaction Parameter String A typical parameter string passed in an Authorization transaction is the same as a Sale transaction string.
Credit Card Transactions Submitting Authorization/Delayed Capture Transactions used. (Exceptions are ACCT, EXPDATE, and SWIPE. These parameters retain their original values.) TABLE 4.
Credit Card Transactions Submitting Account Verifications With TRXTYPE=A 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.
Credit Card Transactions Submitting Voice Authorization Transactions z The TRANSSTATE is set to 0 to prevent these types of transactions from being credited, voided, or captured. See “VERBOSITY: Viewing Processor-Specific Transaction Results” on page 139 for details on TRANSSTATE. N O T E : RESULT value 4, Invalid Amount, is returned if the processor does not support Account Verifications.
Credit Card Transactions Submitting Credit Transactions 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.
Credit Card Transactions Submitting Credit Transactions ORIGID TABLE 4.5 Credit 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 the value of ORIGID to the PNREF value returned for the original transaction.
Credit Card Transactions Submitting Void Transactions TABLE 4.
Credit Card Transactions Submitting Void Transactions 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 (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.
Credit Card Transactions Submitting Inquiry Transactions “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.
Credit Card Transactions Submitting Inquiry Transactions 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.
Credit Card Transactions Recharging to the Same Credit Card (Reference Transactions) 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.
Credit Card Transactions Recharging to the Same Credit Card (Reference Transactions) 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 Card Transactions Submitting Card-Present (SWIPE) Transactions 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.
Credit Card Transactions Submitting Card-Present (SWIPE) Transactions z 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. z A Sale is the preferred method to use for card-present transactions.
Credit Card Transactions Submitting Purchasing Card Transactions 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.
Credit Card Transactions Example Address Verification Service Request Parameter List TABLE 4.
Credit Card Transactions Card Security Code Validation 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.
Credit Card Transactions Card Security Code Validation TABLE 4.
Credit Card Transactions Card Security Code Validation 48 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&AVSZIP=N&CVV2MATCH=Y Contents of a Response to a Credit Card Transaction Request The table below 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.8 Transaction response values Field Description 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 6 TABLE 6.8 Transaction response values Field Description AMEXPOSDATA Value returned when VERBOSITY=MEDIUM or VERBOSITY=HIGH.. Character length and limitations: 12 alphanumeic characters 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.
6 Responses to Transaction Requests RESULT Values and RESPMSG Text PNREF Format The PNREF is a 12-character string of printable characters, for example: z VADE0B248932 z 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.
Responses to Transaction Requests RESULT Values and RESPMSG Text 6 TABLE 6.9 Payflow Transaction RESULT Values and RESPMSG Text RESULT RESPMSG and Explanation 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.9 Payflow Transaction RESULT Values and RESPMSG Text 60 RESULT RESPMSG and Explanation 23 Invalid account number. Check credit card number and re-submit. 24 Invalid expiration date. Check and re-submit. 25 Invalid Host Mapping. 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.
Responses to Transaction Requests RESULT Values and RESPMSG Text 6 TABLE 6.9 Payflow Transaction RESULT Values and RESPMSG Text 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.
6 Responses to Transaction Requests RESULT Values and RESPMSG Text TABLE 6.9 Payflow Transaction RESULT Values and RESPMSG Text RESULT RESPMSG and Explanation 122 Merchant sale total will exceed the credit cap with current transaction. ACH transactions only. 125 Fraud Protection Services Filter — Declined by filters 126 Fraud Protection Services Filter — Flagged for review by filters I M P O R T A N T : RESULT value 126 indicates that a transaction triggered a fraud filter.
Responses to Transaction Requests RESULT Values and RESPMSG Text 6 TABLE 6.9 Payflow Transaction RESULT Values and RESPMSG Text RESULT RESPMSG and Explanation 1013 Buyer Authentication Service unavailable 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 TABLE 6.9 Payflow Transaction RESULT Values and RESPMSG Text RESULT RESPMSG and Explanation 1052 Buyer Authentication Service — Validate Authentication failed: This PARES was already validated for a previous Validate Authentication transaction RESULT Values for Communications Errors A RESULT value less than zero indicates that a communication error occurred. In this case, no transaction is attempted.
Responses to Transaction Requests RESULT Values and RESPMSG Text 6 TABLE 6.
6 66 Responses to Transaction Requests RESULT Values and RESPMSG Text Website Payments Pro Payflow Edition 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 9 for contact information. TABLE A.2 74 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 76 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 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.
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 TABLE A.8 Additional Paymentech parameters to meet CAPN Parameter Description Required Type Length PHONENUM Account holder’s telephone number No String 20 PHONETYPE Telephone company provided ANI information identifier digits indicating the telephone call type Examples: cellular (61-63), payphone (27) No Alphanumeric 2 CUSTHOSTNAME Name of the server that the account holder is connected to Example: PHX.QW.AOL.
Processors Requiring Additional Transaction Parameters Paymentech TABLE A.8 Additional Paymentech parameters to meet CAPN Parameter Description Required Type Length 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 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 82 Additional Paymentech parameters (legacy) Parameter Description Required Type Length CITY Cardholder’s billing city.
Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions TABLE A.9 A Additional Paymentech parameters (legacy)(Continued) Parameter Description Required Type Length RECURRINGTYPE (Paymentech Tampa only) Type of transaction occurrence. The values are: F = First occurrence S = Subsequent occurrence (default) No Alpha 1 TSYS Acquiring Solutions TSYS Acquiring Solutions, Additional Credit Card Parameters (CAPN) In addition to the parameters in Table 4.
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 CUSTHOSTNAME Name of the server that the account holder is connected to Example: PHX.QW.AOL.COM No Alphanumeric and special characters 60 CUSTBROWSER Account holder’s HTTP browser type Example: MOZILLA/4.0~(COMPATIBLE;~MSIE~5.
Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions A TABLE A.
A Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions TABLE A.
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 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.
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-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.
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 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).
A Processors Requiring Additional Transaction Parameters TSYS Acquiring Solutions TABLE A.11 TSYS Acquiring Solutions additional parameters (legacy)(Continued) 90 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.
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 92 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 “RESULT Values and RESPMSG Text” on page 58.
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 98 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.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 17 SHIPTOZIP Ship-to postal code (called zip code in the USA).
C 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_DESC4 Description of this line item; if not provided, DESC4 (if present) is used No Alphanumeric 40 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.
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.3 American Express Phoenix Legacy Level 2 parameters Parameter Description Required Type Length PONUM Purchase order number Yes Alphanumeric 17 SHIPTOZIP Ship-to postal code (called zip code in the USA).
C Submitting Purchasing Card Level 2 and Level 3 Transactions American Express Phoenix Purchasing Card Transaction Processing Postal code, Merchant No, and Federal Tax ID. The merchant provides the values listed in Table C.4. AMEX Name (per American Express Specification) 106 Mandatory / Optional TABLE C.4 American Express Phoenix Level 3 Parameters Pay Flow SDK parameter XMLPayRequest parameter (See Payflow Pro XMLPay Developer’s Guide for detailed instructions.
Submitting Purchasing Card Level 2 and Level 3 Transactions American Express Phoenix Purchasing Card Transaction Processing AMEX Name (per American Express Specification) Total Transaction Amount Mandatory / Optional TABLE C.4 M C American Express Phoenix Level 3 Parameters (Continued) Pay Flow SDK parameter 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).
C Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services (FDMS) Nashville 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) O L_FREIGHTAMTn Item.FreightAmt 1/15, NUM Handling Amount O L_HANDLINGAMTn Item.
Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing C The following parameters are recommended to obtain the best rates for purchasing card transactions with FDMS Nashville. TABLE C.5 FDMS commercial card parameters Parameter Description Required Type Length COMMCARD One-character value representing type of purchasing card account number sent.
C 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 110 FDMS North purchasing card parameters Parameter Description Required Type Length SHIPTOCOUNTRY Destination country code.
Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing TABLE C.6 C 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 166.
C 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 112 FDMS South Level 2 and Level 3 purchasing card parameters Parameter Description Required Type Length CITY Cardholder’s city.
Submitting Purchasing Card Level 2 and Level 3 Transactions First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing TABLE C.8 C 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).
C 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 10 L_COMMCODEn Item commodity code.
Submitting Purchasing Card Level 2 and Level 3 Transactions Global Payments - Central Purchasing Card Transaction Processing C 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.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Merchant e-Solutions Purchasing Card Transaction Processing C 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.
C 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 M PONUM Value of TransID is sent if no value is provided.
Submitting Purchasing Card Level 2 and Level 3 Transactions Merchant e-Solutions Purchasing Card Transaction Processing C 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.
C 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 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 Merchant e-Solutions Purchasing Card Transaction Processing C TABLE C.17 Merchant e-Solutions Level 3 Visa extended data (Continued) Merchant eSolutions Name Mandatory / Optional 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 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Elavon (Formerly Nova) Purchasing Card Transaction Processing C 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.
C 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).
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing C TABLE C.21 Paymentech Salem (New Hampshire) CAPN Level 2 parameters Parameter Description Required Type Length L_DESC1 Description of this line item; if not provided, DESC1 (if present) is used No 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.
C Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing TABLE C.
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing C 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.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing C Paymentech Salem (New Hampshire) Level 3 Visa Parameters Level 3 transactions should include at least one line item. TABLE C.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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).
C 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 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).
Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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 Purchase Identifier M PONUM Value of TransID is sent if no value is provided.
C 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.
Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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 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 TSYS Acquiring Solutions Purchasing Card Transaction Processing TABLE C.32 TSYS Acquiring Solutions Level 3 Visa extended data (Continued) Name 136 Mandatory / Optional Length, Data Type Payflow Parameter 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 TSYS Acquiring Solutions Purchasing Card Transaction Processing C 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 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 138 Submitting Purchasing Card Level 2 and Level 3 Transactions TSYS Acquiring Solutions Purchasing Card Transaction Processing Payflow Pro Developer’s Guide
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 140 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 152 ISO Country Codes 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 154 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 156 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 158 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 160 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 162 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 164 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 168 XMLPay Payflow Pro XMLPay Developer’s Guide Payflow Pro Developer’s Guide
I Additional Processor Information This appendix provides additional processor information. Moneris Solutions The Moneris Solutions processor has the following characteristics: z It supports ecommerce and mail order or telephone order (MOTO) transactions. z It supports the four basic credit card types: American Express, Discover, MasterCard, and Visa. z To process live transactions, it requires undergoing a certification process.
Additional Processor Information Moneris Solutions 170 Payflow Pro Developer’s Guide
Index A Account Verification 23, 32 ADDLMSGS 101 address verification service 44 ALTERNATETAXAMT parameter 128 ALTERNATETAXID parameter 128 ALTTAXAMT parameter 118, 133 American Express 67 American Express CAPN 68, 83, 102, 124 AMT 101 AMT parameter 27, 107 APIs documentation 17 downloading 17 application testing 49 AUTHCODE parameter 34, 106 B BALAMT 57 BALAMT parameter 57 Bank Identification Numbers.
Index H HANDLINGAMT parameter 107 HOSTCODE parameter 95 I inquiry transaction type 38 INVNUM parameter 73, 74, 76, 78, 82, 88, 89, 106, 112, 118, 121, 133, 136 INVOICEDATE parameter 106 L L_AMTn parameter 111, 114, 122, 128, 129, 137 L_CATALOGNUMn parameter 107 L_COMMCODEn parameter 111, 114, 122, 137 L_COSTCENTERNUMn parameter 107 L_COSTn parameter 107, 111, 114, 122, 129 L_COSTn parameterPayflow parameters L_COSTn 137 L_DESCn parameter 107, 111, 114, 119, 122, 128, 129, 134, 137 L_DISCOUNTn 137 L_DISCO
Index testing 49 ORDERDATE parameter 73, 74, 88, 112, 120, 135 ORDERDATETIME parameter 73, 75, 89 ORDERTIME parameter 113 ORIGID parameter 30, 35, 37, 38 P parameters required for electronic check 91 PARTNER parameter 21 Payflow parameters ACCT 21, 28, 30, 31, 35, 37, 41, 43 ACCTTYPE 41 ADDLAMTn 71, 86, 104, 126 ADDLAMTTYPEn 71, 86, 104, 126 ADDLMSGS 101, 140 ALTERNATETAXAMT 128 ALTERNATETAXID 128 ALTTAXAMT 118, 133 AMEXID 142 AMEXPOSDATA 142 AMT 21, 27, 28, 30, 31, 35, 37, 91, 92, 101, 107 AUTHCODE 33, 3
Index L_QTY2 103, 125 L_QTY3 103, 125 L_QTY4 104, 125 L_QTYn 68, 83, 102, 107, 111, 114, 119, 122, 128, 129, 134 L_TAXAMTn 107, 111, 114, 119, 122, 129, 134, 137 L_TAXRATEn 119, 122, 129, 134, 137 L_TAXTYPEn 119, 128, 134 L_TRACKINGNUMn 108 L_UNSPSCCODEn 108 L_UOMn 107, 114, 119, 122, 128, 129, 134, 137 L_UPCn 107, 111, 119, 122, 129, 134, 137 LASTNAME 27, 31, 36, 37, 41, 73, 74, 88, 112, 145 LOCALTAXAMT 118, 120, 133, 135 MERCHANTCITY 70, 85, 104, 125 MERCHANTCOUNTRYCODE 70, 86, 104, 126 MERCHANTNAME 70,
Index ZIP 24, 27, 31, 36, 37, 41, 44, 45, 53, 69, 81, 84, 92, 93, 146 payflowpro.paypal.com 13 payment types 15 PayPal Developer Central 9 PHONENUM parameter 69, 81, 84, 93 pilot-payflowpro.paypal.
Index sale 28 void 36 TRXTYPE parameter 26 TSYS Acquiring Solutions 83 type N transactions 26 U USER parameter 21 V VATREGNUM parameter 121, 136 VATTAXAMT parameter 121, 136 VATTAXPERCENT parameter 121, 136 VENDOR parameter 21 VERBOSITY 101 VERBOSITY parameter 139 void transaction type 36 Z zero dollar Authorization 23, 32 ZIP parameter 27, 69, 81, 84 176 Payflow Pro Developer’s Guide
