FirstData Nashville Retail File Batch UML

FirstData Nashville specific File Batch representation for the settlement process. It represents a group of FirstData Nashville Capture Retail Transaction objects that are settled together as a group within a single file.

During Generation Process, FirstData Nashville Retail File Batch is converted into a settlement file, which is then registered into File Store for further processing.

Four (4) digit ACCEPT/HELD/REJECT Reason Code, that indicates whether FDMS accepted, held, or rejected the transaction or submission. This field is found on the Detail Acknowledgment and General Acknowledgment records.

Zeroes (signed) – the Debit/EBT acknowledgement records are a ‗receipt‘ that the records were received, not an indication if they were successfully processed through the debit system.

The Charge Descriptions are agreed upon by the client and American Express, at the time the Electronic Submission Addendum is completed. American Express will notify FDMS of the Charge Description that must be used by the client.

Assigned by FDMS.

Twelve digit account number assigned to merchant outlet by FDMS. This field is found on the Merchant record. Right justified leading zeros. Zero fill if using Field #15.

City of Merchant — This field is left justified, with trailing spaces.

Merchant DBA Name. For Direct Marketing merchants processing installment payments, the appropriate installment descriptor (e.g., 1 of 5, 2 of 5) must be included in this field. Merchant no longer needs to provide the Q code. The following 14 special characters are allowed as part of the merchant name field ! @ # $ & ( ) - ' . / + , "

Numeric State Code of Merchant (i.e., ‗47‘ for Tennessee)

Assigned by FDMS.

This FDMS-assigned code is found on the Merchant (M) record. When more than one Merchant Record is present, the Security Code must remain same throughout the entire file.

This field, which is found on the Merchant (M) record, contains the Julian date (YYDDD) that the batch file was created. The Submission Create Date is also represented in Gregorian (MMDDYY) format in the 40 & 80 Byte formats.

This field, which is found on the Merchant (M) record, contains the Julian date (YYDDD) that the batch file was created. The Submission Create Date is also represented in Gregorian (MMDDYY) format in the 40 & 80 Byte formats.

Comprised of the Submission Create Date (Julian format), Submission Sequence Number, and Security Code.

Twelve digit number which contains the total transaction amount of all Detail Records with Transaction Code '6‘. This field is found on the Total 1 (T) record.

Twelve digit number which contains the total transaction amount of all Detail Records with Transaction Code ‗5‘. This field is found on the Total 1 record.