|
|
|
|
|
The data columns in the report depend upon your selection from the Search Criteria panel's Data drop-down list:
A four-digit number assigned by TSYS Acquiring Solutions to identify the banks that a client has set up for processing.
The billing element table number.
The Billing Element Table category. These categories include:
BET Indicator
A user-defined description of a billing element table (BET) that can be used to select a BET from a BET assignment menu.
Selection 1
Selection 2
Selection 3
Selection 4
A four-digit number assigned by TSYS Acquiring Solutions to identify the banks that a client has set up for processing.
A description of the pricing option. The option name must be unique, but all other field values may be shared between pricing options.
Discount Percentage Range (From)
Discount Percentage Range (To)
Discount Per Item Range (From)
A range of values within which the discount per item amounts for a merchant-level discount rate table (DRT) must fall when the pricing option is assigned to the merchant.
Discount Per Item Range (To)
The overall minimum discount rate. If the operator does not override the minimum discount rate at the merchant level, the rate shown in this field is applied.
Indicates if a discount is calculated according to gross or net sales.
Indicates that the system uses the number option to accumulate qualified interchange volume. Acceptable values for this field are:
Indicates that the system uses the dollar option to accumulate qualified interchange volume. Acceptable values for this field are:
A four-digit number assigned by TSYS Acquiring Solutions to identify the banks that a client has set up for processing.
The name of the merchant's bank.
Provides the ability to find specific merchant information relating to a charge record.
The amount that a merchant is charged. A decimal point is implied to the left of the last two digits in this field.
This indicates whether (y) or not (n) the Charge Seasonally field was selected for the charge record.
The default for this check box is not selected. If it is selected, the user must determine the frequency of the charges, using the Frequency field.
This indicates whether (y) or not (n) the Disable field was selected for the charge record.
The default for this field is not selected. It indicates whether or not the charge record description is included in the Selection menu of bank default charge records that can be added to merchants from the Merchant Charge Records page. If the check box is selected, the record remains in the current charge records table at the bank level, but will be considered inactive and will not appear on the Selection menu at the merchant level.
Information that identifies the form. The description in this field corresponds to the printed description of the form that is in the GCF catalog. As part of the bank default charge records process, the Description field enables the user to enter a 30-character description of the charge record that is displayed in the Bank Defaults Selection menu on the Merchant Charge Record Details page. The description must be unique (ignoring case) across all default charge records defined for the bank.
A message that appears on a merchant statement.
With tokenization, the transaction data is replaced by a token, which is a randomly generated code that cannot be mathematically reversed. When a merchant submits a debit or credit card payment, a unique token is generated and returned to the merchant for future use.
Because the token can always be referenced back to the original card number, it can be used to process recurring payments on that card. Tokens can also track customer transactions for marketing purposes.
A Token Zone Name field is available on the Merchant Parameters page, and is initially disabled (NONE). A token zone name can be selected only at the merchant level if the BIN is participating in tokenization. Once the first terminal with tokenization is set up for the merchant, the Token Zone Name field is enabled populated with the value chosen at the terminal level.
Only those custom token zone names that are flagged for display at BIN level are displayed at the merchant level. Should the user attempt to change a Token Zone Name that terminals are currently using, a warning message displays, indicating that changing the Token Zone Name at the merchant level will prevent the use of existing tokens at the terminals. A user cannot de-select tokenization participation at the merchant level if there are still terminals participating in tokenization.
Note: After the first Token Zone Name is selected with the first terminal setup, the subsequent token zone names are selected at the merchant level. the token zone name selected at the merchant level is applied to all terminals.
Jan - Billing
Feb - Billing
Mar - Billing
Apr - Billing
May - Billing
Jun - Billing
Jul - Billing
Aug - Billing
Sep - Billing
Oct - Billing
Nov - Billing
Dec - Billing
The month and year (mm/yyyy format) in which charges for this record begin.
A value of 1 through 12 indicating the number of months to delay between seasonal charges.
The date (mm/dd/yyyy format) on which charges for this record will expire. A value of 99/99/9999 indicates that the charge record has no expiration date. As part of the bank default charge records process, The purpose of this field is to allow users to charge a fee monthly for a specified number of months, up to 1 year after the merchant is boarded. When used with Frequency = One-Time, this allows the user to charge a fee once, but to set the expiration date out for up to 13 months, so that they can choose to re-assess the fee during that time period by selecting an additional month for this charge record at the merchant level without having to also change the expiration date.