MICR Validation

MICR validation provides the ability to validate a MICR field for the data in the field and its relationship with other MICR fields (inclusion and exclusion rules). The functionality is encoded as a Business Rules node that is called as part of the Business Rules workflow. The node is called from multiple nodes in the Business Rules workflow to validate the MICR fields present in a transaction.

At the start of a batch, Gateway looks up the Business Rules workflow from the partner tables as part of the collection type defined by context validation. Gateway passes the workflow name to Business Rules at initialization. Business Rules returns MICR validation results to the Gateway for storage in the item validation results table with the associated errors and warnings.

When MICR validation fails, the Business Rules node assigns an error code based on the configuration for the rule. Each MICR validation rule is assigned its own unique error code. The attributes of the error code are used to determine rejection actions. The rejection actions are:
  • Reject the transaction by flagging it as a validation error
  • No rejection, only a warning is issued

Transactions in the FTM database have a repairable indicator when they are eligible for correction. The error code and indicator are stored in the database with the actual failing data and indications of which MICR fields failed. The information stored includes warning rejection levels. The rejection level controls subsequent processing.

Gateway stores the failing results in the item validation results table while inserting the corresponding transaction in the FTM database. In addition to MICR fields, validation can be performed on several bank of first deposit (BOFD) fields during returns processing.

The MICR validation node supports a user exit. The preProcess routine is called prior to the standard validation function. The buildClientResponse routine is called after standard validation.