Developer's Guide

Gateway Developer Guide and Reference 31 July 2012 131
TeleCheck Electronic Check Processing
TeleCheck NFTF Processing Overview
B
System. Various optional data elements throughout each of the message packets could be
affected by this requirement.
 First Data Gateway Partners, External Gateway vendors, First Data Platforms, and the
Global Gateway Router (GGR) that route merchant transactions to TeleCheck via this
specification must code for all fields, features, and functionality available in this
specification. Nothing is optional for these partners. Additionally, these partners are
required to maintain their NFTF specification as new revisions and addendums become
available.
NFTF Processing Considerations
TeleCheck and the Merchant must determine any of the following additional optional features
during contract negotiations.
 MIA Duplicate Checking – TeleCheck has the ability to detect duplicate adjustment
transactions in back end processes. Adjustments can be submitted up to 90 days after the
original Sale transaction. While multiple adjustment transactions are allowed for a given
sale transaction, each adjustment transaction must have a unique merchant trace ID.
Duplicates are detected when an adjustment transaction is submitted that has the same
merchant trace ID as a previously submitted adjustment transaction. If a duplicate
adjustment is detected, and the original adjustment was accepted by TeleCheck, the
duplicate will also be accepted. The duplicate transaction will then be filtered out by
TeleCheck’s back end settlement processes.
NFTF Guidelines
The following guidelines should be followed when adhering to the above NFTF Requirements
to electronically process a check payment:
 Fields marked as Required are required to process an electronic transaction.
 Not all fields are required by every merchant.
 Unused fields should be completely omitted from the message.
 Each field is variable in length (justification and fillers are not used).
 The order of tagged fields from the POS and from the TeleCheck host are not significant.
 Fields must not have any hard-coded data values.
 The transaction number increments on every attempt.
Message formats outline fields (tags) that are required, not required, or conditional to the Sale,
Status, and Adjustment Inquiry packets.
Message Types:
 Merchant Authorization Message and the TeleCheck Authorization Response Message
 Merchant Delayed Capture Message and the TeleCheck Delayed Capture Response
Message