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
TeleCheck Electronic Check Processing
TeleCheck NFTF Processing Overview
B
130 31 July 2012 Gateway Developer Guide and Reference
Dual ID is required for all transactions. For personal checks, it must be MICR data and
personal check writer identification such as a driver’s license. For company checks, it must
be MICR data and Federal Tax ID. In the event that a company does not have a Federal Tax
ID, the driver’s license can also be used.
For ICA and NFTF PPD, the merchant must retain the customer’s authorization of the
transaction for a period of 2 years and, for ICA, prompt the customer to print a copy of this
confirmation for their records. The merchant must adhere to all authorization requirements,
data elements, legal verbiage, and check return fee requirements.
For CBP, the merchant must audio record the customer’s verbal confirmation of the
transaction or provide a written confirmation of the transaction to the customer prior to
settlement. In either case, the confirmation must be live; IVR is not acceptable for
confirmation. If a merchant chooses audio, the merchant must have the technical capability
to retain these recordings for a period of 2 years; else the written confirmation may be
substituted and retained for the same time period. The merchant must adhere to all
authorization requirements; data elements, legal verbiage, and check return fee
requirements.
Only select US accounts drawn on U.S. banks participating in the ACH Network are
eligible for processing via the ACH Network.
TeleCheck Trace ID (TTID) is required for all supplemental messages, change, void, and
adjustment transactions.
Merchant Trace ID is required for all adjustment transactions. This field allows additional
capabilities to be enabled such as Overflow Credits and MIA Duplicate Checking.
Change and Void transactions are only allowed within the original Sale processing window.
For NFTF, cutoff time is 4:00PM CST (recommend working with 3:30PM CST).
Adjustment transactions are electronically allowed within 90 days after the Sale
transaction. After the 90 day period, all adjustments must be manually processed.
A prompt or process must be in place to identify a check as either personal or company.
Duplicate Checking – TeleCheck has the ability to detect duplicate sale transactions at the
point of sale if sent within a predetermined time limit. Duplicates are identified when a sale
inquiry is received with the same amount, MICR number, and check number matching a
sale inquiry received within the last 2 minutes. If a duplicate is detected it will return an
ineligible response for ACH. The 2nd transaction will also receive an ineligible response
for ACH with the same ACH Transaction Status and Response Code as the original sale
transaction.
The appropriate Application Type value must be sent to TeleCheck to indicate the type of
NFTF transaction (ICA, CBP, or NFTF PPD).
In the NFTF technical specification several data element fields and features are described
as “optional.” While these are technically optional, meaning that the product can be
technically implemented with or without them, TeleCheck may require the merchant to
code to one or more of these optional items based on the agreed upon contractual terms.
The merchant may need to account for and enable additional data element fields and
product features in their system(s) and in communications to TeleCheck’s Authorization