It would be nice to incorporate a reverse functionality to existing HTTP JSON Service wherein an upstream service could be a REST interface and a ISO8583 request could be mapped to REST field by name such as
ISO Request:
Message Type Indicator [0].......................1210
Bitmap [1].......................................F23005418AE080000000000004000000
Primary Account Number [2].......................1140463000
Processing Code [3]..............................400201
Amount, Transaction [4]..........................50100
Transmission Date and Time [7]...................20170627104904
Hi Shoaib!
I have some doubts if there will be any reason using SocketQueue in this scenario. Not sure if there is any kind of system that supports HTTP JSON ant doesn't support ISO8583.
Hi,
It would be nice to incorporate a reverse functionality to existing HTTP JSON Service wherein an upstream service could be a REST interface and a ISO8583 request could be mapped to REST field by name such as
ISO Request: Message Type Indicator [0].......................1210 Bitmap [1].......................................F23005418AE080000000000004000000 Primary Account Number [2].......................1140463000 Processing Code [3]..............................400201 Amount, Transaction [4]..........................50100 Transmission Date and Time [7]...................20170627104904
Upstream Mapping: { "0": "1210", "1": "F23005418AE080000000000004000000", "2": "1140463000", "3": "400201", "4": "50100", "7": "20170627104904" }