Terminal Merchant Report

This report lists terminals that have been boarded in Express during the date range that you specify. The data contained in this report reflects data from the previous day.

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

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 serial number assigned to this terminal.

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

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.

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

AMEX PIP
DialPay
Stage Only