The unique, 12-digit number that identifies the merchant to the client or agent bank.

A six-digit number that identifies a client bank. A BIN is assigned by TSYS Acquiring Solutions and is the highest level of the front-end hierarchy. The front-end hierarchy is used by TSYS Acquiring Solutions to route an authorization or batch to the correct acquirer. BINS contain agents, the second level of the front-end hierarchy.

A six-digit number used by client banks to identify a smaller bank (or ISO) that processes credit card transactions through the client bank. Agents are the second level of the front-end hierarchy. They contain Chains and roll up into BINs. If a merchant does not process transactions using the Agent level of the front-end hierarchy, this value may be 000000.

A six-digit number identifying a chain of locations or stores of a merchant. The client or agent bank assigns a chain. Chains are the third level of the front-end hierarchy. They contain merchants and roll up into agents. If the merchant does not process transactions using the chain level of the front-end hierarchy, this value may be 000000.

The merchant name associated with the terminal.

A unique identification number applied to terminals.

The name of the terminal manufacturer.

The name, number, or code identifying the terminal model.

The type of terminal software the merchant will use to submit charges.

Indicates the terminal's alternative build type, if applicable. Valid values include:

• AMEX PIP
• DialPay
• Stage Only

The date the terminal profile was completed.

A code that indicates the services that TSYS Acquiring Solutions provides for a merchant. The service level can impact client billing. Before building files, you should verify which service level you should use with your supervisor or a TSYS Acquiring Solutions Relationship Management representative. Depending on the services you have signed up for, available codes might include:

• DCO - FULL DLL FILE INSTALL, FULL HELP DESK SERVICES, BANK OWNED (no longer used for new builds)
• PIP - PIP/AMEX INSTALLED, AMEX SERVICES, AMEX OWNED EQUIP (no longer used for new builds)
• RAO - OLA FULL DLL INSTALL, PARTIAL SERVICE, BANK OWNED EQUIP
• RBO - OLA STAGE ONLY BUILD, PARTIAL SERVICE, BANK OWNED EQUIP (no longer used for new builds)
• RHO - OLA STAGE ONLY BUILD, AFTER HOURS SUPPORT, BANK OWNED EQUIP
• RMD - OLA FULL FILE LOAD, MEMBER HELP DESK 2, BANK OWNED EQUIP
• RNO - OLA STAGE ONLY BUILD, NO HELP DESK SUPPORT, BANK OWNED EQUIP
• TAO - HOST CAPTURE STAGE ONLY, PARTIAL SERVICE, BANK OWNED EQUIP
• VAO - OLA FULL DLL INSTALL, PARTIAL SERVICE, BANK OWNED EQUIPMENT
• VNO - OLA STAGE ONLY BUILD, NO HELP DESK SUPPORT, BANK OWNED EQUIPMENT

A code that indicates the type of file being built. Possible values:

• SA - STANDALONE
• IV - IVR DATA CAPTURE MERCH
• IT - IVR AUTH ONLY MERCH

For DialPay file builds:

• A merchant only needs one terminal configured as IT or IV; any other terminals the merchant has can be configured as SA.
• A merchant cannot have a mix of IT and IV configured terminals.
• Any terminal type can be configured with the IT option.
• The IV Attachment Code should not be applied to any Class A, Class B+. or Class B terminal that uses authentication; it can cause issues with the dial transaction process. The merchant would need to configure a separate IV DialPay terminal.