The MICR Parser tool was created to accept a single string data field and parse it into segments. Up to six segments can be created.
This tool only works with American Code lines from checks.
The “Mappings” section is for letting the parser know what character will be used to represent each of the MICR special characters in the incoming data. They default to the four randomly chosen by OPEX.
|
Mappings |
Description |
|---|---|
|
Amount Char |
Specify the character used to represent the amount character. |
|
Dash Char |
Specify the character used to represent the dash character. |
|
On-Us Char |
Specify the character used to represent the on-us character. |
|
Transit Char |
Specify the character used to represent the transit character. |
|
Input |
Description |
|---|---|
|
MICR |
The data field used for the incoming code line. |
|
Data Fields |
Description |
|---|---|
|
Account Number |
Links the account number to a data field. Select the data field that should receive the parsed portions of the code line. |
|
Auxiliary On-Us |
Links the auxiliary on-us to a data field. Select the data field that should receive the parsed portions of the code line. |
|
EPC |
Links the EPC to a data field. Select the data field that should receive the parsed portions of the code line. |
|
On-Us |
Links the on-us to a data field. Select the data field that should receive the parsed portions of the code line. |
|
Transit Number |
Links the transit number to a data field. Select the data field that should receive the parsed portions of the code line. |
|
Check Number |
Links the check number to a data field. Select the data field that should receive the parsed portions of the code line. |