Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Feature Request: ISO8583 to Upstream HTTP JSON Mapping #15

Open
shoaibjdev opened this issue Jun 28, 2017 · 1 comment
Open

New Feature Request: ISO8583 to Upstream HTTP JSON Mapping #15

shoaibjdev opened this issue Jun 28, 2017 · 1 comment

Comments

@shoaibjdev
Copy link

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"
}

@juks
Copy link
Owner

juks commented Nov 7, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants