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
Gateway Developer Guide and Reference 07 January 2014 135
Processors Requiring Additional Transaction Parameters
SecureNet Additional Credit Card Parameters for American Express
A
Location Transaction Advice Addendum Parameters
SHIPTOPHONENUM (Optional) Shipping telephone number.
Character length and limitations: 10 alphanumeric characters
Parameter Description
MERCHANTNAME (Optional) Name of merchant.
Character length and limitations: 38 alphanumeric characters
MERCHANTSTREET (Optional) Merchant’s street address (number and street name).
Character length and limitations: 38 alphanumeric characters. If more than 38
characters, use proper and meaningful abbreviation. Do not truncate.
MERCHANTCITY (Optional) The name of the city were the transaction took place.
If you are a third-party biller (bill for services or goods rendered by another
entity), you must enter the name of the city in which the seller is located.
If you are a mail order, phone order, or internet industry, you may substitute the
name of the city in which the merchant’s order processing facility is located.
Character length and limitations: 21 alphanumeric characters. If more than 21
characters, use proper and meaningful abbreviation. Do not truncate.
MERCHANTSTATE (Optional) The region code that corresponds to the state, province, or country
subdivision of the merchant location where the transaction took place.
Region code examples:
CA = California, USA
NS = Nova Scotia, Canada
COS = Colima Mexico
If you are a third-party biller (bill for services or goods rendered by another entity),
you must enter the region code that corresponds to the state, province, or country
subdivision in which the seller is located.
Character length and limitations: 3 alphanumeric characters
MERCHANTCOUNTRYCODE (Optional) Country code of the location where the transaction took place. The
Payflow API accepts 3-digit numeric country codes. Refer to:
http://en.wikipedia.org/wiki/ISO_3166-1_numeric.
Character length and limitations: 3-character country code.
MERCHANTZIP (Optional) The 5- to 9-digit zip (postal) code excluding spaces, dashes, and non-
numeric characters where the transaction took place.
If you are a third-party biller (bill for services or goods rendered by another entity),
you must enter the postal code that corresponds to the seller’s location.
Character length and limitations; 15 alphanumeric characters
Field Description