we did something similar to that back in 1999 in one of the banks, where we would send the statement data in one of the generic private use fields, where it would allow the format ANS 999
but that means you are either to restrict the data to less than 999 characters, or to split the data on multiple messages. and have a multi legged transaction.
you would have the following flow
- Customer request for statement on ATM
- ATM sends NDC/D912 message to ATM Switch
- ATM Switch look up account number after authenticating the card and forward the request to Core Banking Application
- Core banking application would generate the statement and format it according to predesigned template and send the statement data into a generic field (say 72)
- ATM Switch collects the data and formats it to NDC or D912 format where the statement data is tagged to statement printer (in NDC it is a field called q and the value should be ‘8’ - Print on statement printer only)
and on the field r place the preformatted data
however, it is not a good practice to do so, since we have faster means to generate a statement and send to email or internet banking. but this is the bank s preference anyways.