These data fields are slightly different based on the network, so we would like to use a JSON configuration file for parsing the data elements rather than hard coding the logic for every use case.
JSON configuration file
We need to use JSON configuration file to specify any card messaging,
Although don't take all of the specification documents of ISO8583, we can get a hint of JSON configuration from the link http://iso8583.free.fr
JSON configuration file should contain protocol encoding definition and data elements definition.
mfdeveloper508
commented
3 years ago
These data fields are slightly different based on the network, so we would like to use a JSON configuration file for parsing the data elements rather than hard coding the logic for every use case.
The goal is to allow for ascii, XML, or JSON requests into the library and transpose the message data. Example: https://github.com/kamshory/ISO8583-JSON-XML
SPEC Learn more about ISO8583 https://en.wikipedia.org/wiki/ISO_8583 https://www.codeproject.com/Articles/100084/Introduction-to-ISO https://github.com/moov-io/iso8583/blob/base-logic-pkg/docs/iso8583.pdf https://github.com/moov-io/iso8583/blob/base-logic-pkg/docs/MDSSEC04.PDF
JSON configuration file We need to use JSON configuration file to specify any card messaging, Although don't take all of the specification documents of ISO8583, we can get a hint of JSON configuration from the link http://iso8583.free.fr JSON configuration file should contain protocol encoding definition and data elements definition.
message checker we can check any message of ISO 8583 with ISO8583Editor and ISO8583_1987.pro (https://github.com/moov-io/iso8583/blob/base-logic-pkg/docs/ISO8583_1987.pro)