Developer's Guide
Table Of Contents
- Contents
- Introduction
- Downloading, Installing, and Activating
- Simple Payflow Transaction
- Credit Card Transactions
- Credit Card Features
- About Credit Card Processing
- Parameters Used in Credit Card Transactions
- Submitting Sale Transactions
- Submitting Authorization/Delayed Capture Transactions
- When To Use Authorization/Delayed Capture Transactions
- Required Authorization Transaction Parameters
- Typical Authorization Transaction Parameter String
- Required Delayed Capture Transaction Parameters
- Delayed Capture Transaction: Capturing Transactions for Lower Amounts
- Delayed Capture Transaction: Capturing Transactions for Higher Amounts
- Delayed Capture Transaction: Error Handling and Retransmittal
- Submitting Account Verifications With TRXTYPE=A
- Submitting Voice Authorization Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Submitting Purchasing Card Transactions
- Using Address Verification Service
- Processing Platforms Supporting Address Verification Service
- Example Address Verification Service Request Parameter List
- Example Address Verification Service Response
- Card Security Code Validation
- Credit Card Testing
- Responses to Transaction Requests
- Processors Requiring Additional Transaction Parameters
- Performing TeleCheck Electronic Check Transactions
- Submitting Purchasing Card Level 2 and Level 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions - Phoenix Processor
- American Express Phoenix 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
- Merchant e-Solutions Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- VERBOSITY: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- ISO Country Codes
- Codes Used by FDMS South Only
- XMLPay
- Additional Processor Information
- Index
Submitting Purchasing Card Level 2 and Level 3 Transactions
First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
C
112 Payflow Pro Developer’s Guide
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. No Alpha 13
SHIPTOCOUNTRY Destination Country Code. Visa and MasterCard
are different. Refer to Country Code tables. (See
Appendix F, “ISO Country Codes)
No Alpha 4
CUSTCODE Customer code/customer reference ID. No Alpha-
numeric
17
DISCOUNT Discount amount on total sale. No Currency 10
DUTYAMT Sometimes called import tax.
If the currency uses a decimal, then 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.
No Currency 10
FIRSTNAME Cardholder’s first name. No Alpha 15
FREIGHTAMT Freight amount.
If the currency uses a decimal, then 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.
No Currency 10
INVNUM Merchant invoice number. This reference number
(PNREF—generated by PayPal) is used for
authorizations and settlements.
The acquirer decides if this information will
appear on the merchant’s bank reconciliation
statement.
No Alpha-
numeric
9
LASTNAME Cardholder’s last name. No Alpha 15
ORDERDATE Order date.
Format is mmddyy with no slashes or dashes. For
example,
July 28, 2003 is 072803.
No Numeric 6