TSYS Retail File Batch UML

TSYS specific File Batch representation for the settlement process. It represents a group of Tsys Capture Retail Transaction objects that are settled together as a group within a single file.
During Generation Process, TSYS Retail File Batch is converted into a settlement file, which is then registered into File Store for further processing.

This field contains Bank Identification Number (BIN) issued by the merchant’s member bank or processor. The Acquirer Bank Identification Number identifies the member bank or processor that signed the merchant using the POS application.

This field is issued by the merchant’s member bank or processor for purposes of identifying a specific agent entity of the member bank or processor.

This field is issued by the merchant’s member bank or processor for purposes of identifying a specific chain of an agent organization.

The TSYS Acquiring Solutions authorization system supports a number of communication interface applications.

These applications include:
• Single Transaction: a half-duplex, single-threaded interface option where only one authorization is performed per host connection.
• Multi-Transaction: a half-duplex, single-threaded interface option where multiple authorizations can be performed per host connection.
• Interleaved: A full-duplex multi-threaded interface option where multiple transactions are performed per host connection.

Refer to the EIS 1051 (Authorization Link Level Protocol) specification for additional information on these communication applications.

The Hashing total is the gross dollar amount of the batch and is generated by adding together the absolute value of all Detail record amounts.
Void and purchase return settlement amounts are treated as positive and added to the total, not subtracted from it.

The net deposit total is generated by adding the settlement amounts of all Detail transaction records and subtracting credit or refund amounts from it.
Void transaction amounts are not factored into this amount.
This field is represented as an “absolute value.”

This field contains a batch sequence number generated by the POS device.
The batch number must be a number within the range of 001-999. If the POS device is automatically incrementing the batch number, it should automatically advance the number from 999 to 001 (000 is invalid). Batch Numbers must not be reused or repeated within five
consecutive days.

This field contains a batch record count calculated by the point of sale device.
This field is supplied in the Batch Trailer record and must contain the total number of records in the batch – including Header, Parameter, Detail(s), and Trailer records.
Blocking has no effect upon the record count.
When this field is returned by the host in a batch response message, it will reflect the total number of records having been received by the host. In the case of a GB (Good Batch) response, the value returned should match the value supplied. However, in the case of an RB (Rejected Batch) response, the batch record count will reflect the total number of records received until the point of failure. Hence, the returned record count will reveal the sequential number of the record responsible for causing a rejected batch condition.

This field contains the response code returned by the host indicating the status

This field will contain the text “_ACCEPTED” when a settlement batch has been successfully received by the host; however, the POS device should examine only the Batch Response code to determine the status of particular batch status.

This field contains the transmission date of the settlement batch. The
transmission date must be provided in MMDD format.

This fixed 16-character numeric field contains the total sum of cash back amount.

This field is used to identify the merchant Postal/ZIP Code.
This field entry must be identical to the value provided in the original authorization request.

The date of duplicate batch transmission.

This field contains the error data contained within the field which generated the rejected batch response message.
This information can be useful in identifying and correcting the rejected batch condition.

This field contains the sequential field number within the data record which generated the rejected batch response message

This field contains the sequential number of the data record which caused the rejected batch state

This field defines the data record which generated the rejected batch response message

This field defines the nature of a rejected batch.

Authorization request and response message data elements are separated into functional data groupings.
TSYS Acquiring Solutions currently defines and supports three separate data groupings for both authorization request and response messages.

Group II fields are directly associated with performing Direct Debit transactions. To perform a Debit Card transaction, Group II data elements must be combined and concatenated with Base Group I and III. When Groups I, II, and III are supplied in the authorization request, the host responds with a corresponding set of Group I, II, and III response fields.

This field used to identify the industry type of the merchant submitting the settlement batch

This field used to identify a merchant’s industry classification

This field contains the merchant city as provided to the bank or processor. The Merchant Location provided will appear on the cardholder’s statement. If the merchant is categorized as a Direct Marketer, this field should contain a Cardholder Service Phone Number (a merchant telephone number that the cardholder may call for service)

This field contains a value providing additional information on the location of the merchant

This field contains the merchant name as provided to the bank or processor. The Merchant Name provided will appear on the cardholder’s statement.

This field used to identify the merchant within the member systems.

This field contains the merchant state as provided to the bank or processor.
The Merchant State/Province provided will appear on the cardholder’s statement.

This field is used to define the characteristics of a settlement record being submitted for processing on the TSYS Acquiring Solutions system.

This field is used to identify a specific merchant store location within the member systems.

This field contains the number to accommodate a POS device tracking number

This field contains a number used to identify a specific store terminal within the member systems.

This field used to calculate the local time within the TSYS Acquiring Solutions authorization system.
The differential is assigned by the merchant’s bank or processor and provides the standard local time zone differential from Greenwich Mean Time (GMT). The first digit specifies the direction of the differential and offset increment as well as whether daylight savings is observed. The last two-character numeric specifies the magnitude of the differential.