Terminal Format

TSYS private-use field for miscellaneous information that involves multiple uses and field formats for different types of transactions and messages. Terminal Num: This four-digit field contains a number assigned by the signing member, processor, or merchant to identify a unique terminal within a merchant location. Because the terminal number submitted in the authorization request is echoed back to the terminal in the authorization response, this field can additionally be used in controller-based environments to assist in the matching and routing of authorization request and response messages at the point of concentration.

Usages are detailed in the following table:

Usage	Definition
Unformatted text in authorization/reversal messages.	This field is used for comments. Position 1 = Field Identifier This is a one-position code, * (asterisk). This code indicates this field contains unformatted, user-determined text for the destination endpoint or issuer. Position 2-255 = Text In authorization or reversal requests, the input consists of endpoint comments for the Issuer. In authorization or reversal request responses, the input consists of Issuer comments for the endpoint, such as a referral telephone number.
Error Reason Text in Check Acceptance Responses	This is a check acceptance field usage. When a check acceptance vendor detects an error in an authorization request, it has the option of explaining the error condition in this field in a 0110 response. The exact text in this field is displayed at the point of sale or point of service terminal. There are two subfields after the length subfield. Position 1 = Field Identifier: A 1-position code, * (asterisk) This code means the field contains unformatted, user-determined text for the acquirer. Position 2-255 = Text This text displays at the POS terminal. A center host system supporting terminals that process check acceptance requests should also be programmed to pass this text to the terminal.
Unformatted Text in Network or Administrative Messages	This field can be used in 0800 and 0810 network management messages. There is no field identifier. Position 1-x = Text information the host needs to send to the Endpoint.
Dial Terminal Information	An endpoint that supports dial terminals uses this field for additional information about the terminal that originated an authorization request. There are two subfields after the length subfield. Position 1 = Field Identifier A one-position code, @ (at-sign). It means this field contains dial terminal information for the Issuer. Position 2 or 2-5 = Terminal Information For a Type A dial terminal, position 2 contains the one-character Message Format Code. For a Type B terminal, positions 2 - 5 contain the 2-character numeric Terminal Type Code and the first 2 characters of the Terminal Type.
Check Acceptance Information	This field is used for Check Acceptance information. In a Check Acceptance request, usage six shows the source of the request. When the source is a TSYS ISO 8583 Endpoint, it shows the format of the request message from the POS terminal. There are two subfields after the length subfield. Position 1 = Field Identifier A 1-position code, @ (at-sign). This code means the field contains information for the check acceptance vendor. Position 2 = Message Source Format When an Endpoint generates this field, it contains the 1-character Message Format Code for the Type A POS terminal that originated the authorization request. Position 3 = Additional Request Information Optional free-form text field forwarded at the request of the check acceptance vendor.
Billing/Reporting/Other Data for TSYS Use	This field should not be used unless instructed by the TSYS Implementation Manager.
MasterCard Corporate Fleet Card Data	Endpoints use this field in 0100 and 0200 authorization requests for MasterCard Corporate Fleet Card data. The field has two subfields after the length subfield. Position 1 = Field Identifier This identifier is a 1-position code, $(dollar sign). It means this field contains MasterCard Corporate Fleet Card data in positions 2 through 36. Position 2-36 = Data A maximum of two subfields may occur, each preceded by a dollar sign ($). For example, positions 1 through 18 = subfield 1 and positions 19 through 36 = subfield 2. The first subfield may be empty, in which case a second dollar sign ($) immediately follows the first ($$). Each subfield has a maximum of 17-characters numeric.
Visa Commercial Card Type Request	This is an indicator requesting which type of Visa commercial purchasing card is used at the point of sale or service. In a response, this field contains a value indicating whether the card is Business, Corporate, or Purchasing. The field has two subfields after the length subfield. Position 1-3 = Field Identifier This value is a 3-position code,!01. It signifies a request for the type of commercial card being used at the point of service. It is present in approved responses. Position 4 = Commercial Card Type Request/Response Acquirers enter the value 0 in authorization requests. In approval responses, the zero is replaced with “B” for Business card, “R” for Corporate card, or “S” for Purchasing card. Visa Purchasing cards are identified by BIN ranges.
Visa Purchasing Card - Fleet Service	A supplemental data field usage in 0100 authorization requests by the Endpoints participating in the Purchasing Card-Visa Fleet Service. The data is prompted from the cardholder at keypad-equipped, point of service or point of sale terminals when the Service Enhancement Indicator in the card's magnetic stripe is 1 (Fleet) or 2 (Fleet/fuel-only restriction). The field has two subfields after the length subfield. Position 1-2 = Field Identifier This identifier is a 2-position code, $$(dollar signs). It means this field contains driver or vehicle identification information for the Issuer. Position 3-19 = Visa Fleet Service-Enhanced Authorization Data This value is up to 17-characters numeric containing driver or vehicle identification. NOTE: Because of current POS keypad limitations, Issuers should use numerics only for driver or vehicle identification schemes. For example, 8$$693421 would be the field's representation of driver ID 693421.
Integrated EBT Food and Consumer Service (FCS) ID	This usage is U.S. only. In an Integrated Debit Electronic Benefits Transfer (EBT) Food Stamp transaction, this field contains the Food and Consumer Service (FCS) ID. The FCS ID identifies the merchant as being certified and approved to accept Food Stamps. Two subfields following the length subfield are defined as follows: Position 1-2 = Field Identifier This 2-character code “EB”, identifies the type of information in this field. This code indicates that this field contains the Food and Consumer Service (FCS) ID. Position 3 – x = FCS ID This subfield is unformatted text that contains the Food and Consumer Service (FCS) ID.
Integrated EBT Voucher Serial Number and Food and Consumer Service (FCS) ID	This usage is in U.S. only. In an Integrated Debit Electronic Benefits Transfer (EBT) Voucher transaction, this field contains the voucher serial number and Food and Consumer Service (FCS) ID. This field is mandatory in an EBT Voucher transaction. Four subfields following the length subfield are defined as follows: Positions 1-2 = Field Identifier This 2-character code, “VN”, identifies the type of information in this field. This code indicates that this field contains the EBT Voucher Serial Number (as well as an FCS ID subfield, following the Voucher Serial Number). Position 3-17 = Voucher Serial Number This subfield contains the 1 - 15 digit serial number (with blank space fill to position 17)· Position 18-19 = This 2 character code, “EB”, indicates that the subfield that follows contains the FCS ID· Position 20-x = This subfield is unformatted text that contains the FCS ID.