Authorization checking data fields

Risk Management authorization checking either uses or produces the following data:
Amount
The amount is specified as either a single value or as a range of values. When a single value is entered, the amount of the transaction must match this amount exactly. When a range is specified, the amount of the transaction must be greater than or equal to the lowest amount of the range and less than or equal to the highest amount of the range.

Both values of the range do not have to be specified. If only the lowest value is provided, the amount of the transaction must be greater than or equal to the lowest value. If only the highest value is specified, the amount of the transaction must be less than or equal to the highest value.

Serial number
The serial number is specified as a range of values. To match the record, the serial number of the transaction must be greater than or equal to the lowest value of the range and less than or equal to the highest value of the range.

Both values of the range do not have to be specified. If only the lowest value is provided, the serial number of the transaction must be greater than or equal to the lowest value. If only the highest value is specified, the serial number of the transaction must be less than or equal to the highest value.

Effective date
The effective date has both a begin and end date field. These fields are optional and are not dependent upon each other. Specifying a begin date without an end date indicates that a record becomes effective on the begin date and does not expire. Specifying an end date without a begin date indicates that a record is effective immediately and expires on the end date.
Active
Records can be marked active. If a record is not active, it does not match any incoming transactions. The active state for a record is not automatically enabled when the effective begin date passes and must be set manually.
Error reason
When a transaction fails an authorization filter or positive pay check, text describing a possible reason for not finding a match is stored in the database. For example, if all of the fields of the authorization filter matched the incoming transaction, but the filter was not yet active, the reason text might be Matching filter found but it is not active.

For authorization filter errors, the reason text is stored in the AUTH_FILTER_ERROR_REASON column of the RISK_PAYMENT_REJECT table. For positive pay errors, the POS_PAY_ERROR_REASON column of the table is used.