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 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
- 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
- Merchant e-Solutions, 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
- Submitting Purchasing Card Level 2 and Level 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
- Merchant e-Solutions 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: Viewing Processor- Specific Transaction Results
- ISO Country Codes
- Codes Used by FDMS South Only
- PayPal Acquirer
- Additional Processor Information
- Payflow Link Migration
Gateway Developer Guide and Reference 31 July 2012 157
Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
C
FDMS South Line Item Parameters
Line item data (Level 3) describes the details of the item purchased and can be can be passed
for each transaction. The convention for passing line item data in name-value pairs is that each
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.
FDMS South Purchasing Card Line Item Parameters
ORDERTIME (Optional) Order time and date. Format is either YYYY-MM-DD or YYYY-MM-DD
HH:MI:SS (where HH is in 24-hour time).
If the value does not conform to one of the formats or if the date is not valid (for
example, 2004-17-35), then the transaction is rejected with a RESULT=7
(SIG_FIELD_ERR) and RESPMSG=Invalid ORDERTIME.
A truncated version of the ORDERTIME value (up to 7 characters) overwrites any
value provided by ORDERDATE.
If no value is provided, a NULL value is stored.
Character length and limitations: 19 alphanumeric characters
PONUM (Optional) Purchase order number / merchant-related data.
Character length and limitations: 25 alphanumeric characters, provides best rate when
used
SHIPFROMZIP (Optional) The postal code (called zip code in the USA) from which shipping occurs.
Character length and limitations: 9 numeric characters, provides best rate when used
SHIPTOZIP (Optional) Ship to postal code (called zip code in the USA).
Character length and limitations: 9 numeric characters, provides best rate when used
BILLTOSTATE (Optional) Cardholder’s state.
Character length and limitations: 2 alpha characters
TAXAMT (Optional) 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).
Character length and limitations: 10 currency characters, provides best rate when
used
TAXEXEMPT (Optional) Is the customer tax exempt?
Character length and limitations: 1 alphanumeric character, Y or N
Field Description
L_QTY
n (Required) Quantity (whole units only).
Character length and limitations: 10 numeric characters
L_COMMCODE
n (Optional) Item commodity code.
Character length and limitations: 12 alphanumeric characters
Field Description