Why do we need to do socket programming to implement ISO 8583 messages?

ISO 8583 is transmit over wire and/or wireless using some some communication protocol (i.e. TCP/IP, UDP/IP, X.25, SDLC, SNA, ASYNC, QTP, SSL, etc.).
Spesific to TCP/IP, if we want to process this kind of messages, we usualy open a port (socket) and listen for the incomming request(s).
So you must look into socket programming.
POS terminal and/or ATM usualy finished or closed their transactions in one session. So you don't need to watch the tcp 'stream'.
Only if you want to build WAN routing with (Hypercom) NAC, and do whatever you want to do, maybe you need go to tcp 'stream'.
By all mean, you need to read 'RAW' tcp data to completed (extract them and giving the valid response for it) the ISO 8583 task.

If you want to read at application layer, you must build the application/modules first. Although ISO 8583 is a standard, but the implementation are many, depends on needs and purposes.

I or others can help to build application (or modules so you can read at application layer) for your needs. Especially.., maybe, if you mentions about the price.

Rgds.

The question looks to be abandoned by the user who asked it. If no action is taken within 2 days, a Quomon Moderator will consider closing the question and distributing the points.

The Quomon Team