Developer's Guide
Table Of Contents
- Content
- Preface
- Introducing the Gateway Checkout Solutions
- Secure Token
- Configuring Hosted Checkout Pages
- Payflow SDK
- Sending a Simple Transaction to the Server
- Submitting Credit Card Transactions
- Obtaining an Internet Merchant Account
- About Credit Card Processing
- Credit Card Features
- Planning Your Gateway Integration
- Core Credit Card Parameters
- Submitting Account Verifications
- Submitting Authorization/Delayed Capture Transactions
- Submitting Balance Inquiry Transactions
- Submitting Card Present (SWIPE) Transactions
- Submitting Credit (Refund) Transactions
- Submitting Inquiry Transactions
- When To Use an Inquiry Transaction
- Required Parameters When Using the PNREF
- Inquiry Transaction Parameter String Using the PNREF
- Required Parameters When Using the CUSTREF
- Inquiry Transaction Parameter String Using the CUSTREF
- Required Parameters When Using the Secure Token
- Inquiry Parameter String Using the Secure Token
- Submitting Partial Authorizations
- Submitting Purchasing Card Transactions
- Submitting Reference Transactions (Tokenization)
- Submitting Sale Transactions
- Submitting Soft Merchant Information
- Submitting Voice Authorization Transactions
- Submitting Void Transactions
- Using Address Verification Service
- Using Card Security Code
- Information for the PayPal Acquirer
- Testing Transactions
- Transaction Responses
- Processors Requiring Additional Transaction Parameters
- American Express Additional Credit Card Parameters
- Elavon Additional Credit Card Parameters
- First Data Merchant Services Nashville, Additional Credit Card Parameters
- First Data Merchant Services North, Additional Credit Card Parameters
- Heartland, Additional Credit Card Parameters
- Litle Additional Credit Card Parameters
- Cielo Payments, Additional Credit Card Parameters
- Paymentech Salem (New Hampshire) Additional Credit Card Parameters for American Express
- PayPal Credit Card Transaction Request Parameters
- SecureNet Additional Credit Card Parameters for American Express
- Vantiv Additional Credit Card Parameters
- WorldPay Additional Credit Card Parameters
- TeleCheck Electronic Check Processing
- Payflow Header Parameters
- Submitting Purchasing Card Level 2 and 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions
- American Express Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing
- First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
- Global Payments - Central Purchasing Card Transaction Processing
- Global Payments - East Purchasing Card Transaction Processing
- Heartland Purchasing Card Transaction Processing
- Litle Purchasing Card Transaction Processing
- Cielo Payments Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- SecureNet Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- Vantiv Purchasing Card Transaction Processing
- WorldPay Purchasing Cards Transaction Processing
- VERBOSITY: Processor-Specific Transaction Results
- Country Codes
- Codes Used by FDMS South Only
- Additional Processor Information
- Payflow Link Migration
- Payflow Gateway MagTek Parameters
- Payflow Gateway FAQs
Submitting Purchasing Card Level 2 and 3 Transactions
About American Express Purchasing Card Transactions
D
164 07 January 2014 Gateway Developer Guide and Reference
Level 2 and Level 3 data is generally considered non-financial data. Lack of adequate data
may cause a transaction to be downgraded.
PayPal generally requires up to Level 2 information in an authorization transaction followed
by additional Level 3 data in the associated delayed capture transaction. A sale transaction
should include all Level 3 data since it is authorized and later settled.
Accepted BIN Ranges
Visa, MasterCard, and American Express publish specific Bank Identification Number (BIN)
ranges for purchasing cards. Sometimes the processor determines whether a card is a
purchasing card, for example, TSYS Acquiring Solutions. In other cases, the Gateway makes
the determination based on the BIN range (for example, FDMS South and American Express).
About American Express Purchasing Card Transactions
The information in this section applies to transactions processed by American Express not
necessarily to all American Express cards. Level 2 and Level 3 purchasing card rules may
differ for American Express card transactions processed by other processors such as
Paymentech or First Data Nashville.
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 Gateway decides whether a
transaction meets Level 3 requirements during authorization.
Level 3 data is passed to the American Express processor only during settlement.
Level Description
Level 1 Function as normal credit cards and are authorized and associated with normal
transaction data in authorization and settlement. Any merchant who accepts credit
cards supports this level..
Level 2 Additional data regarding sales tax, customer code, purchase order number, invoice
number are captured at the point of sale. In most cases, this information is combined
with the merchant's tax ID number, state, and postal code data and is then passed
through during settlement. For some processors and banks, however, a Level 2
authorization may include some of this data.
Level 3 Significant additional information such as line items, product codes, item
descriptions, unit price, unit quantities, and ship-to postal data are added to the Level
2 data to provide optimal reporting to buyers and sellers. Settlement transactions
typically carry Level 3 data.